PRIVACY POLICY

The short version

The game itself plays on your device, except in a friend room, which plays on our game server. Optional analytics and, in the phone app, crash reports are off until you say yes: before your first tutorial or match the app asks once, and you can change your answer at any time with ANALYTICS & DIAGNOSTICS in Settings. Your settings and match record are saved in the app's own storage.

This release also gives your save an account, so it survives a new phone, and it sells coin packs and a one-off Launch Pass through the App Store or Google Play. From version 1.0.1 it can also offer one optional advertisement at the end of a match, which you may choose to watch for a coin bonus. It also shows your player alias or Game Center nickname and your best score for each game type, from a SOLO RUN or a room match, with the level it was played at, to other players on a shared leaderboard unless you hide yourself from it. All of that is set out below.

You can wipe the device copy at any time: Settings → CLEAR GAME DATA ON THIS DEVICE, or by uninstalling. You can delete the account itself at Settings → Account → Delete account, or from the account & data deletion page.

Who we are

Shift Right Studios SRL ("we"), a company registered in Romania, is the controller of any personal data described here. Write to support@brickbreakeroverdrive.com about anything on this page.

What the app keeps on your device

The game stores these on your device:

• your sound, haptics and reduced-motion switches;
• the mode and difficulty you last chose;
• a record of your completed matches and your best scores per mode;
• the paddle skin and ball trail you have equipped;
• whether you have played the tutorial;
• your answer to the analytics & diagnostics question, which version of the question you answered, and when — so the app does not ask again;
• a random player identifier the app mints on its first run. It is a label for this device's save, not an account, and it is not tied to your name, your phone number or your Apple or Google identity.

This local copy goes when you clear game data or uninstall. Account backup and optional analytics send the limited data described below.

What the app sends — and what it contains

Every build includes Firebase Analytics, and the phone app also includes Firebase Crashlytics, both with collection disabled by default. Before your first tutorial or match the app asks once — Help improve Brick Overdrive — with two equal answers, Enable analytics & diagnostics and No thanks. Collection begins only if you choose to enable it, and the same ANALYTICS & DIAGNOSTICS switch is in Settings. Signing in, linking an account or buying something never turns it on.

We will not, however, tell you the app is empty. Google's Firebase Authentication gives your save an account identifier, and RevenueCat records what you buy through the App Store or Google Play. From version 1.0.1, Google Mobile Ads (AdMob) also runs, to serve the optional rewarded advertisement. Each is described in its own section below.

Up to version 1.0, Google Mobile Ads is built into the app and is never started. No screen in those versions can request an advertisement, none is shown, and your device's advertising identifier is not read. We checked that against the built app rather than against our own source. If you ever see it behave otherwise, tell us — that is a defect and we want to hear about it.

Optional analytics and diagnostics

If you enable ANALYTICS & DIAGNOSTICS, Firebase Analytics (Google) receives, from then on, tutorial and mode choices, match starts and outcomes, rematch choices, screen views, and limited error categories and performance timings. For a friend room match it also receives how the connection behaved: how many people played, the friend room steps you took, which game server region hosted it, round-trip times, delays between game updates, reconnects, how long you stepped away, how long a bot held your paddle, and whether you watched or left once knocked out. It never receives your display name, your account identifier, a room's invite code or other players' names. We use a random local player identifier, session identifiers and build/cohort labels to understand where play sessions succeed or fail. Test and friends-research sessions are labeled separately from ordinary production play.

These records are pseudonymous, not anonymous. We do not include your email, raw error messages, gameplay controls or movement traces. Analytics also processes technical information such as device/browser details and network requests. Web analytics can store identifiers in cookies. Advertising storage, advertising user data and ad personalization are disabled for this analytics integration.

This collection is optional and based on your consent; nothing from before you said yes is sent afterwards. The game, saving, rewards and your account work the same whichever you choose. Turn the switch off to stop future collection: the app stops recording at once and resets the analytics identifiers on this device. CLEAR GAME DATA ON THIS DEVICE also turns it off, resets those identifiers and forgets your answer, so the app asks again. Neither erases records already received by Google; contact us using the support address for a data request.

Crash reports, in the phone app only. With the same switch on, Firebase Crashlytics (Google) also receives a report when the game crashes or hits an error: where in the game's code it failed, your device model, operating system and app version, which screen and game mode you were on, and a random identifier Crashlytics makes for this installation. Error text leaves your device only when it is one of the standard descriptions a browser engine or our own code gives of a programming fault, such as "x is not a function"; any other error text is dropped. A report waits on your device and is sent the next time the game starts — only if the switch was on when it happened and is still on; otherwise it is deleted. Turning the switch off discards reports not yet sent. Clearing game data does not reset the Crashlytics identifier, but nothing more is sent from this device unless you say yes again. The web version of the game sends no crash reports.

Your account and your save

This release keeps a copy of your progress on our servers, so a new phone can pick your save back up. Settings → ACCOUNT & SUPPORT tells you which kind of account you are on; a build without account backup shows LOCAL ONLY there instead. Optional analytics has its own separate switch.

Guest. The app asks Firebase Authentication (Google) for a random account identifier. No name, no address, no password. Your progress, cosmetics and coin balance are stored against that identifier in Firebase Firestore (Google).

Linked. If you choose to attach an Apple or Google sign-in so the save survives a lost phone, we store the identifier that provider hands us, and the email address if it gives us one. We never see your password. Sign in with Apple's "Hide My Email" works normally.

The same identifier is your RevenueCat customer. What you have bought and what coin balance you hold are stored against it, not against your name. Deleting your account deletes that RevenueCat customer with it, in the same request.

Deleting it. Settings → Account → Delete account inside the game, or the account & data deletion page if the app is already gone. Either one removes the account, the save stored against it and the RevenueCat customer.

Our legal basis is performing the service you asked for — keeping your game save — and our legitimate interest in stopping fraud against the reward system.

Purchases and coins

This release sells coin packs and a one-off Launch Pass. You buy them through the App Store or Google Play, and RevenueCat keeps the record: which product you bought, when, and the coin balance you hold — all against your random account identifier, which is also your RevenueCat customer identifier.

Your card details go to Apple or Google and never reach us or RevenueCat. We never see a card number, a billing address or a bank. We see that a purchase happened and what it was for.

Coins are spent inside the game on cosmetic items. They are not money, they cannot be cashed out, and they exist only against your account identifier. A refund is Apple's or Google's to give; write to us and we will help you ask.

If a purchase fails, the Shop offers SEND REPORT. Only when you press it do we receive a report about that one purchase: the product, the error the store gave, how long it took, your device's system version and the purchase library's recent log lines, stored against your account identifier. It helps us fix purchases that do not work, and it is deleted with your account.

Rewarded ads — from version 1.0.1

From version 1.0.1, when a match ends you may be offered one advertisement to watch for a coin bonus equal to that match's own coins. Watching is always your choice: the game, your save and your rewards work the same if you never watch one. A Launch Pass owner gets the same bonus without an advertisement.

Google AdMob serves the advertisement. When the app starts, Google's consent form asks for your choices where the law requires it — for example in the European Economic Area and the United Kingdom — and you can change them later with AD PRIVACY CHOICES in Settings wherever that form applies. On iPhone, the app then shows a short explanation followed by Apple's own question about tracking, and your device's advertising identifier is used only if you allow it there; you can change that answer in the iPhone's Settings under Privacy & Security → Tracking. On Android, Google reads the advertising identifier under its own policy, and you can reset or delete it in your phone's settings.

Whatever you answer, AdMob receives technical information from your device — such as the device model, operating system, app version and IP address — and what happens with each advertisement, so that it can show it, measure it and prevent fraud, under Google's own privacy policy. So that an advertisement is ready when a match ends, the app may load one in the background during the match; it is shown only if you choose to watch it.

How the bonus is paid. When an advertisement has been watched, Google tells our servers (Firebase Cloud Functions and Firestore) directly, with your random account identifier and a transaction number. We check Google's signature, add the coins through RevenueCat, and store the claim against the same identifier so that one advertisement cannot be paid twice. RevenueCat also receives a record that an advertisement was loaded or shown and what it earned, against that identifier.

Where the law requires consent to use your advertising identifier or to personalize advertisements, we rely on the choices you make in Google's form and in Apple's question. Paying and checking the bonus is part of the service you asked for when you chose to watch.

Up to version 1.0, none of that happens. The AdMob library is built into the app and never started, no advertisement is requested or shown, and no advertising identifier is read.

Friend rooms

If you play in a friend room (PLAY WITH FRIENDS), your display name, your random account identifier, your moves and your match results go to our game server, and your display name and results are shown to the other players in that room. Your display name is the one at the top of your screen: the name from your Apple or Google sign-in if you linked one, or the start of its email address, and otherwise a GUEST label. The game server is hosted in the European Union by Colyseus. It keeps the room's invite code, against the account that opened the room, until the room closes, and each player's result only briefly after the match, so that a player whose connection dropped can still see it; both are kept in Firebase Firestore (Google) and then deleted automatically. Deleting your account deletes any results still held and takes your account off any invite code still open.

High score leaderboard and gaming profiles

New players automatically participate in the shared high score leaderboard. It keeps one board per game type, and each board keeps one best score per player, whether it came from a SOLO RUN (a timed match you play on your device against five bots) or from a room match (see below). Your generated player alias or Game Center nickname, public discriminator, best qualifying score, the level that score was played at and where it was played (a SOLO RUN, a friend room or a quick match) are visible to other players of the versions that carry the leaderboard, on any device. Older match history is never published. Analytics and diagnostics are optional and independent of leaderboard participation. You can hide yourself from the leaderboard, which deletes your public leaderboard data, at any time.

We use your existing Firebase account to keep one best across devices. On an iPhone, the game signs in to Apple Game Center when its home screen first opens; if you are not signed in, Apple shows its own sign-in, which you may decline, and the game plays the same either way. When you are signed in, your Game Center nickname becomes your public leaderboard name and the name the game shows for you, including to the other players in a friend room. The game reads the nickname from Game Center each time it opens and does not store it on your device. Without Game Center, your generated player alias is used. We do not automatically publish your ordinary Apple or Google sign-in name or email address. We verify the gaming identity with Apple, retain a private hashed association, and treat nickname text as presentation data. This does not link or merge your Firebase accounts, purchases or progress. We do not request gaming friends or avatars.

Leaderboard runs send a server-issued run identifier, game settings, score and limited completion statistics. Credentials used to verify a gaming profile are processed in memory and are not stored or logged. Short-lived proof fingerprints prevent replay. Proof fingerprints, run records, rate counters and administrative invalidation records are retained temporarily, then removed by automated database expiry. Your public best and public name remain until replaced, you hide from the leaderboard, or you delete the account.

In Settings, HIDE ME FROM THE BOARD removes your public profile, scores on every board and gaming-name association, and invalidates queued publication. Your ordinary game progress is kept. We retain a private opt-out marker so reopening the game, starting a match or using another linked device does not enroll you again. Turning the switch off, or TURN LEADERBOARD ON in the leaderboard, explicitly enables future submissions under a fresh entry. Existing opt-outs remain off. Other devices may display a previously loaded board until refreshed. Temporary run and anti-abuse records expire as described above. Account deletion also removes the opt-out marker and remaining leaderboard data, so deleting your account is the way to erase all of it. Clearing only local data does not remove a server leaderboard entry.

Room matches on the leaderboard

A room match you finish (a friend room, or a quick match where the game offers one) counts on the same leaderboard, on the board of its game type. Its scores come from our game server, never from your phone: when the match ends, the game server records each player's random account identifier, score and how much of the match that player played, and our backend publishes your best qualifying score under the same public name as your other entries, your player alias or Game Center nickname with its public discriminator. When a room's match starts, the game server also reads your level from your account, so that the room's bots play at the level of the people in it. A room match counts even if you were the only person in it. A match you left with QUIT or LEAVE before it ended is never published, nor one a bot played for you for more than half of the time you were in it. The players you shared a room with saw that match's scores on their own results screen, so they may recognise your entry, and with it your public name, on the leaderboard.

Taking part works exactly as it does for a SOLO RUN. If you have hidden from the leaderboard, your room matches are not published, and HIDE ME FROM THE BOARD removes your room match scores together with the rest. A match you played before hiding is never published afterwards, even if you turn the leaderboard back on. The game server's records of finished matches are kept for a limited period so they can be published, then deleted automatically. Your public best remains until it is replaced, you hide from the leaderboard, or you delete the account, which also deletes those records.

This website and our support inbox

brickbreakeroverdrive.com sets no cookies and runs no analytics or tracking. It is static files on Firebase Hosting (Google), whose servers log requests — IP address, user agent, time — as every web host does.

Mail you send to support@brickbreakeroverdrive.com is forwarded by Cloudflare Email Routing to our own mailbox. We read what you send and reply. This is separate from anything in the app: emailing us does not connect your message to a game save unless you tell us which one you mean.

Who else touches it

We sell nothing. Advertising reaches the app only as the optional rewarded advertisement described above, from version 1.0.1. These are our service providers, each acting on our instructions or under its own published terms:

• Google (Firebase) — hosting for this site; optional analytics, diagnostics and crash reports (Crashlytics), and sign-in and save storage in the versions that have them.
• Google (AdMob) — the optional rewarded advertisement, from version 1.0.1. Built in and never started in earlier versions.
• RevenueCat — the record of what you bought and your coin balance, and from version 1.0.1 a record of rewarded advertisements shown, against your random account identifier.
• Colyseus — the game server for friend rooms, hosted in the European Union.
• Apple and Google — the stores themselves, for the app and any purchase; and, on an iPhone signed in to Game Center, Apple Game Center, which confirms that gaming profile is yours.
• Cloudflare — DNS for this domain and forwarding for our support address.

These providers operate outside the European Economic Area, including in the United States, so data that reaches them is transferred there under the safeguards in each provider's own terms. Their privacy policies are the authority on that, not ours.

How long we keep things

On your device: until you clear it or uninstall the app. It is yours, we set no expiry on it, and we cannot read it.

An account, where one exists: until you ask us to delete it. Asking is the account & data deletion page, and it is the whole of what you have to do.

Friend rooms: an invite code until its room closes, a match result briefly after the match, and the record a room match's leaderboard score is published from for a limited period; see Friend rooms and Room matches on the leaderboard above.

Support mail: only for as long as we need it to answer you and to show a request was handled.

Web server and mail logs: for whatever period Firebase Hosting and Cloudflare keep their own logs. That is their setting, not ours.

Deleting your data

In the app: Settings → CLEAR GAME DATA ON THIS DEVICE, with a confirmation step you can cancel. Uninstalling does the same.

The account itself: Settings → Account → Delete account, which erases the account, the save stored against it and the RevenueCat customer. If the app is already gone, the account & data deletion page is the full route, including how to ask us without reinstalling anything. We process requests within 7 business days.

Your rights

Where the GDPR applies you can ask us for a copy of what we hold, ask us to correct or erase it, object to a use, or ask us to stop. Write to support@brickbreakeroverdrive.com. You can also complain to your national data protection authority; ours is Romania's ANSPDCP.

Children

The app is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has given us something, write to us and we will remove it.

Changes

This page is dated at the top. We update it when the app changes, and we change it before the feature ships rather than after.