1. Neutral age check
Where required, age is requested neutrally before child personal-data collection. The interface must not encourage a user to select an older age.
GROWTH · PRIVACY BY DESIGN
Age & Privacy Architecture
How Growth is designed to separate adult, teen, and child experiences before personal data is collected.
2. Route by age and region
The service determines the applicable adult, teen, or child route using the user’s age band and relevant regional rules.
3. Parent or guardian step
Where law requires verifiable parental consent, the child route pauses before personal-data collection until the required parent or guardian process is completed.
4. Age-appropriate experience
Assessment language, conversation behavior, safety handling, purchases, external links, and privacy choices can differ by age group.
5. Review and deletion
Users and, where applicable, verified parents or guardians receive appropriate routes to review, delete, withdraw consent, or stop further collection.
Design status
This page documents the intended architecture. Child personal-data collection must remain disabled until the production consent, verification, deletion, SDK, AI-processing, and store-disclosure gates are verified.