The short version
Drillwake plays offline and needs no developer account. Game progress stays on your device. Versions through 1.4.0 are paid and have no advertising or in-app purchases. From version 1.5.0, the first expedition is free, with optional Apple purchases and Google rewarded videos. Version 1.6.2 adds RevenueCat purchase validation and revenue accounting. Optional Game Center features send scores and achievements to Apple when you are signed in. Data practices depend on your installed version, as described below.
Information stored on your device
Drillwake stores game progress and settings locally on your iPhone or iPad using Apple UserDefaults. Your saved worlds and settings remain on your device; Game Center receives only the gameplay results described below, not your complete save file. Replacing or deleting a save slot removes that slot’s progress. Removing Drillwake removes its locally stored data, but does not automatically remove records held by Apple Game Center.
Advertising
From version 1.5.0, Drillwake offers optional video ads. You choose when to watch one; nothing in the game is locked behind them, and no ad ever appears without you asking for it.
Ads are requested as non-personalised. Versions through 1.7.0 do not request Apple's App Tracking Transparency permission. From version 1.7.1, the separate, optional Meta measurement described below may request it. IDFA access is governed by your device's permission state; non-personalised requests do not mean all advertising data is anonymous. Google may process device or app identifiers, IP-derived approximate location, advertisements viewed, interactions, crash information and performance diagnostics for advertising and measurement. Some information may be associated with your device. Google's SDK also declares a Device ID tracking capability where permitted by the device's privacy settings. See Google's SDK data disclosures and privacy policy.
Beginning with version 1.6.2, the game disables Google's publisher first-party ID and publisher privacy personalization before starting the ad SDK. Earlier ad-supported versions did not disable publisher first-party ID. Non-personalised requests do not eliminate all collection: Google may still use identifiers for frequency capping and aggregate reporting. See Google's privacy controls and ad-serving explanation.
The game runs Google's consent-management flow before initializing ads where required and does not request an ad unless that flow permits it. Ad privacy choices are available in game settings where required. A confirmed Full Expedition owner does not initialize the ad SDK on a fresh launch. Buying Full Expedition stops ad offers, but an already-initialized SDK may remain active until you close the app.
Analytics and tracking
Version 1.6.2 uses RevenueCat for purchase validation and revenue accounting. It does not forward ad-impression earnings to RevenueCat; advertising earnings remain in AdMob. Google's permission to serve ads is not treated as consent for a separate advertising analytics processor. Versions before 1.9.0 do not include TelemetryDeck. Version 1.9.0 adds the separate, opt-in play statistics described below. The optional Meta events beginning with version 1.7.1 are also described below. The game does not create developer accounts or use third-party sign-in.
Optional play statistics from version 1.9.0
Play statistics are off unless you choose “Share stats” when the game asks, or turn on “Share anonymous stats” in Settings. Before you opt in, the game creates no statistics identifier and sends no play-statistics signals. Declining does not change gameplay, purchases or rewards.
If you opt in, the game sends a small set of gameplay signals to TelemetryDeck GmbH: first launch and whether the install is fresh; later sessions, whether they are return visits and the number of days since opt-in; first-job tutorial steps and completion; the start and end of your first descent, including its depth and whether you surfaced or were wrecked; your first ore sale; and your first upgrade. Each signal carries a one-way hash of a random identifier created for statistics, a random session identifier, app version, platform and time. The game does not attach your name, email, Game Center identity, advertising identifier, device model, location, save contents or purchase records. There is no screen recording, tap capture or session replay.
Signals can wait in a bounded on-device queue while offline. Turning “Share anonymous stats” off deletes the statistics identifier and unsent queue and stops new play-statistics requests. A request already sent may still complete. Turning it on again creates a new identifier. This switch does not delete signals already received by TelemetryDeck. We have no player account or identity mapping with which to associate these statistics with you. The separate Meta and advertising permission controls described below still apply independently.
These play-statistics signals are not forwarded to Meta, Google or other advertisers. TelemetryDeck processes them under its privacy policy. Publication of this section does not mean version 1.9.0 has been released.
Optional Meta advertising measurement from version 1.7.1
To understand whether our advertising brings new players to Drillwake, version 1.7.1 adds permission-gated Meta measurement. It remains off while Google's regional consent status is unknown or requires consent, including in the EEA, UK and Switzerland. Where that status confirms no additional regional consent is required, the app may ask for Apple's tracking permission. Meta measurement starts only when that permission is authorised. From version 1.8.1, a Full Expedition owner may also have Google's consent-management service check the region without loading a consent form or starting the ad SDK. This check is only attempted while the app is active and Apple's tracking permission is undecided or authorised. It does not itself start Meta measurement; the same regional and Apple permission gates still apply. This description of 1.8.1 does not mean that version is already available.
When enabled, Meta receives app activations and return-session information, session timing, device identifiers and Meta advertising-link information to measure advertising effectiveness and understand early engagement. The game also reports three milestones by name: tutorial completion, first ore sale and first upgrade. These limited events help us understand whether players attracted by our advertising reach the core game loop. Automatic gameplay-event and purchase-event logging remain disabled. The game does not attach save contents, ore quantities, gem balances, purchase values, RevenueCat purchase records or Game Center identity to these milestone events. Meta's SDK also processes technical information, other analytics data and crash data under Meta's privacy policy. These practices begin with the measurement-enabled version 1.7.1; publication of this policy does not mean that version has been released.
Declining or restricting tracking does not affect gameplay, purchases or rewards. You can change the permission in iPhone or iPad Settings. When the app becomes active again, it rechecks permission and stops new app-triggered activations, milestone logging, event flushes and advertising-link forwarding if permission is no longer authorised, and turns off advertiser-identifier collection through the SDK setting. This does not delete previously received information or purge Meta's existing event queue. Events already queued may remain on the device and may be sent if you later grant permission again. An already-started SDK may continue technical configuration requests until you close the app; we do not promise that every SDK request stops immediately. In versions through 1.8.0, a confirmed Full Expedition owner may have no regional advertising-consent result, so Meta measurement can remain off for that player. From 1.8.1 the region check above can resolve that case, but Meta still remains off when the region requires consent, Apple tracking is denied, or the check cannot complete.
Session timing and milestone delivery can be incomplete, for example if a player does not return, is offline or declines tracking. A small on-device record limits repeat milestone logging attempts; it is not a guarantee of event delivery. App Store Connect separately supplies Apple's available download and opt-in usage reports. These are aggregate reports, not a complete individual player history or an account shared with Meta and RevenueCat.
Apple Game Center
From version 1.4.0, Drillwake uses Apple GameKit for optional rankings and achievements. When you are signed in to Game Center, the game submits your best Deep Bore depth, your Daily Dig depth where available, and earned achievement completions to Apple. Apple associates these results with your Game Center player account, and your nickname and scores may appear to other players according to your Game Center settings.
The developer does not receive your Apple Account password or operate a separate player database. Apple processes Game Center information under its Game Center privacy notice. You can manage your profile, sharing and sign-in in your device’s Game Center settings. You can play the main game without Game Center; online rankings and achievement reporting require a connection and sign-in.
Purchases and accounts
Drillwake does not create developer accounts. From version 1.5.0 it offers Full Expedition, which opens the remaining worlds and removes ads, plus optional Core Gem packs and a limited-time Starter Pack. Core Gems can also be earned in play and spent on optional in-game items and cosmetics. Purchases are handled by Apple under Apple's terms and privacy policy; the developer does not receive your payment details. Gem balances and credited transaction identifiers are stored with the local game save to prevent duplicate crediting. If you bought Drillwake while it was a paid app, Full Expedition is granted automatically after your App Store purchase history is verified. If that check is unavailable, the game does not start ads.
Optional daily reminders are scheduled locally on your device after you enable them; no game server sends them. You can disable them in the game or iPhone or iPad Settings.
Beginning with version 1.6.2, RevenueCat receives verified Apple purchase records and an automatically generated anonymous app-user identifier to validate purchases and understand revenue. The game does not add your name, email, phone number, Game Center identity, advertising identifier or custom identifying attributes to this purchase-accounting integration. RevenueCat may also process SDK protocol metadata. Apple handles payment-card details; Drillwake does not receive them. Your complete game save is not sent to RevenueCat. See RevenueCat's privacy policy.
Signed purchase records awaiting reporting are stored in a protected local outbox, excluded from cloud backups. They retain the original anonymous customer identifier and retry when the app runs again. Successful reporting removes the queued record; deleting the app removes the local queue. These records are not written to logs or used to grant purchases again. Apple transactions finish after the game credit is safely saved and the accounting record stored, without waiting for RevenueCat's server. A local write failure retains Apple's transaction for recovery. RevenueCat reporting is separate from Apple and Google's payment systems and does not change your rewards, purchase access or ability to play offline.
Children
The developer does not request personal information from children. Apple manages Game Center accounts and related parental controls under its own policies and device settings.
Website
This static website does not use cookies, analytics, advertising, or tracking scripts. A future support form will receive its own disclosure before it is enabled.
Changes to this policy
If Drillwake’s data practices change, this policy will be updated before the relevant app version is released. The effective date at the top of this page will also change.
Privacy questions
Use the Drillwake support page. No personal address or developer profile is published here.
Your choices and data deletion
There is no Drillwake developer account to delete. You can delete local save slots in the game, or remove the app to remove its local data, including queued purchase-reporting records. Deleting local data does not revoke an Apple purchase or automatically erase records held by Apple, Google, RevenueCat, Meta or TelemetryDeck.
For a request concerning information held by the developer, use the Drillwake support page and describe the privacy request. For information held independently by a provider, use that provider's privacy controls and request procedures linked in this policy. Revoking Apple's tracking permission stops future app-triggered Meta measurement after the app rechecks permission; it is not a deletion request for earlier information.