Privacy Policy · Wrecklanders: Idle Island

As of 1 November 2026 · Wrecklanders: Idle Island · The German version is legally binding: Datenschutzerklärung

Wrecklanders: Idle Island is a free game. It runs in the browser (web version at wrecklanders.com) and as an Android app. This policy also describes the iOS Store version. The web version shows no ads, uses no third-party trackers and needs no sign-up with name or e-mail. Sections 1 to 7 apply to the web version and the app. What the app adds (optional ad videos, notifications) is described in section 8. This page explains which data is processed, where it is stored and how you can delete it.

1. Controller

Simon Streblow
Quintenzstraße 1
77723 Gengenbach
Germany
E-mail: hello@wrecklanders.com

2. What we store

DataWherePurpose / legal basisHow long
Game progress, settings (sound, statistics yes/no, language), a friend's invite codeYour browser's local storageSo the game works (§ 25(2) TDDDG, Art. 6(1)(b) GDPR)Until you delete it
Pseudonymous player account (random ID, without name, e-mail or password), cloud save, island name, invite code, friendships, help between friends, receipts for one-time friend rewards and their payment confirmation timestamp (to prevent duplicate payouts after restarting an island), a random device ID (so only one device plays at a time)Supabase (data centre in Frankfurt am Main, Germany)Saving progress, playing on several devices, friend features (Art. 6(1)(b) GDPR)Automatic deletion of inactive accounts (after 30 days without activity if you have never opened a bag, otherwise after 12 months without activity) is being prepared. The current dry run only counts and does not delete accounts. Until activation, your account and cloud save remain stored until you choose “Delete all my data”.
Your browser's push address, scheduled remindersSupabase; delivered via your browser's push service (e.g. Apple, Google, Mozilla)Only if you allow notifications (Art. 6(1)(a) GDPR)Until you turn them off in the browser or delete everything; sent reminders after 2 days
Game statistics: game version, interface variant UX13 (on/off), platform (web, Android or iOS), session length, era reached, features used, rescues, sharing, friends joinedSupabaseOnly with your consent, to improve the game (Art. 6(1)(a) GDPR). You can switch it off any time under ⚙️ Settings13 months
Source channel: once, the name of the link you first came from (e.g. “whatsapp-status”, “reddit”, “invite”). If you come without such a link, only the rough kind of site you came from (e.g. “suche-google” for a Google search, “ki-chatgpt”, “reddit”, “web-andere”), never its address. Without another source link, the channel is “android-app” in the Android app and “ios-app” in the iOS app. We read the Google Play installation referrer for invitations and game-save transfers. Before your statistics consent, we hold it only in memory for channel attribution; we do not evaluate utm_source or utm_campaign for this purpose, persist an installation channel or transmit a source channel. Only with your statistics consent do we form “source~campaign” (at most 32 characters per component; just “source” without a campaign), store this installation channel locally for offline starts and send the source channel once to your account. Invitations take priority, including those arriving during login. On withdrawal, we delete the local installation channel and pending referrer; without consent, the pending referrer is lost when the app restartsSupabase; Android: also local app storage, only with statistics consentOnly with your statistics consent: counting which channels bring players (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). You can withdraw consent any time in settingsLocally until withdrawal or deletion of app data; on the account like your account and cloud save
Anonymous usage numbers: how many islands of a start day or start week are played again on day 1, 3 and 7, roughly how long visits last (in steps like 1–5 minutes), how far islands have come overall, how often new visitors press “Play” on the start page, and how often the hints (install the app, notifications, feedback) are accepted or postponed. Since 1.1 we also count first steps (seeing/tapping the intro, first bag, first build, eras 2 and 3) as anonymous daily totals, split by app/web and game version: only “+1” with fixed categories, without account, user or device identifiers or IP addresses. For these anonymous totals we store the day of your last game on your account; separate pseudonymous player counting is described in the next row. Nothing is stored on your device for thisSupabaseImproving the game (Art. 6(1)(f) GDPR, legitimate interest). You can object any time by e-mail to the address in section 1.Sums 13 months; the last day played until the account is deleted under the periods above
Pseudonymous player counting: From your cloud save we note on the server once when we first observed a completed bag. This note survives restarting your island. For qualified accounts we keep at most five return records: for days 0, 1, 3 and 7, and day 30 after that first observation, each containing only the calendar day and the last save time on that day. We use these records to count qualified players and their return, without collecting new data from your device for this. These records contain no additional game content, device or advertising identifiers or IP addresses; they are linked through the pseudonymous account identifier and are therefore not anonymous. Existing saves are included in the baseline without inventing an unknown historical first day. A later separate app analysis requires reliable platform evidence; missing platforms remain unknown. We use acquisition channels only as described above, without copying statistics events into the qualification note.SupabaseImproving the game and counting progress consistently (Art. 6(1)(f) GDPR, legitimate interest). You can object any time by e-mail to the address in section 1.Qualification note and at most five return records until your account is deleted under the periods above; these records do not extend those account retention periods.
Feedback you send from inside the game (text, mood, era reached, phone or computer)SupabaseImproving the game, because you send it to us (Art. 6(1)(a) GDPR)Until you choose “Delete all my data”, at most 13 months
Error and stability reports, including performance details in section 2.1 (platform web, Android or iOS, interface variant UX13 (on/off), error message, code location, page, phone or computer, operating system and browser with main version only, installed app or browser, game version; for crashes and hangs also the affected view or loading step). No account and no IP addressSupabaseOnly with your statistics consent: finding and fixing bugs (Art. 6(1)(a) GDPR)90 days
Anonymous operational monitoring: only the latest cloud-save timestamp per hour, without an account ID or IP addressSupabase; readable only by our teamDetecting and fixing cloud-save outages (Art. 6(1)(f) GDPR)Current day and the seven preceding days
Island name reports: random account ID of the reporter, island account ID, reported name and timeSupabase; readable only by our teamReviewing inappropriate island names and protecting friend featuresUntil either account is deleted

Blocking islands: When you block another island, we store your random account ID, the blocked island’s account ID, whether the block is active, and creation and update timestamps at Supabase. The block prevents mutual visits and new help; existing saves, friendship records and already earned rewards are preserved. Only you can see and remove your own active blocks; other players receive no list of your blocks. Unblocking marks the relationship inactive without deleting your save. Active and inactive block records remain until either account is deleted under the account retention rules above. Purpose: preventing unwanted contact and protecting the friends feature (Art. 6(1)(b) and (f) GDPR). This is independent of statistics consent.

Local preferences remember whether the island name question for this island and the statistics question on this device have already been displayed. These flags contain no gameplay actions or new identifier and are not transmitted. Closing the statistics question does not give consent. You can change your choice at any time in Settings.

From the Android browser to the app: When you use our Google Play button, we first save your progress and generate a random account transfer key. It appears only in the Play referrer: for a new installation it is passed to Google Play and read by the Android app; if already installed, “Already installed? Open app” can pass the same referrer directly to our app. It is valid for 24 hours and can connect only one receiving account. Our server stores only its SHA-256 digest, account IDs, expiry and usage timestamps; expired receipts are removed hourly (within 25 hours). If offline, the app keeps the key in local storage until transfer succeeds or it is confirmed invalid. It does not appear in website addresses, error reports or usage statistics. Purpose: automatically continue your progress and friendships (Art. 6(1)(b) GDPR, § 25(2) TDDDG). Google Play receives the installation referrer; Google’s privacy rules also apply.

Only with your statistics consent do we collect pseudonymous information about which game features are used (for example tour destinations, tabs, game help, the workshop and video entry points), how often they are used, progress by game day, and choices when changing islands (island, specialization and fixed heirloom IDs for each rescue). We add era, rescue count, whole days since the game began and a local sequential session number; no precise installation time and no additional device identifier. We use the existing random account ID, including the automatic guest account without Google sign-in. We send no names, free text or game content. Facts already in cloud saves are evaluated there; new usage data add missing detail and history. Frequent actions are grouped in bounded counter batches and rare progress milestones are recorded individually. Batches are sent to our existing provider Supabase at session end, at least every 30 minutes and when leaving. With consent, offline batches are stored locally for at most seven days (at most 32 batches of 8 KiB payload each). Without an available account ID, a bounded count stays in memory only; no new tracking identifier is created. Withdrawal in Settings stops collection and clears pending local batches and the session number. Statistics already sent remain stored for at most 13 months as before; account deletion removes them too. Legal basis: Art. 6(1)(a) GDPR and § 25(1) TDDDG for the local statistics buffer. No new provider.

Platform comparison: Only from the statistics events described above, with your consent, we compare Web, Android and iOS: accounts per platform, session starts and progress, and returns on the next, third and seventh Berlin calendar day (D1, D3, D7) after the first observed session on that platform. This is not an installation date. One account may count on several platforms when switching devices; missing historical platform evidence remains unknown. Acquisition channels such as Reddit stay separate. We collect no new identifier and extend no retention period for this comparison. Error reports without account identifiers are counted separately by platform.

Measurements from 1.3.3

Anonymous daily onboarding totals additionally distinguish technical source (Web, Android, iOS, CrazyGames, itch, Game Jolt or unknown). This category comes exclusively from the game build or host, never link parameters, referrer or device information. Existing app/web totals stay separate and are not added twice. On first reaching era 2 or 3, we also count only a coarse bucket of active minutes since starting: under 10, 10–20, 20–40 or 40+. We use the existing local game-interface clock; no exact durations are transmitted and no new statistics data are stored on your device. Without a reliable active clock, such as on old saves, we do not estimate a duration. These totals contain no account, user, device or advertising ID, IP address or save contents. Purpose, legal basis and retention match anonymous usage totals above: improving the game, Art. 6(1)(f) GDPR, 13 months, objection by e-mail. We do not store a first technical source channel on your account or server save for this.

Reminder openings are counted exclusively with your statistics consent both when tapping and immediately before transmission. We count anonymous daily totals using fixed categories: web push or local Android/iOS reminder, reminder type (expedition returned, camp full, boat, daily chest, inactivity) and game version. Not every type is available on every platform. Measurement data contain no recipients, contents, push endpoints, message, job, account or device identifiers. CEO, test and unrecognised reminders are excluded. Supabase receives only “+1” per category, with no additional pseudonymous event copy. Legal basis: Art. 6(1)(a) GDPR; retention: 13 months. On your device we keep a random revision of your current statistics choice (crashcamp.idle.stats.revision) and mirror that choice with its revision in the service worker cache. Each choice replaces the revision; clearing local site/app data removes it. It prevents delayed clicks from being counted after withdrawal and re-consent. This consent receipt is never sent to the statistics server and contains no click history. These openings are not delivery confirmations and do not yield a complete click-through rate.

The web service worker remembers only your statistics choice as a technical consent setting in a separate browser cache (until changed or site data are cleared; § 25(2) no. 2 TDDDG). A permitted click is handed to the game window in memory for at most 30 seconds and consumed once; the category-only URL marker is removed immediately and cannot produce a count by itself. The app attaches only fixed reminder types and the already scheduled time locally to the notification for classification and in-memory deduplication, never as measurement data. Clicks without statistics consent are discarded, with no record for later. Withdrawal stops pending transmissions; later consent never backfills openings. Notification permission and statistics consent are separate decisions.

2.1 Performance and stability (web and app)

Only with your statistics consent do we add game version, the interface variant UX13 actually displayed (on/off) and platform (web, Android or iOS) to usage events and error diagnoses. A variant change begins a new measured session segment. This lets us compare stability and usage within the consenting sample; it does not describe all players. As before, usage statistics are linked to your random account ID (13 months); error diagnoses have no account ID (90 days).

We additionally report only fixed technical error categories, at most once per category and session: local_save_failed (local save failed), local_save_unreadable (local save unreadable), cloud_sync_failed (authentication, permission, schema or repeated online network failure only), cloud_conflict_shown (a displayed, genuinely divergent save conflict), ump_privacy_options_failed (Google privacy options failed to open) and review_request_failed (technical review request failure). Video load failures are already covered by ad_fail. These additional categories are transmitted without names, save contents, tokens, account identifiers in error text, complete server responses or consent strings. Expected offline behaviour is not reported. Statistics consent is required; withdrawal stops further diagnoses. These diagnoses do not change your Google advertising choice or your game progress.

We count sessions, starts, sessions affected by freezes, and video attempts, results and loading/return times as anonymous daily totals by version and platform (web, Android, iOS). These totals contain no player, account, device or advertising ID, no full user agent, device model or IP address. Counters are summed in memory per fixed key and sent as a batch at most once per flush. Legal basis: our legitimate interest in a stable game (Art. 6(1)(f) GDPR); retention: 13 months. You can object at any time on grounds relating to your particular situation by e-mail to the address in section 1 (Art. 21 GDPR).

Only with your statistics consent do we send at most five aggregated performance details per session: freezes, slow taps, slow starts over 5 seconds (start), slow video loading (ad_slow), video errors or no available offer (ad_fail, failed/nofill), native hangs and crashes. Details include duration, fixed input type and element class without text or identifiers, input delay, processing/presentation time, technical attribution to own/foreign code or native, game version, platform, operating system/browser main version, era and active tab, seconds since video and foreground return, whether the ad SDK started, the page path without query parameters, and phone/computer. On the next start Android can also report renderer loss (crash yes/no) and the reason and hour-rounded time of an earlier process exit; for ANRs at most 15 filtered program stack frames without messages, file paths or personal information. Purpose, recipient and retention match the error reports in the table: finding and fixing bugs, Supabase, 90 days (Art. 6(1)(a) GDPR).

Only with your statistics consent do we collect and count slow tap response times from 200 ms using Event Timing in coarse time buckets, native renderer hangs/loss and process exit reasons. Reading historical Android process exit reasons and ANR traces and storing renderer diagnoses on your device also require this consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). The resulting anonymous daily totals are retained for 13 months. For this Android reads historical process exit reasons and keeps a local diagnosis mailbox (wl-stability) bounded to 20 entries, plus the last-read exit timestamp. The game acknowledges the revisions it read and clears those entries; without statistics consent no tap counters are collected, no exit reasons or ANR traces are read, and no renderer diagnoses are stored or sent. Withdrawal clears the diagnosis mailbox and read marker; a new consent does not collect exits from the time before it. Anonymous session, start, freeze and video counters from our own timer remain active. “Delete all my data” also clears this mailbox and its read marker. There is no new permission or additional monitoring provider.

2.2 Friends, camp visits and shared salvage

Your linked friends can see your island name, current era, rescue count, building levels, number of workers and book finds, and the timestamp of the last cloud save. Camp visits additionally show only the counts and tiers of carried worker tools from your saved game, without worker names, tool origins or complete inventories. These views are accessible only to you and linked friends, not to the public.

For shared salvage, we store at Supabase in Frankfurt the camp account’s pseudonymous ID, a fixed project key, the persistent solo salvage counter, the last counted bags and the island restart count as baselines to prevent double counting, the reached salvage stage, and up to five permanently occupied contribution slots per stage. For each slot we store the contributing friend’s pseudonymous ID, a bounded contribution counter and the day of their latest contribution. For the help limit we also store the number of issued help chests and incoming helps at the target camp per account and UTC day, without helper IDs in the daily counter. Purpose: showing the same project progress to all authorised friends, counting voluntary contributions only once and allowing at most five help chests per account daily and five incoming helps per target camp (Art. 6(1)(b) GDPR). Friends see the stage, total progress and up to five anonymous contribution badges with help counts; their own badge is marked. Other contributors’ IDs and precise contribution times stay hidden.

Project progress and contribution slots remain until the respective camp account is deleted. Daily help quotas cover the current and preceding 13 UTC days as a short reconciliation period against duplicate or delayed payouts; older quotas are removed on the next authorised help call involving that account. Without further help calls, they remain until account deletion. Deleting a helper account does not reset another camp’s incoming counter; deleting the target camp also deletes its daily quotas. Deleting a camp account deletes its project and contribution slots. Deleting a contributor’s account removes its ID from other camps’ contribution slots; their earned parts and occupied slots remain without an account association. This preserves other players’ progress. On your device we additionally store the remembered solo progress with bag/restart baselines, latest loaded shared counter values and daily help counter per account until you clear local storage or choose “Delete all my data” (§ 25(2) TDDDG, Art. 6(1)(b) GDPR).

The sharing card for a legendary find is generated exclusively on your device from its name, rarity, game artwork and story. It contains no island name, account or device ID, or invitation code. We do not upload the image to our servers. Only after previewing it do you decide whether to save it locally or share it through a service of your choice; that service’s rules apply to the transfer and retention period. The game preview is discarded when closed. To share in the Android/iOS app we additionally create a temporary PNG copy in the internal app cache (up to ten files, up to 3 MB each); copies older than 24 hours are removed on the next app start or share. The operating system may clear the cache earlier. A file you save remains until you delete it.

2.3 Reviews in the Android app

Reviews in the Android app: After at least two full days since your island was created and a gameplay milestone (era 2 or twelve opened bags), we may call Google Play’s review feature. The request does not depend on positive feedback sentiment. We do not request a review during a video or for ten minutes afterwards; after feedback we wait 90 days. Locally we store only version and timing receipts for review attempts and video/feedback interruptions (wl.play-review), until app data is deleted. These limit attempts to at most once per version and at least 90 days apart (Art. 6(1)(f) GDPR: our legitimate interest in preventing repeated requests; storage under § 25(2) no. 2 TDDDG because this is necessary to prevent repeated requests). Only with statistics consent do we count review.requested in Supabase (13 months): it records only the attempted call, not whether a dialog appeared or a review was submitted. Google gives us no result. Google processes a voluntarily submitted review under its privacy policy; it may appear publicly on the Play Store and can be deleted through your Google account.

3. Hosting

The website is delivered by Cloudflare Pages (Cloudflare, Inc., USA); individual previews may use Vercel Inc. (USA). When you open it, the respective hosting provider processes technically necessary connection data such as your IP address to deliver the page (Art. 6(1)(f) GDPR). Cloudflare and Vercel are certified under the EU-US Data Privacy Framework (Cloudflare details). The database and server functions run at Supabase Inc. in the Frankfurt am Main data centre (AWS eu-central-1), i.e. inside the EU. Supabase technically processes the IP address in short-lived server logs; we do not store it.

Visitor analytics at the host: Cloudflare Web Analytics is currently disabled; the production version does not load a Cloudflare analytics beacon. Vercel Web Analytics and Speed Insights are not loaded on our test devices and previews or in the app. Our own anonymous game counters are described in section 2.

Fonts and images are loaded from our own server, not from Google or other third parties.

External links (e.g. to PixelPicked) connect to the respective provider only when clicked; that provider’s privacy policy then applies.

4. Your rights

You have the right to access, rectification, erasure, restriction, data portability and objection, and you can withdraw any consent at any time. The fastest way is inside the game via the gear (⚙️ Settings) at the top of your island: switch off statistics or, at the very bottom, choose “Delete all my data”. This deletes your account and all related data on the server, as well as the save on this device. If you no longer have the game or the app, you can request deletion by e-mail: How to delete your account. You can also complain to a data protection supervisory authority.

5. Children and teens

Wrecklanders is not directed at children under 13 years of age.

6. Processors

Supabase, Cloudflare and Vercel process data on our behalf, based on their standard data processing agreements under Art. 28 GDPR. Google (ads in the app, Google Play) is not a processor but responsible for its own processing (see section 8).

7. Changes

If new features are added (for example ads in the web version or purchases), we will update this policy beforehand and ask for your consent where required.

8. App version (Android and iOS)

Applies to the Android and iOS app

The Android and iOS apps contain the same game with the same pseudonymous account (random ID, without name, e-mail or password). Everything in sections 1 to 7 applies there too. The game files are part of the app and are not loaded from web hosting. In addition, the app works like this:

8.1 Optional ad videos (Google AdMob)

Optional rewarded videos are intended for Android and the iOS Store version. They start only at your request and after the required consent; availability and configuration fixed in the app release may limit the offer. Personal test builds use Google test ads.

The app can show short ad videos, but only when you tap a video button yourself. Before every video it says what you get for it (for example a longer tailwind). Without a video you keep playing normally. There are no banners, no ads in between and no ads that start by themselves; at most 10 videos a day. The videos are delivered by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, via the Google Mobile Ads SDK (AdMob).

DataWherePurpose / legal basisHow long
IP address (Google may infer an approximate location), device and app details (e.g. model, OS version, language, app version), ad interactions (loaded, watched, tapped), crash and performance data. Android: also advertising ID and app set ID according to Google configuration. iOS: SDK data and app-related identifiers may be processed even for non-personalised ads; IDFA only with the corresponding ATT permission for advertising measurement (details below)Google (Ireland; transfer to Google LLC in the USA possible, which is certified under the EU-US Data Privacy Framework)Delivering the video, confirming the reward, measuring ads, preventing fraud. Access to your device and personalised ads only with your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). Google is an independent controller for this (Google Ads Controller-Controller Data Protection Terms)According to Google's rules: Privacy Policy, How Google uses information from partners' apps
Your consent choice (TCF string)Stored on your device, in the app's storage; sent to Google with every ad requestRemembering your choice and telling Google what is allowed (Art. 6(1)(c) with Art. 7(1) GDPR)Until you change it or uninstall the app
How many videos you watched today (counter for the daily limits)In your save: on your device and as a backup at SupabaseSo the daily limits apply (Art. 6(1)(b) GDPR)Like your save

Consent: On the first tap on a video offer, the app uses Google’s User Messaging Platform (UMP, based on the IAB TCF standard) to check whether consent is required and shows Google’s consent dialog when needed. Only then can a video be loaded. If you agree on Android, Google may tailor ads within the permitted scope. iOS requests only non-personalised ads; UMP first checks whether an ad request is permitted even for these. If you decline, non-personalised or limited ads may be available depending on Google’s permission to request ads. The game keeps working; videos may be limited depending on availability. The maximum ad content rating remains “General” (G).

Withdrawing consent: You can change your choice at any time in the app under ⚙️ Settings → Ads → “Privacy options”. You can also reset or delete the advertising ID in your Android settings (usually under “Privacy” or “Google → Ads”, depending on the device).

What we get from Google: only summary reports (e.g. how many videos were shown in total and what they earned), nothing about individual players. We also count offers (button visible for at least one second), starts, completions, cancellations, errors and unavailable videos for each video moment as anonymous daily totals, split by app/web and app version. These counters contain no account, user, device or advertising ID, no IP address and no game progress or age. Only “+1” with fixed categories is sent; nothing is stored on your device for these totals. Like our start-page counters, they do not require statistics consent; retention: 13 months. Statistics consent and Google’s advertising consent remain separate.

iOS and tracking: On the first voluntary video request, Google UMP first checks whether an ad request is permitted. iOS may then ask for App Tracking Transparency (ATT) permission to use the advertising identifier IDFA so Google can measure ads and their effectiveness across providers. This is a separate choice: UMP permission to request ads does not mean consent to every purpose, and ATT does not replace Google consent. IDFA may be used only with the corresponding permission; when denied or restricted, the SDK does not use IDFA and we create no replacement identifier. You can keep playing without tracking. Where Google permits it, non-personalised or limited ads without IDFA may be available. Change ATT under iOS → Privacy & Security → Tracking and your Google choice through Privacy options in the app. Before SDK startup we disable Google’s Publisher first-party ID and personalised ads through Publisher Privacy Treatment; every iOS request stays non-personalised even if you allow ATT. Google may still process IP addresses, app-related technical identifiers, ad interactions, crash and performance data for delivery, advertising measurement and fraud prevention. SKAdNetwork may attribute installations without IDFA. Our own account identifiers and gameplay statistics are not sent to Google. Details: Google’s iOS data disclosure. Statistics consent remains independent.

8.2 Notifications

The app reminds you with local notifications (e.g. “Expedition is back”). The app schedules them directly on your device. There is no push server and no push address for this; the push details in section 2 only concern the web version. On iOS and from Android 13 the device asks for your permission first (Art. 6(1)(a) GDPR). You can turn them off any time in the app’s system settings.

The web app suggestion remembers only locally whether you chose “Later” (at most twice, three days apart) or the store button (wl.store-card), until you clear website data. This prevents repeated suggestions. Only with statistics consent do we count store_cta: shown, store click or later and target platform Android/iOS. The existing account association and 13-month retention for game actions apply; this does not confirm an installation.

8.3 App stores (Google Play and Apple)

You get the app via Google Play. Google itself is responsible for downloads, updates and reviews (Google Privacy Policy). In the Play Console we only see summary numbers (e.g. installs) and, if you allowed sharing diagnostics in Android, crash reports without name or account.

The iOS Store version is distributed through the Apple App Store. Apple is responsible for downloads, updates, store transactions and diagnostics voluntarily shared with Apple (Apple Privacy Policy). We receive aggregate usage and installation reports in App Store Connect to the extent Apple provides them; these do not replace our consent-based gameplay statistics. The app currently offers no In-App Purchases.

8.4 Deleting your account

In the app: ⚙️ Settings → “Delete all my data”. Without the app: request deletion by e-mail. Data that Google processes for ads is managed at Google (reset the advertising ID, My Ad Center).

Legal notice · Delete account · ← Back to the game