Child Safety

This page describes the rules and the technical boundaries that protect a student while they are using KAERON. It is written for the parent or guardian who is deciding whether to let their child use it.

We are not going to tell you the platform is “completely safe”. No one running an internet service can honestly promise that, and a promise like it is a reason to distrust the rest of the page. What we can do is tell you exactly what is and is not possible inside the product, so you can judge it yourself.

By default and by design, KAERON publishes nothing about a student. Specifically:

• No public profile. There is no page anywhere on this site that shows a student's name, photo, age, school or work.
• No leaderboard or ranking. Your child is never displayed next to, or compared against, another named student.
• No student directory. A student's account cannot look up, search for, or list any other student.
• No project showcase by default. Work your child builds is theirs. We ask separately, as an optional tick at checkout that you may decline, before using any of it publicly — and declining changes nothing about the course.

If we ever want to show a student's work, we will ask you at that point, for that piece of work. A consent you gave once is not a standing permission.

Most of what goes wrong for children online goes wrong in a message. KAERON has no messaging. There is no chat, no comment thread, no direct message, no forum and no group. Not restricted or moderated — absent. It was never built, and that is deliberate.

The only written communication your child can receive inside the product is feedback from a mentor on a specific piece of their work, attached to that work, visible to you as their guardian. A mentor cannot open a private channel to your child, because none exists.

Your child also cannot upload a file, image or video. That route is restricted to staff accounts, so the most common way inappropriate material reaches a children's platform is closed.

A course is bought by an adult. During setup, that adult identifies themselves as the parent or guardian and can create the student account for their child, which links the two: you keep visibility of your child's progress from your own account.

A student account is for one student. Please do not share its password — including with a sibling or a friend — because everything the account does is recorded as your child's work, and feedback intended for your child would go to whoever is signed in.

If you believe your child's account has been accessed by someone else, tell us and we will help you reset it.

Being finalised. We are reviewing whether a student should be able to hold an account that a parent did not create, and tightening the setup flow so that the guardian link is established before a student reaches any lesson content. Until that lands, if you want your child's account created under yours, buy the course from your own account and add your child during setup.

Students are asked to do the obvious decent things: do your own work, be honest about where you got help, and do not try to break things that other people rely on.

The following are not allowed and can end access:

• submitting written answers containing abuse, threats, sexual content or hate speech;
• putting another person's private information into an answer — a classmate's number, a family member's details, anyone else's photograph;
• attempting to attack, overload or find holes in the platform, or to reach another account's data;
• sharing or reselling course material, or sharing an account.

Because written answers are read by an AI grader and can be read by a mentor, an answer is never a private diary. The lessons teach students this directly — see Responsible AI for what is and is not sent to an AI provider.

If anything about your child's experience worries you — feedback that reads wrongly, content that seems inappropriate for their age, a suspicion that someone else is using their account, or anything else — report it through the contact page. A concern about a child is not treated as a support ticket; it goes to a person.

Tell us your child's account email and what you saw, and keep anything you can (a screenshot, the lesson name). If you believe a child is in immediate danger, contact the police on 112 or the child helpline on 1098 first — then tell us, so we can act on our side.

Being finalised. The response time we are prepared to commit to for a safety report, and the escalation path inside KAERON, are being written down properly rather than promised loosely. The reporting route above works today and is read by a person.

Inside KAERON, your child's work and progress can be seen by: you, as their linked guardian; a mentor reviewing their work; and an administrator maintaining the platform. Nobody else — and no other family — can see any of it.

Mentors and administrators reach that data through accounts whose permissions are enforced on our server, not merely hidden in the interface. A parent account is scoped to its own children; there is no view that shows one family another family's data.

Being finalised. Our written policy on staff conduct, and what checks we carry out before someone is given a mentor account, is being documented before we take on mentors beyond the founding team. We will publish it here rather than describe it vaguely now.

We collect as little about a child as we can: a name, a class band, and the work they do in the course. We do not collect a date of birth, a school name, a home address or a photograph, because the programme does not need any of them.

The privacy policy is the full account. As a guardian you can ask us what we hold about your child, ask us to correct it, and ask us to delete it. Write to us and we will do it and confirm in writing.