For Telcos
Signal kid-status. Expose nothing else.
SafeGen is built on CAMARA-aligned APIs. You already have the plumbing. We just need a yes/no signal — no PII, no age, no identity.
Executive Summary
SafeGen enables telcos to participate in Australia's child safety framework without compromising subscriber privacy or network security.
CAMARA-Ready
Built on Number Verification and future Age Verification APIs you're already exposing.
Zero PII Exposure
No names, no DOBs, no addresses. Just a binary signal: tagged or not tagged.
Privacy-First Architecture
Parent tags device via SIM/MSISDN. Platform queries operator. No identity flows upstream.
New Revenue Stream
Per-query commercial model. National-scale volume. Government-backed rollout.
CAMARA Alignment
SafeGen is designed around the GSMA Open Gateway / CAMARA framework. We're not asking you to build something new — we're asking you to expose what you're already building.
Relevant CAMARA APIs
Number Verification API
LiveConfirms MSISDN ownership without exposing the number to the application.
Age Verification API
EmergingReturns age-bracket or threshold confirmation. SafeGen only needs under-16 flag.
Device Status API
FutureCould signal parental-control or kid-tagged status directly from SIM profile.
Why CAMARA Works for SafeGen
- No custom API development required
- Leverages existing GSMA Open Gateway investments
- Interoperable across Australian MNOs
- Privacy-by-design compliance built-in
- Scalable to millions of queries per day
What SafeGen Needs From Telcos
Four capabilities. All privacy-preserving. All within existing technical reach.
Binary Kid-Flag Response
When queried, return only: 'tagged' or 'not tagged'. No age. No identity. No metadata.
Parent Registration Pathway
Allow parents to tag a SIM/MSISDN as belonging to an under-16 via existing parental control flows.
Pre-Allocated Number Ranges (Optional)
Designate specific MSISDN ranges as 'kid SIMs' — automatically tagged at activation.
Query Response Infrastructure
Expose a CAMARA-compliant endpoint that SafeGen's accredited operator can query at scale.
What Telcos NEVER Provide
SafeGen is architecturally incapable of requesting this data. The API simply doesn't accept it.
The telco's role is signal confirmation, not identity provision.
Integration Model
How the query-response flow works — end to end.
Parent Tags Device
Parent registers child's SIM/MSISDN as under-16 via telco's existing parental control interface or SafeGen portal.
Telco Stores Flag
Telco records kid-tag against MSISDN in existing subscriber management system. No new database required.
Platform Initiates Check
When user attempts age-restricted action, platform sends device signal to SafeGen's accredited operator.
Operator Queries Telco
Accredited operator (e.g., AusPost, Thales) queries telco's CAMARA endpoint with hashed device identifier.
Telco Returns Signal
Telco responds with binary flag only: 'tagged' (block) or 'not tagged' (allow). No identity data flows.
Commercial Model
SafeGen creates a new, privacy-preserving revenue stream for participating telcos.
Per-Query Revenue
Each platform verification generates a micro-transaction. At national scale, this becomes material recurring revenue.
Regulatory Alignment
Participation positions telco as a trusted child-safety partner — valuable for licence renewals and government relations.
Operator Partnership
Commercial terms negotiated with accredited operator (not SafeGen directly). Standard B2B API commercial arrangements.
Revenue share and query pricing to be negotiated between telco and accredited operator during partnership onboarding.
Intellectual Property Notice
The SafeGen architecture — including the device-tagging model, binary-signal verification flow, and privacy-preserving age assurance mechanism — is the subject of a patent application pending in Australia.
Telcos interested in deploying similar mechanisms independently are encouraged to engage with SafeGen Pty Ltd to discuss licensing arrangements and ensure freedom to operate.
Partner With SafeGen
We're seeking foundation telco partners for Australia's first privacy-preserving, national-scale child safety infrastructure. Early partners shape the standards.
What Partnership Looks Like
Technical
Joint API specification review. Integration testing with accredited operator. CAMARA alignment validation.
Commercial
Revenue share negotiation. Volume commitments. SLA and support arrangements.
Strategic
Co-announcement opportunities. Government liaison support. Industry working group participation.
Telco FAQ
Common questions from carrier technical and commercial teams.