Safety

How CodeQuest is built to keep children safe, in plain language.

A grown-up is always in the loop

Every publication passes through a named adult — the child’s own parent or guardian. There is no route by which a child’s work reaches the public without that step, and no automated system that publishes on a child’s behalf.

We publish as little about a child as possible

A published page carries a display name of your choosing and nothing else about the child. No real names, no ages, no photographs, no location, no contact details. Children have no email address on the platform and no way to message each other.

Uploaded projects are checked before they are stored

Every upload is inspected before it is published: only file types a browser can safely show are accepted, size and file-count limits apply, and archives that try to write outside their own folder are rejected outright. Projects are served from a separate internet address from the site you sign in on, so a published project can never reach your account.

Where we are still improving

We would rather tell you this than not. CodeQuest is new, and a security and child-safety review is part of how it is being built, not an afterthought. Two things we are actively working on:

• Giving every project its own internet address, so one child’s project cannot see anything belonging to another child’s project.
• Tightening what a published project is permitted to do once it is running in a browser.

If you find something that worries you, tell us and we will treat it as urgent.