Divisible Dash

Privacy policy

Last updated: 13 July 2026

The Divisible Dash app collects no personal data from players. Players get an anonymous account and a made-up name, and never type their real name anywhere. Teacher accounts and class rosters exist only on this website, not in the app. Nothing is sold or shared for advertising, and there is no tracking or third-party analytics.

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 pupil 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.

The app shows no advertising, does no tracking, and includes no third-party analytics.

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.
  • 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 pupil (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 and run no analytics. 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.

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.

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 removes their player record and their board entries, and 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 needs no parental consent and no age gate because it collects no personal data from players. Players are anonymous, use a made-up name, and never type any personal detail.

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 pupil 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.