English · Português
Effective date: 2026-07-27 · Last updated: 2026-09-25
Melbees (“the app”, “we”) is provided by Melbee Games, Brazil, which is the controller of the data described in this policy. For any privacy question or request, write to melbees.games@gmail.com.
This policy explains what information Melbees handles, how, and what your choices are. It applies to the Melbees game distributed on Google Play, in every country where it is available. If the game is ever distributed through another store, this policy will be updated first.
Depending on where you live, besides Brazil's LGPD (Law 13.709/2018) the GDPR of the European Union and the United Kingdom, the United States' COPPA and other local laws may apply to you. Section 15 describes the rights each of them gives you and how to use them.
Melbees keeps the following on your device only, so the game can work; none of it is sent to us or to any server:
Deleting the game, or using Settings → Delete my data, removes all of it.
If you signed in with Google, the device also keeps your account session, as section 8 describes.
Melbees is a general-audience, family-friendly game, and we know that children and teenagers play it. That is why the version of the game everyone gets is already the version a minor is allowed to have: there is no chat, no messaging between players, no nickname you choose on the leaderboard, no paid random reward, and no advertising profile built out of what you play.
There is no age screen at the door and no parental gate. A date-of-birth form is trivially bypassed by a child, and a weak control gives parents a safety that does not exist. The strong control is the parents', at the platform: Google Family Link and Google Play's purchase approval. Section 12 says where they are.
The one thing that needs an age is the ad, because the advertising rule is different for each band. So, the first time an ad is about to be shown, the game asks your age once:
United States. We do not knowingly collect personal information from children under 13 for the purposes COPPA restricts. European Union and United Kingdom. Some countries set the age at which a teenager can consent alone anywhere between 13 and 16; where that limit is higher than ours, ad personalisation depends on the valid consent described in section 6.
If you are a parent or guardian and believe a child has sent us personal information — through the feedback screen, for instance — write to melbees.games@gmail.com and we will delete it.
The game shows rewarded ads, and only those. There is no banner, no interstitial, and no ad ever appears by itself: one is shown only after you tap to earn an extra Petal when you lose your last one. If you never tap, you will never see an ad.
Ads are served by Google AdMob, which acts as an independent controller of the data it receives. The treatment of each request depends on the band from section 5:
For a personalised ad, AdMob receives your device's advertising identifier — an identifier you can reset or delete yourself in the Android settings, under Google → Ads. We do not receive it, we do not store it, and we do not use it anywhere else in the game, analytics included (section 10).
The game offers three items, and none of them is required to play: two Petal packs (one-off purchases) and the monthly Premium subscription. There is no loot box: you always know exactly what you are buying, and nothing bought turns into a draw.
The account is optional, and you need none to play or to buy. The game never asks you to sign in on launch. It offers the sign-in for two things only, and signing in is always an action of yours: the online leaderboard and restoring a subscription on another device. A subscriber who has not signed in also sees that offer as a quiet line before a game, saying it will not reach the online leaderboard without the account, and as a button on the screen that celebrates the subscription. Neither stops you from playing.
The account is Google only: no e-mail-and-password sign-up, no anonymous login. When you sign in, Google confirms to us that it is you, and of what it sends us we keep only an opaque account identifier — a meaningless string that lets us recognise you next time.
We do not store your name, your picture or your e-mail address.
So that you do not have to sign in again every time you open the game, the session is kept on this device: only the credential that renews it, never your name or your e-mail. It is encrypted, with a key Android creates and that never leaves the device, and it sits in a place Android keeps out of backups and out of transfers to another device, so your session never shows up on a device you did not sign in on. It is erased when you tap Sign out, Delete my data or Delete my account, or when you uninstall the game. Opening the game does not connect to the account: the session is used only when something needs it, such as the online leaderboard.
If — and only if — you enter the online leaderboard, this leaves your device:
What the public sees is only the fifty best marks of each board: rank, generated name and time. No identification of who played appears there, neither to other players nor to anyone looking from outside.
The raw list of moves is deleted 60 days after submission; the time and the rank stay for as long as your account exists. We do not store your IP address: the server uses it in memory only, at the instant of the call, to rate-limit requests, and it is never written to a log or to any column.
We use Google Analytics for Firebase and Firebase Crashlytics to know whether the game works and where it breaks. They are configured as internal operations, and that configuration is the reason we can use them with every player:
What is recorded are game events, such as a run started or finished, the Premium screen being seen, a purchase completed, a Petal obtained by ad, by purchase or for free, and a subscription starting or lapsing. The events are the same for every player. Alongside them go those services' standard technical data: the device model, the system version, the country and the language.
What changes with age, and only this. Before the first ad, the game asks your age (section 6) and keeps only the band.
Crash reports are the same for everyone. Whatever your age, and whether or not you answered, when the game fails Crashlytics sends a crash report: the error's stack trace, the state of the game at that moment and the device's technical data above. The only identifier it carries is an installation identifier, made of a random number Crashlytics generates itself and Firebase's installation number; it identifies this installation of the game, not you. It carries no name, no e-mail, no text you wrote and not your age band.
Your age band decides what analytics keeps on your device and is not sent. Settings → Delete my data also reaches Firebase: it stops sending the game's errors to Crashlytics at once, erases Firebase's installation number (on the device and on Firebase's servers), denies every storage again and erases from the device the analytics data, before erasing the rest. Crashlytics stays off until you close the game. The next time the game opens, it first erases any crash report still waiting on the device, unsent; then Crashlytics works again as for everyone, with a new installation identifier. If a report had to be erased, Crashlytics stays off in that opening, and each later opening checks again; it works again from the first one that finds nothing waiting. Erasing the installation number needs an internet connection: without one, the game tells you the deletion was not complete, and you can try again. After it, the game treats you as someone who has not answered.
What this does not erase. What had already been sent stays with Google, tied to identifiers that no longer exist on your device, and is erased by the retention period: 2 months for analytics data and 90 days for crash reports.
The game has a Send feedback screen (Settings ▸ Account) and a per-word report on the results screen. They exist so you can tell us about a problem, a wrong word, an idea or a compliment. There is no automatic sending: nothing leaves the device until you tap “Send”.
What is sent, and nothing beyond it: the category you chose (one of four fixed labels), your message as free text, and a technical block the app assembles and shows you on screen before you send — the app version and build type, the platform and the operating-system version string cut at 40 characters (on Android this is usually a kernel line, not the device model), the interface language, the tap mode, the screen you were on, and a list of up to 20 recent actions as internal game codes. Errors appear as a label from a closed list, never the error message and never the stack. A per-word report also carries the category, subcategory, secret count, phase and the word's internal identifier.
Important: the message field is free text and reaches us exactly as you wrote it. Do not write your name, e-mail, phone number, address or any other personal information there — yours or a child's. We do not need it to fix the game, and the app says so under the field.
Where it goes. The report is sent over HTTPS to a Google Apps Script service operated by Melbee Games, which appends it as a row in a Google Sheets spreadsheet of ours, with access restricted to us. Google acts only as a hosting provider, under its own terms. Nothing is sold, shared with third parties, used for advertising or used to build profiles.
The row carries no identifier tied to you. There is no account, no device id, and we do not keep your IP address — in practice we cannot link a report to a person, or join two reports from the same person, except by what is written in them.
If sending fails, the app says so (it never says “sent” when it did not) and offers two ways out, both started by you: opening your e-mail app with a pre-filled message — if you send it, we come to know your address, because it is ordinary e-mail — or copying everything to the clipboard.
How long we keep it, and how to delete it. We keep the row while it is useful for fixing what it describes and, in any case, for at most 24 months. You can ask for it to be deleted sooner by writing to melbees.games@gmail.com. Because the rows carry no identifier, we need your help to find yours: tell us the date you sent it and an excerpt of what you wrote. We delete the matching rows and confirm by e-mail. Without those two details we cannot locate your report — not out of refusal, but because the spreadsheet stores nothing that ties a row to a person.
Inside the game, under Settings, there is a For parents and guardians page. It asks for no age, sits behind no purchase, and shows:
The game measures and shows time of use and never interrupts a run. It also sends no notifications, gives no reward for time spent connected, and has no daily streak that is lost by missing a day.
We do not sell your data and we do not give it to data brokers. The services below are the only ones that receive anything, each for one purpose:
We may also disclose data where the law requires it, to comply with an order from a competent authority, or to investigate fraud and abuse of the leaderboard.
The services above run servers outside Brazil, so the data described here may be processed in other countries, under those providers' contractual safeguards — including the standard contractual clauses that apply to transfers out of the European Union and the United Kingdom.
The LGPD gives you, among others, the rights of confirmation, access, correction, anonymisation, portability, erasure, information about sharing, and withdrawal of consent. Where the GDPR applies, you also have the rights to object, to restrict processing and to portability, and the right to complain to your country's data-protection authority — in Brazil, the ANPD.
In practice:
The legal bases. We perform the contract of using the game in order to make the game work, deliver what you bought, and keep your account and the leaderboard (LGPD art. 7 V; GDPR art. 6(1)(b)). We rely on legitimate interests to fix defects, to measure whether the game works, and to defend the leaderboard against cheating (LGPD art. 7 IX; GDPR art. 6(1)(f)). We rely on your consent for personalised advertising where it is required (LGPD art. 7 I; GDPR art. 6(1)(a)), and you may withdraw it at any time. We also comply with legal obligations, such as those of Brazil's Law 15.211/2025, the Digital Statute of the Child and Adolescent (LGPD art. 7 II; GDPR art. 6(1)(c)).
Everything that leaves the device travels over HTTPS. Access to the leaderboard database and to the feedback spreadsheet is restricted to us. No system is perfect and we cannot promise absolute security — but we hold no password of yours, no payment data and no IP address, which sharply limits what an incident could expose.
We may update this policy; the “Last updated” date will change and, for material changes, we will say so inside the app. A new feature that sends data is only switched on after this page has been updated, never before.
Melbee Games — Brazil
melbees.games@gmail.com