OCSS · the open standard for child-safety signals
Build child-safety protections once. Enforce them everywhere.
One standard for parental-control apps and the surfaces that enforce them — less time wiring integrations, more time protecting kids.
Two layers, one standard
Meaning and movement, kept separate.
Apps implement both once. Rules say what a signal means; the Trust Framework carries it as a signed payload.
The payoff
Stop building one integration per surface.
App-to-surface wiring is an N×M tangle. Get on the shared Trust List once, and it collapses to N+M.
Pre-ratification, in the open
We publish our zeros.
No production accreditations yet; the committee is forming. Verify every claim against the live signed ledger.
Founding coalition · forming
Help write the standard
you’ll build to.
Founding members shape the taxonomy, the conformance contract, and how trust is granted — before ratification, while it can still change.