1An age-appropriate experience
XOS1 is designed for people of all ages, with an age-appropriate experience.
Age-specific model boundaries, parental controls and automatic adult-mode switching are part of the intended product design. Their implementation has not yet been verified in a customer release.
| Age band | Intended experience |
|---|---|
| Under 13 | Age-appropriate AI with respectful boundaries. The intended design includes optional parental controls; when enabled, they are intended to give a parent or guardian visibility into the child’s XOS1 activity. |
| 13–17 | Age-appropriate AI with respectful boundaries. The intended design does not include parental activity-monitoring controls for this age band. |
| 18 and over | The full adult configuration, with its broader execution capabilities. The transition is intended to happen automatically when the recorded age reaches 18. |
2Age information and corrections
The intended age-based experience uses the recorded date of birth to choose the appropriate configuration and recognise age transitions. Optional profile sharing with XiteAI is a separate setting; it is not a verified age-check or guardian-consent process. A release must explain whether age and guardian information stays on the device or is sent to XiteAI or a verification provider, and collect only what is needed for the stated purpose.
Provide an accurate date of birth. Contact [email protected] if an incorrect age has selected the wrong experience. Any correction must preserve required consent and access protections; it must not be used to bypass safeguards.
3Turning 18
The intended design uses the recorded date of birth to switch automatically to the adult configuration when the user turns 18. That configuration continues to follow permissions, privacy settings and the Terms of Service.
An age transition must not automatically enable a camera, enrol biometrics, expand file permissions, turn on optional reporting, authorise a new payment or provide consent for a new use of personal information. A birthday does not automatically erase existing records; their retention and deletion remain subject to the Privacy Policy.
An age calculation alone is not proof that model configuration, access controls or parental visibility have been updated. The automatic transition must be verified in the release that offers it.
4Consent and guardian involvement
Parental controls and parental consent are separate. Where applicable law requires parent or guardian consent for a child’s personal information, that consent must be obtained before the relevant processing. The absence of parental monitoring for an age band does not remove a legal consent requirement.
A guardian acknowledgement during onboarding does not, by itself, establish that a legally required verifiable-consent process has been completed. Required notices, verification and permissions must be in place before the relevant child-data processing is enabled.
5Parental activity visibility
The intended parental-control feature is for users under 13 and is optional as a product setting. When enabled, it is intended to provide a parent or guardian with visibility into the child’s XOS1 activity. The intended experience for users aged 13–17 does not include parental activity monitoring.
The release must explain the scope of information shared, how parental access is verified, where the information is processed and retained, and how the controls are enabled and disabled. This notice does not promise a currently available parental dashboard or unrestricted visibility into every activity on a device.
Explain activity visibility to the child and guardian before it is enabled. When a user reaches 13, the intended design ends parental activity visibility; the release must verify that access is revoked. This product setting does not remove any separate guardian-consent or request rights required by law.
6Recognition, inference and cloud processing
General account terms or a parental-control setting do not authorise biometric enrolment, emotional inference or every cloud data flow. Each feature must satisfy applicable child-data restrictions, notices and permissions before it is enabled. Prohibited processing must remain disabled even if a guardian wishes to enable it.
Children’s information must not be collected beyond what is needed for a permitted, disclosed purpose. Before release, provider agreements and settings must support the relevant age groups and processing, and any new child or guardian records must have a defined retention and deletion schedule.
7Requests and withdrawal
A parent or guardian may request access, correction or deletion of a child’s company-held information, or withdraw consent, where applicable law gives them that authority. We must verify the requester’s identity and authority before disclosing information or acting on their behalf. Paying for an account does not by itself grant access to its conversations.
If legally required consent is refused or withdrawn, the affected processing must not begin or must stop, subject to applicable legal exceptions. This may make the affected feature unavailable. Disabling optional activity visibility is separate from withdrawing consent or requesting deletion.
8Respect other people’s information
Do not enrol another person’s voice or face, submit their personal information or access their activity without the permissions and lawful basis required for that use. A parental relationship is not a substitute for the release’s consent, access and privacy controls.
9Tell us about an issue
For a child-safety concern, an incorrect age configuration, a parental-control problem or a question about a child’s personal information, contact [email protected]. Provide only what is needed to identify the issue; do not send unnecessary identification documents or further sensitive information.
We will investigate and take appropriate steps, including restricting access or deleting information we are not permitted to hold. We may need to verify the request. The Data Deletion policy explains the separate treatment of local data and company records.