planwell

Privacy

Last updated 10 October 2026. Written under UK GDPR and the Data Protection Act 2018.

1. Who we are

Planwell is made by Codex Education Ltd (company number 16423970), 128 City Road, London EC1V 2NX. Questions about this page or about your data go to [email protected].

2. This website

planwell.digital uses no analytics, no advertising and no tracking cookies. The web server records the IP address and browser of each request in its log for security, and those logs are kept for no more than 12 months. The domain's DNS is served by Cloudflare.

3. A Planwell account

You sign in with your Microsoft account. Planwell never sees or stores your password. It stores your name, your email address, your school, the Microsoft account and tenant identifiers that tie the sign-in to you, and when you last signed in. A strictly necessary cookie, pw_session, keeps you signed in for 30 days or until you sign out. A product you sign in to with this account may save your progress in it against your account. To have an account deleted, email us.

4. Inspective

Inspective needs no account. Everything in it is Ofsted's and the Department for Education's published data about schools, used under the Open Government Licence v3.0. Lead inspectors' names appear as Ofsted prints them on each report. The school you mark as yours and the phase you choose are kept in your own browser's storage and are never sent to us. A search inside the reports is sent to our server to run and is not stored. Report PDFs are fetched from Ofsted's own files service by our server and passed to you; nothing about you is kept.

5. The demo school

The demo school is made up: its pupils, staff, attendance and lessons belong to no real person. Signing in as a role sets a signed cookie, elc_demo_demo, for that visit. Anything you type into the demo is visible to other visitors and can be cleared at any time, so do not enter real data there.

6. A school using Planwell

Each school has its own address, its own database and its own sign-in. The school is the data controller. Codex Education is the data processor under a written data processing agreement, and processes the school's data only on the school's instructions.

What the school importsPupils: name, UPN, MIS identifier, year group, tutor group, attendance marks, timetable and class lists. Staff: name, school email, roles, timetable. The school calendar.
What staff and pupils createCatch Up Cards, catch-up work and the work pupils submit, sign-offs, extensions, reflections, notes about a pupil's card, lesson plans and resources, settings and role assignments.
Who can see itThe school's staff and pupils, by role, as the school sets. Codex Education's staff only to support the school, and each such access is logged.
Where it is heldA server in the United Kingdom (OVH, Erith), in a database that holds that school alone.
EmailNotifications to staff and to pupils' school addresses from [email protected], under switches the school controls.
Sub-processorsOVH (hosting, UK). Microsoft (sign-in). Cloudflare (DNS). Anthropic (generated catch-up work, from lesson text only; see the AI statement). The school is given 30 days' notice before a sub-processor is added or replaced.
RetentionFor the life of the school's contract. At its end the data is returned to the school and deleted. Individual records are deleted earlier on the school's instruction.
SecurityHTTPS throughout. Session cookies are HttpOnly, Secure and SameSite. One database per school. Access by role.

7. Your rights

Under UK GDPR you can ask for access to your data, for it to be corrected or erased, for its processing to be restricted, and you can object and complain. For records held for a school, ask that school's data protection contact; for a Planwell account, email us. You can complain to the Information Commissioner's Office at ico.org.uk.

8. Changes

This page carries the date it was last changed. A change that affects a school is sent to that school before it takes effect.