Privacy Policy — Brick City

Last updated: 2 October 2026

This policy explains how BloomyCraft Labs Ltd ("we", "us") handles information in the Brick City mobile application (the "App"). Brick City is a town-building game made for children and their families, and it is built to need as little information as a game can.

1. Information stored on the device

The App keeps its games and settings in its own storage on the device (a handful of localStorage entries inside the App). What is stored is:

• the games that have been started and which one was last played, and up to five of them;
• the towns saved in each game — their buildings, layouts, people, coins, day, and where they stand on the country map — together with the motorways, railways and technologies that game has unlocked;
• the story progress of each game;
• settings: whether sound and music are on and their volumes, and how far the view has been turned;
• things earned or discovered in a game, such as paints and building parts unlocked, guide pages read, and visit questions answered;
• any house designs that have been saved.

None of it is an identifier of any kind, and deleting the App removes it. The saved games themselves never leave the device. Two numbers taken from the town being played — how many people live in it and how many coins it has — are included in the usage statistics described next.

2. Information we collect

There is no account system and no contact form inside the App, and we operate no servers of our own for it. To understand how the game is played and where it is hard, from version 1.2 the App uses Google Analytics for Firebase, which receives:

• that the game was opened, how many times that day, how long it was played, and on how many days in all;
• whether the tutorial was started, finished or skipped;
• which mini-game was finished;
• whether the request to rate the App was shown and how it was answered;
• the size of the town being played: its population, its coins, its age in game days and the mayor's level; and
• general technical information that Firebase records for every app, such as the device model, operating system version, app version, language and country (worked out from the network address, which is not stored).

These are tied to a random identifier that Firebase creates for the installation. It is not a name, an account or an advertising ID, it is not shared with other apps, and deleting the App discards it. We do not send a town's name, a player's name, or any text a player has typed, and we cannot tell who a player is.

Because the audience is children, analytics is set up to count and nothing more: collection of the advertising ID and of the Android ID is switched off, on iOS the vendor identifier is not collected, and the statistics are not used for advertising. There is no crash reporting. Google processes this information on our behalf under Firebase's privacy and security terms.

3. Advertising

From version 1.2 there is none. Brick City shows no adverts of any kind and contains no advertising software.

Versions 1.0 and 1.1 offered optional rewarded videos supplied by Google AdMob, shown only when a player chose to watch one. Every request was marked child-directed, under the age of consent and non-personalised, and Google's advertising SDK may have processed limited technical information to serve and measure them, under Google's Privacy Policy. Updating the App removes the adverts and that SDK. Those versions sent no usage statistics; section 2 applies from version 1.2.

The App does not use an advertising ID. On Android it does not hold the permission that would let it read one. On iOS it never presents the tracking prompt, which is what an app must do before it may read the equivalent identifier there.

4. Reading aloud

Some of the game's help text can be read aloud using the device's own text-to-speech engine. The words are produced by the device, nothing is recorded, and no audio is sent anywhere. The App does not use the microphone.

5. Children's privacy

Brick City is made for children. We do not knowingly collect personal information from a child, or from anyone else: the App asks for none, and the usage statistics in section 2 carry no name, contact detail, photograph or precise location. We handle data consistently with applicable law, which may include the U.S. Children's Online Privacy Protection Act (COPPA) and the EU and UK GDPR, including their rules on the age of consent.

If you believe a child has somehow provided us with personal information, contact us at the address below and we will delete it.

6. Permissions

The App requests no device permissions that need your consent. It does not use the camera, the microphone, the photo library, contacts, precise location, or the file system outside its own storage. Android declares the internet permission, which is used only by the usage statistics described above.

7. Your choices

• Remove everything the App has stored by deleting the App. That also discards the random identifier the usage statistics were tied to; to ask for statistics already sent to be deleted, contact us at the address below.

8. International transfers

We run no servers of our own. Processing by Google in connection with usage statistics may involve transfers outside your country and is governed by Google's own policy and safeguards.

9. Changes to this policy

If the App changes in a way that affects this policy — analytics, a purchase, an online feature — we will update this page and change the date at the top before that version is released.

10. Contact us

BloomyCraft Labs Ltd
Email: info@bloomycraftlabs.com
United Kingdom