Tell us who you are. We'll route you to the right person.
Six doors, one team behind them. Choose the lane that matches how you reach a kid — operator, platform, network, regulator, press, or parent — and we send you to the person who has done this before. Phosra is the reference implementer of OCSS; it doesn't own the standard, which lives at openchildsafety.com.
A real person replies within 2 business days. Urgent security issues skip the queue — write [email protected] directly and we triage on receipt.
Each door routes differently. Same team behind them.
Pick the one that fits — the form is tailored to your lane, so the first reply is from someone who already speaks your context, not a generic inbox.
Prefer email? Here's where each one lands.
Every door above writes to one of these inboxes. If you already know who you need, write directly — same people, same two-business-day reply.
Security disclosures go to [email protected] and are triaged on receipt.
We don't own the standard. That's the point.
OCSS is a pre-release standard — Draft 4, an individual IETF Internet-Draft, not yet ratified. Phosra is building toward OCSS Certified: a status earned from the standard and its conformance suite, never issued by us. We don't self-certify and we don't ship a “Phosra Certified” badge.
The canonical spec, rule registry, and conformance suite live at openchildsafety.com — not here. Phosra implements OCSS; it doesn't host it.
Reach the right person in one message.
Choose your lane and the form routes you straight to someone who has done this before — or browse the statute registry first if you're here to check a mapping.