Dashphalt · NegativeZero
Privacy Policy
Effective date: 18 October 2026
Last updated: 18 October 2026
1. About this policy
This policy explains how NegativeZero ("we", "us") handles information in the Android game Dashphalt, package ID com.negativezero.dashphalt, and its purchase-verification and reviewer-access services. You can contact us at [email protected].
Gameplay and game saves are primarily local to your device. Optional Google Play coin purchases, purchase recovery and reviewer access use online services. You do not need to create a player login account to play.
2. Game information stored on your device
Dashphalt stores information locally to operate the game and retain your progress and preferences. This includes your coin balance, owned cars and tracks, upgrades, selections, scores and run records, progression, tutorial state, and settings such as music and sound volumes, graphics, vibration and steering preferences. Saves also contain technical version information and purchase-credit records used to avoid applying the same purchased coins more than once.
Ordinary game progress, steering inputs, scores and upgrade spending are not uploaded to our purchase service. We do not provide cross-device cloud saves or public player profiles.
3. Coin purchases and purchase verification
Coin packs are optional, one-time consumable purchases through Google Play. Each purchase is a separate payment; packs do not create a monthly subscription or automatic renewal. Google handles checkout. We do not receive your payment-card number, bank credentials or Google account password.
To verify purchases, deliver coins and recover interrupted delivery, the app and our server process:
- A randomly generated installation/profile credential and its hashed identifier. This is not an advertising identifier and is not derived from your name or email address.
- The app package name, purchased product ID, Google Play purchase token and purchase status.
- Purchase information returned by Google's verification API, which can include order identifiers, quantity, acknowledgement/consumption status and the installation/profile identifier attached to the purchase.
- A persistent server ledger containing hashed receipt references, product IDs, installation/profile identifiers and cumulative delivered coin totals. Purchase tokens are retained for unfinished consumption/retry work and removed from our ledger's receipt record after consumption is recorded as complete.
The installation credential is sent to our service to authenticate delivery and recovery requests. A hashed identifier is supplied to Google Play to associate a purchase with the relevant installation/profile. Our service verifies the receipt with Google, records the coin grant and consumes the purchase so the same pack can be purchased again. Google Play purchase notifications may also trigger verification and recovery.
These records support coin delivery, duplicate prevention, fraud prevention and purchase support. They are not a server copy of your current spendable balance or game progress. Clearing app data or changing devices may remove the credential and local progress needed to reconnect to previous deliveries; consumed packs are not a cross-device restore or cloud-save feature.
4. Network information and reviewer access
Our service runs on Cloudflare. Requests necessarily expose network information such as your IP address, request time and HTTP headers to the hosting provider. Cloudflare and Google may process service, security and diagnostic information under their own policies and applicable service settings. Our application code does not deliberately log purchase tokens, installation credentials, reviewer codes or request bodies.
The restricted reviewer-access form sends the entered access codes to our service for validation. To limit repeated attempts, the service stores a hashed IP reference, an attempt count and a time window. The attempt limit uses a 15-minute window; expiry of that window does not automatically delete the stored entry. A successful reviewer login opens separate local reviewer progress and a separate purchase identity, rather than changing normal player progress. Reviewer codes do not bypass Google Play payment confirmation.
5. Permissions, device features and advertising
Dashphalt uses internet access for online features, Google Play Billing for purchases, and optional vibration and device-orientation readings for gameplay feedback and tilt steering. Orientation readings are processed on the device and are not sent to our purchase service.
The current app does not include advertising, advertising-identifier tracking, third-party marketing analytics or a developer-operated crash-reporting SDK. It does not request your contacts, precise location, camera, microphone or photos. We do not sell personal information or use purchase information for targeted advertising.
6. Service providers and disclosures
We use Google Play and Google Cloud services for payment processing, purchase verification and purchase notifications, and Cloudflare for hosting and persistent purchase-ledger storage. Information is processed by these providers as needed to deliver and secure those services. Their infrastructure may process information in countries other than your own.
We may also use information you voluntarily send when contacting support, such as your email address, correspondence and relevant purchase details, to respond to your request. We may disclose information when required by law or reasonably necessary to protect rights, investigate fraud or secure the service.
See Google's Privacy Policy and Cloudflare's Privacy Policy for their practices. These providers may independently process installation, billing, security, backup or diagnostic information under their own terms and your settings.
7. Retention, deletion and your choices
Local saves remain until reset, replaced or removed. You can use Android Settings → Apps → Dashphalt → Storage → Clear storage/Clear data to remove local app information. Uninstalling normally removes local data, subject to platform backup and restoration. The in-game progress reset is not a request to delete server purchase records and retains purchase-credit bookkeeping to prevent replay of previously delivered credits.
Purchase-ledger records are retained while the service supports delivery, recovery and duplicate prevention; they are not automatically deleted when you reset progress or uninstall. There is currently no scheduled automatic expiry of ledger or reviewer-attempt records. Support correspondence is retained as needed to resolve requests and handle disputes. Some records may need to be retained for legal obligations, security, fraud prevention or transaction disputes.
To request access, correction or deletion of information held by us, email [email protected] and identify Dashphalt. We may ask for information necessary to verify the request and locate the relevant records. Do not send passwords, private keys or payment-card details. Because purchase records use installation/profile identifiers rather than a named player account, we may be unable to locate or verify particular records after you clear app data. We will explain any applicable retention limitations when responding. Depending on your location, you may have additional data-protection rights, including a right to complain to your local supervisory authority.
8. Android backup
Android backup is enabled. Depending on your device, Google account and backup settings, Android or your device provider may back up and restore app data. We do not operate or receive these platform backups. Removing local data may not delete an existing backup; manage backups through your device or provider settings.
9. Children's privacy
Dashphalt does not request a player's name, age or contact details and does not provide public chat. Installation identifiers and purchase/network information are still processed for the online features described above. Parents and guardians should manage purchase access through Google Play's controls. If you believe a child has provided personal information to us, contact us so we can investigate and respond as required.
10. Security and policy changes
Connections to our purchase service use HTTPS. Local information relies on device and Android application-storage protections, and access to hosted records is restricted through service credentials and access controls. No transmission or storage method is completely secure.
We may update this policy when the app or our practices change. The latest version will show an updated date, and we will provide additional notice where required.