Privacy Policy — Brokk

Last updated: September 12, 2026

Brokk — Runes of Dawn ("Brokk", "the app", "we") is a single-player physics puzzle game set in the nine Norse worlds, with a daily challenge. This policy explains what information the app handles, where it goes, and how you can control it.

1. Summary

• The whole game is playable without signing in. Your progress is stored on your device.
• Signing in with Apple or Google is optional. It puts your name on the account plate and puts you on the leaderboards; it does not transfer your progress anywhere.
• The app shows no advertising of any kind and contains no in-app purchases.
• The app has leaderboards: a daily, a weekly and an all-time board. A row carries a name and a score, and everyone using the app can see it. If you are not signed in, nothing of yours goes up until you say so; signing in puts you on the boards under the nickname you choose.
• Usage analytics are switched off until you answer the question the app asks once, inside the game. Crash reports are collected so we can fix what breaks.
• We do not sell your data.

2. What information is handled, and why

2.1 Always, whether or not you sign in

• Game state stored on your device — stars, scores, attempts, unlocked fortresses, hint charges, daily-challenge results and streak, settings (language, sound, music, vibration) and the nickname you may enter. This is kept in the app's local storage. Your progress is never uploaded; the nickname is, but only as the name on your own leaderboard row, and only once you are on the boards (2.2).
• An anonymous account (Firebase Authentication) — at launch the app signs in anonymously so it can fetch its fortress catalogue from our backend. The anonymous identifier is not tied to your name, your e-mail or your device's advertising identifier.
• Fortress catalogue and settings we publish (Firebase Firestore) — the app reads the level bundle and a small configuration document. The only thing it ever writes is your own leaderboard row, and only once you are on the boards (see 2.2). Your progress itself is never uploaded.
• Crash reports (Firebase Crashlytics) — if the app crashes, a report with the crash trace, the app version, the device model and operating-system version and a random installation identifier is sent to us. It contains no name, e-mail or location.
• App integrity (Firebase App Check) — when the app talks to our backend, the device attests that the request comes from a genuine copy of Brokk (Apple App Attest / Google Play Integrity). The attestation token identifies the app instance, not you.

2.2 Only if you are on the leaderboards

• Your leaderboard row (Firebase Firestore) — one row per board, stored under your user identifier: name, total score, stars, points and the time the row was written on the daily board; name, score and the number of days you turned up for on the weekly board; name, score, stars and points on the all-time campaign board. Nothing else: no e-mail address, no device information, no message of any kind, and no free text other than the name.
• The name on the row — the nickname you chose, or, if you have not chosen one, a name the app generates from your anonymous identifier (for example Brokk·7f3a). A chosen nickname is at most 16 characters and has to pass an automatic profanity filter before it is accepted.
• Who can see it — everyone using the app. The boards are public by design: that is what a leaderboard is. The row does not say who you are beyond the name on it.
• How your row gets there — if you are not signed in, the app asks first and nothing is uploaded until you accept. Declining is a real answer, and the whole game — campaign, daily challenge, stars — is complete without ever joining. If you sign in, you are on the boards: that is part of what signing in is for, and your existing rows are renamed to the nickname you chose.
• Taking it down — see sections 7 and 8. Deleting your account removes your weekly and all-time rows; the name on a daily row is replaced with "—" instead, because a day's board is a shared record of who played that day.
• Reporting a name — if you see a name on a board that should not be there, write to contact@fluttech.com and we remove it.

2.3 Only if you allow analytics

• Usage analytics (Firebase Analytics) — collection is disabled when the app starts. The first time you return to the menu after clearing a fortress, the app asks once whether it may measure how the game is played: which fortress was opened, won or lost, how many throws it took, which hint was used, which screen was shown. Nothing is collected before you say yes, and you can change your answer at any time in Settings → Privacy. These events carry a random app-instance identifier and coarse device information, and are used to balance the levels.

2.4 Only if you sign in with Apple or Google

• Provider-issued user identifier — used by Firebase Authentication to associate your sign-in with a stable account.
• E-mail address and display name — when you sign in with Apple or Google we receive an e-mail address (or Apple's private relay address if you chose Hide My Email) and the name the provider hands over. They are stored only in Firebase Authentication, so the app can recognise you and show whose account is signed in.
• Signing in does not upload your progress in this version. What it does add is the account plate in Settings and your place on the leaderboards (2.2); your e-mail address is never shown on a board.

2.5 Features a later version may add

None of the following is in the app today. If we add any of them, we will update this policy, the store questionnaires and the app's privacy settings before the feature ships:

• Cloud-synced progress — your progress mirrored to a private document so it survives a reinstall.
• Optional rewarded video (Google AdMob) — a video you start yourself in exchange for an in-game reward, with a consent form in the European Economic Area, the United Kingdom and Switzerland, and without App Tracking Transparency on iOS.
• In-app purchases — processed by Apple or Google; we would never see your payment details.

3. Who has access to what

4. Third-party services we rely on

• Firebase (Google LLC) — Authentication, Firestore, Analytics, Crashlytics, App Check. See firebase.google.com/support/privacy.
• Sign in with Apple (Apple Inc.) — optional sign-in provider. See apple.com/legal/privacy.
• Sign in with Google (Google LLC) — optional sign-in provider. See policies.google.com/privacy.
• Apple App Store / Google Play — app distribution, under their own privacy policies.

5. Tracking and ads

The app contains no advertising, and we do not track your use of the app across other companies' apps or websites or build an advertising profile of you. On iOS the app never asks for App Tracking Transparency permission.

6. Children

The app is not directed at children under 13 (under 16 in the EEA), and we do not knowingly collect personal information from them. Signing in is optional, and the only thing a player can publish to others is the name on a leaderboard row: there is no chat, no messaging, no profile and no way to send an image, a sound or a message to another player. Chosen nicknames pass an automatic profanity filter, and any name can be reported to us and will be removed. We recommend not using a real name on a board. If you believe a child has provided personal information through sign-in, contact us at contact@fluttech.com and we will delete the account and associated data.

7. Your choices

• Analytics: Settings → Privacy. Your choice is stored on the device and can be changed at any time.
• Reset local progress: Settings → Progress → Erase progress, or Fresh install, or uninstall the app.
• Sign out: Settings → Account → Sign out. The app returns to an anonymous session; the progress on your device is untouched, and the rows already on the boards stay there under your account until you delete it.
• Delete your account: Settings → Account → Delete account. This removes your Firebase Authentication record and, for an Apple account, revokes the token Apple issued to Brokk. You can also request deletion at fluttech.com/brokk/delete_account.html or by e-mail to contact@fluttech.com from the address tied to your sign-in.
• Nickname: Settings → Account. Changing it renames the rows you already have on the boards.
• Leaderboards: if you are not signed in, you decide whether to join when the app asks, and declining costs you nothing in the game. Deleting your account (above) takes your rows down as described in section 8. To have a name removed from a board — yours or someone else's — write to contact@fluttech.com.

8. Data retention

Local game state is kept on your device until you erase it or delete the app. Crash reports are retained by Firebase Crashlytics for 90 days. Analytics events, if you allowed them, are retained for 14 months. Your Firebase Authentication record is kept while the account exists and is removed when you delete it — immediately from the app, or within 30 days of an e-mailed request.

Leaderboard rows stay up while the board does: a daily board is a record of that day, and the all-time board is the campaign's standing. Deleting your account deletes your weekly and all-time rows and replaces the name on your daily rows with "—", which leaves the day's record intact but nameless. The app does this for the last 30 days of daily rows and for the current and previous week; if you want an older row removed as well, write to contact@fluttech.com and we will do it by hand.

9. International transfers

Data is processed on Google Firebase infrastructure. Google may process data in various regions under the standard contractual clauses and the EU–US Data Privacy Framework; see the Google privacy policy linked above for details.

10. Legal basis (EEA/UK)

We process device-local data, the anonymous session, app-integrity attestations and crash reports on the basis of our legitimate interest in providing a working game; analytics on the basis of your consent; the sign-in data and your leaderboard row on the basis of the service you asked for — a board you joined, or the sign-in that put you on it. You have the right to access, correct, export and erase your data, to object, and to lodge a complaint with your supervisory authority.

11. Changes to this policy

If we update this policy, the "Last updated" date above will change. Continued use of the app after a change means you accept the updated policy.

12. Contact

Data controller: Fluttech. For questions about this policy or to exercise the rights in sections 7 and 10, contact: contact@fluttech.com