← Bloom

Bloom — Privacy Policy

Document version 2

Effective date: 13 November 2026 Data controller: Bloom Game Privacy contact: bloom.mobile.game@gmail.com

1. In short

• You do not need to give us your name, email, or any account details to play. The Game creates an anonymous account for you automatically.
• We collect what we need to run the game (your progress and your garden), to keep it fair (anti-cheat and abuse signals), to make it better (gameplay analytics), and — if you choose to watch one — to show a rewarded advertisement.
• We never see your payment details. Apple and Google process every purchase.
• We do not sell your personal information, and we do not share it for cross-context behavioural advertising unless you have opted in to personalised advertising.
• The Game is for players aged 18 and over and is not directed to children.

2. Who we are

Bloom Game is the controller of the personal data described here. You can reach us about anything in this policy at bloom.mobile.game@gmail.com.

3. What we collect

3.1 An account identifier, created automatically

When you first open the Game, Firebase Authentication creates an anonymous account and gives it a random user id. That id is what every other record below is keyed by. It is not your name, and on its own it does not identify you — but because everything is linked to it, we treat it as personal data.

We also store, against that id:

• a player id and a display name and avatar (the Game gives each player a name and an avatar from a fixed list; you can change your name in your profile, and other players see the name you choose);
• your platform (iOS or Android) and the app/config version you are running;
• account creation and update timestamps;
• a friend code — a short random string you can share so somebody can send you a friend request;
• the gardens you have chosen to hide, kept so the Game can leave them out of what it shows you;
• a record that you accepted these Terms and this Privacy Policy — which document, which version of it, the time, and the app/config version you were running when you accepted. We keep this because it is the evidence that you agreed, and because a store or a regulator can ask us to produce it.

3.2 Your game progress

Your progress is stored on our servers so it survives a reinstall and so other players can visit your garden: your level and progression counters, currency balances (coins, gems, energy), the state of your board, your garden layout, plants, ornaments and appearances, your collection progress, defensive structures, daily counters, and your tutorial progress.

3.3 Things other players can see

Some of the above is visible to other players by design, because the Game has a social layer. When another player visits or raids your garden, or sees you in a list, they can see: your display name, avatar, level, your garden and what is in it, and the number of appreciation coins ("Favourite Coins") you have received. The Game may also suggest your garden to other players, and they can find it by typing the start of your display name; turning on Quiet Garden in the Game takes it out of both. Your account identifier travels with that public garden record — it is the address a visit or a raid is sent to, so it is visible to any signed-in player who is shown your garden. What they do not see is your currency balances, your purchase records, or your email address.

3.4 Purchases

If you buy something, the store (Apple or Google) processes the payment. We never receive or store your card number, bank details, billing address, or store password. We receive and store: which item was bought, the store's transaction identifier, the time, and whether it was later refunded — so we can grant what you paid for exactly once, and revoke it if it is refunded.

3.5 Gameplay analytics

The Game sends gameplay events to Google Firebase Analytics so we can understand how Bloom is played and where it is confusing or unfair. These are events about the game, not about you: which tutorial step you reached, that a plant was sold, that a level was cleared, that you ran out of energy, that a purchase screen was opened, that a rewarded advertisement was offered or completed, that a raid landed or was blocked, and similar. Each carries game context (item, tier, level, config version), and each is attached to your account id and to the Firebase app-instance identifier.

Firebase Analytics also collects, automatically: app instance identifier, device model and operating-system version, language and country, session and first-open events, app version, and a coarse approximate location derived from IP address (country, region and city level — not precise location; the Game never requests location permission).

3.6 Advertising

The Game shows rewarded video advertisements, which are always optional and which you choose to start. They are served by Google AdMob.

When an advertisement is requested and shown, the advertising SDK may process: your device's advertising identifier (Android Advertising ID, or on iOS the IDFA only if you have given permission), IP address, device and app information, coarse location derived from IP, and how you interacted with the advertisement. AdMob uses this to select the advertisement, to measure it, and — where you have consented — to personalise it.

AdMob may also tell our analytics (§3.5) how much money each advertisement shown to you earned us, and we keep that amount with your account id.

We also generate a one-time random token per advertisement so that the network's "this advertisement really was watched" callback can be matched to your account. That token is not shared with anyone but the network, and it is discarded once used.

Your choices are in §8.

3.7 If you link a third-party sign-in

Linking a sign-in is optional, and today the Game offers one: Sign in with Google. If you choose it, Google sends us, after you agree on Google's own screen, your Google account identifier, your email address, your name, and the web address of your profile picture. Firebase Authentication (§5) stores them on your sign-in record. The Game uses them only to sign you in and to recover your progress on another device: it does not display them, show them to other players, or use them for anything else. We do not receive your Google password, your contacts, or anything else in your Google account.

You can sign out in the Game at any time, which removes the Google link from your account. Deleting your account (§9) deletes the sign-in record and everything stored on it.

3.8 Anti-cheat, integrity and security

To keep the Game fair and our servers safe we process: app attestation results (Google Play Integrity on Android, Apple DeviceCheck on iOS, through Firebase App Check) confirming that requests come from a genuine, unmodified copy of the Game; server-side audit records of significant actions — a purchase grant, a raid, a support grant, an account reset — recording your account id, the action, and its parameters; rate-limit and abuse counters; and fraud-and-abuse flags — a record, raised by an automated check on unusual patterns in an account's coins, sales, refunds or Favourite Coins, that names your account id, what was measured and the threshold it crossed, for a person to review. A flag is a prompt for review: it does not by itself ban, limit or change an account.

3.9 Crash and performance diagnostics

If the Game crashes or stops responding, it sends a crash report to Google Firebase Crashlytics so we can find and fix the fault. A report contains: the error and the stack trace that produced it; device and app information — device model, operating system version, language, orientation, whether the device was rooted or jailbroken, free storage and memory at the time, and the Game's version; the anonymous account identifier from §3.1, so we can tell one player's repeated crash from many players' single ones; and a short trail of our own diagnostic breadcrumbs — which screen you were on, which action ran last.

A crash report never contains anything you typed, and it never contains your progress, your wallet, your purchases or your friends. Reports are sent when the Game next starts, not at the moment of the crash, so a crash that takes the app down still reaches us.

(We collect this because we cannot fix what we cannot see: the store measures the Game on its crash and not-responding rates, and a fault that only appears on one make of device is otherwise invisible to us.)

3.10 If you contact support

Support runs by email, and there is now also an in-game form: Help & Support → Contact → Report a problem.

If you write to bloom.mobile.game@gmail.com we hold your message and the email address you wrote from, and nothing else about you that you did not put in the message. If we need diagnostic information to answer, we ask for it and you paste it in — §9 says where to find it.

The in-game form holds more, and the list is fixed rather than something you choose: the message you type, the email address you give us for the reply (this is the one place in the Game we ask for it), and the category you choose (payment, account, bug, player report, or other), and, attached by us automatically: your player id, your level, your platform, the app version you are running, the config version your game is running, whether your account has ever made a purchase — a yes/no flag, never a list of what you bought — and, only when you report a garden from that garden's own page, the player id of the garden you are reporting, attached so that we can find the right garden (player names are not unique). There is no tick-box for any of this; the list above is everything we collect when you send a ticket, disclosed here rather than offered as an option to opt out of piece by piece. What you type is stored as you wrote it — we do not filter, summarise or moderate the message itself. A ticket is not a second, separate mailbox: replies happen by email, from the same published address above, to the address you gave us, no different in kind from writing to us directly. Retention is the same as any other support correspondence — see §10 — except that deleting your account removes your tickets (message, reply email and all) immediately as part of that deletion, sooner than §10's own window if it comes first; see "Erasure is permanent" below.

Your tickets are part of your data export. The copy of your account data the Game can hand you includes up to 100 of the tickets you opened from the in-game form (if you have more than that, the export says it was cut short). Each ticket comes with everything listed above — except the player id of a garden you reported, which belongs to that player and is left out — and with what we record about it after you send it: its state, its dates and, once it is closed, the note our support staff write when they close it. The other thing the export leaves out is which member of our staff closed the ticket.

3.11 What we do not collect

We do not collect: precise device location, your contacts, the photos on your device or your camera, your microphone, your health data, your calendar, your browsing history outside the Game, biometrics, or your payment details. The Game requests no runtime permissions beyond what the advertising SDK needs to show an advertisement, with one exception that you choose: on Android 13 and later, when you turn on the Game's energy notification, your phone asks whether the Game may show you notifications. Your phone schedules and shows that notification itself, and nothing is sent to us to make it work. Gameplay events (section 3.5) record when you turn it on or off, when one is scheduled and when you open one. You can turn it off at any time in Menu → Settings → Energy notification, or in your phone's own settings.

4. Why we use it, and our lawful basis (GDPR / UK GDPR)

Where we rely on legitimate interests we have weighed them against your rights, and you can object at any time (§9).

5. Who we share it with

We do not sell your personal data. We share it only with the service providers below, each acting under contract, and only for the purposes described.

We may also disclose data:

• when the law requires it — a court order, a lawful request from an authority, or to establish, exercise, or defend legal claims;
• to protect people — where necessary to prevent fraud, abuse, or harm, or to investigate a breach of the Terms of Use;
• in a business transfer — if Bloom Game is merged, acquired, or its assets sold, your data may transfer to the successor, who will remain bound by this policy or give notice of a new one.

6. International transfers

Our processors are primarily in the United States and operate globally. If you are in the EEA, the UK, or Switzerland, your data will be transferred outside your country. Those transfers rely on the European Commission's Standard Contractual Clauses (and the UK Addendum), or on an adequacy decision such as the EU–US Data Privacy Framework where the processor is certified, together with supplementary technical measures — data is encrypted in transit and at rest.

You may request a copy of the relevant transfer safeguards at bloom.mobile.game@gmail.com.

7. Children — COPPA and equivalents

Bloom is not directed to children and is not listed in a children's category on either store. The Terms of Use require players to be at least 18 years old (Terms §2), which is also how comparable games in this genre set their floor.

• We do not knowingly collect personal information from children under 13, and we do not knowingly offer the Game to anyone under 18 at all.
• The Game does not target children in its advertising: it is configured as a general-audience app for adults, and the advertising it shows is filtered accordingly.
• If you are a parent or guardian and believe someone under 18 has an account, contact bloom.mobile.game@gmail.com and we will close it and delete the associated data promptly, without needing anything from the child.
• We do not knowingly enable a child to make a purchase. Apple and Google both offer device controls that require a password for every purchase; we recommend enabling them.

8. Advertising choices

• iOS: before any tracking identifier is used, the system asks you for permission through App Tracking Transparency. If you decline — or if you never allow it — advertisements are non-personalised. You can change your answer at any time in Settings → Privacy & Security → Tracking.
• EEA, UK and Switzerland: you are shown a consent form before any personalised advertising. You can reopen it from Menu → Settings → Privacy choices and change your answer at any time.
• Android: you can reset or delete your advertising identifier in Settings → Privacy → Ads.
• Everywhere: declining personalised advertising does not stop you from watching rewarded advertisements or earning their rewards. It only means the advertisement you see is chosen without a profile.
• Google's own controls are at https://adssettings.google.com and its advertising practices are described at https://policies.google.com/technologies/ads.

9. Your rights, and how to use them

Depending on where you live you have some or all of the following rights over your personal data:

• Access — a copy of what we hold about you.
• Portability — that copy in a structured, machine-readable format.
• Rectification — correction of anything inaccurate.
• Erasure — deletion of your account and data.
• Restriction and objection — including objecting to processing based on our legitimate interests, and to direct marketing at any time.
• Withdraw consent — for anything we do on the basis of consent, at any time, without affecting what we did before you withdrew it.
• Not be subject to automated decision-making with legal or similarly significant effects. We do not make any such decisions. Automated anti-cheat measures can restrict an account; a human reviews any appeal you send to bloom.mobile.game@gmail.com.
• Non-discrimination — we will not degrade the Game because you exercised a right.

How to exercise them. Write to bloom.mobile.game@gmail.com from a device that has the Game installed, and include your player id — it is how we find an anonymous account. To read and copy it, open Menu → Help & Support → Contact; the cloud/sync chip's Diagnostics panel also shows it. We answer within 30 days (extendable by two further months for complex requests, with notice). We do not charge, unless a request is manifestly unfounded or excessive.

Verification. Because most accounts are anonymous, the only way we can verify that an account is yours is through the device that holds it. We may ask you to confirm the request from inside the Game. We cannot delete or export an account we cannot verify — this protects you from somebody else deleting your progress.

What your copy says about other players. Your copy lists your friends, the friend requests you received and sent, and the Favourite Coins you gave and received, as numbered lines — friend 1, friend 2, request 1, Favourite Coin 1 — oldest first. Each line says when it happened, and a friend or a request you received also says how it was made (by friend code). No line names the other player: their account id, player id, name, avatar and level belong to them, so they are left out. Your copy gives the gardens you have hidden only as a count, never which gardens they are.

Erasure is permanent. Deleting your account removes your progress, garden, currency, purchases, and any support ticket you opened — the message, the reply email you gave us, and everything attached automatically — and they cannot be restored. Some records are kept even after deletion where the law requires it — in particular purchase and tax records, and records we need to defend a legal claim. Those are kept in the minimum form needed. Security and fraud-prevention records (§3.8) — the server-side audit records and fraud-and-abuse flags that name your account id — are also kept after you delete the account, for the period in §10, on our legitimate interest in keeping the Game fair and secure.

California (CCPA/CPRA)

If you are a California resident: the categories we collect are identifiers, commercial information (purchases), internet or other electronic network activity (gameplay and advertising interactions), coarse geolocation inferred from IP, and inferences drawn for advertising. We collect them for the purposes in §4 and share them with the processors in §5.

We do not sell personal information for money. Showing personalised advertisements may be treated as "sharing" for cross-context behavioural advertising under the CPRA — you can opt out at any time by declining personalised advertising (§8), which is the mechanism we honour. You have the right to know, delete, correct, and to limit the use of sensitive personal information; we do not collect sensitive personal information as the CPRA defines it. You may use an authorised agent. Use bloom.mobile.game@gmail.com.

Complaints

If you are in the EEA or UK you may complain to your local data protection authority. We would rather you came to us first at bloom.mobile.game@gmail.com.

10. How long we keep things

11. How we protect it

Access to player data is restricted to the people who need it and is administrator-only. Our database is default-deny: a client can read and write only its own account, and only the fields it is allowed to own — currency, levels, another player's records and every friend connection are written exclusively by our servers. Requests to those servers are attested by Firebase App Check, so a modified copy of the Game is refused. Data is encrypted in transit (TLS) and at rest by our cloud provider. Administrative access is restricted to an explicit allow-list of accounts, granted individually and revocable at any time.

No system is perfectly secure. If a breach affects your personal data and is likely to result in a risk to you, we will notify the relevant supervisory authority within 72 hours where GDPR requires it, and notify affected players without undue delay.

12. Changes to this policy

We may update this policy. The effective date at the top changes when we do, and the current version always lives at https://bloom-12d81.web.app/privacy. If a change is material we will give notice in the Game before it takes effect, and where the law requires it we will ask for your consent again. In practice, the Game asks you to acknowledge this policy again inside itself whenever the version you last acknowledged is not the version currently in effect — the same first-run screen the Terms of Use share, shown again.

13. Contact

Bloom Game Privacy enquiries and rights requests: bloom.mobile.game@gmail.com Shlomo HaMelech St 72, Tel Aviv-Yafo, Israel