Privacy policy

Game progress, accounts and cloud copies

The game stores campaign progress, settings, unlocks, and ordinary rewards locally on your device. When the device is online, the game automatically creates an anonymous account identified by a random internal identifier. The game retains an authentication credential on the device and the server processes authentication sessions, limited profile and stage records, request-retry records, and records needed for optional rewarded advertisements.

Creating the guest account does not require your name, email address, password or social sign-in. Uninstalling the game, clearing its storage or losing the device may permanently remove local progress and the only credential for an unlinked guest account. Ordinary campaign play and base victory rewards remain available offline.

In builds offering optional account linking and recovery, the server processes the selected sign-in provider's account identifier and verification proof to connect that identity to your game account and verify a recovery request. We do not ask for the provider account's password. If cloud backup and restore are enabled, the server stores the progress copies and limited version/history information needed for the choices you make. These features do not by themselves promise continuous synchronization across devices; the game explains the available save, restore and retained-copy controls. A local progress backup cannot establish or overwrite server-authoritative paid benefits.

Optional rewarded advertisements

The game may offer optional rewarded-advertisement placements. Depending on the feature enabled in your build, a completed, server-verified advertisement may grant an Addy Ticket for a later optional stage bonus or provide the specified stage bonus directly. The game explains the offered reward before you watch. A stage bonus uses the saved ordinary stage-clear reward; milestones, Journey grants, unlocks and paid benefits are not duplicated. Advertisements are never required to complete the ordinary campaign, and the approved baseline does not show banner or interstitial advertisements.

Advertisements are provided through Google AdMob and the Google Mobile Ads SDK. Google and its partners may process information such as IP address, device or advertising identifiers, advertisement interactions, consent choices, and diagnostic information to deliver and measure advertisements, prevent fraud and abuse, and comply with applicable law. The information processed and available choices may vary by device, region, age treatment, consent status, and Google's services.

Before the initial game route, the game requires the player's date of birth through a neutral day, month, and year entry. It stores that date only in local settings on the device and uses it to recalculate an under-13, 13-to-17, or 18-and-older advertising group when the game starts. Neither the date nor the derived group is sent to our game server or recorded in our observability system. Settings shows the current derived group and lets you correct the saved date. If the derived group is under 13, the game does not request rewarded advertisements. Ages 13 to 17 use Google's teen advertising treatment, an under-age-of-consent signal, and a restricted maximum advertisement content rating.

Where required, Google's User Messaging Platform separately asks for privacy choices before the game requests an advertisement. When Google requires an ongoing privacy-options entry point, the game makes it available from Settings. Declining consent, closing an advertisement, losing connectivity, or an advertisement failing to load does not block ordinary gameplay or remove progress already saved.

For server-side verification, Google sends our server a signed callback containing the configured ad unit, reward metadata, a transaction identifier, a timestamp, and opaque account-bound opportunity data. We use this callback to prevent duplicate or forged bonus grants.

Google provides more information in its Privacy Policy, its explanation of how it uses information from apps that use its services, and My Ad Center.

Purchases, refunds and security

In builds that enable purchases, the store processes payment details. Our game does not collect payment-card numbers or security codes. Our server processes purchase identifiers and verification proof, the associated game account and product, purchase/delivery/reversal states and dates, and the benefits or adjustments required to deliver an order once, recover interrupted delivery and handle refunds, revocations or chargebacks. Store reports may be retained separately where necessary for accounting and payment reconciliation.

Where supplied by the store and supported by the enabled service, refund evidence can include the order reference, refund reason, initiator and refunded quantity, alongside relevant purchase/adjustment history. We use relevant records for verification, benefit reconciliation, security, support and review. A refund event alone is not a finding of fraud. We do not collect a card number to link players by their payment card.

If a normal in-game Terms agreement is introduced, it may record the accepted version, game account and acceptance time. It is separate from advertising consent and does not replace required privacy choices. The Terms of Service explain the applicable purchase and refund rules. Publishing these pages does not mean that a player has accepted an in-game agreement.

Other information and platform services

The approved baseline does not include a custom email/password service, multiplayer, production gameplay analytics, an external crash-reporting service or direct messaging. Optional sign-in, cloud copies and purchases are included only when enabled for the actual build. Development diagnostics and their local event history are not uploaded by production builds.

Google Play and Google AdMob may still provide aggregated or service-generated information such as installations, device compatibility, crashes, application-not-responding events, advertisement impressions, and rewarded-ad completion under their own terms and policies.

Support communications

If you email contact@fateinfinite.com, we receive the information you choose to include, such as your email address, device details, screenshots, and problem description. We use it to respond, diagnose the reported issue, protect users and the service, and meet legal obligations. Please do not send passwords, payment details, government identifiers, authentication tokens, or other unnecessary sensitive information.

Support correspondence is retained only as long as reasonably needed for those purposes and is not sold. The email provider may process the correspondence.

Age treatment

The planned public audience is ages 13 and older. The required neutral local date entry described above keeps optional advertisements off for the derived under-13 group and applies the configured teen treatment for ages 13 to 17. Before public release, we will complete and review device testing, the launch countries, store declarations, consent flow, public wording, and exact advertising SDK configuration together. Optional rewarded advertisements remain unavailable where the required treatment is not ready.

Hosting, security, and international processing

During pre-release testing, the online account and advertisement-verification service is hosted on Google Cloud in Singapore. The public pages containing this policy are hosted by Cloudflare. These providers, Google AdMob, Google Play, and the support email provider may process information in countries other than the one where you live, subject to their safeguards and applicable law.

We use safeguards including HTTPS, protected local credential storage, restricted server access, short-lived access tokens, rotating refresh sessions, and bounded deletion retention. No method of storage or transmission is completely secure.

Retention and deletion

We do not delete an account merely because the player has not logged in for 30 days. Refresh sessions use a rolling inactivity expiry of up to 365 days. Expiry ends that credential's ability to authenticate; it does not itself delete the account or its profile. Short-lived advertisement opportunities can expire before a delayed callback arrives, while durable receipts preserve an already verified outcome.

A verified deletion request revokes sessions and removes associated gameplay, sign-in links, cloud copies and operational data as applicable. A deleted-account marker and protected deletion-response replay record may remain for 30 days so the same request can be retried safely after its session has been revoked.

Some limited transaction or security records may be retained separately where needed to prevent duplicate claims, reconcile refunds, meet financial obligations or review abuse. Deletion removes live account links and unnecessary purchase proof and gameplay details where applicable. A reduced transaction record may retain product, status, dates, transaction fingerprints and aggregate benefit-adjustment quantities; these records are not necessarily fully anonymous. We retain them only for the relevant transaction/security obligations and remove them under the applicable retention process. Restricted service backups expire through their configured retention cycle, so deletion is not necessarily immediate in backup copies.

If an installation's guest credential is lost, support will explain what can be verified without treating an email address alone as ownership of an unlinked account. Linked recovery or a retained cloud copy can help only where those features were enabled and the request is verified.

See the account-deletion instructions for the available routes and the limits of an unlinked anonymous account.

This policy website

These static public pages contain no publisher-operated analytics, advertisements, consent tags, forms, or JavaScript, and we do not set cookies through them. Cloudflare may process ordinary web-request and security information, such as IP address, request headers, requested page, and time, to deliver and protect the site under its own policies.

Your choices

• Play the ordinary campaign and receive base rewards without choosing a rewarded advertisement.
• Review and correct the device-local date through Settings; under-13 players continue ordinary gameplay without rewarded advertisements.
• Change available advertising privacy choices through the in-game Settings screen where Google requires that option.
• Use any enabled account-linking and cloud-copy controls to manage the provider links and progress copies that the game actually offers.
• Delete the online game account through the in-game account controls while its credential is available, or use the external account-deletion route.
• Reset local game data through the device's application settings or uninstall the game. This does not itself send an online account-deletion request.
• Contact us about this policy or a support communication.

Changes to this policy

We may update this policy when the game, its providers, or legal requirements change. The current version and effective date will remain available at this address.