AnyRun is the registration technology; organisers run the events. The Platform handles entries, payments, volunteers, results and photos. The organiser stages the event and owns on-the-ground child safety for their jurisdiction: supervision on course, their state's child-safe obligations, and the conduct of their own staff and contractors.

What we own is what the software enforces. The age gate, the photo consent controls, the encryption around Working With Children records and the restrictions on sponsor content near children are built into the code. Each is described below, and each is checkable in the product as well as promised on this page.

You must be at least 16 to hold an AnyRun account and to enter an event yourself. The age check runs twice (in the entry form and again on our servers) from a single shared rule, so it cannot be bypassed by a browser trick or drift between the two layers.

Under-16s are not entered through the site. An account is the way in and the account floor is 16, so a child does not manage their own presence on the Platform and the registration form turns an under-16 entry away.

16- and 17-year-olds can hold accounts and enter. The Terms of Use require entries for participants under 18 to be made or approved by a parent or guardian, and where an event needs written consent (school events especially) collecting it is the organiser's responsibility under the Organiser Agreement.

No under-16 accounts means no child-managed profiles. The Platform holds no self-managed profile for anyone under 16.

We do not collect health or medical information, from anyone, at any age. There is no field for it, organiser questions must not request it, and the Organiser Agreement bars using event communications or uploads to gather it through the Platform.

What is collected around a child is the minimum, held with extra care. Emergency contact details and Working With Children records are treated as sensitive information and encrypted at the field level: readable to the systems that need them, ciphertext to everything else. School and junior events collect only what the event genuinely needs.

Photos find runners by bib number. Faces are not used. Bib matching reads the printed number on a bib and cross-checks it against chip times, with a human reviewing uncertain matches. Facial recognition is switched off across the entire Platform: no face index of participants, bystanders or children exists. The consent gate for any future face-based feature already exists in our code and is off: the promise is enforced by software.

What is visible is your choice. Photo matching is a revocable consent, chosen at entry. The public start list is opt-in and off by default, and shows a first name and initial only. Public galleries show only images the organiser has curated and featured.

Removal is immediate. Any matched photo can be removed from an account immediately, and a single confirmed action in account settings removes every photo match at once, processed on the spot: no request queue, no waiting on a human. Profile images are stripped of embedded location and camera metadata before they are stored. If you are a parent or guardian worried about a specific image of your child, use the reporting channel below and we will treat it as a priority.

Volunteer roles belong to organisers; the Platform makes the safety requirement visible. Organisers create and staff volunteer roles, and a role that involves minors can be marked as requiring a Working With Children check. From there:

• What we store: the check's type, reference number, issuing state, verification status and expiry, with the reference encrypted at the field level.
• What coordinators see: whether a volunteer's check is recorded and current. The reference number and the underlying document details stay hidden from them: a coordinator needs the on-file answer, and the paperwork behind it is the volunteer's. Volunteers see the fuller status of their own record, including whether it has been verified yet.
• What stays with the organiser: the legal duty. WWC checks are issued and governed by state schemes, and applying the right scheme's rules to the right roles is the organiser's obligation: software cannot discharge it for them.

No alcohol or gambling creatives around school and child-focused events. Sponsor placements near events aimed at children are held to a stricter bar, set out in the Content Standards. Every sponsor logo is reviewed and approved by the organiser before it appears, and either we or the organiser can decline or remove content unsuitable for a community sporting event.

Sponsorship does not buy access to children, or to anyone. A placement is exposure on described surfaces: sponsors do not receive personal information about any participant, of any age, except with that individual's express consent. The Sponsor Terms hold sponsors to that.

If a child is in immediate danger, call 000 first. Police, then us.

To report a concern on the Platform (a photo, a message, a listing, a volunteer, anything that worries you) email support@anyrun.net with "Child safety" in the subject. Child-safety reports go to the front of the queue, ahead of routine support. Include what you can: the event, the date, what you saw, and a link to the content if there is one.

What we can do, and will: remove content, revoke photo matches, suspend accounts, and put the organiser on notice: quickly, and without asking you to prove the concern before we act to reduce a child's exposure.

We cooperate with the people whose job this is. Where police or a child-safety authority make a lawful request, we answer it, and we preserve relevant records so routine deletion does not overtake an investigation. We support organisers in meeting their own mandatory-reporting and child-safe obligations; we do not stand in for them.

A material change to this statement bumps the legal pack's version (currently 2026-09) and the effective date at the top of this page. Questions or concerns: support@anyrun.net.