PROJECT HEAT / Privacy

Privacy policy.

This notice explains how Digital Drift handles information in PROJECT HEAT for Android and on this website. The game is currently in development.

Last updated: 19 October 2026

Who is responsible

Digital Drift s. r. o., company ID (IČO) 56 089 007, Kozia 600/12, 811 03 Bratislava – Staré Mesto, Slovakia, is responsible for the processing described here. Contact: digitaldriftplay@gmail.com.

Game progress and local diagnostics

The game stores progress, vehicles, garage choices, in-game currency, fuel and settings on your device. Bounded local diagnostic logs record gameplay events, event times, a temporary session reference and the game version. These files support saving and troubleshooting. Local game files are not uploaded as part of our custom analytics events. The Android configuration disables app-data backup.

Optional analytics and crash reports

PROJECT HEAT integrates Google Analytics for Firebase and Firebase Crashlytics. When diagnostics sharing is enabled, Google receives gameplay interactions and progression events, app usage, performance information, crash reports, app/device information and installation or app-instance identifiers. Google Analytics can derive approximate location from the device’s masked IP address. The game does not request GPS location, and we do not attach your name, email, game-save contents or free-form text to custom events. Firebase advertising-ID collection and personalized-ad signals are disabled.

We use diagnostics to understand progression, improve game balance and performance, and investigate failures. The revised diagnostics choice uses your consent: sharing stays off until you choose “Share diagnostics” in Settings and confirm the explanation. You can refuse and continue playing, or withdraw later by switching it off. Old default-on preferences are not accepted as a new consent choice.

Earlier test versions: pre-release versions including build 127 enabled diagnostics on a fresh installation and provided an off switch. The revised consent flow was prepared on 15 October 2026 and is not included in those existing packages. If you use an earlier test version, switch off “Share diagnostics” in Settings to stop future collection.

Switching off disables future Analytics and Crashlytics collection, resets local Analytics app-instance data, and deletes unsent crash reports. It does not automatically delete reports already uploaded. This choice is separate from any advertising privacy options.

Google account, cloud saves and purchases

In current Google Play versions with cloud saves, a new installation must sign in with Google through Firebase Authentication and complete the cloud-save setup before playing. A device with an existing linked save can continue offline and synchronize later. The separate development/demo app can be used offline without a connected account. Google/Firebase processes the selected Google account identifier and basic profile (which can include email, name and profile image). We use the Firebase user identifier to associate cloud progress and purchase records; we do not add your email or name to custom gameplay analytics.

When you connect an account, the game saves a copy of your progress in Cloud Firestore: completed jobs, virtual currency, fuel, garage choices, vehicles, upgrades and purchased benefits. This is separate from optional diagnostics sharing. It is needed to provide cloud saving, deliver purchases once, and restore the last successfully synchronized progress. Unsynchronized offline changes may not be recoverable after clearing app data or uninstalling. Conflicting cloud and local saves are not silently merged.

Google Play handles checkout and payment details. We do not receive or store card details. Our server receives purchase tokens for verification with Google, product and order identifiers, test-purchase status, purchase/confirmation/refund state, a reference to your player account, and verification timestamps. Raw purchase tokens are transmitted for verification but are not saved in our application database or custom logs; a hash is used as the purchase record key. We use these records to deliver items, prevent duplicate grants and fraud, and process refunds and purchase restoration. Purchased virtual currency has no cash-out value.

Firebase App Check with Play Integrity helps verify that requests come from our genuine Android app. Google processes integrity attestations and associated app/device information to prevent abuse. Our purchase functions require an authenticated player and a valid App Check token.

Account processing and cloud saves support the service you request. Purchase processing supports fulfillment and necessary legal obligations; fraud prevention and system security serve our legitimate interests. Optional analytics continues to use your separate diagnostics choice.

Optional rewarded advertising

The game offers optional rewarded video ads in exchange for in-game benefits, including fuel. Watching an ad is your choice. Development versions may show Google test ads or local promotional videos; these do not produce advertising revenue. When production rewarded ads are enabled, PROJECT HEAT uses Google Mobile Ads and Google’s User Messaging Platform (UMP). The app requests an update to advertising privacy choices at launch and presents a message when required. It requests an ad only when you choose a rewarded placement and UMP permits the request. You can reopen available advertising privacy options from the in-game Settings menu. This choice is separate from “Share diagnostics”.

For advertising, measurement and fraud prevention, Google Mobile Ads can process your IP address (which may reveal approximate location), interactions such as ad views and taps, diagnostic and performance information, and device or app identifiers. The Android project removes permission to access the Android advertising ID; other identifiers may still be processed by Google. Google may use the information according to your privacy choices and its own policies. We do not send your game-save contents, name or email to the ad request. Rewarded ad events are also recorded in bounded local diagnostic logs; they are sent through our optional gameplay analytics only when diagnostics sharing is enabled.

Existing internal builds up to 131 have real checkout disabled. Internal purchase tests are restricted to designated testers and Google Play test purchases. Public Early Access build 144 blocks checkout for other players. The separate development store uses simulated purchases; those isolated demo events are blocked from cloud analytics.

Providers and international processing

Google provides our authentication, cloud storage, purchase verification, integrity, analytics and crash-reporting services. The purchase functions and Firestore database are configured in europe-west1 (Belgium); this does not mean all Google authentication, payment or support processing stays in that region. Processing may take place outside Slovakia or the European Economic Area. The applicable Google data-processing terms and transfer safeguards govern those services. Details: Firebase privacy and security, Analytics data disclosures, Mobile Ads data disclosures and Google Privacy Policy.

Retention, deletion and your choices

Local progress and logs remain until you clear app data or uninstall; older local logs rotate at the size limit. Turning diagnostics off does not delete saves. Cloud saves and the linked player account remain until you request deletion. Uninstalling does not delete cloud records.

You can request deletion of your PROJECT HEAT account and associated cloud progress using the in-game “Delete account / data” link or our account deletion page. We verify the request using your sign-in email and remove the linked Firebase player account and cloud save. Necessary purchase, refund and anti-fraud records may be retained where required for legal obligations, disputes or abuse prevention; we explain any applicable retention exception when handling your request. Local device files can be removed through Android app storage settings. Deletion does not automatically cancel or refund a purchase.

Uploaded diagnostics are used for progression analysis and investigation of technical issues and are subject to the configured Google Analytics retention controls. Aggregated reports can have a different lifetime from individual event records. Firebase states that Crashlytics retains crash information and associated identifiers for 90 days before starting removal from live and backup systems. We do not promise that uninstalling the app deletes previously uploaded data.

To request access, correction or deletion, or to exercise applicable rights to restriction, objection or portability, email digitaldriftplay@gmail.com with the subject “PROJECT HEAT privacy request”. Describe the request and the game version. Do not send passwords or payment-card details. For a connected player account, send the request from the Google email used to sign in. For installations without an account or older diagnostic records, we may need more information to locate the relevant record. We will explain any limitation. You may withdraw consent without affecting earlier lawful processing and may complain to the Office for Personal Data Protection of the Slovak Republic or your competent supervisory authority.

This website and correspondence

The website presents company and game information. We have not added website analytics, advertising scripts or a contact form. The hosting service may process connection information to deliver and secure the website. If you email us, we use your address and message to respond and keep necessary correspondence for the inquiry, legal obligations or the establishment and defence of claims. This processing is based on our legitimate interests in handling inquiries and, where applicable, legal obligations. Do not include unnecessary sensitive information.

Security and updates

Local files use app-specific storage. Firebase uses encrypted transport for the transmitted information described above. No service can guarantee absolute security. We will update this page when our practices change, including when the production advertising or purchase setup changes.

Contact

digitaldriftplay@gmail.com
Digital Drift s. r. o., Kozia 600/12, 811 03 Bratislava – Staré Mesto, Slovakia.