Privacy Policy
What Stackadoo keeps on your phone, what it sends to others, and what you can do about it.
The short version
- Stackadoo has no accounts of its own and no server of its own. Your progress, coins and settings are kept on your phone. If you use Google Play Games, a backup of your progress is also kept there (see Google Play Games).
- The game is free and supported by ads (Google AdMob). Where the law requires it, Google's consent form asks you before ads are requested.
- Google's Firebase gives me crash reports, usage statistics and remote settings. Google Signals may link usage to your Google account if your Google account settings allow it and, where Google's consent form or a US opt-out applies, your choice there allows it. Adapty handles purchase records. Both are explained below.
- I do not sell your data for money. Ads served by Google may count as "selling" or "sharing" for advertising under some US state laws. You can opt out (see Your rights).
- Notifications are off until you switch them on in Settings ▸ Notifications. A Daily reminder is scheduled on your phone; news messages use Google's Firebase Cloud Messaging (see Notifications).
- The game never asks for your location. Google (ads, analytics) and Adapty still work out an approximate location, at country or region level, from your IP address.
- The game never asks for your name, e-mail or contacts. But if you use Send feedback or write to me, I receive your e-mail address and what you write, and keep it for 12 months after the matter is closed (see When you e-mail me). The game makes a random Support ID on your phone so I can find your data if you ask me to delete it: see Your Support ID.
- You can object to crash reports, remote settings and the Shop note: see Your right to object.
Who is responsible
Stackadoo is made and published by Mohammad Khakpaki, an independent developer. This is not a company. For the data described in this policy, I am the one responsible for it (the "controller" in data-protection law) and the person you can write to:
E-mail: mkhakpaki.ksas@gmail.com
Google and Adapty also handle some of the data below, and for ads, other advertising companies working through Google may too (see Advertising). Each has its own privacy policy, linked in the relevant section.
Data that stays on your phone
The game keeps its own data in a settings file on your phone. Almost none of it is sent anywhere by the game itself. The exception is the Support ID (see Your Support ID). It includes:
- Settings: sound, music, haptics, reduced motion, language and similar choices.
- Progress: your best height, tutorial progress and event records.
- Wallet and inventory: coins, power-ups and skins you own or have equipped.
- Daily Tower and streaks: the day you last played, attempts, bests and streak counts. These use your phone's clock.
- Purchase records: which purchases you have made (for example the No Ads Pass), so the game never grants the same purchase twice.
- Support ID: a random code the game makes once, so I can find your data if you ask me to delete it.
- Rating state: how often the game has asked you to rate it, and when it last asked.
- Notification state: your on/off choice, how often the game has asked, the last three times of day you started the Daily tower, your phone's UTC offset and which reminder lines were shown last. This stays on your phone.
- Play Games link: if you use Google Play Games, your Play Games player ID, so the game knows whose save it holds, and marks of which scores and achievements Google has already confirmed.
- Privacy and ad state: a few values the game and Google's consent form store so they remember your choices.
Deleting the game removes this data (on Android you can also clear the game's data in the phone's settings). Your phone's own backup features, such as Android backup or iCloud backup, may copy app data depending on your phone's settings. That is controlled by your phone, not by the game. A cloud save in Google Play Games is a separate copy that deleting the game does not remove (see Google Play Games).
The game stores no name, e-mail address or account, because it has none.
What is stored on or read from your device
The game and its services keep small items on your phone and read some device details: the settings file described above, Google's consent values, Firebase's random installation and app-instance identifiers, your Support ID, Adapty's profile ID, the advertising ID where allowed, and, if you switch on news notifications, a push token. Where the law requires consent for ads and analytics (EEA and UK), I ask through Google's consent form.
Crash reporting and purchase handling run without asking, because they are needed to keep the game stable and to deliver what you buy. Once the game has started Google's ads software (only after Google's consent tool says the game may request ads), it can also send Google error reports, as described under Advertising. Remote settings also run without asking and use the Firebase installation identifier; you can object to this by e-mail (see Your rights).
Your Support ID
The game makes a random 8-character code once on your phone, using a secure random generator. It is not made from your device, an account or your advertising ID. It looks like XXXX-XXXX and uses digits 2 to 9 and capital letters A to Z, leaving out I and O, so it never contains 0, 1, I or O and nothing is misread.
You can find it in Settings ▸ Help & legal ▸ Support ID, the last row. Tap it to copy it.
The game uses it in four places:
- as your customer ID at Adapty;
- as the user ID in Firebase Analytics, only while your analytics consent setting is granted (and removed if you decline);
- as the user ID on Crashlytics crash reports;
- in the e-mail draft that Send feedback opens (see When you e-mail me).
It contains no name or e-mail. It is attached to crash reports (always on) and, where analytics is allowed for you, to analytics. I use it to match purchases and restores, to match a support e-mail or a deletion request to your data, and to find crash and usage data you ask me to delete. Quote it when you ask (see Your rights).
The code is pseudonymous personal data: it names no one, but I can use it to link records. It is not a password. Deleting the game or clearing its data makes a new code the next time you play. On Android, your phone's backup may restore the old one.
Firebase (Google)
Stackadoo uses three Firebase services from Google. See Google's Privacy and Security in Firebase page for how Firebase handles data.
At launch, before any consent form, Firebase's start-up (which registers the installation ID), Remote Config and Crashlytics contact Google to fetch game settings, such as the ad configuration, and to send crash reports. Google's consent tool also contacts Google to check which rules apply to you. This sends the Firebase installation ID, your IP address and the details listed under Crashlytics and Remote Config below.
On Android, the Google Play Games library that is part of the game also contacts Google Play services at launch, whether or not you have signed in to Play Games (see Google Play Games). What that library sends is Google Play services' own behaviour, under Google's privacy policy. Adapty also starts at launch (see Purchases).
Analytics
Firebase Analytics tells me how the game is used, such as sessions, screens, and in-game events. It uses an app-instance identifier (a random number for your installation, not your name) and device and app details such as device model, OS version, app version and an approximate location based on IP address.
Analytics works with Google's consent mode. Before the game knows your consent decision, all of Google's consent settings for analytics and advertising storage are set to denied. The rules after that depend on where you are:
- EEA and UK (and Switzerland, where Google's tool treats it the same way): the settings stay denied unless your answer in Google's consent form switches them on. Whether your answer can switch analytics on depends on how Google's form is configured for the game, so declining always keeps analytics storage off, and consenting may not by itself turn it on.
- US states with opt-out laws: the settings are on unless you have opted out. If you opt out, the advertising settings go to denied. Where I cannot read your choice reliably, it is treated as an opt-out for advertising.
- Elsewhere: there is no consent form, and the settings are on.
While a setting is denied, Google's tools may still receive limited pings that Google uses for aggregate counts and modelling. Google describes these as not carrying advertising identifiers or cookies. I cannot promise that no technical identifier of any kind is involved.
In the EEA and UK (and Switzerland, where Google's tool treats it the same way), analytics does not start until you have answered the consent form; once you have answered, these limited pings can be sent even if you declined. Elsewhere, analytics starts once Google's consent tool has told the game which rules apply to you, with the settings described above.
Before analytics starts, the game holds a short list of in-game actions, for example screens opened, at most 200, in its memory only. It is never stored, and it is discarded if the game closes before analytics may start. Once analytics starts, the list is sent with the consent that applies to you: normal events where your settings are on, limited events where they are denied (for example after you decline).
In the EEA and UK, no analytics events are sent before you answer, apart from the brief case in the next paragraph. Elsewhere, once Google's consent tool has told the game where you are, analytics starts, usually within seconds, and the list is sent with the consent that applies to you. If the tool has not answered after about 30 seconds, nothing is sent until it does.
At launch, and for as long as Google's consent tool cannot answer (for example when you are offline), analytics may follow your previous answer until the tool re-checks it, for example after you travel or when your consent has expired.
Analytics also receives your Support ID as its user ID (see Your Support ID).
The game sets it on Analytics only where Analytics storage is allowed for you. In the EEA, UK and Switzerland that means you accepted in Google's consent form; if you decline, it is not set, and it is removed if you decline later. Elsewhere there is no form and it is set by default; a US opt-out of ad personalisation leaves analytics storage allowed, so it stays.
If Google's consent tool cannot answer during a launch (for example when you are offline), the game may keep what it did on your last launch, so analytics events and the Support ID can carry on until the tool answers or you change your answer in Settings ▸ Privacy choices. It is a random code, not your name.
Analytics collects some events automatically, such as first open, session start, app updates and screen views. If you buy something, or see or tap an ad, it may record that too.
The game also records what you do in it: runs and results, heights, power-ups, coins earned and spent, the Shop, the Daily Tower and tutorial steps, settings changes, purchase outcomes, consent outcomes, and ad events (an ad shown or tapped, how long a banner was on screen before a tap, and the ad revenue Google reports for each ad shown). The set may grow.
Analytics also keeps a few properties about your installation: your game language, whether you own the No Ads Pass, a banded best height, tutorial progress, and your notification state. The game sends them again at each launch, also after a decline; Google says it does not keep them while analytics storage is denied.
Google Signals and data sharing
I have turned on Google Signals in Google Analytics. If you are signed in to a Google account on your device and have ad personalisation turned on in that account, Google can connect the game's analytics data with your Google account. This turns on Google Analytics' advertising features: cross-device reporting, demographics and interests reporting (aggregated age ranges and interests), and the building of ad audiences (remarketing) for Google's advertising. To provide them, Google Analytics uses the game's own app-instance identifier together with Google's advertising identifiers, such as your device's advertising ID where allowed.
I only see aggregated reports, never your Google account.
I have also turned on Google Analytics' data sharing settings. These let Google use the game's analytics data to improve its own products and services, for modelling and benchmarking, for technical support, and for the other purposes listed in those settings. For data used under these settings, Google acts as a separate controller under its own terms, not only on my behalf.
Both follow the consent rules above: where your answer in Google's consent form, or your US opt-out, keeps the advertising settings denied, analytics data is not used for ad personalisation. Google says it applies these consent settings to its advertising features; I rely on Google for that. After a US opt-out, usage statistics continue, and Google Analytics data sharing is not switched off by the opt-out. The same applies to the limited pings described above after you decline in the EEA or UK: they can be part of the analytics data that the data-sharing settings cover.
How to opt out of these advertising features: turn off ad personalisation in Google's Ads Settings for your account at myadcenter.google.com; reset or delete your advertising ID in your phone's ad settings (Android: Settings ▸ Privacy ▸ Ads); change your answer in Settings ▸ Privacy choices where it is shown; or on iPhone turn off the game's permission to track you. See how Google uses data from apps that use its services.
Crashlytics
When the game crashes, Crashlytics sends a report with the stack trace (what the code was doing), your device model and OS version, app version, and the Crashlytics and Firebase installation identifiers. It also receives your Support ID as the user ID on the report, so I can find your reports if you ask me to delete them. Like the reports themselves, this does not depend on your consent choice.
Crashlytics can also send a small record each time the game starts (with the installation identifier, app version and device details), so I can see how many sessions run without a crash. I use it to find and fix bugs. Crash reporting is always on and does not depend on your consent choice. Crashlytics keeps crash data for 90 days.
Remote Config
Remote Config lets me adjust game settings, for example how often ads appear, without releasing an update. At launch the game asks Firebase for the latest settings. That request carries the Firebase installation identifier and basic details Firebase uses to pick the right settings: your country, language, time zone and OS version, and the app's identity. The game adds no values of its own. This is also always on and does not depend on your consent choice.
The Firebase installation identifier is a random per-install number used by Crashlytics and Remote Config. The game does not show it to you.
Advertising (Google AdMob)
The game shows ads from Google AdMob. They are what keep it free. There are three kinds:
- Banners in a strip at the bottom of some screens.
- Full-screen ads at a few natural breaks, such as when you play again or restart.
- Rewarded videos, which are always optional. You choose to watch one in return for something in the game, such as a revive or extra coins.
To show and measure ads, Google's ads software collects standard ad data: your advertising ID and other device identifiers where allowed, your IP address (which can show your approximate location), device and app details, app launches and taps, performance data such as how quickly the game starts, and the ads you see and how you interact with them. Google receives this data.
Other advertising companies that buy, show or measure ads through Google, such as ad networks and ad-measurement companies, may also receive it, or collect it themselves when they serve an ad in the game. Where Google's European consent form is shown, it lists these companies and lets you choose. Google's page on how it uses data from apps that use its services explains more. The game itself adds nothing about you, such as your progress or purchases, to ad requests.
Crash logs and diagnostics from the ads software. The game starts Google's ads software only after Google's consent tool says the game may request ads. Where consent is required, it is not started before you have answered. Once it is running, it also sends Google crash and diagnostic reports about errors in the game: the error's type, message and stack trace, the device model, operating system, the Unity version, the game's app ID, a random session ID, your country and your network type. It collects the errors the game hits and sends them to Google in batches; on Android this is about every two minutes while you play, or sooner if several build up. This happens wherever the game is allowed to request ads, including in US states after you opt out of the sale or sharing of your data, because these reports are error diagnostics, not advertising data.
If you withdraw your consent in Settings ▸ Privacy choices and Google's tool then no longer allows ads, the ads software is not started from the next time you open the game; it cannot be stopped in the middle of a session. If Google's tool allows ads even after you decline (for example limited ads), the ads software and its error reports may still run. Google handles these reports under its own policies (link above). This is separate from the game's own crash reports through Firebase Crashlytics.
Google's consent form
The game uses Google's consent tool (the User Messaging Platform) so you can choose how your data is used for ads.
- EEA and UK (and Switzerland, where Google's tool treats it the same way): a GDPR consent message appears where Google requires one. Ads load only once Google says the game may request them.
- US states with opt-out laws: a message lets you opt out of the sale or sharing of your data and of targeted advertising.
- Settings ▸ Privacy choices: this row appears in the game's Settings only where the law requires it. It reopens the form so you can change your answer at any time.
- iPhone and iPad: the game tracks you across other companies' apps and websites only if you allow it in Apple's App Tracking Transparency prompt. If you decline, or have not answered, Apple does not give the game your advertising identifier.
If you decline, Google decides what kind of ads, if any, can be shown. The game does not show ads when Google's tool says it may not request them. Declining never blocks the game itself.
The No Ads Pass
The No Ads Pass removes banners and full-screen ads. Rewarded videos stay, because you choose them and they give you something. See Purchases.
You can also reset or delete your advertising ID on your phone (Android: Settings ▸ Privacy ▸ Ads; iPhone: Settings ▸ Privacy & Security ▸ Tracking). More in Delete your data.
Purchases (Adapty)
Stackadoo is free to play. You can optionally buy coin packs, power-up packs, a starter bundle and the No Ads Pass.
- Payment is handled by Google Play or the App Store. I never see or store your card or payment details, and neither does Adapty.
- To deliver and check purchases, and to see in aggregate how the Shop is used, the game uses Adapty. Adapty starts when the game starts, not after the consent form, so this happens whether or not you have answered it, and also if you decline. It receives your Support ID as your customer ID, an Adapty profile ID, your purchase history, your store country, a note when you open the Shop, and standard technical data such as IP address, device model, OS and language.
- The game asks Adapty not to use the advertising ID. On Android, Adapty may still receive it where your phone allows it. I do not use it for advertising.
- Adapty acts on my behalf. I decide why the data is used, and I use it to deliver and restore purchases, not for advertising.
- Restore brings back the No Ads Pass and the starter bundle's unlock, not coins. Coins and power-ups that you have used are gone.
- Refunds go through Google Play or Apple, under their rules.
Sharing your tower picture
When you tap Share, the game makes a picture of your tower (its height, landmark and zone) and hands it to your phone's share sheet. It is created only when you tap, and it goes only where you choose to send it. After that, the app you shared it with handles it under its own policy.
Rating prompts
At quiet moments, such as after a new best, the game may ask you to rate it. This uses Google Play's in-app review card on Android and Apple's review prompt on iPhone. The store shows and handles the card. The game gets no answer and does not know whether you wrote a review.
On Android the game may show its own one-to-five star sheet instead. The star score is recorded as a usage event in Firebase Analytics, like other game events, and only where analytics is allowed. It is not tied to any store review. A low score offers Send feedback (see When you e-mail me), and a higher one opens the game's store page.
Google Play Games: leaderboards, achievements and cloud save
On Android, the game uses Google Play Games. When the game starts, it asks Play Games to sign you in quietly. That works only if you already have a Play Games profile on your phone, and nothing is shown. If you are signed out, tapping Settings ▸ Leaderboards or Settings ▸ Achievements in the game asks you to sign in, and Google may show its own screen. If that fails or you decline, the game says so and plays on.
What the game sends
- Leaderboards: your best Endless height and your Daily Tower height. Scores made offline are sent later. A Daily score is not sent if your phone's clock is far from Google's time. Your score appears on the leaderboard to other players, with the public name and picture from your Play Games profile, subject to that profile's visibility settings.
- Achievements: the achievements you unlock and your progress towards them.
- Cloud save: one Play Games Saved Games file, up to 3 MB, holding your progress and best height, coins, power-up counts, skins you own, Daily and streak records, tutorial flags, achievement progress, the ids of purchases already credited, counts of purchases and a random install ID. It holds no settings, name, e-mail or payment details.
If two phones hold different saves, the game merges them rather than throwing one away. It cannot promise the merge is perfect.
Your player ID and name
The game reads your Play Games player ID and keeps it on your phone to link the save to you. It does not read your public name. Google's own leaderboard screens show names. I do not receive your player ID or name, and the game does not send them to Analytics, Adapty or advertisers. If a different account signs in on the same phone, the earlier player's save stays on the phone as a backup and is never sent.
Google's part, clock check and analytics
Google runs Play Games under its own terms and privacy policy. For the scores, achievements and save it stores for the game, it acts as my service provider; for your Play Games account and profile, it acts under its own terms. Because you start the sign-in, the transfer is at your request.
To keep Daily scores honest, the game may ask the same Google server as Remote Config for the time when Play Games is available and leaderboards or cloud save are on. That request carries no ids, only your IP address and standard request data. If you allowed analytics, the game also records that a sign-in, score, achievement or cloud sync happened, without your player ID (these records do carry the height or the achievement's name).
Signing out, legal basis and retention
The game has no sign-out button. Sign out, or delete your Play Games data, in the Play Games app (see Delete your data). My basis for these features is contract (Art. 6(1)(b)), because they are features you use. For the quiet sign-in at launch it is my legitimate interest in offering them; you can object by e-mail or by signing out. Google keeps this data until you delete it. I do not hold it.
Notifications
Notifications are available on Android only for now. They are opt-in. Nothing is asked at install or first launch, and there is no push token until you switch them on. The game asks at a good moment after a Daily goal or a streak reward, or when you flip Settings ▸ Notifications. It asks first with its own card and then with your phone's permission dialog (Android 13 and newer).
Daily reminder
The reminder is scheduled on your phone and nothing is sent through any server. It appears at most once a day, never between 22:00 and 08:59 local time, and only when today's Daily tower is waiting. To choose the time, your phone keeps, on the phone only, the last three times of day you started the Daily, your UTC offset, which reminder lines were shown last, and your on/off choice.
News messages (Firebase Cloud Messaging)
News messages start only when you have switched notifications on, your phone allows them, and you have answered Google's consent form. Any answer counts: this is not tied to your ads or analytics choice. Firebase then creates a push token for your installation, using the Firebase installation ID. The game subscribes it to the topic announcements and to a topic for your game language, such as lang_en.
Google processes the token for me to deliver the messages. I send them to those topics from the Firebase console. The game sends the token nowhere else. Notifications never give rewards.
Notification analytics
If you allowed analytics, the game records events such as the notification card shown and answered, the permission result, a reminder scheduled or opened, a news message opened, and topics subscribed or unsubscribed. It also sets a user property for your notification state. If you did not allow analytics, they are sent at most as the limited events described under Firebase, or not at all where analytics has not started. See Firebase.
Turning notifications off
Switch off Settings ▸ Notifications in the game. That cancels the pending reminders, unsubscribes the topics and deletes the push token. You can also turn notifications off in your phone's settings. That stops them being shown, and the game notices when you return and stops scheduling reminders.
My legal basis for news messages is your consent (Art. 6(1)(a)): switching them on and allowing them on your phone. The switch is how you withdraw it. The game has no separate "delete my data" button for notifications. See Delete your data.
When you e-mail me
If you use Send feedback or write to me, I receive your e-mail address and what you write, and anything you attach, such as an order number. I keep it for 12 months after the matter is closed. I use it only to answer you, fix problems and handle privacy requests (contract, legitimate interests, and legal obligation for rights requests). My e-mail is provided by Google (Gmail), which stores it on its systems under its own terms and privacy policy.
Send feedback. Settings ▸ Help & legal ▸ Send feedback, and the low-score button on the game's rating sheet, open your own mail app with a draft addressed to me. The draft has four lines: your Support ID, the app version, your device model and the game language. The rating sheet also puts your star score in the subject.
You can edit or delete any of it before you send. The game itself sends nothing: only your mail app does, and only if you send the message.
Permissions
| Permission (Android) | Why |
|---|---|
| Internet and network state | Ads, purchases, Firebase and checking whether you are online. |
| Advertising ID | Lets Google AdMob show and measure ads where allowed. On Android, Adapty may also receive it (see Purchases). You can reset or delete it any time in your phone's settings. |
| Billing (Google Play) | Lets the game start purchases through Google Play. Google Play takes the payment, and I never see your payment details. |
| Vibration | Haptic feedback, if you leave it on. |
| Notifications (Android 13 and newer) | Lets the game show its Daily reminder and news messages, if you allow them. |
| Receive boot completed | Lets the game set its Daily reminder again after your phone restarts. |
The game asks for no camera, microphone or contacts access, and it never asks for your location. It does not read your GPS. When the game goes online, though, Google (ads, analytics, Remote Config) and Adapty receive your IP address and derive an approximate location from it, at country or region level.
Some further technical permissions, such as keeping the device awake or running background work, are added automatically by the Google and Adapty software the game uses, including permissions for Android's ad services (attribution and topics), which Google's ads software can use where your phone allows it. On iPhone, the only prompt is Apple's App Tracking Transparency one described above; the game has no notifications on iPhone yet. The game uses no exact-alarm permission.
What I never do
- I never sell your data for money. Advertising through Google is described above and can be opted out of.
- The game never asks for access to your contacts, photos, files, messages or precise location. Google and Adapty do derive an approximate location from your IP address (see Permissions).
- The game never asks for your name, e-mail or an account of its own. Google Play Games, if you use it, is Google's account, not mine. If you use Send feedback or write to me, I do receive your e-mail address and message (see When you e-mail me).
- I never build profiles of you myself. The only analysis is the usage statistics and crash reports described above, and whatever Google does within its ad services under its own policies.
- I never see your payment details.
Because ads, analytics and purchases involve Google and Adapty, I cannot honestly say "no personal data is collected". Identifiers, IP addresses, crash data and purchase history do reach them, as described above. The game never asks for your name, e-mail or contacts. If you write to me, I see your e-mail address (see When you e-mail me).
How your data is protected
The game has no server of its own. Apart from your phone (and any backup your phone makes) and any e-mail you send me, your data is held only by Google, Adapty, the advertising companies working through Google, and the app stores.
- On your phone: the game keeps its data in its own app storage, which your phone's operating system keeps separate from other apps. The game does not add its own encryption to this file.
- On the way: Google (Firebase and AdMob) and Adapty state that the data their software sends is encrypted in transit (HTTPS/TLS).
- At Google and Adapty: they store and protect the data under their own security measures and terms, linked above. Adapty acts under a data-processing agreement with me.
- If something goes wrong: if I learn of a security problem affecting your data, I will act on it, and tell the people affected and the authorities where the law requires.
Why I am allowed to use your data (GDPR)
If you are in the EEA or UK, the law requires a legal basis for each use of your data. Mine are:
- Contract (Art. 6(1)(b)): the on-phone data, and Adapty's delivery, checking and restoring of your purchases, including the Support ID as its customer ID.
- Consent (Art. 6(1)(a)): personalised ads, ad measurement, analytics storage (including the Support ID as the Analytics user ID), Google Signals and Google Analytics data sharing, where Google's consent form asks you. You can withdraw it at any time (see Changing or withdrawing your choices).
- Consent for notifications (Art. 6(1)(a)): the push token and topics for news messages, when you switch notifications on and allow them. Switching them off withdraws it (see Notifications).
- Legitimate interests (Art. 6(1)(f)): (a) crash reports: my interest in finding and fixing crashes so the game stays stable and secure; (b) remote settings: my interest in adjusting game and ad settings, such as how often ads appear, without an update, so the game can stay free and balanced; (c) the Support ID on crash reports, and in support and rights requests, so I can match your reports, purchases and e-mails and answer you; (d) the note Adapty gets when you open the Shop, and the limited, aggregate pings Google's analytics can still receive after you decline: my interest in knowing, in aggregate, how the game and its Shop are used. The data is small and technical, includes no names, and I do not build profiles from it. I also use the law's requirement to answer rights requests (Art. 6(1)(c)) when I handle them. You can object (see Your rights).
- Outside the EEA and UK, where no consent form is shown because the law there does not require one, analytics, Google Signals and ad settings are on. I rely on my legitimate interest in understanding how the game is used and in showing the ads that keep it free. You can limit this by resetting your advertising ID, turning off tracking on iPhone, or writing to me.
Google, and the advertising companies that work through it, decide for themselves how they use ad data, and Google decides how it uses the error reports from its ads software, under their own policies and legal bases.
You do not have to give me any data to play. Crash reports, remote settings and purchase handling are sent automatically; the only way to stop them is not to play.
Transfers outside your country
Google and Adapty process data on their own systems and those of their sub-processors, in the United States and in other countries where they operate. Where the GDPR or UK GDPR applies, such transfers rely on a safeguard such as an adequacy decision (for example the EU-US Data Privacy Framework, for certified companies), the EU standard contractual clauses or the UK addendum. You can ask me how to get details of the safeguards used by e-mailing mkhakpaki.ksas@gmail.com.
Adapty processes data for me under a data-processing agreement. For Firebase, Google generally processes data on my behalf under its data-processing terms; for ads, Google Signals and Google Analytics data sharing, Google uses data under its own terms. Adapty, and Google for its services, provide the same or equal protection of your data as this policy describes and as Apple's and Google Play's rules require. Advertising companies working through Google are bound by Google's policies and, where Google's consent form is shown, by your choices there. See their policies: Firebase, Google advertising and Adapty.
How long data is kept
- On your phone: until you delete the game or clear its data.
- Support ID: on your phone until you delete the game or clear its data (Android's backup may restore it). Records that carry it are kept as set out in the entries below for each service.
- Play Games data (scores, achievements, cloud save): kept by Google until you delete it. Your player ID stays on your phone until you delete the game or clear its data.
- Push token: kept by Google until you switch notifications off in the game, which deletes it. If you uninstall the game without switching off, Google removes the token on its own schedule. Reminder times stay on your phone until you delete the game or clear its data.
- Remote settings on your phone: Firebase keeps the last settings it fetched in a cache on the phone and manages it itself.
- Crash reports: Crashlytics keeps them for 90 days. Temporary crash dump files may also sit on the phone until they are sent or the game is deleted.
- Firebase Analytics: data linked to your installation's identifier is kept for 14 months after the last time you play, then deleted automatically. Age, gender and interest data from Google Signals is kept for 2 months. Totals that identify no one, such as daily counts in reports, are kept longer.
- Google Signals data linked to your Google account: kept by Google under its own policies.
- Firebase installation identifiers: Firebase keeps them until I ask Firebase to delete them, which I do not do routinely. After deletion, Google removes them from its systems within 180 days.
- Adapty: as long as needed to deliver and restore purchases, and as long as the law requires, for example for tax and accounting.
- Ad data and error reports from the ads software: kept by Google under its own policies.
- Google Play and Apple purchase records: kept by the stores under their policies.
- E-mails to me: 12 months after the matter is closed.
Your rights
If you are in the EEA or UK (GDPR and UK GDPR), you can ask to access, correct or delete your data, restrict or object to its use, and receive it in a portable form. Where I use your consent, you can withdraw it at any time, without affecting what happened before. You can also complain to your local data-protection authority. In the UK, that is the Information Commissioner's Office (ico.org.uk).
Your right to object. Where I rely on legitimate interests (crash reports, remote settings, the Support ID on crash reports, the note Adapty gets when you open the Shop, and the limited analytics pings after you decline; see Why I am allowed to use your data), you can object at any time, on grounds relating to your situation, by e-mailing mkhakpaki.ksas@gmail.com with "Objection" in the subject.
I will weigh your objection against my reasons and reply within one month. The game cannot switch these uses off for one person, so the sure way to stop them is to uninstall the game (see Changing or withdrawing your choices). Where you gave consent, you can withdraw it at any time in Settings ▸ Privacy choices.
I make no decisions about you by automated means that have legal or similarly significant effects. Google chooses which ads to show you, and may personalise them if you allow it.
If you live in a US state with a privacy law, you may have the right to know, access, correct and delete your data, and to opt out of its sale or sharing and of targeted advertising. You can opt out through Settings ▸ Privacy choices where it is shown. I do not discriminate against you for using these rights.
US state notice. The game collects the following, and discloses it to Google, and through Google to other advertising companies, for advertising and ad measurement (which some US state laws treat as "sale", "sharing" or targeted advertising): identifiers (advertising ID, app-instance ID, Support ID, IP address), app and ad activity and purchase events (including analytics data through Google Signals and Google Analytics data sharing), device information and approximate location derived from IP.
It discloses to service providers (Firebase, Adapty, and Google Play Games if you use it) for running the game: identifiers (including a push token, if you switch on news notifications), purchase history, crash and diagnostic data and, if you use Play Games, your scores, achievements and cloud save.
Google's ads software also sends error reports to Google (see Advertising). The game collects this information from you and your device, through the game and the Google and Adapty software in it. The game collects no sensitive personal information. I do not knowingly sell or share the personal data of anyone under 16.
To opt out, use Settings ▸ Privacy choices. Where your device sends an opt-out preference signal such as Global Privacy Control and Google's tool reads it, it is treated as an opt-out.
To check that a request is yours, I ask for your Support ID and, for a request to access or export your data, one more detail only you are likely to have, such as the store order number of a purchase. The code is not a password. You can use an authorised agent to make a request for you; I will ask the agent for your signed permission and may ask you to confirm the request with me directly.
If I refuse a request you may appeal by writing to mkhakpaki.ksas@gmail.com with "Appeal" in the subject; I answer within 45 days, and you may then contact your state attorney general. Retention periods are in How long data is kept.
To use any right, write to mkhakpaki.ksas@gmail.com and include your Support ID (Settings ▸ Help & legal ▸ Support ID). With it I can find the records linked to it at Adapty, in Firebase Analytics, in Crashlytics and in my mailbox. Without it I may not be able to identify you in that data, and the law lets me say so. I answer within one month. For what the code does not reach, see Delete your data.
Changing or withdrawing your choices
- Ads and analytics consent: open Settings ▸ Privacy choices where it is shown, and change your answer. If Google's tool then no longer allows ads, Google's ads software, including its error reports, is not started from the next time you open the game.
- Advertising ID: reset or delete it in your phone's settings, or on iPhone turn off tracking for the game.
- Google's ad settings: manage them at myadcenter.google.com.
- Notifications: switch off Settings ▸ Notifications in the game, or turn them off in your phone's settings.
- Crash reports and remote settings are always on. You can object by e-mail, or stop all of it by uninstalling the game.
Asking for deletion
Send me your Support ID (Settings ▸ Help & legal ▸ Support ID) with your request. The steps, and an honest account of what I can and cannot find, are on the Delete your data page.
This website
This site is a set of plain pages hosted on GitHub Pages. It sets no cookies, runs no analytics and loads nothing from other sites. Like any web host, GitHub may log technical data such as your IP address when it serves the pages. See the GitHub Privacy Statement.
Children
Stackadoo is for people aged 16 and over. It is not made for children, and it is not part of any "Families" or "Kids" programme in the app stores. The game does not ask for your age. I do not knowingly collect data from anyone under 16. If I learn that someone under 16 has used the game, I will delete what I can find and they should stop playing. A parent or guardian can write to me at mkhakpaki.ksas@gmail.com.
In the EEA, the age at which a person may consent to data processing themselves is between 13 and 16, depending on the country. Because Stackadoo is only for people aged 16 and over, it is not offered to anyone below that age in any EEA country. If you are under 16, please do not play.
Changes to this policy
When the game adds or removes a service that touches your data, I update this page and change the date at the top. Larger changes will also be mentioned in the game's release notes.
Contact
Mohammad Khakpaki · mkhakpaki.ksas@gmail.com