Privacy Policy
Last updated 10 October 2026
What changed since 30 September: play reminders and the notification question that comes with them, Mosaics in your saved game and in the measurements, and the purchase record on Android.
This policy covers the Brickworks mobile game for Android and iOS, published by Miljar Productions.
The short version
Brickworks is a block puzzle game. You can install it and play every mode without an account, without signing in, and without an internet connection.
Whether or not you sign in, the app sends us two kinds of technical information when it is online: measurements of how the game is played (for example which modes are played, how long games last and which buttons are used), and crash and freeze reports. We use them to find problems and make the game better. They carry a random identifier, never your name or email address, and they are not used to show you adverts.
Signing in is optional. It exists so your progress follows you to another device and so you can appear on the leaderboards. Your saved game only reaches our database if you sign in.
The game shows adverts, which are supplied by Google AdMob. There is a single one-time purchase that removes the full-screen adverts. Nothing else is for sale, and nothing in the game is locked behind either one.
What the app measures, whether or not you sign in
Brickworks uses two Google services for this, Google Analytics for Firebase and Firebase Crashlytics.
How the game is played
While you play, the app records events such as:
- which game modes you play, when a game starts and ends, its score, level, lines cleared, pieces placed, how long it lasted and how it ended
- which screens you open and which buttons you tap
- power-ups and saves you use or earn, and adverts you are offered, shown or given a reward for
- when you change a setting or a theme, open a leaderboard, open, pause or leave the app
- in Mosaics, the puzzle pieces, gold and trophies you earn and the daily presents you open
- whether play reminders are on, and when a reminder opened the game
- when the game shows its welcome, what's new, a suggestion to sign in or an encouraging line, and what you chose
- that the Remove Ads purchase was completed. On iPhone and iPad that is all: not the price, and never any payment detail. On Android, Google's software may also note which item was bought and its price, and never any payment detail
With these events Google's software also records the kind of device and system version, the app's version, your language, and an approximate location (town or city, region and country) that Google works out from your network address. Each installation of the app is given a random identifier so that one person's events can be told apart from another's. If you are signed in, the events also carry our random player identifier (described below). They never carry your name, your email address or your sign-in account. The app also notes its own build number and, on iPhone and iPad, whether this copy came from the App Store or a test version.
On both Android and iPhone the measurements do not use your device's advertising identifier.
Crashes and freezes
If the app crashes, or stops responding for several seconds, it sends a report with technical details: where in the app's code it happened, the kind of device, its system version, the app's version, and the state of the game at the time (such as the mode, the level and the last thing that happened on screen). If you are signed in, the report carries our random player identifier so we can tell whether a problem keeps happening to the same player. It never carries your name or email address.
Only in test versions of the app
People who help us test Brickworks before release use test versions (TestFlight on iPhone and iPad, a Google Play testing track on Android). In those versions only, and only when the tester is signed in, the app also tells us which phone model, system version and app version the tester is using and when they last played, together with the email address of the signed-in account, so we can match a problem to a tester. Once a tester is matched, we can also see the approximate location described above (town or city, region and country) beside their name, so we know roughly where a problem was seen. The Android test version also has a feedback button: a report sent with it contains the message you write, a picture of the game screen, the kind of device and app version, the last few things that happened in the app, and your leaderboard name and player identifier if you have them. None of this exists in the versions of Brickworks sold in the App Store or on Google Play.
What we collect if you sign in
On iPhone and iPad you can sign in with Apple or with Google. On Android you sign in with Google. Whichever you choose, Firebase Authentication tells us an account identifier, an email address and a display name. We use these for one purpose: recognising that a device belongs to a player we have seen before.
If you use Sign in with Apple and choose Hide My Email, Apple gives us a forwarding address instead of your real one. We never receive the real address, and that works perfectly well for everything above.
Once signed in, the game stores the following in our database:
| What | Why |
|---|---|
| A random player identifier, linked to your sign-in | So your saved game can be found again from another device |
| Your game progress: lifetime statistics, best score in each mode, recent game history, any game still in progress, your settings, Odyssey progress, your Today's Game attempts, your Mosaics puzzles and presents, and how many days in a row you have played | So the same game continues wherever you pick it up |
| Your chosen display name, if you set one | So a name can appear next to your score, and so nobody else can take the same one |
| Your display name and score on each leaderboard you appear on | To show the leaderboards |
Leaderboard entries are public. Anyone using the app can see the display names and scores on them. Your display name is chosen by you and does not have to be your real name, your email address or anything that identifies you. We would suggest it is not.
Adverts
Brickworks shows adverts supplied by Google AdMob. To do that, the Google Mobile Ads software in the app may collect your device's advertising identifier, information about your device, and whether you saw or interacted with an advert. That information goes to Google, not to us, and Google's handling of it is covered by Google's own privacy policy.
Where the law requires it, the app shows you a consent form before any advert is requested, and your answer is respected. If you decline, the game works normally and simply offers fewer adverts.
The one-time purchase removes the full-screen adverts between games. The video adverts you are offered in exchange for a power-up stay available, because they are optional and they give you something you asked for.
Purchases
Purchases are handled entirely by Apple or by Google Play, depending on which store you installed from. We never see and never receive your card number, your billing address or any other payment detail.
Nothing about a purchase is written to our database or attached to your saved game. The app asks the store you bought from whether this account owns it, and acts on the answer. The measurements described above record that the purchase was completed, so we can count how many players buy it (on Android, as said above, Google's software may also note the item and its price). One consequence is worth stating plainly: because the two stores do not talk to each other, buying on one does not remove adverts on the other.
What is kept only on your device
- Your sound and music preferences and the theme you have chosen. These stay on your device (and in your saved game if you sign in); the measurements above only note that a setting was changed.
- Your current game, if you are not signed in.
- Your play reminders. Their words and times are worked out and scheduled on your device and are never sent to us; the measurements only note whether reminders are on and when one opened the game.
What Brickworks does not do
We think this list matters as much as the ones above.
- The app does not ask for and cannot access your location, your contacts, your camera, your microphone, your photos, your files, your messages or your call history. The approximate location in the measurements (town or city, region and country) is worked out by Google from your network address, not from your device's location.
- We do not sell your information to anybody, and we do not share it with anybody except the Google services described above that are needed to run the game: Firebase and AdMob.
- We do not use the measurements or crash reports to advertise to you, and we do not use your information to build a profile of you or to advertise to you outside the game.
Permissions
On iPhone and iPad, Apple requires an app to ask before it may use the device's advertising identifier. Brickworks asks, once, with Apple's own prompt. If you say no, the game plays exactly the same and every reward stays available. You still see adverts either way; saying yes only makes them more relevant. You can change your answer at any time in Settings, under Privacy and Security, then Tracking.
We ask because the Google Mobile Ads software in the app can use that identifier, so Apple counts it as tracking and we would rather say so than word our way around it. Beyond that question, the only thing Brickworks may ask on iPhone and iPad is permission to send you notifications, for play reminders. It asks only after you say yes to reminders on its own card or turn on Play reminders in Options. If you say no, nothing else changes. You can turn reminders off in the app, or notifications off in Settings, at any time.
On Android, Brickworks itself requests internet access, the ability to check whether you are online, and the ability to vibrate the phone. For play reminders it also asks, on Android 13 and later, to show notifications (only after you say yes to reminders), and it can set your reminders again after the phone restarts. The Google software it includes adds a few more that Android grants without asking you: access to the advertising identifier and related advertising settings (for AdMob), Google Play billing (for the purchase), and the ability to finish sending measurements in the background. None of these asks for your approval, and none of them can reach your contacts, location, files, camera or microphone.
Deleting everything
- In the app. Open the Account screen and choose to delete your account. That removes your saved game, the record linking your sign-in to your player, and your display name reservation. It takes effect immediately.
- On the web. If you no longer have the app installed, you can ask us to delete your data at miljarpro.com/delete-account.
Deleting your account removes the data listed in the table above, Mosaics included. Leaderboard entries associated with the deleted player are removed with it. Game measurements and crash reports are held separately and are not removed automatically; if you would like the ones linked to your player identifier deleted, write to the address below and we will delete them. Anything already handled by Google, such as advertising data, is governed by Google's policies and you can manage it through your Google account settings.
How long we keep things
Your saved game and leaderboard entries stay until you delete them. There is no automatic expiry, because a game you come back to after two years should still be there. Game measurements and crash reports are kept, in Firebase and in our own copy in Google BigQuery, for as long as they help us improve the game, and are deleted on request as described above.
Children
Brickworks is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has signed in and provided information, write to us at the address below and we will delete it.
Where your information is held
The game's data, the measurements and the crash reports are stored using Google Firebase and Google BigQuery, on Google's servers. Miljar Productions is based in the United States, and information is processed there.
Changes to this policy
If this policy changes, the date at the top of this page changes with it. If a change is significant, we will say so in the app.
Contact
Questions about this policy, or about anything above, can go to developer@miljarpro.com.