Privacy and participation

Operated by Dingcolabs · Contact hello@dingco.net. Updated 26 October 2026. TINY GAP keeps local course progress, cosmetic skins, achievements and settings on your device. These local records are not imported into official rankings.

Audience and choices

TINY GAP is intended for a general casual audience aged 16 or older. This version does not enforce a game-wide age gate. The separate 16+ confirmation controls optional analytics only; it does not verify age. The G ad-content limit describes ad content, not the user’s age.

Automatic service security

When a connection is available, the app automatically requests the daily challenge at startup and on refresh, before you join competition or allow usage analytics. For service security, the server processes the request IP address and derives a pseudonymous HMAC rate identifier and per-minute request count. Rate-count keys expire after 61 seconds. Hashing does not make this identifier anonymous; it is not shown on the leaderboard.

Optional anonymous competition

Only after you choose to join, the service creates a generated Player alias and private token. A server-issued run ticket and bounded input journal—paddle movement, aim, item decisions and their timing—verify your daily score. Your alias, best score, active time and dated rank are public. No nickname, email or contact-list access is required. Your private anonymous credential stays on this device. Resetting app data loses access to that credential; it does not itself delete server records. Use the in-app deletion action before resetting data when possible.

Anonymous registration is retained until you delete it or security cleanup removes it. Daily boards and public share receipts expire 30 days after that UTC day begins. Run/replay data, input journals, reward grants and verification/transaction references expire 24 hours after the run ticket is created. The local outbox holds one completed run for at most 15 minutes, within its original ticket expiry. Settings → Participation lets you delete the anonymous identity and associated available boards, runs and public shares. Local course and cosmetic progress remains on your device.

You can also submit a deletion request outside the app, including after uninstalling. You do not need to reopen or reinstall the app to send it. Ownership checks, the deletion scope and current verification limits are explained on that page.

Optional rewarded advertising

An exhausted item may offer one optional rewarded ad per run. The Google Mobile Ads SDK handles ad delivery. Every rewarded-ad request in this version uses non-personalized ads. Non-personalized ads still involve Google SDK data collection and sharing, including app/device identifiers, approximate network location, ad interactions and diagnostics for advertising, analytics and fraud prevention, under Google’s SDK disclosures and your privacy choices. It does not require this game to request precise GPS access. Cancellation or failure does not add an item use. A server-side reward check may delay public ranking verification. Use Ad privacy options in Settings to review choices. An ad being shown is not treated as revenue.

Consent information and privacy choices

On iOS, Google’s User Messaging Platform refreshes consent information when the app launches, even if you do not choose a rewarded ad or enable usage analytics. Android requests consent information in the ad or ad-privacy flow. This privacy-choice processing can include consent information, approximate location, performance and interaction data under Google’s SDK disclosures.

Optional usage analytics

Optional analytics is only available after you confirm you are 16 or older and grant a separate choice; it can be withdrawn in Settings. The device stores only that eligibility confirmation, not a birth date, and does not send it to the analytics service. Declining leaves the full game and ranking available. With separate analytics consent, the relay sends GameAnalytics an installation UUID/session, build and platform, and actual interactions, progression/scores, share-sheet openings and ad request/load/show/failure/reward/paid events. These events are linked to that installation identifier. Paid events describe actual SDK-reported publisher advertising revenue, not a purchase by you. Withdrawal cancels pending analytics and clears local analytics IDs and queues; it does not erase data already accepted by the provider or change separate ad-privacy choices. Share-sheet opening does not prove that you posted externally. Ranked participation does not grant analytics consent.

Questions

Contact Dingcolabs at hello@dingco.net or the developer contact in the actual store listing. Google privacy and GameAnalytics privacy describe the SDK providers. Files or screenshots already exported through an external share sheet cannot be retracted by deleting the in-app share receipt. Public share links contain an opaque receipt ID and no private token or run ticket.