Privacy Policy

01. Who this policy is from

Bloom Craze is built and published by Jeevan Kumar, an independent developer based in India. This policy explains what the app does and does not do with information when you use it. In it, "I" and "my" refer to the developer, and "the app" refers to Bloom Craze.

02. Information I collect

I do not myself collect, store, or transmit any personal information about you. The app has no servers of mine that it talks to, and nothing you do inside it reaches me in a form that could identify you.

There is no account and no sign-in. You are never asked for an email address, a phone number, or any other identifying detail. The app lets you pick a display name if you like, and it stays on your device.

The app does include three Google SDKs that send some information to Google: Google AdMob — showing ads; Google Firebase Crashlytics — reporting crashes; Google Analytics for Firebase — measuring how the game is played. Each is described in its own section below. Here is what they receive, in one place:

Nothing else leaves the device: no name, no email address, no contacts, no precise location, no files. None of these services receives anything from me that could identify you, and all of them encrypt what they send in transit.

The game itself runs entirely on your device and works with no connection at all.

03. Data stored on your device

The app saves the following to your device's own storage so it can work between sessions:

• Your level progress and stars
• Your coins, hearts and garden tools, and the number of attempts you have made on each level
• Your settings, and the name and garden friend you pick. The name is never sent anywhere

The app never sends this data anywhere and I cannot read it. If you have Android's own backup turned on, Android may copy it to your Google account, which is between you and Google. It is removed when you clear the app's data or uninstall the app.

04. Advertising

Ads are served by Google AdMob, through the Google Mobile Ads SDK. The game shows a banner on the level screen, full-screen ads between levels, and optional rewarded videos that you choose to watch. To show them, the SDK sends Google your device's Advertising ID, technical details about your device and the app, and which ads were shown, viewed or tapped. Google also works out an approximate location, roughly to the city, from the IP address of your connection; the app itself never asks for location permission. Ad content is limited to Google's teen rating and no user is treated as a child. All of this happens inside Google's SDK: I never see or store it, and Google shares it with its advertising partners under its own terms.

How Google AdMob handles this information is governed by Google's own policy, which you can read here: https://policies.google.com/technologies/ads.

05. Crash reporting

If the app crashes, a diagnostic report is sent to Google Firebase Crashlytics so I can find the fault and fix it. The report describes the failure: the error, the stack trace, your device model and operating system version, and which build of the app you were running, along with a random installation identifier Google generates for the app on your device. To show what led up to the crash, it also includes the level being played and the most recent events described under Analytics below. It carries no name, no email address and no contact detail.

Crashlytics deletes individual crash reports after 90 days.

How Google Firebase Crashlytics handles this information is governed by Google's own policy, which you can read here: https://firebase.google.com/support/privacy.

06. Analytics

The app uses Google Analytics for Firebase to answer a handful of questions about how the game is played: whether levels get finished and how many attempts they take, how many stars and moves are left at the end, how coins and garden tools are earned and used, which offers people choose, how the ads between levels and the rewarded videos are used, and which features people unlock. The SDK also records installs, sessions, updates and uninstalls on its own, and, when an ad is shown, that it was shown and roughly what it earned. Every event is tied to an app-instance id, a random identifier the SDK creates for this installation; it identifies the installation, not you, and a fresh one is issued if you reinstall. Google also derives an approximate location from the IP address. The name you pick is not part of any event. The Advertising ID is deliberately not collected for analytics, so this data cannot be joined to the advertising profile above.

Google Analytics keeps the app-instance id and the events tied to it for 14 months, then deletes them automatically. Aggregated figures, such as how many levels were finished in a month, outlive that, but describe no individual device.

How Google Analytics for Firebase handles this information is governed by Google's own policy, which you can read here: https://firebase.google.com/support/privacy.

07. Your choices

Your Advertising ID is controlled by Android, not by the app. Open Settings → Privacy → Ads (on some phones, Settings → Google → Ads). There you can reset the ID, which breaks the link to anything collected under the old one, or delete it, after which apps receive a string of zeros in its place and ads can no longer be personalised to you. The app keeps working normally either way; you simply see less relevant ads.

Ads in this version. This test version shows only Google's sample test ads and does not yet include Google's consent form. Before the game shows real ads, that form will be added for regions where the law requires it, such as the European Economic Area and the United Kingdom, and this page will be updated. Analytics, described above, is on in this version.

08. Permissions the app requests

• Internet accessUsed to load ads, to send a crash report if the app stops working, and to send the analytics events described above. Every part of the game itself works with no connection.
• Network stateUsed by the ads SDK to check whether the phone is online before it tries to load an ad.
• Advertising IDRequested through Google's ads SDK so that AdMob can show ads, as described above. It is not collected for analytics.
• Android ad servicesDeclared by Google's ads SDK for Android's Privacy Sandbox ad features, on phones that have them. You control these in Android's own settings.
• Install referrerLets Google Analytics for Firebase see how the app was installed, such as from a Play Store link.
• Wake lock and foreground serviceDeclared by libraries inside Google's SDKs, so background work such as sending queued reports can finish. The game itself runs no background service.

The app does not ask for location, camera, microphone, contacts, or storage permissions.

09. Children's privacy

Bloom Craze is intended for people aged 13 and over. It is not directed at children under 13, is not part of Google Play's Families programme, and I do not knowingly collect information from anyone under 13. Because there is no account, the only name the app holds is a display name, if one is picked, and it stays on the device. If you believe a child under 13 has used the app and that information about them has reached one of the services above, contact me and I will help you address it, including through Google's own controls.

10. Keeping and deleting your data

There is no account, so there is nothing to delete on my side: I hold no data about you to request, export, or erase, and the app has no delete-my-account function because there is no account to delete. Everything the app saves lives on your device and is entirely under your control: clear the app's storage from your device settings, or uninstall the app, and it is gone from your device.

What Google receives through the services above is held by Google under its own retention rules, not by me:

• Google AdMob — governed by Google's advertising retention policies and by your Advertising ID. Resetting or deleting the ID, as described above, is how you break the link to anything collected under it.
• Google Firebase Crashlytics — Crashlytics deletes individual crash reports after 90 days.
• Google Analytics for Firebase — Google Analytics keeps the app-instance id and the events tied to it for 14 months, then deletes them automatically. Aggregated figures, such as how many levels were finished in a month, outlive that, but describe no individual device.

11. Changes to this policy

If the app changes in a way that affects this policy, I will update this page and move the effective date at the top. Material changes will also be noted in the app's release notes on the Play Store.

12. Contact

Questions about this policy, or about the app in general, reach me directly at g1mishra.dev@gmail.com. I read everything.