Product scope. These legal documents apply only to the Dodgemaxxer game, offered by Asetral. They are not the general terms or privacy policy for our company website as a whole or for other products, unless we say otherwise on those pages.

Dodgemaxxer — Privacy Policy

Last updated: 2026-04-26

This Privacy Policy describes how Dodgemaxxer (the "App") handles information when you install and use it. The data controller (the person or organisation responsible for decisions about your personal data in connection with the App) is Asetral ("we", "us"), an independent software studio established in the Republic of Turkey. Asetral operates exclusively online and does not maintain a public physical address; the primary contact channel is the email address listed in the Contact section and on the app store listing.

This Policy applies to the current version of the App unless we publish an updated Policy with a new "Last updated" date. If you do not agree with this Policy, please do not use the App.

1. Summary

The App is a free-to-play mobile game. Depending on how you use it:

• You may play as a guest without creating an account. In that case, gameplay progress, settings, and related data are stored on your device (local storage).
• You may optionally create an account or sign in using email and password or Google (on iOS and Android). If you do, we use Google Firebase Authentication to verify your identity and Google Cloud Firestore to store an encrypted-in-transit cloud backup of your progression and settings linked to your account, so you can restore them on another device or after reinstalling.
• The App shows third-party advertisements through Google AdMob (banner, interstitial, optional rewarded video).
• The App uses Google Firebase components including the core Firebase SDK, Firebase Authentication, Cloud Firestore, and Firebase Crashlytics (for crash diagnostics on native builds). We do not integrate Firebase Analytics for product analytics in the current version.
• Web builds of the project (if published) do not load the same native sign-in and cloud-save flow; account features are described for the iOS and Android apps.

Your device, Apple, Google (for the app stores, AdMob, Firebase, and – if you use it – “Sign in with Google”), and other providers may process information under their own terms. See Platform and service providers below.

2. Use without an account (guest / local only)

If you do not create an account or sign in, the App does not send your gameplay or settings to our own servers or to Firestore as part of a user account. Your progression and preferences are held locally as described in Local storage on your device below. Third-party SDKs (for example AdMob and Firebase core) may still transmit limited technical or diagnostic data to Google as described in this Policy, regardless of sign-in.

3. Optional accounts, authentication, and identity

Native mobile app only. In the iOS and Android app you may:

• Sign up with email and password (we require a minimum password length in the app for basic security);
• Sign in with email and password; or
• Sign in with Google (Google account OAuth).

What we and our service providers process for authentication

• For email/password sign-up and sign-in, Firebase Authentication (Google LLC) processes your email address and account credentials according to Google’s and Firebase’s terms and this Policy. We use this to create and authenticate your user ID in Firebase.
• For Sign in with Google, Google processes your Google account in line with your Google settings. The App uses the Google Sign-In flow to obtain an ID token that Firebase exchanges for a Firebase user session. We do not receive your Google password. Your name and email address may be available to us through Firebase in connection with that account, as well as a stable user ID (UID).

Display name may be set when you register or may come from your Google account; we use it to label your cloud save and in-app where relevant.

You are responsible for keeping your sign-in details confidential and for activity that occurs on your account if someone else has access to your device or credentials. If you believe your account is compromised, change your password (where applicable) and contact us and/or use Google’s account security tools for Google sign-in.

4. Local storage on your device

The App uses on-device storage (for example React Native AsyncStorage) to save settings, game state, and ad-pacing data that is kept on the device for a consistent experience, including for guests. Categories of information that may be stored locally include:

• Audio and playback settings: music and SFX toggles, volumes, reduced motion, optional gameplay performance mode, and similar preferences.
• Progression and gameplay statistics: best distances, objectives, run counts, difficulty use, in-game currency, missions, retention features, cosmetics, and related flags as implemented in the App.
• Interstitial ad pacing (device-only): a local counter is used to pace full-screen ads (for example, approximately every three completed runs). A related numeric field may also appear in your cloud document for compatibility with older app versions, but the App does not use the cloud value to overwrite your on-device counter when you sync from the cloud.
• Debug or development options if present in a build (for example, hitbox debugging in development).

Local data is not a substitute for the cloud backup: clearing app data, uninstalling, or losing a device can permanently remove local information unless you have signed in and allowed the cloud to receive updates.

We do not use the local data described in this section to build an advertising profile about you on our systems. Ad networks and operating system services may use identifiers under their own policies, as described under Third-party advertising and Platform and service providers.

5. Cloud save and Firestore (signed-in users)

If you are signed in with a Firebase account, the App can store a versioned cloud document (for example in the userSaves collection) in Cloud Firestore (Google), keyed to your Firebase user ID (uid). The document may include, among other things:

• Schema version and JSON-serialised progression (such as best distances, unlocks, and related gameplay data as designed for backup);
• JSON-serialised playback settings (for example, audio toggles, volumes, and accessibility-related preferences, subject to the App’s merge rules with local data when you restore);
• A display name string;
• A small non-identifying numeric or compatibility field used for ad-related bookkeeping in older flows.

Processing is for enabling cross-device restore and resynchronisation, defending against abuse of the backup feature, and improving reliability of the service. The default rules in our documentation and deployment are that only the authenticated user with matching uid can read or write that document, subject to correct Firestore security rules in your live backend.

Location of processing: Firestore and Firebase Authentication are operated by Google in accordance with Google’s data centre and privacy documentation. Data may be stored or processed in multiple countries (including the United States and the European Union), depending on Google’s infrastructure and your project configuration.

No sale: We do not sell the contents of your cloud save. Google may process data as an independent subprocessor / service provider under the Firebase terms you accept through use of the App, and as described in this Policy and Google’s documentation.

Deletion: The App may not include a one-tap "delete my account" button in every version. You may request erasure of your cloud data and, where technically feasible, deletion of your authentication account by contacting us at contact@asetral.com and identifying the email you used. You can also use Google’s and Firebase’s account and privacy tools for Google-related processing where applicable. Uninstalling the App or signing out does not automatically delete the Firestore document; you should request deletion if you want the cloud copy removed. Local data on your device can be removed by clearing app data or uninstalling on the device.

6. Crash diagnostics (Firebase Crashlytics)

On native iOS and Android builds, the App may use Firebase Crashlytics (Google LLC) to collect diagnostic information when the App crashes or in certain error cases, such as stack traces, device model, operating system version, app version, and a pseudonymous installation identifier associated with the Firebase installation. Crashlytics is typically disabled in development builds that run with __DEV__ in supported configurations, to avoid polluting production crash data; release-style production builds are intended to enable collection to help us fix stability issues. Crash reports are not used by us to sell your personal data or to personalise ads in the App. For how Google processes Crashlytics data, see Google’s and Firebase’s documentation and the Crashlytics product terms.

7. Platform and service providers (stores, device, and Google)

• App stores (Apple, Google, others): When you install or update the App, the store and your device OS process data under Apple’s and Google’s (and any other applicable) privacy and store terms. We do not control that processing.
• Google Firebase (core, Auth, Firestore, Crashlytics): The App integrates Firebase services as described in this Policy. A Firebase Installation ID and basic device and app information are typically transmitted to Google for infrastructure and service operation even when you are not signed in, as is standard for Firebase-enabled apps. See https://policies.google.com/privacy and Firebase’s privacy and security information.
• Open-source libraries: A list of relevant software notices is in THIRD_PARTY_NOTICES.md in the project repository; that is for transparency and does not change the roles described in this Policy.

8. International transfers, Turkey, and your region

Asetral is established in the Republic of Turkey. If you are in the EEA, UK, Switzerland, Turkey, US, or elsewhere, your local data protection and consumer laws may give you additional rights (for example, access, correction, erasure, restriction, objection, or complaint to a supervisory authority). In Turkey, the KVKK (Law No. 6698) applies. International transfers of data processed by Google in connection with Firebase, AdMob, and Sign in with Google are subject to Google’s terms and safeguards and your account settings with Google, where Google is a separate controller or provider in respect of your Google account. For the data we and Google process as described in this Policy, you may contact contact@asetral.com to exercise your rights, and for Google’s processing, also see Google’s Privacy Help and, where you use a Google sign-in, your Google Account tools.

Turkey (KVKK). You may contact us to exercise the rights in KVKK Article 11 (to learn whether your data is processed, to request information, correction, deletion, or anonymisation, and to lodge a complaint with the Kişisel Verileri Koruma Kurumu [KVKK Board]). For requests to us: contact@asetral.com.

9. Retention

• On device: Local data remains until you clear app data, uninstall, or replace the device, subject to the OS and backup tools (for example, device backups may copy local app data according to the OS).
• Cloud (Firestore): We retain the cloud document while your account exists and we support the service, subject to this Policy, deletion requests, and abuse handling. We may delete or anonymise data when no longer needed for a legitimate purpose, in line with this Policy and applicable law.
• Authentication: If your Firebase / Google authentication record is deleted (by you, by us, or by Google, as applicable), you may not be able to sign in the same way again without creating a new account, and cloud records associated with a deleted uid may be removed or made inaccessible, depending on technical implementation and your requests.

10. Security

We use reasonable technical and organisational measures in designing the App and in configuring TLS-protected connections to Firebase and Google services. No mobile app or online service is completely free of risk. You should protect your device (for example, with a passcode) and your email and account credentials. Do not share passwords or one-time codes. If the App or Firebase alerts you to suspicious sign-in activity, follow the instructions from Google or us.

11. Children and age requirements

The App is intended for a general audience and is not directed to children under the age of 13 in the United States, or the higher age where the law of your country requires parental consent to create an account or to process personal data for online services. We do not knowingly permit children under the applicable minimum age to register for an account if we are aware that the person is a child, subject to the limits of the information we have. If you are a parent or guardian and believe a child has created an account or we have process data in a way that concerns you, contact contact@asetral.com. Local (guest) use that does not involve an account is limited to the device; parents can also use device parental controls and the store’s child-account tools.

12. United States — California and similar state laws

If you are a California resident or a resident of another U.S. state with a comprehensive consumer privacy law, you may have rights to know, delete, opt out of sale or sharing for cross-context behavioural advertising, and more. We do not sell your personal information (including children’s) for money in the traditional sense, and we do not "sell" or "share" your personal data for cross-context behavioural advertising in the CCPA/CPRA sense for our own ad network — ad delivery is handled by Google under Google’s policies. You may have rights regarding sensitive personal information and automated decision-making under law; the App is not designed to use sensitive categories for profiling as defined in CCPA, beyond what is technically involved in sign-in, crash reporting, and advertising through third-party SDKs. You may request more information or a deletion request for data we control as Asetral by writing to contact@asetral.com and, for Google-processed data, use Google’s and Firebase’s privacy and account tools.

13. What we do not do (high level)

In addition to the points above, we do not:

• use the App, by itself, to sell your email to unrelated companies for their mailing lists;
• use Firebase Analytics in the current app version to analyse your in-game behaviour for our marketing profiles (if we add a different analytics product, we will update this Policy in advance and the in-app and store copy as needed);
• require an account to play the core game; accounts are optional for cloud backup and sign-in on native mobile.

Third parties (Google, ad networks) may use technical and ad-related data under their own policies, as when AdMob shows an ad. See §14 and Google’s AdMob help.

14. Third-party advertising (AdMob), identifiers, and iOS

AdMob (Google). The App uses Google Mobile Ads / AdMob to show:

• a banner on the main menu;
• interstitial (full-screen) ads after runs, according to a device-local run counter (and not in the middle of active gameplay in the way that is typical for a run);
• optional rewarded video ads when you choose to watch an ad in exchange for in-game benefits.

AdMob and its partners may use identifiers (for example, advertising ID where available) and technical and engagement data to deliver and measure ads, including under Google’s policies and the AdMob programme policies. We do not receive your name or email from AdMob solely because an ad is shown; your ad experience is governed in part by Google and your OS-level ad and privacy settings.

iOS and tracking. If you use the App on iOS, Apple’s App Tracking Transparency (ATT) prompt or Privacy Nutrition Label-related options may apply to certain ad-related or app-linked processing. Your choices in iOS Settings and in any ATT dialog apply to those flows as Apple and Google describe in their own documentation. If you are on iOS 14+, review Settings → Privacy for the App and for Tracking.

15. Marketing analytics

We do not in the current version embed Firebase Analytics or a separate in-house "product" analytics SDK to track your taps and levels for our ad targeting on other companies’ properties. If we add a new first-party or third-party analytics product, we will update this Policy and, where the stores require, the app metadata and in-app notices before or at the time that product goes live in production builds.

16. Changes to this Policy

We may change this Policy. The "Last updated" date at the top will change when we publish a new version. For app store listings, the privacy policy URL should point to the current text on the web. If you keep using the App after an update, you acknowledge the new Policy, except where your jurisdiction requires a separate step (for example, re-consent for a material change in certain regions).

17. Contact

For privacy questions, requests (including access, correction, and deletion where applicable), and data protection correspondence: contact@asetral.com.

You can also use the support or contact information on the app store page for your download, and any form published on our official website for the game. If you need this Policy in another format (for example, plain text for assistive use), request it through the same channels.