Privacy policy

Last updated: 14 October 2026

Who we are

Divisible Dash is made by Peter Browne, an international maths teacher. For teacher accounts on this website, Peter Browne is the data controller. For student roster names that a teacher enters, the teacher's school is the data controller and Peter Browne acts as the data processor on the school's instructions (see the Teacher Terms and the Schools Data Processing Agreement). You can reach us at privacy@divisibledash.com.

The app (players)

The app never asks a player for any personal detail. There is no sign-up, no login screen, and no free-text box anywhere a player could type a real name.

• Anonymous identity. On first launch the app creates an anonymous Firebase account. It is a random identifier used only to run the game and the leaderboards. It is not tied to your name, email, phone, or contacts.
• Made-up display name. The name a player is shown by, for example SwiftFalcon42, is picked from curated word lists. Players never type their own name.
• Scores. Game scores are stored against the anonymous identity. For the Daily Challenge, the app also records per-rule accuracy (how you did on each divisibility rule) so leaderboards and progress can be shown.
• Class codes. A player can type a class code to join a class their teacher created. A class code is not personal data. Once joined, the class shows only the made-up display name.
• Web login code. A player's Profile also shows a separate 8-character login code, which can be typed into the web version of the game, when it launches, to play the same account on another device, such as a school laptop; the browser there only remembers the sign-in for as long as the tab stays open, and closing the tab logs the player out.

The app shows no advertising, does no tracking, and includes no third-party analytics. For completeness, it also does the following, none of which is tied to a player:

• Usage counts. When a run ends, the app adds one to a set of daily totals: runs played, level reached, run length, right and wrong answers per divisibility rule, bonus tile and freeze use, app version, whether the Pro screen was shown, purchases started and completed, and how many players that day were new or returning. These are plain counters shared by every player that day. They carry no player identifier, so nothing in them can be traced to a person. They are used only to see whether the game is working and how the levels play.
• Purchases. Divisible Dash Pro is bought through the App Store or Google Play. The store handles payment and keeps the receipt; we never see your name, card or billing details. The app stores only a flag on the device that Pro is unlocked, and Restore Purchases asks the store to set it again.
• Notifications. If you allow notifications, the app schedules reminders on your device only. There is no push notification service and no notification token is sent anywhere. You can switch them off in the app's settings or in the system settings at any time.
• App integrity. The app uses Apple App Attest or Google Play Integrity (through Firebase App Check) to prove to the server that requests come from the real app. This is a check on the app binary, not on you, and it sends no personal detail.

The website and teacher dashboard

Teachers create an account on this website only. There is no teacher account or login inside the app.

• Teacher account. To sign up, a teacher provides an email address and password (handled by Firebase Authentication), a school name, and a school email address. The school email is used as evidence of eligibility for free school pilots.
• Sign in with Google. A teacher can sign in with a Google account instead of a password. Google then gives us the name, email address and profile picture on that account, and Firebase Authentication stores them with the teacher account. We use the email address to identify the account. We do not use or display the name or the picture, and they are deleted with the account. We never see your Google password and get no access to anything else in your Google account. The button is Google's own: when the login page shows it, your browser loads it from Google, which receives your IP address and browser details and may set its own cookies. Google's Privacy Policy applies to that. Students are never asked to sign in with Google.
• Class rosters. A teacher may optionally enter a class list so their own leaderboard shows real names. Only a first name and a single last initial are entered per student (for example "John S"). These names are visible to that teacher only, and never appear on any shared or public leaderboard. They are entered under the school's authorisation, with the school as data controller. When a file is uploaded to import a roster, it is parsed in the teacher's browser and only the first name and last initial ever leave the teacher's device.
• Browser storage. The public pages of this site set no cookies. They count visits with Cloudflare Web Analytics, which uses no cookies or browser storage and does not identify visitors or follow them across sites. It reports totals only, such as page views, the page a visitor came from, country and browser type. It does not run on the teacher dashboard, the class pages, the boards or the web game. The teacher dashboard and the class board viewer use Firebase Authentication, which stores your sign-in state in the browser (in localStorage and IndexedDB) so you stay logged in. That storage is used only to keep you signed in. The class board viewer also stores your class code in the browser (localStorage), so it can remember it on your next visit.
• reCAPTCHA. The teacher dashboard, the public boards, the class board viewer, the homepage board and the web game use Firebase App Check with Google reCAPTCHA v3 to tell real browsers from scripts, so that nobody can run up our database usage with a copied key. It runs invisibly, with no puzzles. It sets a Google cookie and sends Google your IP address, browser details and how you interact with the page; Google's Privacy Policy and Terms of Service apply to that. We receive only a pass or fail, never anything about you.

Where data lives

Data is stored in Google Firebase, using Cloud Firestore and Firebase Authentication. Where data is transferred outside the UK or the EEA, the transfer relies on the Standard Contractual Clauses that Google includes in its Cloud Data Processing Addendum, which apply to the Firebase services used.

Technical data. Like any online service, the Google servers that host this website and store the game's data record the IP address, device and browser type, and time of each request in their logs. Google uses these logs for security and abuse prevention and keeps them under its own retention periods. When a public page loads, Cloudflare, which provides the visit counter, also receives the IP address and browser type. We do not use any of these to identify players or visitors.

Retention and deletion

There is no automatic time-based deletion.

• Roster names are deleted when a teacher deletes the row, the class, or their whole account, or on written request. Deleting a class or account deletes the roster names in it.
• Players can delete their identity in the app using Reset Identity in the profile. This deletes their player record, display name, friend code and friends list immediately. Past daily leaderboard entries, which carry only the made-up name and a score, are kept and can no longer be traced to anyone. The next launch creates a fresh anonymous identity.
• Teachers can delete their account from the dashboard, which removes the teacher account and its rosters.

Children

The app is made for school students, so we treat every player as a child. It asks for no personal details: no name, email, phone, photo, location, or free-text box, and there is no age gate because there is nothing to gate.

The one thing the app holds per player is the anonymous identifier described above. Under the US Children's Online Privacy Protection Act (COPPA) this is a persistent identifier collected only to support the app's internal operations. Specifically, it is used to save a player's scores and progress, to show the made-up name on leaderboards, to run friend codes and class codes, and to keep one set of scores per player. It is never used for advertising, profiling, or contacting anyone, and is never shared with anyone else for their own purposes. It is never combined with data from any other source, with one exception: a teacher who runs a class may match a player's made-up name to a first name and initial on their own roster, on this website only, under the school's authority, as described above. It is kept to those uses by design: the app contains no advertising software, the Google Analytics library that Firebase bundles on Android is switched off in the app's manifest with the advertising identifier permission removed, and the identifier is stored only with the game data it belongs to. No parental consent is needed for this, and no parent or child contact details are ever collected by the app.

Roster names are a separate, website-only feature. They are entered by a teacher under their school's authority, and the school is the data controller for them. See the Teacher Terms and the Schools Data Processing Agreement for how that works.

Your rights

Under UK GDPR you have rights over your personal data, including the right to access it, to have it corrected, and to have it erased. For a teacher account, contact us directly. For student roster names, the school is the data controller, so requests usually go to the school; we will assist the school as its processor. To make a request or ask a question, email privacy@divisibledash.com.

Changes to this policy

If we change this policy, we will update the date shown at the top of this page.

Contact

Questions and data requests: privacy@divisibledash.com. Divisible Dash is governed by the laws of England and Wales.