Start as a guest and optionally connect your account. Learn about local and cloud information, providers, privacy choices, and deletion below.
01. Who we are
First Zero Studio develops Fury Road Survivor. This policy explains how we handle information when you play the game, visit this website, or contact us. First Zero Studio is responsible for the information it processes as described here.
Android package: com.firstzero.furyroadsurvivor
Features vary by version. Older or offline builds may store progress only on your device. Android test builds may include Google sign-in and cloud saves, Google Play license-test purchases, Google AdMob test rewarded ads, and Adjust sandbox measurement. The related processing takes place when the relevant service is enabled and used. Test ads and sandbox measurement can still send information to service providers.
02. Information and purposes
Local progress and settings
We store your journey progress, unlocks, upgrades, preferences, and in-game journey images on your device to run the game and resume play. Journey images are generated by the game, not taken from your camera or photo library. Saving local-only data does not by itself upload it to us.
Google sign-in and cloud saves
You can start as a guest and optionally connect a Google account in builds supporting cloud saves. Google sign-in and Firebase Authentication process account information, including a unique game user ID and Google profile information such as your display name and email address. The game uses your display name to show the connected account and a Firebase user ID to identify your cloud progress.
Cloud saves use Google Cloud Firestore and Cloud Functions to store and retrieve journey snapshots, progression, unlocks, settings contained in the save, save versions, timestamps, and request identifiers. The service keeps the current and previous snapshot to support recovery and resolve conflicting saves. Cloud saves help you resume with the same account after reinstalling or changing devices, provided the progress was successfully synchronized. Unsynchronized guest progress may be lost when local data is cleared.
Security and service diagnostics
Firebase App Check with Google Play Integrity helps check whether requests come from the game on a supported device. Online services process authentication and integrity tokens, request timestamps, rate-limit records, connection information such as IP addresses, and technical error or service logs to authenticate requests, protect cloud data and purchases, prevent abuse, and investigate failures. We do not request your Google password.
Google Play purchases
Google Play handles payment in versions supporting purchases. Our game and Firebase backend process your game user ID, product ID, purchase token and its hash, purchase state, verification time, and entitlement records to verify, grant, acknowledge, consume where applicable, and restore purchases and prevent duplicate grants or fraud. Verification uses the Google Play Developer API. We do not receive your full payment-card number. You may provide an order reference when contacting support.
The present purchase-testing integration uses Google Play license-test orders; production payment processing has not been enabled by this integration. Google Play determines the purchase screen, available payment methods, and whether a particular order is a test order.
Rewarded advertising and privacy choices
In ad-enabled test builds, Google AdMob loads Google demo rewarded ads when you choose an advertising reward. This is a network SDK test, not a promise that no information leaves your device. Google Mobile Ads can process IP addresses, device or account identifiers such as advertising ID and app set ID, app or ad interactions, and diagnostic information for ad delivery, measurement, and fraud prevention. IP addresses may be used to estimate general location.
The game processes the selected reward placement, a per-display request identifier, and ad completion or failure state so that a completed reward is granted once. Google User Messaging Platform (UMP) processes and stores applicable consent and privacy preferences. Where required, it presents a privacy message and provides a way to revisit privacy options. Current ad test builds request Google demo ads; commercial ads, interstitials, and additional ad-network adapters are not enabled in this integration.
Adjust sandbox measurement
Adjust is the measurement provider used by the current enabled Android test integration. Its SDK processes install or referral information, sessions and launches, IP address, device and app details, timestamps, advertising or other device identifiers where available, and an Adjust-generated device identifier. These support testing attribution, event delivery, and fraud prevention. Sandbox is a test environment and can still receive real device information.
Configured events cover tutorial start and completion, first battle completion, journey completion, successfully verified license-test purchases, and earned native rewarded-ad completions. Event fields include limited gameplay summaries, product or placement identifiers, a sandbox marker, and deduplication identifiers. For newly verified license-test purchases with an original Google Play quote, the sandbox event includes that product quote and currency to test revenue delivery; these values are not actual receipts of money. This integration does not pass Google account email addresses, Firebase user IDs, full purchase tokens, payment-card information, or ad-impression revenue to Adjust. AppsFlyer and AppLovin MAX are not integrated in these test builds. Future measurement or mediation changes will be disclosed before they are enabled.
Meta (Facebook) App Events in development testing
Selected Android tester builds can include Meta's Facebook App Events SDK for testing app activation, sessions, limited gameplay-event delivery, and advertising measurement. It is enabled only after the tester setup and required disclosures and privacy conditions have been checked. Meta does not provide an Adjust-style sandbox: development and test events can still be transmitted to Meta's systems.
When enabled, events cover tutorial start and completion, the first ordinary battle completed, journey settlement, verified Google Play license-test purchases, and native rewarded-ad completions. Our event parameters are limited to development markers, gameplay summaries, product or reward-placement identifiers, deduplication identifiers, and the quoted amount and currency of license-test purchases as custom test fields. Test purchases use a custom test event, are not actual receipts of money, and are not sent as standard Purchase revenue for production value optimization. Reward completion is not ad-impression revenue.
The SDK can process technical information such as IP address, device and app characteristics, SDK-generated anonymous identifiers, sessions, launches, and timestamps. The current integration disables advertising-ID collection, automatic purchase logging, codeless event collection, automatic metadata collection, and product-improvement collection. It does not send Google account email addresses, Firebase user IDs, raw purchase tokens, or full payment-card details to Meta, and does not include Facebook Login or Audience Network. Where applicable law requires consent or other privacy choices, those conditions must be satisfied before enabling the related processing. Publishing or reading this policy does not enable the SDK or provide consent.
Support
If you email us, we receive your email address, message, and any information or attachments you provide. We use them to respond, investigate problems, and handle privacy requests. Do not send passwords, full card details, or unrelated sensitive information.
Website hosting and measurement
Cloudflare delivers and protects this website, processing technical connection information such as IP address, requested URL, browser details, and access time. Cloudflare can also supply aggregate visit and page-performance measurement through its Web Analytics service, subject to the deployment's security settings. Our authored pages contain no advertising code, tracking forms, or third-party fonts. Website measurement does not link your visit to your Firebase game account. See Cloudflare's notice for its handling of hosting, security, and measurement information.
03. Services and recipients
We disclose information to the providers necessary for the services described above, to support providers, and when needed to comply with law, protect rights, or investigate abuse.
- Google / Firebase / Google CloudGoogle sign-in, authentication, cloud saves and functions, App Check and Play Integrity, security and service logs.Google Privacy Policy · Firebase privacy information
- Google PlayDistribution, license-test purchases, purchase verification and restoration.Google Privacy Policy
- Google AdMob and UMPDemo rewarded-ad delivery and applicable advertising privacy preferences.Google advertising information · Google Privacy Policy
- AdjustSandbox attribution and the limited test events described above.Adjust Privacy Policy · Adjust device privacy choices
- Meta (Facebook)App activation, sessions and limited development-test events, only in explicitly enabled tester builds as described above.Meta Privacy Policy · Meta other privacy policies
- Cloudflare Email RoutingDelivery and forwarding of messages to our support address.Cloudflare Privacy Policy
- CloudflareWebsite hosting, security, and website performance or visit measurement.Cloudflare Privacy Policy
Providers may act on our behalf or determine some processing purposes independently. Their notices explain their roles and choices. We do not sell our account, cloud-save, or support records. If future advertising introduces processing treated as sale, sharing, or targeted advertising under applicable law, we will disclose the actual practices and provide required choices before enabling it.
04. Your choices and rights
You may play as a guest where supported. Signing in enables account-linked cloud services; signing out stops the game from using that signed-in account but does not delete its existing cloud data. Clearing local storage or uninstalling removes local progress and settings, not cloud saves or Google Play transaction records.
For advertising, use the privacy message when it is presented. In builds supporting UMP, Ad privacy settings appears in the game's settings when UMP requires a privacy-options entry. You can reopen it to change the available advertising choices. Your Android device also offers advertising-ID and ad-privacy controls. Declining personalized advertising does not necessarily prevent all technical processing needed for limited ads or security.
Advertising choices and Adjust measurement are separate services. The current test integration does not offer a separate in-game Adjust switch. You can use Adjust's device privacy choices, or contact us to request assistance with measurement opt-out or erasure. Removing an advertising ID alone does not necessarily stop all SDK processing.
Depending on applicable law, you may request access, correction, deletion, a copy, restriction, or object to processing by emailing furyroadsurvivor@firstzerostudio.com. Where processing relies on consent, you can withdraw it without affecting prior lawful processing. We may ask for proportionate verification and will respond within the period required by applicable law. You may complain to your local data-protection authority.
Request game account or data deletion →
Advertising preferences, Adjust measurement, and Meta App Events are separate services. The current Meta tester integration does not provide a dedicated in-game Meta switch; the SDK remains disabled in ordinary builds and while tester activation conditions are unmet. For assistance limiting future test measurement, requesting information, or addressing provider-held data, contact First Zero Studio using the privacy contact below. Android advertising-ID controls alone do not necessarily stop all SDK processing.
05. Legal grounds
Where applicable law requires a legal basis, we process information as necessary to provide gameplay, the account and cloud services you request, purchases, and support; to meet legal obligations; for legitimate interests in service security, fraud prevention, fault diagnosis, and service testing where your rights do not override those interests; or with consent where required. Device storage or identifier access and personalized advertising are subject to the applicable rules and available privacy choices. We do not treat opening this policy as consent.
06. Retention and account deletion
Email furyroadsurvivor@firstzerostudio.com — request deletion with the subject Account deletion — Fury Road Survivor. State whether you want the game account, cloud progress, or specific information deleted. If possible, contact us from the Google email used to sign in. You can submit a request without reinstalling the game. We may request only the information needed to verify ownership; never send your password or a complete payment-card number.
After verifying the request, we will delete the game's Firebase authentication account and associated cloud-save snapshots and routine account-linked service records, and address applicable provider-held measurement data. We will explain any purchase, entitlement, security, legal, or dispute records that must be retained and the reason. A deletion request does not delete your Google account, cancel a Google Play transaction, or automatically grant a refund. It may remove cloud progress and affect restoration of game-account-linked records.
Deletion is currently handled through support, not an automatic in-game deletion button. Signing in again after deletion may create a new game account; local progress is not erased by a support request and could be uploaded again if you reconnect. Clear local game storage if you also want it removed.
How long information is kept
Local progress and preferences remain until cleared or replaced. Cloud progress includes the current snapshot and one prior snapshot, kept to provide continuity and recovery until replaced or removed following a verified request. Authentication and routine service records are kept while needed for the account and online services. There is currently no configured time-based automatic expiry for these game cloud records.
Purchase and entitlement records are kept as needed to provide and restore features, investigate fraud or disputes, and meet applicable recordkeeping duties. Support messages are kept for the request and any related dispute or legal duty, then deleted or de-identified when no longer needed. Hosting, security, advertising, Adjust, and Meta records may follow the providers' own retention rules and service settings. We do not promise an unconfigured fixed automatic-deletion period. Contact us for information about the records relevant to your request and any applicable retention exception.
07. Security and international processing
We use secure connections, authenticated requests, limited backend access, app-integrity checks, and request limits to protect online game information. No storage or transmission method is completely secure.
Our current game cloud-save database and backend functions are hosted in the United States. Google, Adjust, Meta, Cloudflare, and support providers may process information in other countries, including countries outside your home jurisdiction. Where legally required, relevant international-transfer safeguards apply, such as provider contractual protections or recognized adequacy mechanisms. Contact us about safeguards relevant to your information.
08. Adults aged 18 and over
Fury Road Survivor is intended for players aged 18 and over and is not directed to children or anyone under 18. We do not knowingly collect personal information from anyone under 18.
If you believe someone under 18 has provided personal information, email furyroadsurvivor@firstzerostudio.com. If we become aware of such information, we will take appropriate steps to remove it and address related provider processing, subject to applicable legal requirements.
09. Changes to this policy
The October 18, 2026 revision adds conditional Meta App Events development testing and clarifies that verified license-test product quotes and currency may be sent to the Adjust sandbox. This update does not enable production measurement or real payments.
The October 13, 2026 revision adds optional Google account and Firebase cloud-save processing, Google Play license-test purchase verification, Google AdMob and UMP test-ad processing, Adjust sandbox measurement, and account/data deletion instructions. It also updates the description of Cloudflare website measurement.
This revision applies when published on this website. A policy update does not itself enable game features or constitute consent. We will update the policy when actual features, providers, or information practices change, give notice of material changes as required, and obtain new consent where required before affected processing begins.
10. Contact First Zero Studio
Use the subject “Privacy — Fury Road Survivor” for privacy questions, or “Account deletion — Fury Road Survivor” for deletion requests. We do not need your Google password or complete payment details.