Skip to main content
Reading Garden

Security

How Reading Garden protects children's information. Written for schools' IT teams and data protection leads; please ask if you need more detail.

Last updated 15 November 2026.

The server

  • A virtual server rented from Fasthosts, in a UK data centre, running Ubuntu Linux with its long-term support.
  • Security updates install automatically every day.
  • A firewall only lets in web traffic (http and https) and SSH. SSH accepts keys only, never passwords, and only the person who runs Reading Garden has a key.
  • The app runs under its own account with no special rights, and can't be reached directly: everything goes through the web server. The database and backups can only be read by that account.

Connections

  • https only, with a certificate from Let's Encrypt that renews itself, and HSTS so browsers never use plain http.
  • Sign-in cookies are httpOnly, only sent over https, and kept to this site.
  • Every page tells browsers not to show it inside other websites, not to guess file types, and not to send its addresses to other sites, and blocks the camera, microphone and location.

Accounts and codes

  • Teacher passwords and pupil PINs are stored with bcrypt; parent codes and sign-in tokens with SHA-256. None can be read back.
  • Teachers can only create an account with their school's own school code, which puts them in that school.
  • Wrong guesses are limited from each internet connection: 20 wrong teacher passwords in 15 minutes, 10 wrong school codes in an hour, 30 wrong class codes in 10 minutes, or 10 wrong parent codes in 15 minutes. A teacher account also pauses for 15 minutes after 10 wrong passwords in a row, and a pupil's name pauses for 2 minutes after 5 wrong PINs.
  • Pupil sign-ins last 8 hours, teacher sign-ins 7 days.

Schools are kept apart

  • Every teacher, class, pupil and record belongs to one school. Pages and actions only ever look inside the signed-in person's school, and automatic tests check that one school can't see another's information, even with a direct link.
  • Teachers only see their own classes. A school lead sees numbers for every class in their school, not children's names. The site's admin sees numbers for every school.
  • A school can be paused, which signs everyone at it out and stops new sign-ins, without deleting anything.

Backups

  • A checked copy of the database every night, kept on the server for 14 days.
  • Each copy is encrypted on the server, with a passphrase kept offline, then copied to Amazon Web Services storage in London. The server's key can add and read copies but not delete them; they're deleted automatically after 60 days.
  • Restoring a backup is tested at least once a term.

What's kept, and what isn't

  • As little as possible about children: no surnames, emails, photos or full dates of birth. See the privacy notice.
  • No analytics, adverts or third-party scripts. Fonts are served from the site itself.
  • Nothing leaves the UK. Automatic marking with an AI service is switched off.

Testing, and what's next

  • Automated tests run before every change, including checks that schools are kept apart, and pages are checked for accessibility (WCAG 2.1 AA).
  • Reading Garden has not yet had an independent penetration test or Cyber Essentials certification. Both are planned; we'll share the results with schools when they're done.

If something goes wrong

If a school's information were ever lost or seen by someone who shouldn't see it, we would tell the school without delay, and within 48 hours at most, with what happened and what we're doing, so the school can decide whether to tell the ICO and families.

To report a security problem, please write to the email address that will be added to this page soon.