Privacy Policy — Brain Dead Brandon

Effective

Brain Dead Brandon is a maths, grammar and logic game for phones and tablets. It is made by one person, Brandon Lusk.

This page explains what the game keeps, where, and how to delete it. It is written so a grown-up can read it in a few minutes.

Cloud save, and which versions have it

Brain Dead Brandon is gaining cloud save: a copy of the game’s progress kept online, so a child’s pets can follow them to a new phone or tablet. This policy describes the game with cloud save switched on.

Versions of the game without cloud save keep everything on the device and send nothing anywhere. For those versions, nothing below about the cloud happens.

The short version

What the game keeps in the cloud

When the game is online it keeps one cloud copy per account. The first time it goes online it makes an anonymous Firebase account by itself. Nobody signs in for that, and no personal details are asked for. That copy holds:

The game keeps a small key on the device so it can reach its own cloud copy again. That key never goes anywhere except to Firebase.

Linking is optional and sits behind a grown-up check (a question a young child cannot answer), at Restore my stable in the game’s stable. It is what lets the save come back on a new or wiped device. On Android it uses Sign in with Google; on iPhone and iPad it uses Sign in with Apple.

Linking does not change anything in your Google or Apple account itself.

What the game does not do

Who stores it, and who can see it

The cloud copy is kept by Firebase (Firebase Authentication for the account, Cloud Firestore for the save), which is run by Google. Google acts as the game’s service provider: it stores the data for the game and does not use it for its own purposes. No other company receives anything.

How long it is kept

The cloud copy is kept until it is deleted. Nothing expires on its own, and the game does not delete old copies on a schedule.

There are two ways a cloud copy can end up somewhere the game can no longer reach:

The game cannot delete either of those itself.

If you plan to delete the game or reset the device and want the cloud copy gone too, use Delete my cloud account (below) first.

Deleting your cloud copy

This section is for Brain Dead Brandon (Android and iOS), by Brandon Lusk.

In the game. Open Settings from the main menu and tap Delete my cloud account. A grown-up check comes first. Then confirm with Delete the cloud copy. This:

It cannot be undone, and a new device would start fresh. If the screen says the device has lost its key to the cloud copy, the game cannot delete it itself.

Deleting the cloud account does not remove Brain Dead Brandon from your Google or Apple account’s list of connected apps. You can remove it there yourself (in your Google Account’s security settings, or in iPhone or iPad Settings under your Apple Account → Sign in with Apple).

Children

The game is designed for all ages and is rated 4+. Children play it, so it is built to need nothing personal from them: the cloud account is anonymous, the game asks for no name, email, photo or contact details, and there are no ads and no tracking. The only free text is a pet’s name. Anything that involves a real identity, which means linking a Google or Apple account, sits behind a grown-up check, so a grown-up makes that choice. So does deleting the cloud copy.

It is not enrolled in Apple’s Kids Category or Google Play’s Designed for Families programme.

Purchases

This version contains no purchases. If a future version adds them, they are handled entirely by Apple or Google; this app never sees a payment card or a billing address.

Changes

The earlier version of this policy, effective from 2026-09-25, said the game collected nothing, because no version then had cloud save. That version promised that any change would be described here rather than made quietly. This is that description: cloud save adds the anonymous account, the cloud copy of the game save, optional Google or Apple linking by a grown-up, Firebase as the service that stores them, and the ways to delete them.

If a future version keeps anything more, for example purchase history once real purchases exist, this policy will be updated before that version ships, and the change will be described here.