Privacy Policy for Gossan: Deep Mining

Last updated: October 22, 2026

Who we are

Gossan: Deep Mining is published by Discs.dk ApS, Denmark, under the DoctorMogget brand. Our company registration number (CVR) is 42203580. For support or privacy questions, email info@doctormogget.com or call +4552706230.

What this policy covers

This policy covers Gossan: Deep Mining for Android, support correspondence, and the DoctorMogget website. The Android game uses Google Play Games sign-in and cloud saves, advertising through Google AdMob with Google's User Messaging Platform (UMP), and one optional in-app purchase, Full Access, through Google Play Billing, starting with version 0.9.0 build 25100482. Builds after 25100482 can also use Google Analytics for Firebase to measure how the game is played, as described under Analytics below. Earlier 0.9.0 test builds, made before these services were switched on, use none of them.

The game is intended for players aged 13 and older. Core play works offline. We do not operate a player-account service, game-save server, or analytics backend of our own, and the game contains no crash-reporting SDK. Gameplay measurement uses Google Analytics for Firebase only as described under Analytics below.

Local game data

The game stores progress, upgrades, the excavated world, achievements, statistics, records, and settings on your device. It stores your Play Games player identifier locally to separate each account’s cloud-sync record. Before a cloud restore, it keeps local recovery copies of saves and profile data, plus a restore journal until the restore finishes or fails. It also keeps local copies of both versions of a cloud conflict. Recovery and conflict copies share a rolling limit of three sets. Account-scoped sync records and recent deleted-snapshot fingerprints are stored locally. These recovery files and sync records are not added to the game’s cloud-save payload. The game also stores your advertising age answer and its policy version, and, if you buy Full Access, the purchase entitlement. Neither is added to the cloud-save payload. If Analytics is in use, the game also keeps a small local record of which one-time measurement events (described under Analytics) this installation has already reached; it is not added to the cloud-save payload either.

The game does not send these local saves to a server operated by Discs.dk ApS.

You can remove local app data by clearing app storage; uninstalling normally removes it too. Your operating system's backups, or copies held by a separately enabled platform cloud service, may remain and must be managed separately.

Support correspondence

When you contact us, we receive your email address or other contact details and the information you choose to send, including attachments. We use this information to respond, investigate the issue, and complete necessary follow-up. Please avoid sending passwords, payment-card details, or personal information unrelated to your request.

Discs.dk ApS is responsible for its handling of support correspondence. For routine inquiries, our legal basis is our legitimate interest in responding to requests and resolving problems with our game (GDPR Article 6(1)(f)). You choose whether to contact us; without enough contact or problem details, we may be unable to respond or resolve the issue. Our email is hosted by Simply.com.

We delete support correspondence once the inquiry is resolved and necessary follow-up is complete, except where a legal obligation or a concrete dispute requires retention. For records required under the Danish Bookkeeping Act, we rely on compliance with a legal obligation (Article 6(1)(c)) and retain applicable accounting material for five years after the end of the relevant financial year. Where correspondence is needed for a concrete dispute, we retain the relevant material only while necessary to establish, exercise, or defend the claim, based on our legitimate interest in doing so (Article 6(1)(f)). Provider backups may follow a separate retention cycle.

DoctorMogget website

Our website is a static site hosted by GitHub Pages. We do not add analytics, advertising trackers, cookies, third-party fonts, or embedded third-party content to its pages. GitHub receives visitors' IP addresses and logs them for security purposes, even if visitors are not signed into GitHub. GitHub's handling of its hosting and security data is described in its privacy statement: GitHub privacy statement.

Advertising

The game shows full-screen ads from Google AdMob at two pauses only: after an actual death, once the wreck has played and before the RUN ENDED card; and after a full refuel or repair at the surface following a mining trip. It shows at most one ad per trip, none in the first five minutes of active play after each launch, and at least three minutes of active play passes between ads. It never shows an ad on the title screen, at SAVE, RELOAD or ABANDON, or during play below the surface.

Google's Mobile Ads SDK can collect and share IP addresses, app and ad interactions, performance diagnostics, and device or account identifiers, including an Android advertising ID when available. An IP address can indicate approximate location. Google describes these uses as advertising, analytics, and fraud prevention. Collection depends on the SDK, device settings, and the configured advertising and privacy choices. Non-personalized or age-restricted advertising can still involve processing data. Google's disclosure is available at Google Mobile Ads data disclosure.

Before advertising starts, the game asks a neutral question for your month and year of birth, which must be answered to continue. It does not request the day of birth, a country, or a state. The game turns the answer at once into an age range (under 13, 13-14, 15, 16-17, or 18 or older; within the birth month it assumes the younger age) and keeps only that range; the month and year are not stored or sent. The age range and its policy version are stored locally, separately from saved progress, and are excluded from the game's Play Games cloud-save bundle. At startup, a missing answer (for example one that could not be saved), or choosing under 13, prevents the game from starting its advertising or UMP consent flow. This startup guard does not prevent access to previously required privacy choices after an age answer is changed or removed during a session.

For an eligible flow, the game sends protective settings to Google. All 13-17 choices use Google's CHILD restricted-ad treatment and UMP's under-age setting; 18-or-older uses the adult route. These signals concern advertising restrictions and do not establish a player's legal capacity to consent. Google's under-age setting may suppress the consent form. Age-restricted processing is not a promise that Google receives no data.

The adult route refreshes UMP and presents any required regional privacy form before checking whether ads may be requested. If UMP cannot be reached or its form fails, the game asks UMP again later; meanwhile it relies on the answer UMP kept on the device from an earlier session only where that answer still permits ads. With no such answer, or with missing required permission, no new ad requests are made. Where the GDPR route applies, the game also requires evidence of consent for storage/access purpose 1. It has no automatic limited-ads fallback. Refusing personalization may still permit non-personalized ads if the remaining permissions allow them.

Where required, OPTIONS > PRIVACY CHOICES lets you revisit Google's privacy form. OPTIONS > ADVERTISING AGE RANGE and FORGET AGE CHOICE let you change or remove the local age answer; after FORGET AGE CHOICE the game asks the question again. Opening the question, or giving the same answer again, changes nothing. Changing or removing an answer after that session's UMP flow has begun stops new advertising for the rest of the app process; restart the app to apply a new eligible answer. Previously required privacy choices remain available in that session for user-requested, privacy-only UMP access, even if the local age answer is now unknown or under 13. This access does not start or resume advertising. Opening privacy choices retires ads prepared under the old settings. Requests already sent cannot be recalled, and these controls do not erase every record held by Google. Android settings provide separate advertising-ID controls.

We show ads to fund the game. Where the law requires consent for storing or accessing information on your device, or for personalized ads, we rely on the consent you give or refuse in Google's UMP form (GDPR Article 6(1)(a)); you can withdraw it at any time through OPTIONS > PRIVACY CHOICES. Google processes ad data as an independent controller under its own policies, including the Google Ads controller terms. Where Analytics is on, the game also reports the revenue Google states for each ad shown to Google Analytics; see Analytics below.

Analytics (Google Analytics for Firebase)

Android builds of the game can include Google Analytics for Firebase, a measurement service from Google. We use it to understand how players progress through the game, to balance its difficulty, to measure advertising and purchase revenue, and, if we advertise the game, to measure which of our campaigns lead to installs and purchases.

What is collected: app interactions, namely the events the game reports (completing the tutorial, the first dive below 10 metres, the first ore sale, reaching each new depth stratum for the first time, each ad shown with the revenue Google reports for it, and a completed Full Access purchase with its transaction ID, price and currency), and events Firebase records automatically, such as first open, sessions and app updates. Firebase also collects device and app information (for example device model, operating-system version, language and app version), a Firebase app-instance ID, and, where advertising consent permits it, the Android advertising ID. Google uses the IP address to derive an approximate location such as country. The game does not send your saves, your Play Games identity, your age answer, or your name or email address to Analytics. Playtest builds are marked so their data can be told apart.

Consent: Analytics starts with collection switched off and all Google consent-mode signals (analytics storage, ad storage, ad user data and ad personalization) set to denied. The game turns collection on only after Google's UMP form has given an answer that permits storage of and access to information on your device (purpose 1) and allows ad requests, and only on the 18-or-older age route. Where UMP says no consent is required in your region, collection starts once UMP confirms that. It never starts on the 13-17 route, without an age answer, for under-13 answers, or on launches where Full Access was already owned (the consent flow does not run then). Events that happen while collection is off are not sent later.

Our legal basis is your consent where the law requires consent (GDPR Article 6(1)(a)); elsewhere, it is our legitimate interest in measuring and improving the game (Article 6(1)(f)). You can withdraw consent at any time through OPTIONS > PRIVACY CHOICES: opening the form switches collection off and sets every consent signal to denied, and it stays off if you refuse storage consent. FORGET AGE CHOICE also switches it off for the rest of the app session. Withdrawal does not recall data already sent. Android settings provide separate advertising-ID controls.

Google processes Analytics data on our behalf as our processor under Google's data processing terms for Google Analytics and Firebase. If we link Analytics to Google AdMob, Google Ads or Google Play Console, data is shared with those Google services under their terms. Google Analytics keeps event-level data for the retention period we set, no longer than 14 months; aggregated reports may be kept longer. To ask us to delete Analytics data linked to your installation, email info@doctormogget.com. Google's description of how it uses data from apps that use its services: How Google uses information from apps.

Full Access purchase

The game offers one optional, one-time purchase, Full Access, through Google Play Billing. It removes every ad permanently and unlocks the robot's paint colours, and it is the only thing for sale; it changes no game upgrades or progress, which are still earned by playing. Google Play handles payment details. The game processes the product, purchase state, and purchase token to restore and acknowledge ownership, and keeps the entitlement locally. Purchase tokens are not included in the game's cloud-save bundle. Discs.dk ApS does not receive card or bank details through the game; platform sales reports may contain transaction, price, date, and region information.

Once ownership is recorded, the game stops new ad loads and shows and retires pending or loaded ads. On later launches with ownership already recorded, it does not start its advertising or ad-consent flow. This does not delete Google's previous records or stop an SDK already running in the app process. RESTORE PURCHASE asks Google Play for an existing purchase on the same Google account. Where Analytics is on when a new purchase completes, the game reports the purchase (transaction ID, product, price and currency) to Google Analytics; restored purchases are not reported.

Google Play Games and cloud saves

Google Play Games may authenticate you automatically when the game starts, according to your Google Play Games settings. The game receives a player identifier and display name and uses them for the Google Play Games features. When you are signed in, the game also submits achievement unlocks to Google Play Games, where they appear on your Play Games profile. Achievements also remain part of the local game profile included in enabled cloud saves. Core play remains available without Play Games authentication. Google's SDK also collects its own analytics and diagnostic data to improve SDK stability and its products: Play Games data disclosure.

Cloud syncing defaults to ON after authentication and can begin before you open OPTIONS. When enabled, it sends a saved-game snapshot to Google containing the three save slots, the profile with achievements, statistics and records, the last-played slot, a timestamp, and the device's operating-system name. It excludes the local age answer, purchase tokens, entitlement, and audio/input settings. Discs.dk ApS does not run a server that receives this snapshot. The integration does not browse your other Google Drive files.

OPTIONS > CLOUD SAVE > Cloud saves OFF stops this device's cloud-save reads and writes. DELETE CLOUD SAVE requests deletion of this game's remote snapshot, keeps local progress, and switches cloud sync off on this device. A deletion that times out may still finish later for the same account. A different device with cloud syncing enabled or an offline queued save may recreate the cloud snapshot. Turn cloud syncing off on your other devices as well if you want to prevent further game-initiated uploads. Deleting the snapshot does not delete your Google account, Play Games profile, achievements, provider logs, or backups. Manage those through Google's own account and Play Games controls. Google provides separate controls for Play Games profile visibility and game data.

See Google's privacy policy at Google privacy policy and account controls at Google Play Games deletion controls.

Why we process Play Games identity and cloud-save data

We use your Play Games identity and cloud-save data to protect your progress and keep it available across your devices. Our legal basis is our legitimate interest in providing reliable save and recovery features (GDPR Article 6(1)(f)). We limit this processing to those features. You can object to this processing by contacting info@doctormogget.com, switch cloud saving off, and request deletion of the cloud snapshot. Core gameplay remains available locally without cloud saving.

Google processes Play Games data as an independent controller under its own privacy policy, including its SDK analytics and diagnostics. For EEA and Swiss controller data, the Google end controller under the Play Games controller terms is Google Ireland Limited; for UK controller data it is Google LLC. Our legal basis for save protection is not a statement of Google's basis for its separate purposes.

Retention and processing locations

Local game data remains until removed from the device, subject to platform backup behavior. Where online platform services are enabled, their providers retain data under their own applicable rules; deleting an in-game cloud snapshot does not promise immediate removal of all provider backups, logs, or legally required records.

Simply.com describes its email hosting as located in Denmark. GitHub and Google, including Google Play Games, AdMob, UMP, Google Play Billing, and Google Analytics for Firebase, operate internationally and may process data outside your country or the EEA. Their linked privacy statements explain their processing locations and transfer arrangements. Google describes its safeguards, including applicable adequacy arrangements and standard contractual clauses, at Google transfer safeguards. Contact us for information about the handling of personal data for which Discs.dk ApS is responsible.

Your privacy rights

Contact info@doctormogget.com to request access, correction, deletion, restriction, portability, or to object to our processing, where these rights apply. Where processing relies on consent, you may withdraw that consent; withdrawal does not undo processing that occurred beforehand. We will assess your request and explain any applicable legal retention requirement. We may need enough information to verify the request and identify the relevant records. Data held within Google or GitHub services may also require a request through that provider's controls.

You may complain to your relevant data protection authority, including Denmark's Datatilsynet: Datatilsynet.

Delete game data

Policy changes

We will update this page when our data practices change. The date at the top identifies the latest version.