Capybara Boy

Privacy Policy

Effective 16 November 2026. Applies to the Capybara Boy: Epic Adventures mobile game ("the game") published by IdeaInTech (Roman Iakovlev) ("we", "us").

The short version

The game has no accounts, no sign-in, no advertising and no in-app purchases. It works offline. Four things can reach the internet, all described below. Two happen on their own: the game downloads some of its music from our servers instead of carrying it inside the app, and it keeps a copy of your level progress on our servers under a random identity that belongs to your installation of the game, not to you; you can turn the cloud copy off, or delete it, at any time from the game's SETTINGS screen. Two happen only if you turn them on: play statistics and crash reports, which Google's Firebase service processes for us. Both are off until you choose, the game asks you once when it first opens, and you can change either choice at any time in SETTINGS → DATA. You can play the whole game with both off.

What the game stores on your device

The game keeps a few small files in its own private storage on your device: your sound and music volume settings, your level progress (which adventures are open, how many times each has been finished, which one-time hints have been shown, and the lasting rewards a run has earned), the run in progress of a level, downloaded music, a note of which cloud version your progress was last compared with, and your choices about play statistics and crash reports (each choice, when you made it, which version of the explanation you saw, and whether you made it on the first-launch screen or in SETTINGS). While play statistics or crash reports are turned on, Google's software also keeps its own working files on your device: the random code it gave this installation, events or a crash report waiting to be sent, and its settings. The random identity for the cloud copy is kept in the device's protected storage (the iOS Keychain or Android Keystore). These files are deleted when you delete the game, except where the platform keeps protected storage, which it may.

Music downloaded from our servers

The music of the game's levels is downloaded the first time each level is played and kept on your device afterwards. The download is a plain request for a file; it carries no identifier and no information about you. The servers that deliver it (Google's Firebase Storage) see your device's network address, as any server does, for the time of the download. If you are offline, the level plays the game's built-in music instead.

Cloud copy of your progress

So that your progress is not lost if your device's copy is damaged, the game keeps a copy of your level progress on our servers (Cloudflare). To do this it creates, the first time it needs to, an anonymous identity: a random identifier and a random secret, generated by our server and known only to your installation of the game. The identity contains nothing about you, is not linked to any account, email address, name, device identifier or advertising identifier, and cannot be used to recognise you anywhere else.

What is sent and stored under that identity: the level progress listed above (which adventures are open, how many times each has been finished, which hints have been shown, which lasting rewards have been earned), a version number, and the version of the game that sent it. Nothing else: not your settings, not your name, not your location, not what you did in a level. Our server also records the time of the last contact, which is used only to delete identities that have not been used for two years.

This is a device-scoped copy, not an account. There is no way to sign in, to move progress to another device, or to recover the cloud copy if the identity is lost. If the game is deleted and reinstalled, the identity may or may not survive in the device's protected storage, depending on the platform; if it does not, the game creates a new identity and the old cloud copy becomes unreachable (it is deleted by our server after the retention period). Your progress on the device itself is never affected by any of this: it is kept locally first, and the game is fully playable without any network connection.

Purpose: keeping a backup of your level progress. Retention: until you delete it, or two years (730 days) after the last contact from your installation, whichever comes first; every contact the game makes under the identity counts as activity.

Turning it off: the game's SETTINGS screen has a CLOUD SAVE section with a TURN OFF button. Off, the game sends and fetches nothing; the copy already in the cloud is not deleted by this -- it stays until you delete it or it expires -- and TURN ON resumes with the same identity.

Deleting it: the same section has a DELETE CLOUD SAVE button, which asks you to confirm and then removes the cloud copy and the identity from our servers at once; your local progress stays, and cloud save is then off. The game only reports the deletion as done when our server has confirmed it; if the server could not be reached, nothing is changed and you can try again. Turning cloud save on after a deletion creates a new identity starting from your device's progress. You can also ask us to delete a copy by email, giving the date and approximate time of your request from the game, since we have no other way to tell your identity from any other.

Play statistics and crash reports: your choice

The game can send us two kinds of optional information, through Google's Firebase service: play statistics (ANALYTICS in the game) and crash reports (CRASH REPORTS in the game). They are two separate choices. Both are off unless you turn them on.

The first time the game opens after this version is installed, it shows a screen called HELP US IMPROVE CAPYBARA BOY with the two switches, both off, a link to this policy, and a CONTINUE button. Nothing is sent before you have passed that screen, and nothing is sent afterwards unless a switch is on. CONTINUE with both switches off is a complete answer; the screen is not shown again. You can play the whole game whichever way you choose.

You can change either choice at any time in SETTINGS → DATA, where each switch shows whether it is on and, if so, since when. Turning a switch on starts that kind of sending; turning it off stops it. Each switch works on its own: turning off crash reports does not turn off play statistics, and the other way round.

Turning a switch off stops future sending from your device. It does not remove information that has already been sent to Google; that information is kept and deleted according to the retention periods described below. When you turn play statistics off, the game also tells Google's software to forget the random code it had given this installation and to throw away any events still waiting on your device, so that turning statistics on again later starts as a new installation. When you turn crash reports off, the game throws away any crash report still waiting on your device; Google's crash recorder itself stops completely the next time the game starts.

Where the law requires it, we rely on your consent for both kinds of information: the switch you turn on is that consent, and turning it off withdraws it.

Play statistics (ANALYTICS)

What is sent. Moments of play, each with the name of the level and world concerned and nothing about you: the title screen opening; the settings opening; the controls card appearing and being put away the first time; a level being chosen, started, won (with how long it took and how many times you have finished it), lost, restarted, continued or left; a friend being freed; a character or a new world being unlocked. Google's software adds, by itself: that the game was opened for the first time, each time it is used and for how long, when it has been updated, whether it crashed; the game version, your device model, its operating system version, the language and time-zone setting of the device; and a random code for this installation that Google's software creates and that every event is filed under. Google works out an approximate country or region from the network address of the request and states that it does not keep the address itself.

What is not sent. Your name, email address, contacts, location, photos, advertising identifier (the game has no advertising and asks for no tracking permission), the identifier Apple or Google give your device for other apps, or anything you type: the game has no text input.

Purpose. To understand how the game is played -- which levels are played, finished or given up, and how long they take -- so that we can improve it. We use the figures in Google's Firebase and Google Analytics reports.

Who processes it. Google LLC (Firebase, Google Analytics) stores and processes this information for us as our service provider, under Google's data-processing terms. We do not sell it and we do not share it with anyone else.

How long. Google keeps the detailed records filed under the installation code for the period set in our Google Analytics account, which is at most 14 months; aggregated statistics (totals that cannot be traced to an installation) are kept longer in our reports.

Crash reports (CRASH REPORTS)

What is sent. When the game crashes, or an error inside it is caught by the game's own safety net, a report of what went wrong: the technical trace of the failure (which part of the game's code was running), the level and world that were open, the game version and build number, your device model and its operating system version, the language and region setting of the device, the amount of memory and disk space available at the time, the screen orientation, whether the game was in the background, the list of software components loaded in the game, the time of the crash, and a random code for this installation that Google's crash-reporting software creates. Google's software also sends short technical records about each play session (when it began and ended, device and game version) so that crashes can be counted against sessions.

What is not sent. Your name, email address, contacts, location, photos, advertising identifier, or anything you type. The game has no text input, so a report cannot contain anything you wrote.

Purpose. To find and fix crashes and errors in the game.

When it is sent. A crash report is written on your device when the crash happens and sent the next time the game starts, if crash reports are still on then. If you have turned crash reports off in the meantime, the waiting report is deleted instead of sent.

Who processes it. Google LLC (Firebase Crashlytics) stores and processes crash reports for us as our service provider, under Google's data-processing terms. We do not share them with anyone else.

How long. Google keeps crash reports and the installation code attached to them for 90 days, after which it begins deleting them.

Our service providers, and where the information goes

Both providers are bound to protect this information at least as well as this policy describes, through their terms with us.

What the game does not do

Children

The game is suitable for all ages and is made for a broad family audience; it is not directed only at children. We have designed it so that it collects as little as possible from anyone: the cloud copy of progress contains nothing that identifies a person, and play statistics and crash reports are off until someone turns them on. Children's information is treated the same way as everyone else's, and we do not use any of it to build profiles or to advertise.

In many countries only a parent or guardian may give consent for a child below a certain age (for example 13 in the United Kingdom, and between 13 and 16 in the European Union, depending on the country). If you are below that age where you live, the choice about play statistics and crash reports should be made by your parent or guardian, and we ask parents to make or review it in SETTINGS → DATA. The game does not ask for your age and cannot check who is making the choice. If you believe a child has turned one of these switches on without the required permission, or has given us personal information in any way, contact us: we will turn the sending off on request and delete what we can identify.

App store platforms

If you download the game from the Apple App Store or Google Play, those platforms may process data about the download and any purchase under their own privacy policies (Apple, Google). We do not receive personal data from them.

Your rights

Depending on where you live, you may have rights to access, correct or delete personal data, to object to or restrict its processing, to withdraw consent at any time, and to complain to a data-protection authority. You can withdraw consent to play statistics or crash reports yourself at any time in SETTINGS → DATA, and delete the cloud copy of your progress from the CLOUD SAVE section of SETTINGS. For anything else, write to us at the address below.

Please note what we can and cannot do. We hold no names, accounts or contact details, so we cannot find your information from who you are. Play statistics and crash reports are filed under random installation codes that only Google's software on your device knows; we have no way to tell which records are yours, so we cannot single them out for deletion. They are deleted by Google at the end of the retention periods above. What you can delete is the cloud copy of your progress, from the CLOUD SAVE section of SETTINGS, as described above. Withdrawing consent stops future sending; it does not undo sending that already happened.

Changes

If what the game stores or sends changes, this policy will be updated before that version is released, the date at the top will change, and the new policy will be shown in the game's PRIVACY screen. If a change means we need your choice again, the game will ask you again on its next start.

History: 22 September 2026, first version; 26 October 2026, music downloads and the cloud copy of progress; 16 November 2026, optional play statistics and crash reports.

Contact

Questions about this policy, and requests about your information: ideaintech.prokhorenko@gmail.com.