1. Who handles the data
The controller is Gotthard Panic, operator of the game, API and website. Use the address in Privacy contact for personal data requests.
Apple, Google and any infrastructure or email providers handle some data under their own roles and policies.
2. Data handled by the game and API
- Guest profile: random UUID, selected language, last activity time and access token. The technical “device_name” token label currently contains the generic value “mobile”, not the device’s personal name.
- Optional account: name, normalized email address, password stored only as a hash, email verification status and tokens for login, verification or password recovery.
- Email preferences: choice to receive game news, consent or withdrawal time and consent text version. Promotional email requires separate consent and a verified address.
- Progress: level, completion, stars, best score, best time and completion date.
- Daily challenge: attempt identifier, start and finish times, duration, vehicles passed, accidents, maximum queue and completed/not completed result.
- Daily leaderboard: rank, time and accidents are public with a nickname, if present, or a “Driver” alias followed by the last four characters of the public identifier. Account name and email are not shown.
- Connection data: IP address, time, request headers and technical request details may be handled by servers and hosting to deliver the service, enforce anti-abuse limits, protect the API and diagnose faults.
3. Data stored on the device
- Progress and results waiting to sync are saved in local app files.
- The access token and a profile copy are kept in secure operating-system storage: Keychain on iOS and encrypted storage protected by Android Keystore on Android.
- Language, audio, music, tutorial and unlocked chapters are stored as local preferences.
- Advertising choices may be stored locally by Google User Messaging Platform. Remove-ads entitlement is checked with the store and may be cached locally.
4. Email invitations
When you prepare an invitation, the recipient’s address stays in the app field and is passed to your email app through a mailto link. Gotthard Panic does not send it to its API or send the message. You review and send it from your email app.
5. Advertising and consent
The code integrates Google Mobile Ads for interstitial ads between rounds and Google User Messaging Platform (UMP) to collect and refresh privacy choices. The ads SDK is initialized only when UMP reports that ads may be requested. Where legally required, the app also offers a control to reopen privacy options.
Once live ads are enabled, Google Mobile Ads may handle IP address and IP-derived approximate location, app and ad interactions, diagnostics, device or advertising identifiers and ads shown. Purposes and personalization depend on the UMP choices and device settings.
Production ad identifiers are configured, but “liveAds” remains off in test builds. This section applies from the time a published build enables live ads.
6. Purchases
The code provides for a one-time remove-ads purchase. Payment, transaction history, payment method, refunds and receipt are handled by Apple App Store or Google Play. Gotthard Panic receives only the information needed to verify the no-ads entitlement and does not collect card numbers.
The store product is not active in the reviewed configuration. Deleting a Gotthard Panic account does not delete purchase history held by the store.
7. Purposes and legal grounds
- Performance of the requested service: create and authenticate a profile, sync progress, provide the daily challenge, recover an account and verify purchases.
- Consent: send promotional news and, where required, store or use identifiers and data for advertising. Consent can be withdrawn without affecting earlier processing.
- Legitimate interests: security, abuse and fraud prevention, request limits, technical continuity and fault diagnosis.
- Legal obligations: retain or disclose data when required by law or a binding order.
8. Recipients and transfers
Providers hosting the API or website, delivering technical email or maintaining the service may handle data only as needed. The reviewed development configuration does not yet identify the production hosting or email provider.
When ads or purchases are active, relevant data is handled by Google and/or Apple. They may operate outside Switzerland, the EEA or the user’s country and use the transfer mechanisms described in their policies.
Leaderboard entries are visible to other players. Data may also be disclosed to authorities when legally required.
9. Retention and deletion
Accounts, tokens, progress and daily results stay associated with a profile while it exists. The reviewed backend does not yet automatically delete inactive guest profiles, so these records remain until deletion or administrative cleanup.
Email verification links expire after 24 hours and password reset links after 60 minutes. Marketing preferences remain until withdrawal or account deletion. Technical logs and backups depend on production infrastructure settings and are kept as needed for security, recovery and legal duties.
A registered account can be deleted in the app with the password or at api.gotthardpanic.ch/account/delete. Deletion removes the account, tokens, online progress, daily attempts and results, and email preferences through linked database deletion. The app also attempts to erase local profile files. Store purchases remain separately managed by Apple or Google.
10. Website
The landing page is static and its reviewed code contains no accounts, forms, analytics, advertising pixels or site-set cookies. The server delivering pages may still process ordinary request logs such as IP, time, URL and user agent for operation and security.
11. Rights and choices
Subject to applicable law, you may request access, correction, deletion, restriction, objection and data portability, or withdraw consent. You can disable email in the profile or through the link in messages and manage advertising choices in the app when that control is required.
You may complain to the competent authority, including the Swiss Federal Data Protection and Information Commissioner or the authority in your EEA country. We may request information needed to verify identity before fulfilling a request.
12. Children, security and changes
The game does not ask for a birth date and is not designed to knowingly collect personal data from children who cannot validly consent in their country. A parent or guardian may contact us to request deletion.
We use HTTPS for the API, hashed passwords, revocable tokens and secure device storage, but no system is risk-free. We will update this notice when data, providers or features change and show the new date above.