MoltKeeper Privacy Policy
Effective date: November 13, 2026
MoltKeeper is run by ReferenceNull LLC, a California limited liability company, 2108 N ST STE C, Sacramento, CA 95816, United States ("we", "us"). We decide how the data described here is used, which makes us its "controller" under European data protection law.
Contact for anything in this policy: moltkeeper@referencenull.com
In short
- The game makes an account for you so your Den is saved on our server. Adding an email, a Google account, Google Play Games or Steam is optional, and lets you get your Den back on another device.
- Other players see your keeper name, the creatures you release into the Wilds and your keeper page. Friends and clan members see a little more (section 2).
- We use your data to run the game, keep it fair, fix problems and see where new players get stuck. We do not sell it.
- An ad only plays when you tap Watch. Outside the EEA, the UK and Switzerland the Watch offers are on until you turn them off; there they are off until you turn them on (section 2, "Rewarded ads").
- We advertise the game on Google. On Android, Google Analytics for Firebase tells us how many people an ad brought who then opened and played the game (section 2, "Measuring our ads").
- Linking your account to our official Discord server is optional. If you do, we keep your Discord member number so the server can give you keeper roles (section 2, "The official Discord server").
- You can delete your account in the game at any time (section 6).
- Our servers and the companies that help us run the game are in the United States.
1. What MoltKeeper is
MoltKeeper (called Hatchkeep until October 2026) is a creature-building game for Android and Windows (Steam). You raise creatures from parts, fight stages, and can release copies of your creatures into a shared pool ("the Wilds") where other players meet them. This policy says what data the game collects, why, who else handles it, how long we keep it, and how to get it deleted.
2. What we collect
Account
- On a phone, a guest account is made for you the first time you open the game, without asking, so you can start playing at once. Our server makes it: we store an account identifier and a player id of our own. The phone keeps a random sign-in key, which our server stores only as a hash. A phone that has had a guest before shows a sign-in screen instead.
- If you attach an email address, we store the address and a hash of your password (PBKDF2, never the password itself), and whether you have confirmed the address. We send the emails that confirm the address and reset a password through Resend.
- If you sign in with Google (on Android), or put your Google account on a guest account, Google's sign-in service on your phone hands the game a sign-in token, which our server checks with Google. We store the identifier Google issues for the game and the email address on that Google account.
- Accounts made before October 18, 2026 were first made with Google Firebase Authentication and were moved to our own sign-in that day, keeping the same identifier. A password moved over was checked once with Firebase's own method and then stored our way.
- If you play on Steam, or link Steam to an existing account, we store your 64-bit Steam id. The sign-in is a Steam session ticket that our server checks with Valve, which also tells us whether you own your copy or play one lent to you through Steam Family.
- Your keeper name. You choose it, except on a Steam or Google Play Games account: on Steam the keeper name is your Steam profile name, which our server reads from Steam each time you sign in, so a change on Steam follows you into the game. For Play Games, see below. It is shown to other players on released creatures, boards, rankings and reports.
- With your account we also keep: when it was made and when it was last used, the language the game is set to, the version of the game you last played, whether it is a guest, the other sign-ins joined to it (for example a phone and a Steam copy sharing one Den), and whether "Steam friends can find me" is on.
- Playing on one device at a time. Each time the game starts it makes a random number for that launch and tells our server, so the server can tell you when your Den is open somewhere else. It is not an identifier of your device.
- Connecting a phone and a Steam copy. A transfer code you are shown lasts 10 minutes. If you join two accounts, we keep a record of which accounts were joined and when. A Den that was replaced in a join is kept for 30 days, so it can be brought back if the join was a mistake, and is then deleted.
- Verification. We record whether your account is verified, which way (Google, Google Play Games, Steam on a copy you own, or an email address whose link you opened), and when. Only verified accounts can use Keepers (friends, name reports and the boards), Rivals and leagues, to keep throwaway accounts out of them. A defense from an account that is not verified is not offered to other keepers, and what its released creatures earn is held and paid when it is verified. We can take verification away from an account that misuses Keepers; we record when we did.
Google Play Games (Android only)
If you play on Android with Google Play Games, we receive your Play Games player ID and display name from Google. We use the ID to find your Den on a new phone. Your display name becomes your keeper name, which other players can see, and we check it about once a day so a change follows you into the game. There are two exceptions: a Den that also opens with Steam keeps its Steam name, and a display name our word filter refuses or that is too short is not used. We don't keep Google's access tokens or read your real name.
If your Den is linked to Play Games, the game also sends your scores and progress to Google to show on Play Games, as your Play Games settings allow: your deepest floor, keeper level, generations raised and imprint wins for its leaderboards, and stages won, Wilds wins, Rivals wins and parts researched for its Game Stats. A Den that isn't linked sends none of this. We never read your Play Games rank back, and it changes nothing in the game.
If you delete a Den from the Play Games screen, we keep it for 30 days so it can be brought back if you ask, then delete it.
Game data
- Your creatures, parts, builds, research, expeditions, currencies (Chitin, Essence, Amber), stage results and replays, subscription tier, and cosmetics owned and worn. We also keep a record of Amber gained and spent, and of when you tried to buy something without enough Amber.
- Released creatures. When you release a creature into the Wilds, a copy of its build, the name you gave it, the short taunt you wrote for it (up to 60 characters) and your keeper name become visible to other players, who fight it and can view your keeper page. Recalling a creature removes it from the pool. Each day we work out a report for you of who fought your released creatures; it names the keepers who beat them.
- Reports on released creatures. If you report another player's creature, we store the report, the reason you gave and which account filed it. A creature reported by three different verified keepers is hidden from the Wilds automatically until we look at it.
- Name reports. If you report another keeper's name, we store who reported it, the name as it was shown, the reason you picked (offensive, pretending to be someone, or other) and when. Every name report waits for us to review it; reports alone never hide a name. When we review it, we may hide it (other players then see it as "Keeper" until its owner changes it; its owner still sees it, with a note asking them to choose another), change it to the keeper's default name ("Keeper_" and four characters of their player id), or leave it.
- Fair play. The server replays fights to check their results, either straight away or overnight. A result that does not match is recorded against the account and pays nothing, or loses its stars if it is found overnight, and an account that keeps sending results that do not match can be restricted. The game also notices when Replay is pressed in a way that looks automated. When it does, the buttons on the next result screen may change places, and we store against the account which sign it was, how close together the presses landed, the stage, the game version, how many times this has happened and when. We do not store where you tapped. We also note on the account when a fight could not have come from the real game, such as one handed in faster than it can be played: what we saw, the stage, how many times and when. Neither of these notes changes your game by itself; we may look at them when reviewing fair play.
Keepers: friends and Keeper Power
- Friends. Your friends list, the friend requests you send and receive, and the keepers you block. A request you did not answer is deleted after 30 days. A keeper you block stops being your friend, cannot send you a request, and is never told.
- What a friend sees: your keeper name, title and frame, the furthest chapter you have won a stage in, your deepest floor in the Deep, your Rivals rank this week, your favourite creature, your Keeper Power, and whether you last played today, this week or earlier. Never the time, your email or anything about your sign-in.
- Invites. Two keepers joined by an invite code are offered to each other as friends.
- Keeper Power is one number for how strong your creatures are: the strength of your six strongest creatures added up. It is shown on your keeper page, to your friends, on the Friends board, and, if you are among the 100 strongest verified keepers, on the Top keepers board. The boards give no rewards. Past weeks' Wilds boards keep the keeper names that were on them.
Leagues, achievements, generations and your keeper card
- Leagues. The teams you enter, the fights against them and your place on each league's ladder. Other keepers fight your league team and see it, your keeper name and your place.
- Achievements. Which achievements you have earned and when, worked out by our server from your game data. Each one shows the share of keepers who have it, counted over all keepers who played in the last 90 days, never naming anyone. You pick up to three to show on your keeper card. On Steam (PC only), the game also tells Steam each achievement you earn, and Steam shows it on your Steam profile as your Steam privacy settings allow. With Google Play Games, the game also tells Play each achievement you earn, and Play shows it as your Play Games settings allow.
- Generations. When you finish the campaign and begin again, we keep a record of each generation you finished and how. Your generation number and the title it brings are shown beside your keeper name.
- Your keeper card. Your keeper level, Den level and Keeper Power, and up to six more numbers you choose from your own records, shown on your keeper card to anyone who opens it.
Clans and the clan hunt
- Your clan. Which clan you are in, your role in it (leader, officer or member), when you joined, and the clans you have asked to join or been invited to. A clan's name and crest are chosen by its leader and shown to every player; clan names can be reported like keeper names.
- Clan messages. A clan's message board takes only fixed lines picked from a list (such as "Good fight"); there is no typing and no chat. We keep the clan's last 50 messages, with who sent each one and when.
- The weekly hunt. Each fight you have against the clan's hunt creature, the score the server works out for it, and your clan's place on the week's board. Clan members see each other's scores and whether they have fought today; everyone sees the clan boards.
The official Discord server
Linking is optional. If you press Get your role in the game (Options → Help & about) and type the code into our Discord server with /verify:
- What we keep. Your Discord member number (the number Discord gives every account), which game account it is linked to, and when. We never see or keep your Discord name, picture, messages or email. The codes themselves work once, for 15 minutes.
- What we use it for. Only to give your Discord account the server's keeper roles: Linked keeper, plus Keeper or Warden while you hold that subscription. Our server checks once an hour and changes the roles when a subscription starts or ends.
- What others see. Roles show in the Discord server, so its other members can see that your Discord account is a linked keeper and, while you subscribe, which tier you hold. They do not see which game account it is.
- Stopping. Type
/unlinkin the Discord server, or press Unlink in the game. The link is deleted and the roles are taken away. Deleting your game account does the same.
Friend duels and phone notifications
- Duels. When you invite a friend to a duel, we store the invite, both keepers' placements, the fight the server runs and its result. Your friend sees your creatures and where you placed them once both sides have placed.
- Phone notifications (Android only). If you turn on "Duel invites" in the game, so an invite can reach you when the game is closed, the game sends our server the notification address Google Firebase Cloud Messaging gives this app on your phone (a device token). We use it only to send you duel invites and answers. It is removed when you sign out or turn the switch off, and deleted if your phone has not refreshed it for 60 days. You can also turn notifications off in your phone's settings.
Steam friends (PC only)
To show which of your Steam friends play MoltKeeper, and to check that two keepers are Steam friends before a duel, we use your Steam friends list in two ways: the game reads it from the Steam app on your computer and sends your friends' Steam ids (at most 2,000) to our server, and our server can also ask Steam for it directly. We answer with the friends who play MoltKeeper and have not turned off "Steam friends can find me". We use the list only to answer that question at that moment: we do not store it, keep it in our logs, or use it for anything else. Steam only shares a friends list that your Steam privacy settings make visible. To stop other Steam players finding you this way, turn off "Steam friends can find me" on the Keepers screen or in Options. Blocking a keeper also stops them finding you.
Purchases
- Purchases are made through Google Play or Steam. **We never receive card numbers or billing addresses.**
- On Android, RevenueCat processes Google Play receipts for us. RevenueCat and we receive: the product bought, the time, the store's transaction and subscription identifiers, and your account's identifier, which RevenueCat uses as its app user id.
- On Steam, Valve tells our server that an order was approved and for which Steam id, and our server asks Steam for your country and currency so the price is shown and charged correctly. We store the product, amount, currency and country with the purchase. If you buy through Steam's web checkout, our server passes your IP address to Valve, which Valve requires for that checkout.
Rewarded ads (Android only)
- An ad only plays when you tap Watch on an offer, such as hurrying research or doubling a stage's rewards. The switch Optional ad offers in Options shows or hides these offers.
- Outside the EEA, the UK and Switzerland the offers are on until you turn them off, and Google's ad SDK starts when the game does, so an ad is ready when you tap. Turning them off (Options, or "Hide ad offers" in the first research lesson) is kept, and from the next launch Google's ad SDK is not started.
- While offers are on, Google AdMob loads and shows the ads. Google collects the device's advertising identifier, IP address, and device and app information, and may use it to choose ads based on your activity in other apps. How Google uses this information: https://policies.google.com/technologies/partner-sites and https://business.safety.google/privacy/. You can reset or delete the advertising identifier in your phone's settings.
- AdMob can also fill an ad from Unity Ads, the ad network of Unity. Its code runs in the game while offers are on and collects the same kinds of information for its own use: https://unity.com/legal/privacy-policy.
- Before Google's ads load, the game asks Google Play Integrity whether it was installed from Google Play on a genuine device, and we keep the answer and when it was given. A phone that has not passed sees our own ad instead, which pays the same reward and sends Google nothing.
- While offers are on, the switch Personalised ads in Options turns personalisation off: the game then asks Google and the ad networks it works with for ads that are not chosen from your activity in other apps and sites, and for restricted data processing, and Google Analytics stops using your device for ad personalisation.
- In the EEA, the UK and Switzerland the offers are off until you turn them on, and turning them on first opens Google's consent form, where you choose whether ads may use your data to be personalised. Nothing of Google's ad SDK starts before you answer. To change your answer later, use Privacy choices for ads in Options. If you say no, you may still see ads that are not personalised.
- Ads are limited to content rated Teen (T) or below, the same as the game's own rating.
- When you finish an ad, Google sends our server a signed message with your player id and which reward it was for. We keep a record of each reward paid. That is all our server learns from an ad.
- Our own in-game offers (not ads from anyone else) record which you were shown and when; nothing about them leaves our server.
Play events
To see where new players get stuck and which lessons lose them, the game sends our server a short note when certain things happen on your device, mostly the first time: the game opened (and opened again on a later day), the opening scene, the sign-in screen shown, which way you signed in, an account connected, the save reminder shown, each tutorial step reached, the first start and first win of each stage in chapter 1, what's-new and rating prompts shown and answered, offline rewards collected, ads paid and from which ad network, and the Replay button changing place. Each note is just its name and the time on your device; our server adds your player id. We keep them for 7 days, then delete them. Play events go only to our server; the one analytics service from another company is the ad measurement below.
Measuring our ads (Android only)
We advertise MoltKeeper on Google. To learn which ads bring people who actually play, rather than people who download the game and never open it, the Android game uses Google Analytics for Firebase:
- It records the first time the game is opened, and five moments of play: coming back on a later day, and your first win at stages 1-1, 1-3, 1-6 and 1-12. Google Analytics also records, by itself, purchases made through Google Play and the rewarded ads you watch.
- With these, Google collects the phone's advertising identifier, an identifier for this install of the game, the IP address (used to estimate your country, then not kept), and the phone's model, system version, language and the game's version. Google matches this with the Google ads you saw or tapped, and shows us totals, such as how many players an ad brought. It does not get your player id or keeper name from us, and we do not get your advertising identifier from it.
- In the EEA, the UK and Switzerland nothing is collected unless you agreed, in Google's consent form, to information being stored on your device; measuring ads and personalised ads each follow your answer for them. The form appears when you turn Optional ad offers on, so if you never do, nothing is collected. To change your answer, use Privacy choices for ads in Options.
- Elsewhere it runs from the first time the game is opened. You can reset or delete the advertising identifier in your phone's settings, and Google then stops linking it to you.
- Google keeps this data for 2 months, then deletes it. The PC game has none of this.
Errors and crash reports
- When the game fails at something (for example a sign-in that does not go through), it sends our server what failed, the error's text and where in the game it happened, the game's version, and your device model and operating system. These reports carry no player id.
- When our server fails on one of your requests, it records the error, the request's path, the game version and your player id, so we can find and fix it.
- Unity, the engine the game is built with, receives anonymous statistics about the hardware the game runs on (for example the graphics chip and memory), under Unity's own policy (https://unity.com/legal/privacy-policy).
Server logs
Our servers write a log line for each request: its time, path and result. It does not contain your IP address. Our servers hold IP addresses only in memory, for a short time, to limit how many requests one address can make. The log lines stay with Fly.io, which runs our servers, for the short time it keeps logs; we do not copy them anywhere else.
Bug reports
If you send a report from Options > Report a problem, we store what you wrote, the category you picked, the game's version, your device model and operating system, your player id, and the email address on your account if it has one. We read it on our own systems and, if your account has an email, may reply to you. Reports sent before this change were also emailed to us through Resend.
Invites
- Every keeper has an invite code. If you join with a friend's code, we store that you were invited, by whom, when the invite link was clicked and the game installed, and when your first clear of stage 1-10 paid them.
- To stop one person inviting themselves, the game sends our server your device's identifier (on Android, the id Android gives this app; on a computer, the game engine's device id). The server keeps only a one-way hash of it, never the identifier itself, and uses the hash only to tell one device from another.
- On Android, an invite is checked with Google Play Integrity: Google tells our server whether the game was installed from Google Play on a genuine device. Google Play also passes the invite code from the link to the game when it is installed (the install referrer).
Settings on your device
Most settings (sound, text size, tutorials, the Optional ad offers switch) are kept on your device only.
3. Why we use it, and on what legal basis
European data protection law asks us to name a legal basis for each use. Ours are:
| What we do | Data used | Legal basis |
|---|---|---|
| Run your account and the game: progress, the Wilds, friends, clans, duels, boards, connecting devices | Account, game, Keepers, clan and duel data | Our contract with you: the game you asked to play |
| Sell and deliver purchases | Purchase records | Our contract with you |
| Send duel notifications | Device token | Our contract with you, once you turn the switch on |
| Show which Steam friends play | Steam friends list, used once and not kept | Our legitimate interest in helping you find friends; you can turn it off |
| Keep the game fair and safe: reports, verification, fight checks, request limits, invite checks | Reports, verification, fight results, signs of automated play, IP address in memory, device hash, Play Integrity result | Our legitimate interest in a fair game that cannot be abused |
| Find and fix problems | Error and crash reports, server errors, bug reports | Our legitimate interest in a game that works |
| See where new players get stuck | Play events (7 days) | Our legitimate interest in improving the game |
| Measure which of our ads bring players (Android) | Data Google Analytics for Firebase collects | In the EEA, the UK and Switzerland, your consent in Google's consent form; elsewhere, our legitimate interest in knowing whether our advertising works |
| Rewarded ads | Data Google collects | In the EEA, the UK and Switzerland, your consent, given by turning Optional ad offers on and in Google's consent form; elsewhere, our legitimate interest in paying for a free game with ads you choose to watch, and you can turn the offers off |
Where we rely on our legitimate interest, you can object, and you can ask us how we weighed our interest against yours.
What you have to give us. An account identifier is needed to play; the game makes one for you. Everything else is optional: an email, Google, Google Play Games or Steam (they let you recover your Den), a keeper name of your own, bug reports, notifications and ads.
Automatic decisions. We make no decision about you by automated means alone that has a legal or similarly significant effect. Some checks are automatic: an invite reward is refused, and our own ads are shown in place of Google's, when Google Play Integrity or our device check says the install is not genuine; a creature reported by three keepers is hidden from the Wilds; fight results that do not match the server's replay are recorded; and the buttons on a result screen can change places when Replay looks automated. Email us if you think one of these was wrong, and a person will look at it.
4. Who else handles your data
These companies handle data for us, only to provide their service, under their own terms for handling data on a customer's behalf:
| Company | What it does | Where |
|---|---|---|
| Google Firebase Cloud Messaging | Delivers duel invites to your phone when the game is closed (Android only) | United States |
| Google Play Integrity | Checks that an invite, or a phone about to load Google's ads, is a Play install on a genuine device (Android only) | United States |
| Neon (PostgreSQL on AWS) | The game database | AWS us-west-2, United States |
| Fly.io | Runs our game servers | San Jose, United States |
| RevenueCat | Processes Google Play receipts | United States |
| Resend | Sends the emails that confirm an address and reset a password | United States |
| Unity Technologies | Receives anonymous hardware statistics from the game engine | United States |
These companies act on their own account, under their own privacy policies:
| Company | What it does |
|---|---|
| Google Play, Valve (Steam) | Sell the game and its products; Steam also provides sign-in and your Steam friends list, and shows the achievements you earn on PC; Google Play Games also provides sign-in and shows the achievements you earn on Android |
| Google AdMob | Shows rewarded ads, only while they are on (see section 2) |
| Unity Ads (Unity) | Fills some of those ads through AdMob, only while they are on (see section 2) |
| Google Analytics for Firebase and Google Ads | Measure which of our ads bring players (Android only, see section 2) |
| Discord | Runs the official MoltKeeper Discord server; if you link your account, we tell it which keeper roles to give your Discord account (see section 2) |
We do not sell personal data, and we do not share it for advertising based on your activity across other apps or sites, except what Google AdMob and Unity Ads collect themselves while ad offers are on, and what Google Analytics for Firebase collects to measure our own ads (section 2). We share it with no one else except when the law requires it.
Data outside your country. We are in the United States, and the game's servers and the companies above process data there. Where a company takes part in the EU-US Data Privacy Framework (and its UK and Swiss extensions), that is the safeguard; otherwise it is the European Commission's standard contractual clauses in that company's terms. Write to us for details.
What other players can see: your keeper name, your title and frame, your generation, the creatures you have released (their build, name, taunt and cosmetics), your league teams and ladder places, and your keeper page and card, which show your Keeper Power and how far you have got, your keeper and Den levels, the numbers and achievements you chose to show, your Rivals defense, and your clan's name, crest and hunt board. Your friends also see what is listed under "Keepers: friends and Keeper Power", and your clan sees what is listed under "Clans and the clan hunt".
5. How long we keep it
- Your account and game data: until you delete the account.
- A guest account (one with no email, Google, Play Games or Steam on it) that has not been opened for six months: deleted, with its game data, the way a deleted account is. Only the device that made a guest can open it, so one unused that long has almost always been uninstalled. A guest that has made a purchase, or is joined to Steam or another device, is kept.
- A Den replaced when two accounts are joined, or deleted from the Play Games screen: 30 days. Transfer codes: 10 minutes.
- The record of which accounts were joined: 1 year.
- Purchase records: with your account. Google Play and Steam keep their own records of what you bought, under their own policies.
- Play events: 7 days.
- Ad measurement data at Google Analytics for Firebase: 2 months.
- Error and crash reports, and server error records: 90 days.
- Stage replays and Rivals fight logs: 30 days. Wilds fight records: 14 days. Friendly challenges: 30 days.
- Reports on released creatures, daily Wilds reports, and past weeks' Wilds boards: 90 days.
- Name reports: until resolved, then 90 days.
- Friend requests: 30 days, answered or not.
- Friends, blocks and verification: until you delete the account.
- Steam friends lists: not kept at all.
- Clan membership: while you are in the clan. Clan messages: the clan's last 50.
- The link to your Discord account: until you unlink it or delete your game account. Discord role codes stop working after 15 minutes and go with your account.
- Duel invites: 7 days after they are answered or end. Finished duels: 30 days.
- Phone notification tokens: until you sign out or turn them off, or 60 days after your phone last refreshed one.
- Bug reports you send: until we have dealt with the report, then 90 days, or until you delete the account if that comes first. The email copy of an older report in our inbox is deleted with it when you ask.
- Rewarded ad records, the Amber record, the Play Integrity answer before ads, and the fair play notes about Replay and impossible fights: with your account.
- Invites: with your account. If you were invited and delete your account, the record that your invite was paid, with your device hash, is kept so the same invite or device cannot pay twice.
- Backups. Our database keeps a rolling history for recovering from faults, and before each update of the game's servers we keep a restore copy of the database. Both are deleted within 30 days. Deleted data stays in those copies until they go; we do not restore it except to recover from a fault, and if we must, we delete it again. For an account made before October 18, 2026, Firebase removes its old sign-in from its own backups within 180 days of its deletion.
- We may keep counts and statistics that cannot identify you, such as how many players cleared stage 1-10.
6. Deleting your account
- In the game: tap your name at the top left to open your keeper page, then Delete account under Account, and type DELETE to confirm. It takes effect at once.
- If you can no longer open the game: email moltkeeper@referencenull.com from the address on the account, or include your keeper name and player id, and we will delete it within 30 days.
- Deletion removes your account, creatures, progress, currencies, cosmetics, purchase records and entitlements from our servers, and the sign-in behind it (and, for an account made before October 18, 2026, its old Firebase sign-in). Your friends list, your friend requests sent and received, your blocks, the name reports you filed and the ones filed about you go with it, and you disappear from other keepers' friends lists and boards. Your clan membership, the clan messages you sent, your hunt fights, your duels and duel invites, your play events and your phone notification tokens go too. If you led a clan, it stays for its other members and a new leader takes over.
- Creatures you released into the Wilds are anonymised, not removed: the build, its creature name and taunt stay in the pool with no keeper name attached, because other players' stage histories refer to it. Server error records with your player id, and the other items in section 5 with their own time limits, are deleted when that time runs out.
- Deleting the account does not cancel a subscription. Cancel it in Google Play or Steam; those stores control billing.
- Steam, Google (including Play Games), RevenueCat, AdMob, Unity Ads and Unity keep whatever their own policies say about the data they collected. Google Analytics' ad measurement data is not linked to your account, so it is not deleted with it; it goes after 2 months, or sooner if you delete your advertising identifier.
7. Your rights
Depending on where you live (including the EU/EEA, the UK, and California and other US states) you may have the right to:
- see the data we hold about you and get a copy of it;
- correct it (change your keeper name in the game; email us for anything else);
- have it deleted (section 6);
- object to our using it, or ask us to limit how we use it;
- withdraw consent you gave, at any time, without affecting what happened before (for ads, turn Optional ad offers off, or change your answer in Privacy choices for ads);
- complain to us, and to your data protection authority: in the UK the Information Commissioner's Office (https://ico.org.uk/make-a-complaint), in the EU the authority in your country (https://edpb.europa.eu/about-edpb/about-edpb/members_en).
Write to moltkeeper@referencenull.com. We acknowledge a complaint within 30 days and answer a request within one month (we will tell you if we need up to two more months for a complicated one). We may ask you to show the account is yours. We do not treat anyone differently for using these rights.
California. We do not sell personal information or share it for cross-context behavioural advertising as California law defines those terms, other than what Google AdMob and Unity Ads collect themselves while ad offers are on, and what Google Analytics for Firebase collects to measure our own ads. To opt out of ads chosen from your activity, turn Personalised ads off; to stop those ads altogether, turn Optional ad offers off; to stop the ad measurement, delete your advertising identifier in your phone's settings. The game has no web browser and does not respond to "Do Not Track" signals. Apart from those, no other company collects information through MoltKeeper about what you do over time across other apps or websites.
8. Children
MoltKeeper is not meant for children under 13, and we do not knowingly collect data from them. If we learn that an account belongs to a child under 13, we delete it. If you believe one does, email moltkeeper@referencenull.com. In countries that set a higher age for agreeing to data use, rewarded ads are not meant for anyone under that age.
9. Keeping your data safe
Everything between the game, our servers and the companies above travels encrypted (HTTPS). Only the developer can reach the servers and database. Passwords are stored only as salted hashes (PBKDF2), never as the password itself. No system is perfectly safe; if a breach puts your data at risk, we will tell you, and the authorities, as the law requires.
10. Changes
We will post changes here and update the effective date. If a change matters (a new company handling your data, a new kind of data, a new use), the game will tell you when you next open it.