Privacy policy
Updated 20 September 2026 · Applies to Deadshift Android builds and its account service.
Deadshift is provided by Samuel Hajnik Games. Contact samuelhajnik@gmail.com with privacy or data requests.
Playing without an account
Campaign progress, earned credits, upgrades, checkpoints, audio settings and personal Survival records are saved on your device. Clearing app data or uninstalling can remove these saves. The game does not require access to your contacts, camera, microphone or precise location.
Optional Google account and recovery
Google sign-in uses Firebase Authentication. Google processes your selected account, including the email, profile information and a player identifier. The game’s native authentication SDK handles credentials; they are not sent to the game’s browser code. Our server uses the verified player identifier to retrieve your purchases and cloud wallet. Internal testing restricts purchases to approved tester accounts.
If you choose Save Progress, we store a copy of your earned credits, equipment, unlocked sectors and Survival records. These are separate from purchased credits. Saving and restoring are manual actions; checkpoints are not included.
Purchases
Google Play handles payment information. Deadshift does not receive card numbers. Our server stores the player identifier, product, encrypted purchase receipt, a receipt hash, purchase/refund status, purchased credit balance and upgrade transactions. This delivers and restores purchases, retries interrupted transactions and prevents duplicate grants. Purchases may be unavailable during testing.
Advertising and privacy choices
Deadshift integrates Google Mobile Ads and Google’s User Messaging Platform. These services can process IP addresses (including approximate location), advertising and other device identifiers, app interactions, diagnostic information and performance data for advertising, measurement and fraud prevention. Consent and available choices depend on your region and Google’s requirements. Where offered, reopen Privacy Choices from the menu. Development and internal testing builds use Google’s sample ad units.
Optional rewarded videos add earned credits only after the SDK reports completion. Remove Ads suppresses automatic between-sector ads; it does not remove optional reward videos.
Service providers and security
We use Google/Firebase for authentication, Google Play for billing, Google Mobile Ads for advertising, and our hosted server for recovery and purchase verification. Data may be processed outside your country by these providers. Game-to-server communication uses HTTPS. Receipt tokens and backup archives are encrypted. Server requests expose an IP address to the hosting infrastructure and short-lived abuse controls; we do not use it for gameplay profiling.
Optional crash reports and gameplay analytics
Starting with version 0.9.5, you can independently enable Crash reports and Gameplay analytics in Credits → Privacy & Diagnostics. Both start disabled. Firebase Crashlytics processes crash/error reports, stack traces, app and device details and installation identifiers. We attach limited game context such as mode, sector and difficulty. Selected game-display errors are reported with their category and bundled source location; our game-error bridge does not send raw error messages.
If you enable Google Analytics for Firebase, it processes app-instance identifiers, device/app information, session activity and events such as run starts, level outcomes, Survival duration/scores and ad outcomes. The SDK may also collect its standard automatic events, including app updates and in-app purchases. We do not set an Analytics user ID or attach your Google sign-in identity, email, purchase receipt or save file. Advertising-ID collection and advertising personalization are disabled for this analytics integration; the advertising SDK has separate practices described above.
Disabling an option stops future sharing. Turning off analytics also clears its local data and resets the app-instance identifier. Turning off crash reporting requests deletion of unsent reports. Reports already sent follow Google's retention and deletion rules. These choices are device-level and independent of sign-in or your advertising-consent choices. See Firebase privacy information for provider retention and processing details.
Retention and deletion
Cloud progress and purchase records are retained while you keep a Deadshift account. You can request deletion through Delete account or the in-game store. Deletion removes the cloud wallet, upgrades, progress and stored receipts. Minimal one-way hashes of deleted account identifiers and receipts are retained to prevent replay and fraud; they do not include your name, email, balance or saved progress. Google may retain payment records under its own policies. Deleting an account does not issue refunds.
Encrypted recovery backups expire after 30 days. If a backup is restored, deletion records must be reapplied before the service reopens. Local guest progress is removed by clearing the app’s storage or uninstalling. Google account deletion inside Deadshift removes the game’s Firebase sign-in account, not your Google account.
Your choices
You may play as a guest, sign out, manage advertising consent where available, and request access, correction or deletion of your account information. Contact the email above; we may verify ownership without asking for passwords or payment-card details. You may also contact your local data-protection authority.
Children and policy updates
Deadshift is a combat game intended for older players and is not directed at children. Follow the age rating shown by Google Play when the game is released. We update this page if the game’s data practices change.