Privacy policy
Last updated: 14 November 2026
This policy explains what information the game Mixaloon (“the game”, “we”) uses, why, and the choices you have. We have written it to be short and plain.
Who is responsible
The game is made by Fredrik Mattiasson, Östersund, Sweden. We are the “controller” of your data under the EU General Data Protection Regulation (GDPR). Contact for anything about privacy: [email protected].
The short version
- Your progress is saved on your phone, and a copy is kept in the cloud so you can get it back on a new phone. For that the game gives you an anonymous account: an ID made up by Google Firebase, with no name or email.
- You can choose Save with Google in Settings, so your progress follows your Google account. Only then does the account include your Google email address.
- The game asks what year you were born once, on the first start. The answer stays on your phone and is never sent to us or to Google. It only decides what the game may do (see “Children”).
- Where the law requires it (the EU/EEA, the UK and Switzerland), Google’s consent form asks whether gameplay statistics may be collected. Under 13, they are never collected.
- The game sends gameplay statistics (which levels are played, won and lost) and crash reports, to make the game better and fix bugs.
- If you enter a code or collect a gift, the game records that your account used it.
- You can delete your cloud save and account at any time: Settings → Delete my data, or by email (see “Deleting your data”).
- The game may show ads from Google AdMob (see “Ads”). Children under 13 get no ads.
- You can buy coins, a starter pack and Remove ads with real money through Google Play (see “Purchases”). Everything in the game can be played without paying. We never see your card details, and we don’t sell your data.
What we use, and why
Game progress and settings on the phone
What: levels won, stars, coins, boosters, lives, places, and your settings (sound, color symbols, vibration and similar). Why: so the game remembers where you are. Legal basis: necessary to provide the game (contract). Where: stored on your phone. Your phone’s own Android backup may include it, if you have backup turned on; that backup is managed by Google under your own account.
Cloud save
What: the same game progress (not your settings), and when it was last saved. Why: so your progress is safe and comes back on a new phone. Legal basis: necessary to provide the game (contract). Who: Google (Firebase Firestore), stored in Europe.
Codes and gifts
What: when you enter a code, a record of your account ID and the time, one per code you used, and the code’s use count goes up. A gift you collect has no record of its own on the server: it is noted in your cloud save (the list of codes and gifts you have used, with what they gave) and, if statistics are allowed, as a statistics event. Why: so a code works once per account and a gift is not given twice. Legal basis: necessary to provide the game (contract). Who: Google (Firebase Firestore, stored in Europe; events: Firebase Analytics).
Purchases
What: the item you bought (for example 4,500 coins), when, the price and currency, and Google’s transaction ID, linked to your account ID. Google Play takes the payment: we never see your card or payment details. The purchase is also noted in your cloud save, so it is given to you only once. Why: to give you what you bought, restore it on a new phone, and keep a record for accounting. Legal basis: necessary to provide the game (contract); legal obligation (accounting). Who: Google Play (payment); RevenueCat, Inc. (purchase records, on our behalf); Google (Firebase Firestore).
Account
What: an anonymous account ID; with Save with Google, also your Google account’s email address and name. Why: to know which cloud save is yours. Legal basis: necessary to provide the game (contract). Who: Google (Firebase Authentication).
Birth year
What: the year you pick on the first start. Why: to switch off statistics, ads and Google sign-in under 13, and personalised ads under 16 in the EU/EEA, the UK and Switzerland. Legal basis: legitimate interest (protecting children). Who: nobody else: it stays on your phone and is never sent.
Gameplay statistics
What: which tutorial steps, levels and daily challenges you play, win or lose, with moves left, stars, boosters and extra moves used, which booster you used, and the coins, lives and boosters you had when the level ended; how a Pip’s Run ended (town, score, distance, deliveries, and how far its difficulty had risen); coins earned and spent by source (summed per screen); which code you redeemed or gift you collected; when you open the shop (and from which screen) and when you start a purchase; when extra moves, a life or a lives refill is offered, how it is paid for and whether you take it; the highest level you have won and whether you have ever bought something; what you bought (the item, price and currency); where the game offers a free gift in place of an ad; plus Firebase’s standard events (first open, session start, app version), an app-instance ID, country, device model and OS version. No names, no free text. Why: to see which levels are too hard or too easy and improve the game. Legal basis: your consent (EU/EEA, UK, Switzerland); legitimate interest elsewhere. Never under 13. Who: Google (Firebase Analytics).
Crash reports
What: the error message, where in the game’s code it happened and the stack trace of errors the game catches; if the app itself crashes, the crash trace; plus Firebase’s standard crash data (device model, OS version, an installation ID). No user ID, no name, no email. Why: to find and fix bugs. Legal basis: legitimate interest (a game that works); they contain no personal data. Sent at every age. Who: Google (Firebase Crashlytics).
Game settings from our server
What: a Firebase installation ID (a random ID for this install of the game, not tied to you or your phone), your phone’s language setting and the Firebase library’s version, sent when the game downloads its current settings (prices in coins, coin sales, new levels, the update notice). Your app version is not sent: the game compares it on the phone. Why: to tune the game without an app update. Legal basis: necessary to provide the game (contract), and legitimate interest (running and tuning the game). Sent at every age, before any consent choice, as it carries no gameplay data. Who: Google (Firebase Remote Config, Firestore).
Consent choice
What: your answer in Google’s consent form, stored by Google’s consent tool on your phone. Why: to respect your choice. Who: Google (User Messaging Platform); stored on your phone.
Support emails
What: your email address and what you write. Why: to answer you. Legal basis: legitimate interest. Who: Cloudflare (email forwarding) and Google (Gmail).
Ads
The game can show ads through Google AdMob. Some are optional, rewarded ads you choose to watch (for example for extra moves or a life); others may appear between levels, never during one. We switch ads on gradually, so you may not see any.
When an ad is requested, Google’s ad library collects your advertising ID, your IP address (which gives an approximate location) and how you interact with ads, to show and measure ads and to prevent ad fraud. Google uses this data as an independent controller, under its own privacy policy: policies.google.com/technologies/ads. Our statistics never collect the advertising ID.
- In the EU/EEA, the UK and Switzerland, Google’s consent form decides whether ads are personalised; without your agreement they are not.
- Under 16 in those countries, ads are never personalised.
- Under 13, or when the birth year is unknown, no ad is requested at all.
- You can reset or delete your advertising ID in your phone’s settings (Google → Ads).
Your privacy choices
- Birth year: asked once, on the first start, with no year pre-selected. It cannot be changed later in the same install (uninstalling and starting again asks again).
- Consent form: in the EU/EEA, the UK and Switzerland, Google’s consent form (Google User Messaging Platform) appears right after the birth year. It covers statistics and ads together. Until you agree, no statistics are collected there and ads are not personalised. Elsewhere there is no form and statistics are on by default once Google’s consent check has answered (until it has, for example with no internet, they stay off), except under 13.
- Change your mind: where the form is required, Settings has a Privacy options row that opens it again. Statistics follow your new choice from then on.
- Crash reports are not part of the consent form: they contain no personal data and are sent so the game keeps working.
Save with Google
Save with Google is optional. If you choose it, Google tells Firebase which Google account you signed in with (its email address and name). We use this only to find your cloud save, for example on a new phone. If that Google account already has a Mixaloon save, the two saves are combined so you keep the further-along progress, and the game restarts with it. The phone’s earlier anonymous save then stays in the cloud: it holds only game progress, nobody can reach it any more, and we may delete such saves in clean-ups (see “How long data is kept”).
Sharing your painting
After a win you can share a picture of your painting, if your phone supports it. The picture goes only where you choose in your phone’s share menu; we don’t receive it. The same goes for the daily puzzle result you can share as text.
Permissions
- Internet, for the cloud save, Save with Google, codes and gifts, purchases, game settings, statistics, crash reports and ads.
- Vibration, so pops can be felt (you can turn vibration off in Settings).
- Notifications, only if you turn on the daily puzzle reminder. The reminder is scheduled on your phone; nothing is sent to us. Android also lists run at startup and prevent phone from sleeping, so a scheduled reminder survives a restart and arrives on time.
- Google Play billing, so you can buy items through Google Play.
- Advertising ID, used by Google’s ad library when an ad is requested (see “Ads”).
Children
The game is made for a general audience and isn’t directed at children under 13. On the first start we ask what year you were born. We keep only that year, only on your phone, and use it as follows:
- Under 13: no gameplay statistics, and Save with Google is not offered (cloud save with the anonymous account and Delete my data still work). Consent requests are marked as for a child. Crash reports, which contain no personal data, are still sent.
- Under 13, or when the birth year is unknown: no ads. Under 16 in the EU/EEA, the UK and Switzerland: ads are never personalised.
- If the birth year is not known, the game takes the safe side: no statistics and no Save with Google.
Because the age is a year picked by the player, it is not checked.
How long data is kept
- Progress on your phone: until you delete it in Settings, uninstall the game or clear its data.
- Cloud save and account: until you delete them (Settings → Delete my data, or by email).
- An earlier anonymous save left behind by Save with Google (see above), and its code redemption records: kept, holding only game progress; we may delete them in clean-ups, and delete them on request.
- Code redemption records: deleted with your account.
- Purchase records: kept by Google Play and RevenueCat for as long as accounting law requires (in Sweden, 7 years). Delete my data does not remove them; email us and we delete your record at RevenueCat, except what the law says we must keep.
- Statistics (event-level data): 2 months in Firebase; after that only aggregated, anonymous reports remain.
- Crash reports: 90 days.
- Ad data: kept by Google under its own policy (see “Ads”); we receive only totals.
- Support emails: 12 months after the conversation ends.
Where data goes
Firebase and AdMob are run by Google. The cloud save is stored in Europe. Purchase records are kept by RevenueCat, Inc., which works for us as a processor in the United States. Google may process statistics, crash, account and game-settings data outside the EU/EEA, including in the United States; these transfers, and RevenueCat’s, are protected by the EU–US Data Privacy Framework and the European Commission’s Standard Contractual Clauses. Google’s Firebase privacy page: firebase.google.com/support/privacy.
Security
Everything the game sends goes over encrypted connections (HTTPS/TLS). Each cloud save can only be read and changed by its own account.
Error log
The game may also keep a small log of technical errors on your phone. It stays on your phone unless you choose to copy it and send it to us yourself, for example in an email.
Deleting your data
- In the game: Settings → Delete my data deletes your cloud save, your code redemption records under your current ID and your progress on the phone (your settings stay), and removes your sign-in. It also signs the game out of RevenueCat; your purchase history stays with Google Play and RevenueCat (see “How long data is kept”). Coins bought before the delete don’t come back; Remove ads may come back with Restore purchases, but that isn’t guaranteed, so use Save with Google to keep your purchases on a new phone. With Save with Google, the game may ask you to sign in with Google once more to remove it; if you cancel, your save is still deleted and you can email us to remove the sign-in. Without Save with Google, an empty sign-in record (an ID with no game data and nothing about you) can remain. It needs an internet connection; offline, nothing is deleted.
- Without the game: follow the steps at mixaloon.fremtech.se/delete, or email [email protected].
Your rights
Under GDPR you have the right to access the data about you, to correct it, to delete it, to restrict or object to its use, to move it (data portability), and to withdraw consent at any time without affecting earlier use. Email [email protected]; we answer within one month. You can also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), www.imy.se, or to the data protection authority where you live.
Changes
If we change this policy, we update the date at the top and, for important changes (such as a new kind of data), update it before that version of the game is released.