Chemibloom privacy policy
Last updated: 12 November 2026 · Version 1.7
This policy explains what personal data Chemibloom collects, why, who receives it, how long it is kept, and the choices and rights you have. It covers the Chemibloom app for iPhone and iPad, the Android app once it is released, and the game's pages at kend.app/chemibloom.
1. Who we are
Chemibloom is made by Kend, an independent studio ("we" in this policy). We decide how your personal data is used (we are the "controller").
- For privacy questions and requests, including from Quebec: support@kend.app.
2. The short version
- You can play without an account, and without giving us your name, email, phone number or location.
- We ask your birth year once. It stays on your device (and in your device's own backup, if you have that on), sets up the game for your age, and is never sent to us. Where a US state's law says so, the game takes your age range from the app store in its place, and keeps it the same way.
- Players under 13: no play statistics, no purchases, and only child-directed, non-personalised ads, which they choose to watch.
- Play statistics are game events with a random player number, never your name or email. Where the law needs your consent (the EEA, the UK, Switzerland and Quebec), and where your device does not show where you are, we ask first and send nothing before you answer. Teens are always asked. You can change your answer any time in More > Privacy.
- Ads only play when you choose to watch one for a reward. Under 18, they are never personalised.
- We do not sell your personal data. In the US, you can opt out of the "sharing" of data for personalised ads in More > Privacy choices.
- You can delete your account and its cloud data in the game: More > Account > Delete my account.
3. The age question
At first start the game asks for your birth year. It is kept on your device; we never receive it, and the game sends it to no one. With it the game decides, for your age band and your country's rules, what it may collect (section 5). Your device's time zone and languages tell the game which region's rules to apply. The game does not send them for this: only the region group (the EEA, the UK and Switzerland; the US; or elsewhere) is kept with your privacy choices (section 4), and Google Analytics records the language only with statistics you allow. Nothing that identifies you leaves your device before you answer. The game's files and settings, your birth year included, are part of your device's own backup if you have that on: iCloud Backup or a backup on your computer for iPhone and iPad, your Google account's backup for Android. Apple or Google keeps that backup for you under their own rules, and it is yours to delete there: deleting your account in the game does not reach it.
In some US states the law tells an app to take your age range from the app store, not from what you type (Texas today; Alabama, California, Utah and Louisiana during 2027). Where the App Store or Google Play says such a law applies to you, the game asks the store for your age range at each start, and the store asks you, or your parent, before it shares it. A range that is shared takes the birth year's place: under 13, 13 to 15, 16 to 17, or 18 and over, with who set it and whether a parent has approved the game's latest big change. If you typed a birth year before, the younger of the two ages counts. Where the law requires the range and it is not shared, the game plays by its rules for under-13s until it is. The range stays on your device as your birth year does: we never receive it, and the game uses it for its age rules and nothing else.
4. What we collect, why, and on what legal basis
| What | What it contains | Why | Legal basis (EEA, UK) | Who receives it |
|---|---|---|---|---|
| Guest account | A random account ID; the versions of the game the account has run; the IP address and app version in the sign-in service's logs. On iPhone the account ID and its sign-in token are also kept in your phone's Keychain, on that phone only, so the game finds your lab if you delete it and install it again | One account per player, so saves, purchases and rewards reach the right lab | Contract: the game you asked for | Google Firebase, our processor |
| Cloud saves | Your lab's progress, the lab name you typed, and the device name (such as "iPhone") | Keep your lab safe and move it to a new device | Contract | Google Firebase |
| Moving a lab to a new phone | A 12-character code you read off one phone and type on the other; we keep only its hash | Move your lab without an account | Contract | Google Firebase |
| Rewards and purchases | Your account ID, the rewards you collect, and for purchases the store's receipt, the product, its price, currency, tax and the store's commission | Deliver each purchase and reward exactly once, and keep financial records | Contract; legal obligation for the records | Google Firebase; RevenueCat, our processor; Apple or Google as the seller |
| Lab Pass | Your account ID, the season, the points each Lab Order or mission earned, and whether premium is unlocked | Count your season's progress | Contract | Google Firebase |
| Remote settings, news and event packs | Nothing about you: the game reads public settings and downloads event pictures; the services log the IP address and app version of each request | Switch features off in an emergency, tune the game and run events without an update | Legitimate interests: keeping the game working and safe | Google Firebase |
| Play statistics (optional) | Game events: start-up time, tutorial steps, missions, ranks, discoveries, crates opened, store views, purchases (price and a one-way code, never the receipt), ads offered and watched, reminder answers, error messages, session length. Google Analytics adds its own first-open, session and engagement events, a random app-instance ID, the device model and system, the language and a city-level location from the IP address. For adults, also the account ID; never for under-18s | Balance the game: see which ranks feel slow and where players stop | Consent where we ask (teens; adults in the EEA, the UK, Switzerland and Quebec, and where the device's time zone does not show where it is). For adults elsewhere, legitimate interests with an opt-out | Google Analytics for Firebase, our processor |
| Ads (optional, only when you choose to watch one) | A device ID: on iPhone one limited to our apps, since we never ask Apple's tracking question, so no advertising ID is used; on Android the advertising ID, never for players under 13. The IP address, device and app details, and how the ad was watched | Show the ad you asked for, which pays for the free game | Consent through Google's consent message in the EEA, the UK and Switzerland; legitimate interests elsewhere | Google (AdMob), as an independent controller |
| Ad checks for event boosts | Only on the ad for an event's boost: your account ID and a one-time code for the ad go with it, and Google tells our server once you have watched it to the end. We keep the checked view for 90 days | Give the boost only for an ad really watched, so event boards stay fair | Legitimate interests: preventing fraud | Google (AdMob) passes it to us; Google Firebase |
| Game Center on iPhone and iPad, Play Games on Android (13 and over) | Your system game account signs you in; we learn only whether it worked, then send achievements and leaderboard scores | Achievements and leaderboards in the system app | Contract | Apple, or Google on Android |
| Your lab kept with your game account (13 and over) | Once Game Center or Play Games has signed you in, the game proves to our server which game account that is, and the server keeps a scrambled form of that account's ID (a hash, never the ID itself) with your account ID. On a new phone signed in to the same game account, the game offers to bring your lab back | Bring your lab back when a phone is lost or broken | Contract | Our server (Google Firebase); Apple or Google only confirm the sign-in |
| Event boards | Your account ID, a lab name and your event score and rank, shown under an alias for the run to about 50 players in your division (the best 100 labs to everyone in the run, and in a co-op run to your team of up to 6); every score submission is logged for the anti-cheat review. Under 18: a generated lab name | Events with divisions of similar players, kept fair | Contract; legitimate interests for the anti-cheat checks | Google Firebase; other players see the name and score |
| Friends (13 and over) | Your friend code, your friendships with when each began, and the labs you blocked, kept with your account ID; the Funding Flasks you send and receive. Your friends see your lab's name, its rank, discoveries, elements and title, and your event rank in an event you both play, never your account ID. If you tap Add your Game Center (or Play Games) friends, your phone asks first, and then the IDs of the friends it shares go to our server, which keeps them only in a scrambled form (hashes) and makes two players friends when each has added the other this way | Adding friends with a code and a daily gift of Funding | Contract | Google Firebase; your friends see your lab |
| Research Societies | The society's name and code, and each member's account ID, role, join time, last visit and board name; each week's ranks; the society's chat, which has set lines only, no free text | Playing in a society and its weekly goals | Contract | Google Firebase; members see each other's board names, roles and ranks |
| Reminders (optional) | Nothing leaves your device: reminders are scheduled on it | Free crate ready, a hello after 3 days away | Consent: the system permission | Nobody |
| Messages from the lab (optional) | Your device's push token and platform, your switch for the messages, your clock's offset from UTC and when the game last reported, with your account ID; a log of each nudge and the last comeback message | One message in an event's last hours if you drop out of a prize band; one after 3, 7 and 14 days away (the last two with a gift of gems); never at night, and never more than two reminders and messages a day | Consent: the system permission and the game's switch | Google Firebase; Apple's or Google's push service delivers it |
| Your privacy choices | The policy version, the time, your region group, and your statistics and personalised-ads choices | Remember your choices and show what you agreed to | Legal obligation | Your device; with an account, Google Firebase |
| App checks | Nothing about you: Apple's confirmation that a request comes from the real game on a real iPhone (once an install, for a key your phone makes for the game; then a signature with it), or a DeviceCheck token on older phones; on Android, Google Play's confirmation that the game is the one Google Play installed, on a device that passes Google Play's checks. Back comes a token that lasts about an hour, sent with the game's requests to our servers | Keep scripts that pose as the game away from rewards, events and the Lab Pass | Legitimate interests: security | Google Firebase (App Check), which checks it with Apple or Google Play |
| Crash and error reports | The build, your phone's model and system, the lab's rank, how long the session had run, the game's memory, its last 50 log lines and the errors it logged, each with where it came from; no account ID or other ID | Find and fix crashes and errors: sent at the next start after the game crashed, and once a session for the errors it logged | Legitimate interests: keeping the game working | Google Firebase |
| Problem reports (only when you send one) | The kind of problem, what you write, the support code (your save), the game's version, your rank, your device's system, screen and language, and the game's last 50 log lines; with your account ID | Find and fix the problem you report | Contract; legitimate interests | Google Firebase |
| Your data requests | For a copy, nothing is sent: your device receives your own records. For a request, its kind and what you write, with your account ID | Answer your request | Legal obligation | Google Firebase |
| Codes on the website | Your Player ID and the code you type at kend.app/chemibloom/redeem; for failed tries only, a hash of the address the request came from, kept in an hour's count | Deliver the code's gift once, and stop guessing | Contract; legitimate interests for the limit | Google Firebase |
| Support messages | What you write from your own email, with the Player ID or report number you choose to quote | Help you | Contract; legitimate interests | Our support mailbox |
We do not collect your precise location, contacts, photos, camera or microphone. We do not use your data to make decisions about you that have legal or similarly significant effects. Our anti-cheat checks flag impossible event scores for a person to review; a flagged score is hidden until it is reviewed, nothing more.
5. Children and teens
Chemibloom is made for players aged 13 and over and is not directed at children, but younger players can play. The game treats players by the youngest age their birth year, or the app store's age range, allows:
- Under 13: no play statistics, no purchases, no Game Center or Play Games sign-in, no friends, and only child-directed, non-personalised ads. Their guest account, cloud save and rewards still work. For them we use the random account ID only to run the game: to keep their lab saved, to deliver each reward exactly once, and to keep the game secure. It is never used to contact them, to show ads based on their activity, or to build a profile: it never goes with play statistics (there are none) or with an ad, and no ad request for them asks for personalisation or tracking.
- 13 and over, but under the age your country sets for consenting alone (for example 16 in Germany, 15 in France, 14 in Spain, Quebec, South Korea and China): no play statistics, and ads tagged as under the age of consent.
- Teens at or above that age: asked about play statistics, never switched on for them; ads never personalised and tagged as under the age of consent, so Google's consent message asks them nothing.
If you are a parent and believe your child gave us personal data, write to support@kend.app or delete the account in the game (section 8).
6. Your choices
- More > Privacy: play statistics on or off.
- More > Privacy > Privacy choices: statistics; personalised ads for adults (in the US: "Do not sell or share my personal information"; in Quebec they start off, and you can turn them on there); Google's own ad privacy options where they apply, once Google's message has been shown on your device; this policy and the terms.
- Ads: Google's consent message (in the EEA, the UK and Switzerland), when you first choose to watch an ad.
- Reminders and nudges: your device's notification settings, and the game's reminder switches in More.
7. Who receives your data
- Our processors, who use it only for us under data processing terms: Google Firebase (accounts, cloud saves, Cloud Functions, remote settings, push), Google Analytics for Firebase (play statistics), and RevenueCat (purchases).
- Independent controllers, under their own privacy policies: Apple (the App Store, Game Center, push delivery) and Google (Google Play, Play Games, and ads through AdMob under the Google Ads Controller-Controller Data Protection Terms).
- Other players see an event board's lab name and score, your society's members see your board name and rank, and your friends see your lab's name and progress.
- Authorities, when the law requires it.
We do not sell personal data for money. Under California law, letting Google use data to personalise the ads you watch can count as "sharing". Adults in the US can turn it off in Privacy choices: from then on the ads you watch are not personalised, and each ad request also carries Google's restricted data processing signal, which limits how Google uses your data. We never do it for players under 18: their ads are never personalised, and they always carry that signal.
8. How long we keep it, and deleting it
| Data | Kept |
|---|---|
| Birth year, settings, privacy choices on your device | Until you remove the game; in your device's own backup, under Apple's or Google's backup rules |
| Guest account | Until you delete it in the game, which also removes the iPhone's Keychain copy (deleting only the app leaves that copy on the phone). Firebase then removes it from live and backup systems within 180 days, and keeps sign-in IP addresses for a few weeks. A guest account not used for 24 months is deleted with its data |
| Cloud saves | Until you delete your account. Of older copies we keep the newest 20, the newest of each day for 30 days, and a backup or a copy made when two devices disagreed for 90 days; the rest are deleted every night |
| A code for moving a lab | Its hash until it is used, or 24 hours |
| Reward and purchase records | As financial records, for as long as tax and accounting law requires (up to 10 years); when you delete your account, your account ID on them is replaced by a pseudonym: a one-way code made from it |
| Lab Pass points, event boards and score logs | 90 days after the season or the event ends, or until you delete your account |
| Your lab's link to your game account | Until you take it away in More > Account, or delete your account |
| Friendships, friend codes and blocks | Until you remove or block the friend, make a new code (the old one), or delete your account |
| Research Societies | While you are a member: a member silent for 14 days is removed; a week's ranks go 90 days after the week, chat lines after 30 days |
| Push tokens and nudge logs | A token 60 days after the game last reported it; a nudge's log 90 days after its event ends; both when you delete your account |
| Problem reports and data requests | Until you delete your account |
| Crash and error reports | 90 days |
| Codes on the website | That your account used a code, until you delete your account; the count of failed tries, 2 days |
| Play statistics | 14 months in Google Analytics; totals in reports may be kept longer |
| Support messages | Until your request is closed, then 12 months |
| Google's ad data | Google's own retention: it anonymises advertising data in its logs by removing part of the IP address after 9 months and cookie information after 18 months |
How long we keep children's data. From players under 13 we keep only what the game needs to run, and delete it when the account is deleted in the game, when a parent asks, or after 24 months without play:
| Data | Why we collect it | Why we keep it | Deleted |
|---|---|---|---|
| Guest account ID | One lab per player | Saves and rewards must reach the right lab | When the account is deleted, or after 24 months without play |
| Cloud save, with the lab name | Keep the lab safe | A lost phone must not lose the lab | With the guest account; older copies pruned as above |
| Reward records | Deliver each reward exactly once | Stop a reward being paid twice | Account ID replaced by a pseudonym when the account is deleted |
| Privacy choices | Remember the choices made | Show what applies to the account | With the account |
Deleting your data. In the game: More > Account > Delete my account deletes your account, your cloud saves, your profile and privacy choices, your Lab Pass progress, your event entries and scores, your friendships and society membership, your push tokens, and your problem reports and requests. It also deletes your customer record at RevenueCat and asks Google Analytics to delete the play statistics kept under your account ID (statistics only for adults who allowed them), which Google does within about two months. Financial records and our support log stay, with a pseudonym in place of your account ID. Without the game: write to support@kend.app with your Player ID, as https://kend.app/chemibloom/delete-account explains; we delete the account within 30 days.
9. International transfers
Our providers may process data outside your country, including in the United States. Google relies on the EU-US Data Privacy Framework and its UK and Swiss extensions, and on the European Commission's standard contractual clauses; RevenueCat on the standard contractual clauses in its data processing addendum.
10. Your rights
Depending on where you live, you can ask to access your data, correct it, delete it, receive a copy in a portable format, restrict or object to how we use it, and withdraw consent at any time (which does not affect what happened before). Many of these you can do in the game: in More, under Your data, a copy of what our server keeps about you and requests to delete something or about a concern; and Delete my account. Otherwise write to support@kend.app. We answer within one month (EEA, UK), 45 days (California) or 30 days (Australia), and tell you if we need longer. You can also complain to your data protection authority: in the UK, the Information Commissioner's Office (ico.org.uk); in the EU, the authority of your country.
In the US, depending on your state, you also have the right to know, delete and correct, to opt out of the sale or sharing of personal data and of targeted advertising, and not to be treated differently for using these rights. We do not use sensitive personal information.
11. Security
Data travels encrypted (HTTPS). Our database lets each player read and write only their own data, and only our server writes rewards, purchases and scores. We look up a player's records only through audited support tools.
12. Changes
When we change this policy we update the date and version above; the game shows the policy in More > Privacy. If a change needs your consent again, the game asks again.
13. Contact
Kend · support@kend.app · https://kend.app/chemibloom