What it does
Every rule that protects a young athlete on Neylo is enforced at the data layer, not just in the interface. Age gating decides what a profile can show and who can see it. Permissions decide who can contact whom, and how. And every sensitive action lands in an append-only audit log, which means nothing can be quietly edited after the fact.
For athletes and their parents
Under-18 accounts run through parental consent before anything is visible, and the athlete controls visibility from there. Profiles on Neylo are ID-verified, so there are no anonymous accounts approaching kids.
For scouts and clubs
Verification cuts both ways. A club knows the athlete is who the profile says, and a family knows the scout is real. Contact runs through age-appropriate rules and every interaction is logged, which protects the club as much as the athlete: a clean, reviewable record of how first contact happened.
Where it fits
Most of the talent Neylo exists to surface is under 18. A discovery platform for minors only deserves to exist if safety is structural, and building this layer before the growth features was a deliberate ordering, not an accident of the roadmap.
How it’s built
The rules live in the database schema, so no client and no future feature can route around them. The audit log is append-only by design. The framework is built around the obligations of Australia’s Online Safety Act, and it is live in production today, running underneath every feature we have shipped.