Information we handle
- Account information: if you choose email or Google sign-in, Supabase Auth processes your email address and account identifier, authentication codes or credentials, and session information. Google sign-in uses Google account identity information and a short-lived identity token to authenticate with Supabase. The app stores its sign-in session on your device. Signing in alone does not upload or replace game progress. In builds with Save recovery enabled, you can choose to back up or restore your campaign.
- Purchase and account records: when purchase verification is enabled, we process your account identifier, Google Play product, selected ship model when relevant, purchase state and timestamps, Google Play order identifier, and a one-way hash of the purchase token. The device temporarily holds a purchase token while verification is pending. We use these records to deliver account-bound items, restore purchases, handle refunds or revocations, and prevent duplicate or fraudulent claims.
- Rewarded-ad records: in ad-enabled builds, the app and our server process the reward type, a short-lived reward request identifier, callback and claim status, ad unit, and reward timestamps. The server does not put your email address or account identifier into AdMob’s custom ad data.
- Connection and support information: the API temporarily processes an IP address in memory for rate limiting. If you choose to copy and send the in-game diagnostics report, that report may include device details and recent error information. It is not sent to us by the copy action itself.
- Game progress: gameplay saves remain on your device. If you choose Save recovery, we also store an account-linked copy of your campaign, including progress, inventory, earned currency, settings and in-game names, in Supabase through our API. Automatic backups are optional after linking this device. Restoring a backup replaces the current local campaign and keeps a pre-restore copy on the device. These backups do not turn local progress into verified online balances.
Google Mobile Ads in ad-enabled builds
Google’s current disclosure for Google Mobile Ads SDK 25.5.0 says the SDK automatically collects and shares IP address (which may be used to infer approximate location), app interactions such as launches, taps, and video views, diagnostics such as launch time, hangs, and energy use, and device or account identifiers such as advertising ID and App Set ID. Google describes these uses as advertising, analytics, and fraud prevention. The SDK encrypts this data in transit. Details can change with SDK versions and configuration; see Google’s Google Play data disclosure.
Ad-enabled builds use Google’s User Messaging Platform (UMP) to request and present consent information where required. When Google requires a privacy-options entry point, the game provides a control to reopen those choices. See Google’s UMP guidance.
How information is used and shared
We use account information to authenticate you, provide optional campaign backup and recovery, and operate account-bound purchase services; purchase information to verify, deliver, restore, and reconcile purchases; and security information to limit abusive requests and investigate billing disputes. Supabase provides authentication and database hosting. Resend delivers account verification email. Google Play processes app purchases. Google also provides optional Google sign-in. Google processes data through its Mobile Ads and UMP SDKs in ad-enabled builds. DigitalOcean hosts the API service. These providers process information as needed to provide their services under their own terms and privacy policies.
We do not receive or store your full payment-card number through VOIDWAKE. Google Play handles payment details.
Storage and security
Account sessions remain in local app storage until you sign out or the session expires. Cached purchase history is stored separately by account and may remain in app storage until it is replaced or app data is removed; signing out alone does not clear that cache. The server stores account-linked purchase, wallet, and rewarded-ad records needed to provide and protect those services. Access is restricted to server-side systems. Connections to the API and service providers use encrypted transport.
Retention
We keep account and service information while needed to provide the requested account and purchase features, resolve purchase or fraud disputes, and meet applicable legal requirements. Account-linked purchase and security records may be retained for those purposes. Save recovery keeps the latest three campaign snapshots and at most 64 recent backup request identifiers per account. Deleting an account removes its active campaign snapshots and request records. Infrastructure backup copies may remain according to their backup lifecycle.
Your choices and deletion
Account sign-in is optional. You can sign out on a device, decline rewarded ads, and use Google’s device controls for advertising identifiers. Signing out does not delete the account or its server-side records.
To request deletion of your VOIDWAKE account and associated server-side data, visit Delete your VOIDWAKE account. If your build shows Delete account in Settings, you can use that control with a recent sign-in and typed confirmation. You can also email us from the address associated with the account to start a deletion request. Account deletion does not erase the game save or locally earned currency stored on your device, or Google Play’s own purchase history. Account deletion also removes active cloud campaign backups. A deletion request can remove access to account-bound purchases and their restoration.
Children
VOIDWAKE is not designed to collect a child’s personal information through a child-directed account experience. If you believe a child provided account information, contact us to request review and deletion.
Contact
For privacy questions, contact admin@bipolarparadigm.com.