Cookie Policy

1. The short version

We use a small number of cookies. Some are essential and cannot be turned off, because without them you cannot stay logged in. The rest are analytics, and they run on public pages only. No analytics or session recording tag ever loads on a screen that shows a child's records.

This policy sits alongside our Privacy Policy, which explains what we do with personal information generally.

2. What a cookie is

A cookie is a small file a website asks your browser to store. On return visits the browser sends it back, which is how a site remembers you are logged in.

We also use two related technologies and treat them the same way in this policy: local storage, which holds preferences in your browser, and pixels, which are tiny requests that report a page was viewed.

3. What we actually set

Google Analytics and Microsoft Clarity are each switched on by configuration. If they are not configured, those tags never render and those cookies are never set.

4. Where analytics runs, and where it does not

Analytics and session recording are blocked on /studio, /portal, /login, /signup and /auth.

That block is enforced in three independent layers, each failing closed:

1. On a blocked route the tag scripts are not rendered into the page at all, so a session that begins on /studio loads no analytics cookie and no recorder.
2. A runtime guard stops the tag on client-side navigation into a blocked route.
3. The send hook itself refuses to fire on a blocked path.

This is deliberate and it is the most important line in this document. The studio and the parent portal display student records, including children's names, lesson notes and attendance. No third-party tag runs there.

5. Managing your cookies

Analytics. Use the cookie preferences control in the site footer to turn analytics off. Your choice is stored in tm-consent and applies to this browser.

Everything. Every browser lets you block or delete cookies in its settings. Blocking essential cookies will stop you being able to log in, so the Platform will not work.

Do Not Track. Browsers send this signal inconsistently and there is no agreed standard for honouring it, so we do not currently respond to it. We would rather say that plainly than imply a protection we do not provide.

6. Things that are not cookies but still reveal something

Map tiles. Our maps load tiles from CARTO and OpenFreeMap. Requesting a tile tells those providers your IP address and roughly which area you are looking at. There is no way to show a map without this.

Fonts and scripts. We self-host our fonts, so no font provider sees your visit.

Vercel Analytics is cookieless. It does not set a cookie and does not track you between sites.

7. Changes

If we add a cookie or a new provider, this page changes first, and the table in section 3 is the list we keep current. Material changes are notified in line with clause 30 of the Terms of Service.

8. Contact