Topics

Privacy

Last updated 1 November 2026

In short

For parents: the details

Who looks after it

Jotter is run by Steven Webster, a parent in Scotland, and was made for their own family. Steven Webster is responsible for your information (the “controller”, in data protection law). Get in touch at jotter-maths-support@googlegroups.com.

What's kept, and why

Signed out, nothing leaves the device: see what's kept on this device.

Signing in keeps this, so progress is saved on every device:

It's used only to save progress and show it back: the rings for each skill and the suggestion of what to do next are worked out from it. Nothing is decided about anyone, there are no adverts or analytics, nothing is sold or shared, and Jotter never emails you.

The legal basis is legitimate interests: saving the progress you ask Jotter to save. It's kept to the least it needs: no surname, age, school or photo of a child.

Who else handles it

Jotter is built on Google services, which handle the information for Jotter under Google's data processing terms:

Firebase Authentication and reCAPTCHA are run by Google largely in the United States. Google protects those transfers with the safeguards UK law requires (the UK–US data bridge and standard contract terms).

Steven can see the stored information in Firebase's console, and looks only if something needs fixing, or if you ask.

How long it's kept, and deleting it

It's kept until you delete it, or until nobody's used it for 2 years. Then your household, every learner, all their progress and your sign-in are deleted. Jotter checks for these once a year, each August.

To delete it yourself:

Your rights

You can ask for a copy of your information, have it corrected or deleted, ask for it not to be used, or object to how it's used. Email jotter-maths-support@googlegroups.com, and you'll get a reply within a month. If you're not happy with the answer, you can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.

What's kept on this device

Jotter keeps these in your browser, signed in or not. Each one is needed for something you've asked Jotter to do, which is why there's no cookie banner. Jotter sets no cookies of its own.

Kept asWhat it's for
mt.lesson.…
local storage, one per skill
Where they've got to in a lesson, so they can carry on. Signed out only. Gone when they finish the round.
mt.rounds
local storage
How their finished rounds went, for the rings that show how well they know each skill. Signed out only. The last 10 rounds of each skill.
mt.flags
local storage
The method steps they've said aren't how their class does it, with what's different if they said, the questions they think were marked wrong, with what they typed and Jotter's answer, and when they switched to another way of working a skill, and when, for you to look at. Signed out only.
mt.variants
local storage
Which way they work each skill that's taught more than one way, if they've chosen one. Signed out only.
mt.milestones.…
local storage, one per learner
Badges and the week's dots they've already seen, so they aren't shown twice.
mt.tours.…
local storage, one per learner
Which guided tours they've seen, so each is shown once. One more, "parent", for the tour of parent mode.
mt.parentPin
local storage
The parent PIN, scrambled so it can't be read back. Signed out only: signed in, it's kept with your household.
mt.parentUnlocked
session storage
That parent mode is unlocked. Gone when the tab closes.
mt.learner.…
local storage, one per parent
Which of your learners is practising on this device. Signed in only.
mt.sounds
local storage
Whether sounds are on.
mt.soundsOffered
local storage
That they've been asked about sounds, so they aren't asked again.
mt.theme
local storage
Light or dark, if they've picked one.
firebaseLocalStorageDb
IndexedDB
Keeps a parent signed in. Made on every visit, but empty unless you sign in.
firebase-heartbeat-database
IndexedDB
Firebase notes which versions of its code ran on which days. Sent to Google only with a signed-in parent's requests.
Firestore's copy of your household
IndexedDB
Signed in only: a copy of your learners and their progress, so Jotter works offline.
firebase-app-check-database
IndexedDB
Signed in only: App Check's pass, which shows Google the requests really come from Jotter.
jotter-v1 (offline copy)
offline cache
The pages and pictures you've opened, so Jotter works without a connection. Nothing about you.

Google's cookies. While a parent is signed in or signing in, reCAPTCHA sets a cookie on google.com (_GRECAPTCHA) as part of its checks, and Google's sign-in uses Google's own cookies. Neither is set for a visit without signing in.

Changes

If this changes, this page will say so, with a new date at the top.