Legal

Privacy Policy

Last updated: 26 August 2026 · Applies to the Whaaack! Android app, the Amazfit watch edition, and to this website.
What changed on 26 August 2026: a second Whaaack! now runs on Amazfit watches under Zepp OS, sharing this account and this backend with the Android game. What it keeps on the watch, what it sends, and what it deliberately has no way to reach are set out at the end of section 2.
What changed on 16 August 2026: Google Play Games was added to the app — achievements, run statistics, and the option to create an account from your Play Games identity. That is section 4, and it also changed what section 2 and section 7 have to say.

The short version. You can play Whaaack! without an account, without giving us anything, and offline. If you want to appear on the leaderboard you give us a display name and your scores, plus either an email address or your Google Play Games identity — and you can erase all of it from inside the app at any time, permanently. Ads are shown by Google AdMob unless you buy the ad-free unlock, and you are asked for consent before any personalised ad loads. Separately, if your phone is signed in to Google Play Games, the app reports your runs and achievements to Google — see section 4 for what that involves and how to stop it.

1. Who is responsible (administrator danych)

The controller of your personal data — administrator danych osobowych within the meaning of the GDPR / RODO — is:

IDCT Bartosz Pacholek
Kaszubska 12/8C
70-403 Szczecin, Poland
NIP (EU VAT): PL7642542255

Contact for any privacy matter: the contact form.

We have not appointed a Data Protection Officer (inspektor ochrony danych); we are not required to. Requests go straight to the address above.

2. What we collect, why, and on what legal basis

Article 13 GDPR requires us to name a lawful basis for each purpose rather than a single blanket one, so here they are separately.

Two items in the table below do not come from you, and a different article governs them. Your Play Games player ID and gamer tag are not typed in or handed over by you: when you choose Continue with Play Games, our backend asks Google for them and Google answers — we never take them from the app, precisely so that nobody can claim to be somebody else. Article 14 GDPR is the information duty for data obtained that way, and this page is the notice it requires: the source is Google Play Games Services, which is not a publicly accessible source, the categories are exactly those two, and everything else on this page — purposes, legal bases, retention, your rights — applies to them as it does to the rest.

Data	Why	Legal basis	Kept for
Email address	To create and secure your account, confirm it, and let you reset a password.	Art. 6(1)(b) — performance of the contract you asked for.	Until you delete the account.
Display name	To identify you on the public leaderboard.	Art. 6(1)(b) — the leaderboard is the service requested.	Until you delete the account.
Scores (milliseconds survived, hits, top speed) and their timestamps	To rank ranked runs, all-time and weekly.	Art. 6(1)(b).	Until you delete the account.
Google account identifier and email, if you use Google Sign-In	To authenticate you without a separate password.	Art. 6(1)(b).	Until you delete the account.
Your Google Play Games player ID and gamer tag, if you create your account with Play Games	The player ID is what the account is: it is how signing in again on any device finds the same account, and we hold no password or usable address for it. The gamer tag becomes your starting display name on the leaderboard.	Art. 6(1)(b) — without it there is no account to perform anything against.	Until you delete the account.
Your Play Games gamer tag as Google supplied it	Kept with the account as the name we were given, separately from the public display name derived from it. Renaming yourself in Settings changes the public name, not this copy, and changing your tag at Google does not update it here. Ask us through the contact form if you want it corrected — that is the Art. 16 right to rectification.	Art. 6(1)(b). Obtained from Google, not from you — see above.	Until you delete the account.
A derived address of the form `pgs-<player ID>@pgs.whaaack.invalid`, for Play Games accounts	Our sign-in system requires every account to carry an address, so one is generated from the player ID. It is an internal label, not a mailbox: `.invalid` is a reserved domain that can never receive mail, so no message could ever arrive there — and the app never offers an email or password row for such an account, because there is neither to change.	Art. 6(1)(b).	Until you delete the account.
Run statistics and achievement unlocks sent to Google Play Games — time survived, fruit hit, fruit missed, top speed, whether the run was ranked, and your best run	To show your achievements and Game Stats on your Play Games profile. Sent whenever your phone is signed in to Play Games, for casual runs as well as ranked ones, and whether or not you have a Whaaack! account.	Art. 6(1)(f) — our legitimate interest in providing the achievements and profile stats the app offers. You can stop it entirely by signing out of Play Games; see section 4.	Held by Google on your Play Games profile, under their retention rules.
Which sign-in method the account uses (email, Google or Play Games)	To show the right controls — an account held by a provider has no password or address for us to offer to change — and to know how to authenticate you.	Art. 6(1)(b).	Until you delete the account.
Advertising ID and ad-related device signals	To show ads, and — only if you agree — to personalise them and measure them.	Art. 6(1)(a) — your consent, collected through Google's consent form wherever that form is required, which covers the EEA and the UK; there you can withdraw it at any time. Where the form is not required, no consent is collected and ads are served without it.	Per Google's own retention; see their policy linked below.
Technical request data (IP address, timestamps) at our backend	To keep the service up and to stop abuse of the leaderboard.	Art. 6(1)(f) — our legitimate interest in a working, non-cheated service.	Short-lived operational logs.
Your name, email and message, if you use the contact form	To answer you.	Art. 6(1)(f) — legitimate interest in replying to correspondence; Art. 6(1)(c) where the message is a legal request we must handle.	As long as needed to deal with the matter.
Purchase status of the ad-free unlock	To stop showing you ads, and to keep them off when Google Play cannot be reached.	Art. 6(1)(b).	The purchase itself is held by Google Play. On your device we keep only what the ad gate needs: whether you own it, when that was last confirmed, and the Google Play order number, which is there so we can look up a purchase if you ever ask us about one. None of it is sent to us or used for anything else.

What stays on your device and never reaches us

None of the following is sent to our servers. One caveat first, because "on your device" is not quite the whole story on Android: your settings file — which holds the four toggles below and your best time — is included in Android's own cloud backup and in device-to-device transfer, so a copy of it may sit in your Google account. That is Google's backup of your phone, working as you have configured it, and restoring it on a new phone is what carries your best time across. Your sign-in session is deliberately kept out of both.

Your sound, music, haptics and parallax settings.
Your best time on this device, set by any run — ranked or casual. We never receive it: a ranked run posts its own score to the leaderboard separately, and that posted score is what we hold. Note that this is about us — if you are signed in to Google Play Games, your runs are also reported to Google, casual ones included. That is described in section 4, and it is the one thing on this list that leaves the phone.
Your sign-in session, so you are not asked to log in every time: the access and refresh tokens, plus a local copy of your account id, email address, display name and sign-in method, which is what lets the app greet you before the network answers. For a Play Games account the stored address is the derived one, so that copy contains your player ID. All of it is deliberately excluded from Android cloud backup and from device-to-device transfer, so a restored backup cannot carry your session onto another phone.

The Amazfit watch edition

There is a second Whaaack! that runs on Amazfit watches under Zepp OS. It shares this account and this backend with the Android game, so everything above applies to it — but it is a different device with different capabilities, and the differences are all in your favour. Setting them out plainly:

It stores one thing on the watch itself: your best time. That is the whole list — the watch edition makes no sound and has no settings of its own, so there is nothing else for it to remember. There is no equivalent of the Android settings file, and nothing on the watch is included in any cloud backup of ours.
Your sign-in session never reaches the watch. The access and refresh tokens are held by the companion service inside the Zepp app on your phone, which is what makes every network call. The watch asks it for a leaderboard and gets rows back; a token never crosses to your wrist.
Signed in, it sends exactly three things: your email address and password, to sign in or create the account; the display name you choose; and, for each finished run, how long it lasted and how many fruit you hit. Nothing else about the run, the watch or you is transmitted.
Opening the leaderboard fetches the public rankings — display names and times — whether or not you are signed in. That request asks for data rather than sending any about you.
It reads one thing about your watch: the screen size, so it can lay the board out for a round display. It does not read or collect heart rate, activity, sleep, location or any other sensor or health data, and it holds no permission that would let it. The only hardware it drives is the vibration motor, which is output rather than collection.
No ads, no analytics, no tracking, and no Play Games. Section 3 and section 4 describe things the watch app simply does not contain.

Watch runs are ranked on a board of their own rather than mixed with phone scores, because a three-by-three grid tapped with one finger does not produce comparable times to a four-by-four tapped with two thumbs. They are still your rows, on your account: deleting your account under section 7 removes them along with everything else, in the same operation and by the same cascade. You can also simply play without an account, in which case the watch keeps your best time locally and sends nothing at all.

3. Ads, and your control over them

Whaaack! shows ads through Google AdMob. In practice that means at most one full-screen interstitial between runs, capped to roughly one every couple of minutes. There are no ads during a run and none on launch.

Where Google's platform decides a consent form is required — in practice the EEA and the UK — the app shows it before any ad is requested, via the User Messaging Platform, a Google-certified consent management platform operating under the IAB Transparency & Consent Framework. That form is where you allow or refuse personalised advertising, and where you can see every advertising partner involved. Where Google's framework does not require a form, none is shown and no consent is collected.

Two separate rules apply and we treat both as requiring your agreement:

GDPR — personalised advertising rests on your consent under Art. 6(1)(a), not on legitimate interest.
ePrivacy — storing or reading anything on your device for advertising needs consent under art. 399 of the Polish Prawo komunikacji elektronicznej (ustawa z 12 lipca 2024 r., Dz.U. 2024 poz. 1221, in force since 10 November 2024), which replaced the old art. 173 Prawa telekomunikacyjnego.

The same rule about your device is not confined to advertising, and we would rather draw the line ourselves than let this section imply otherwise. Play Games also stores and reads on your device — from the moment the app starts, before this form appears. We rely there on the exemption for what is necessary to provide a feature you are using, rather than on consent, because achievements and profile statistics are the feature and cannot work without it. The consent form below governs advertising alone; it neither authorises nor refuses the Play Games storage, and the way to refuse that is to sign out of Play Games. See section 4.

You get the game either way. If you allow the device storage that ads need but refuse personalisation, you still get ads — just non-personalised ones. If you refuse everything, the app requests no ads at all. You can change your mind whenever you like: wherever Google's form applies to you, the app's Settings carries an Ad privacy options row that reopens it. If you would rather have none at all, the ad-free unlock removes them.

The app requests the Android advertising ID (AD_ID permission). The Google Mobile Ads SDK also adds the Android Privacy Sandbox permissions (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS) to the app automatically. How Google uses that data is described in Google's own policy.

4. Google Play Games

Whaaack! uses Google Play Games Services for achievements and for the run statistics shown on your Play Games profile. This is worth reading even if you have no Whaaack! account, because it is the one part of the app that sends anything anywhere without one.

It starts by itself

The app initialises the Play Games SDK when it starts, and the SDK signs you in automatically against whichever Play Games profile your device already has — before you have touched anything in the app, and independently of the advertising consent form, which governs advertising only. That first attempt is the SDK's, not ours: version 2 performs it without asking us or you. (If it does not succeed, the app does offer a Play Games sign-in you can press — in Settings, and on the sign-in screen — but those are invitations after the fact, not the thing that starts it.) If your device has no Play Games profile, or you have signed out of it, that automatic attempt finds nothing, no achievements or statistics are ever sent, and the rest of the game is unaffected.

Two consequences worth stating, because both are easy to miss. The SDK keeps state of its own on your device as part of that sign-in, so it stores and reads there before you have agreed to anything; we treat that as necessary to the achievements the app provides rather than as advertising storage, and the ad consent form neither covers it nor can refuse it. And if you already have a best time on the device, it goes to Google in that same opening moment — the app re-sends it whenever it comes to the foreground, which is the first thing that happens.

So by the time this page could have been read, something may already have been sent. The only way to prevent that in advance is to be signed out of Play Games before opening the app.

What we send Google

When you are signed in to Play Games, and only then, the app reports:

Achievement unlocks — the four survival milestones. Awarded from the run you have just finished, and also replayed from the best run stored on the device each time the app comes to the foreground and after a Play Games sign-in, so that milestones earned while signed out are not lost. Casual runs count; you do not need an account.
A record of every run that ends — how long you survived (in milliseconds and in seconds), how much fruit you hit, how much escaped, the top speed you reached, and whether the run was ranked. Including a run you back out of before it starts, which reports as a zero.
Your best run so far — sent alongside every run above, and again each time the app comes to the foreground and after a Play Games sign-in, so a profile is not left showing less than you have actually done, including runs you played before you were signed in.

Google does not merely store these. It adds them up: the events become seven lifetime figures on your Play Games Gamer profile — runs played, total time survived, fruit whacked, top speed reached, runs over a minute, ranked runs, and your best run. They are totals for as long as the profile exists, not a private log, and who else can see them is decided by the visibility setting on your Play Games profile rather than by anything here. Ranked runs is the one to know about: it counts runs played with a Whaaack! account, so it says something about this app specifically.

Each event is uploaded as it happens rather than batched for later. All of it is attached to your Play Games profile, not to any Whaaack! account, and it is the game's own numbers — nothing about your device, your location or your identity beyond the Play Games profile you are already signed in to. The one field that says anything else is whether the run was ranked, which implies you also hold a Whaaack! account, since only those can play ranked.

Who controls it

Google is an independent controller for your Play Games profile and for everything on it. Their handling is governed by the Google Privacy Policy and the Play Games Services terms, not by this one. We send achievements and statistics to that profile and read nothing back from it — not your friends, not your other games. The single exception is the account-creation flow below, where our backend exchanges a one-time code with Google and uses the resulting access token exactly once, to ask Google who you are. We deliberately do not request offline access, so no lasting key to your profile is issued to us or stored by us.

How to stop it

Sign out of Play Games — in the Play Games app, or in your device's Google settings. From that moment the app sends nothing and unlocks nothing, and the game plays exactly as before: the achievements simply stop happening. There is no switch for it inside Whaaack!, because there is nothing of yours held here to switch off.

To clear what Google already has, use Google's own controls — the route is in section 7, and it works whether or not you ever had a Whaaack! account.

You may also object to this processing under Art. 21 GDPR through the contact form. In candour about what that achieves: we hold no per-player switch to flip, because the sending is decided on your device by whether Play Games is signed in. Signing out is therefore both the faster remedy and the complete one, and it is entirely in your hands. If you object to us, what we can do is confirm the position and help you apply it.

If you use Play Games to create a Whaaack! account

Signing in to Play Games does not create an account by itself. If you choose Continue with Play Games, or accept the offer when you first tap Play ranked, the app asks Google to confirm who you are and we then create a Whaaack! account from that answer. What we receive and keep is your Play Games player ID and your gamer tag, which becomes your starting display name on the public leaderboard — so the name other players see is the one your Play Games profile carries, until you change it in Settings. We receive no email address in this flow, and there is no password. Deleting the account removes all of it from our side; see section 7.

5. Who else sees your data

Supabase — our backend (database and authentication). A processor acting on our instructions under a data processing agreement. The password-reset page on this website (/whaaack/auth/) is the one page here that talks to it: follow a reset link and the new password you type goes from your browser straight to Supabase, and nowhere else. Your browser reaches pklrfcbyseitdbxkmsnw.supabase.co only on that page.
Google Ireland / Google LLC (AdMob and UMP) — advertising. Google acts as an independent controller for advertising data.
Google (Sign-In) — if you choose Google Sign-In, Google is a separate controller for the sign-in event itself. We receive only the email and name from the token.
Google Ireland Limited (Google LLC outside the EEA) — Play Games Services: achievements and run statistics, as an independent controller for your Play Games profile. If you create your account with Play Games, our backend additionally exchanges a one-time code with Google's servers (oauth2.googleapis.com, games.googleapis.com) to confirm your player ID and gamer tag. Fully described in section 4.
Google — Android Backup. Android's own backup of your phone includes the app's settings file, which holds your four toggles and your best time. That is your device backup working as you have configured it, and it is how a best time survives onto a new phone; you control it in Android's own settings. Your sign-in session is deliberately excluded from it.
Google Play — distribution and payments. For purchases in the EEA, Google is the seller of record. When you buy the ad-free unlock while signed in, the app sends Google a one-way scrambled form of your account id with the order — Google asks for it to spot fraud, it cannot be turned back into your id, and it is never your email address.
Web3Forms — delivers messages from the contact form. A processor.
Intuition Machines (hCaptcha) — the "confirm you are human" box on the contact page. Your browser loads it from js.hcaptcha.com as soon as that page opens, so it sees your IP address and browser signals whether or not you send the form.
Resend — delivers the emails the account itself needs: confirmation, password reset and address changes. It processes your email address and the contents of those messages on our instructions.
GitHub — hosts this website on GitHub Pages, and its servers log the IP address of every visitor as part of serving it.
The public — anyone can read the leaderboards, signed in or not. A row shows your display name, your best ranked score and the date you set it, and the response also carries the internal account id your scores are stored against. Your email address is never included. Choose a display name you are comfortable being public; you can change it once every 30 days.

We do not sell your data, and we do not use it for advertising profiles of our own.

6. Transfers outside the EEA

Some of the providers above are established in, or use infrastructure in, the United States. Where data leaves the European Economic Area it is protected by the European Commission's Standard Contractual Clauses, and in some cases additionally by the provider's certification under the EU–US Data Privacy Framework. You can ask us for a copy of the safeguards relied on via the contact form.

7. Deleting your account — the important bit

Whaaack! has a real delete button, and it really deletes.

In the app: Settings → Delete my account, then type DELETE to confirm. That single action:

deletes your authentication user, so the email address is gone — or, for a Play Games account, the player ID and the derived address we held against it;
deletes your profile row, so the display name is gone and freed for someone else;
deletes every score you have ever recorded, so you disappear from the leaderboards;
clears the best score and the sign-in session held on the device, so the account is gone from the phone too. Your sound and display settings stay, and so does the record of an ad-free purchase — that one belongs to your Google Play account, not to this one, and deleting a Whaaack! account does not undo a purchase or refund it.

It is immediate and irreversible. There is no deactivated state, no grace period and no way for us to undo it. Two things do outlive it, and the deletion page says the same: encrypted backups retain traces until the backup they sit in rotates out, and our backend keeps a sign-in log — the address used and the IP it came from — as security record keeping. Neither is used for anything else. For a Play Games account that log entry is worth naming, because the address on such an account is derived from the player ID and therefore contains it.

Your Play Games profile is not ours to delete. Achievements and run statistics live on your Google Play Games profile, and Google is their controller — so deleting a Whaaack! account removes our records but leaves those untouched, exactly as it leaves an ad-free purchase untouched. You can clear them yourself, and it takes about as long as our own delete button: in the Play Games app → Settings → Delete Play Games account & data, under Delete individual game data, find Whaaack! and delete it — or do the same at play.google.com/games/profile. Google's instructions are here. Deleting a Whaaack! account created from Play Games also does not sign you out of Play Games; if you later sign in again the same way, a fresh account is created, because the player ID is the only thing that identified the old one and we no longer hold it.

Deleting a Whaaack! account also does not stop the reporting described in section 4: for as long as the device stays signed in to Play Games, runs and achievements keep going to your Play Games profile, because that has never depended on having an account with us. Signing out of Play Games is what ends it.

If you cannot get into the app — you lost the device, or you already uninstalled it — use the out-of-app deletion page. It covers Play Games accounts too, which have no email address we could write to; the page explains what we ask for instead.

Deleting your account does not cancel the ad-free purchase: that belongs to your Google Play account, not to your Whaaack! account, and it will still be there if you come back.

8. Your rights

Under the GDPR you have the right to:

access your data and get a copy of it (Art. 15);
rectify anything inaccurate (Art. 16) — the display name is editable in Settings;
erasure (Art. 17) — the delete button above, or ask us;
restrict processing (Art. 18);
data portability for the data you gave us (Art. 20);
object to processing based on legitimate interest (Art. 21);
withdraw consent at any time where consent is the basis — for ads, in Settings → Ad privacy options. Withdrawal does not affect the lawfulness of what happened before it.

Exercise any of them through the contact form. We answer within one month, as Art. 12(3) requires.

Complaints

If you think we have handled your data badly, you can complain to the Polish supervisory authority:

Prezes Urzędu Ochrony Danych Osobowych (UODO)
ul. Stanisława Moniuszki 1A
00-014 Warszawa, Poland
Tel. 22 531 03 00 · uodo.gov.pl

Note: the UODO moved from ul. Stawki 2 in July 2025. The address above is the current one.

9. Children

Whaaack! is not directed at children. In Poland the age at which a child can consent to an information society service on their own is 16 — Poland did not lower the GDPR default. If you are under 16, please do not create an account without the agreement of a parent or guardian; casual play needs no account at all.

The app is not listed in Google Play's Families programme and is not designed for children. If you believe a child has given us data, tell us and we will erase it.

In fairness we should say what we do not do: the app never asks your age. There is no age screen and no age gate, and because there is none, every consent request it makes tells Google's framework that the user is not below the age of consent. That is the consequence of not asking, not a judgement we have made about you, and it is why the two paragraphs above are a request rather than a control. On a phone a child uses, the effective measures are the ones a parent holds: buy the ad-free unlock, or sign out of Play Games, or both.

One point specific to Play Games: casual play needs no Whaaack! account, but it is not the same as playing anonymously. If the device is signed in to a Play Games profile, that profile records the achievements and run statistics described above, whoever is holding the phone. A Play Games profile for a child is set up and controlled through Google's own family tools, not through this app — we neither create one nor can we see whose it is. If a child should not be building one, sign that profile out on the device and the app stops sending anything.

10. Security

Traffic between the app and our backend is encrypted in transit (HTTPS/TLS). Passwords are hashed by our authentication provider and are never visible to us. Sign-in tokens are stored in the app's private storage and are deliberately excluded from Android cloud backup and device-to-device transfer, so a restored backup cannot hand your session to another device. Access to leaderboard data is restricted by row-level security so no client can read another player's raw records.

11. Automated decision-making

None. We do not profile you and there is no automated decision-making producing legal or similarly significant effects on you within the meaning of Art. 22 GDPR. Ranking is an ordinary sort by score.

12. Changes to this policy

If this policy changes materially we will update the date at the top and, where the change matters to you, say so in the app. The current version always lives at this URL.