Dot Dodge Privacy Policy

Effective and last updated: October 3, 2026

App: Dot Dodge for Android
Package: com.andrix.dotdodge
Developer and privacy contact: Ashwin S Ashok — andrix.android@gmail.com

This policy explains how Dot Dodge handles information when you play, view ads, use optional purchases, or enable diagnostics. No Dot Dodge account is required. Some features depend on the build, Google Play availability, and your privacy choices.

1. Game progress stored on your device

The app saves scores, personal bests, coins, mission progress, statistics, cosmetic unlocks, daily-reward status, Premium access status, and settings in its local app storage. There is no player-account system or cloud-save service in Dot Dodge. The complete game save is not uploaded to us. Selected gameplay events and scores may be sent separately if you enable Usage analytics, as described below.

Dot Dodge does not request access to your contacts, photos, microphone, camera, or precise device location. Network services can receive your IP address and infer an approximate location without a device location permission.

2. Advertising and ad consent

Dot Dodge integrates Google AdMob for rewarded ads and, where enabled, interstitial ads between runs. Google and its advertising partners may process IP addresses, approximate location inferred from IP, advertising or app-set identifiers, ad interactions, and device or diagnostic information to deliver ads, measure performance, and prevent fraud. The information processed depends on your device settings, consent, and Google's ad configuration. Non-personalized ads may still involve data processing.

The app uses Google's User Messaging Platform to request applicable advertising consent. Where Google requires a privacy-options entry point, you can revisit it through Settings > Ad privacy choices. Android settings also provide advertising-ID controls. The app's optional Usage analytics and Crash reports switches do not disable AdMob's separate data processing.

See Google's Privacy Policy and Google Mobile Ads SDK data disclosures for advertising data details.

3. Optional usage analytics

Usage analytics starts off. If you enable it in Settings, Google Analytics for Firebase receives limited gameplay events: mode selection, run start/end, score and new-best status, star collection, revives, ad format shown, Premium activation, and support-link use. The SDK may also process app-instance identifiers, device/app information, sessions, and interactions to produce usage reports.

Our event code does not send your name, email address, purchase token, payment details, or a player-account ID to Analytics. Firebase Analytics advertising-ID collection is disabled in the app, and its advertising-storage and ad-personalization consent flags remain denied. AdMob is configured separately.

4. Optional crash reporting

The Crash reports option starts off independently of Usage analytics. If enabled, Firebase Crashlytics processes Java/native crash traces and selected nonfatal error codes, app/device details, installation identifiers, and game-mode context to help us fix failures. Gameplay event breadcrumbs can accompany a report when both options are enabled. Native crash processing may include diagnostic minidump data. We do not intentionally attach purchase receipts or free-form personal information to crash reports.

These services are described in Firebase's privacy and security information and Google's Privacy Policy. Development builds may pause collection even when your choices are saved.

5. Purchases and verification

Where available, optional Premium purchases are processed by Google Play Billing. Google handles payment information; Dot Dodge does not receive your card number or billing address. The app receives product identifiers, purchase tokens, and purchase state to unlock and restore access.

When production purchase verification is enabled, the app sends the product identifier and purchase token over HTTPS to our verification service. That service checks and acknowledges the purchase with Google Play. Purchase tokens are not sent to Analytics or Crashlytics. The current verification code does not persist receipt tokens in a database or intentionally log them. Hosting infrastructure may process connection metadata for operation and security. We store Premium access status locally so it can be used in later sessions.

6. Support and this policy website

If you email us, we receive the address and information you choose to include so we can answer your request. Please do not send passwords or full payment-card details.

This policy is hosted on GitHub Pages. Visiting it sends normal web-request information, such as your IP address, to GitHub. This page contains no analytics scripts, advertising scripts, or embedded tracking assets. See GitHub's Privacy Statement.

7. Sharing, security, and international processing

Information is processed by Google for advertising, analytics, diagnostics, and billing as described above, and by service providers needed to host the policy or an enabled purchase verifier. We do not sell the local game-save file or deliberately provide names or contact details to advertisers. Advertising identifiers and ad interactions may be shared through Google's advertising services under their terms and your choices.

Network transfers to these services use encrypted connections. We take reasonable steps to limit access and avoid putting receipts or personal text in diagnostics. Local game storage is not represented as an encrypted vault, and no security measure can guarantee absolute protection. Google, GitHub, and hosting providers may process information in countries outside yours under their applicable safeguards and policies.

8. Retention and deletion

Local progress remains until you clear the app's storage or uninstall it. Google's analytics, advertising, billing, and diagnostic records follow each service's retention rules and applicable configuration; withdrawing consent does not automatically erase records already sent. Purchase records held by Google Play may be retained for transaction and legal purposes. We keep support correspondence only as needed to respond, handle follow-up, and meet applicable obligations.

For a privacy or deletion request, email andrix.android@gmail.com with "Dot Dodge privacy request" in the subject. We will use the information reasonably available to locate records we control. Because the game has no player account and some SDK data is identified only by installation identifiers, we may need additional details to locate relevant data. Do not email full payment information.

9. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, restrict, or object to personal-data processing, withdraw consent, or complain to a data-protection authority. Contact us to make a request concerning data we control; Google and GitHub also provide their own privacy controls.

10. Children's privacy

We do not ask players to create an account or provide their name or age. Please follow the age guidance on the app's Google Play listing. If a parent or guardian believes a child has provided personal information to us, contact the privacy address above so we can investigate and remove information within our control as appropriate. Advertising and diagnostics remain subject to the consent controls described in this policy.

11. Changes and contact

We will post policy changes on this page and update the date above. Where required, material changes to data processing will be accompanied by additional notice or consent.

Privacy questions, deletion requests, and support: andrix.android@gmail.com
Developer: Ashwin S Ashok.