Checked before display
Tutor explanations must fit a reviewed teaching format. A response that cannot be shown safely is replaced with a checked explanation.
Safety is part of the product
Learners should not have to manage the safety system.
Kwazi checks what is shown, collects as little information as possible and keeps public child access closed until the full safeguards are ready.
Less learner data
The learning journey should use only the information it needs, with clear deletion and access choices for guardians before public child use opens.
Adult-led access
The first release is for approved adults. Public child accounts stay off until consent, privacy and data-handling checks are complete.
Before public child access
What must be ready first
- Guardian consent and age-aware identity flows are working end to end.
- Privacy notice, retention schedule, export and deletion are approved and tested.
- Every enabled learning service has approved data terms and verified privacy settings.
- Safety events can be reviewed without exposing child data to public issue trackers.
- Android, web and later iOS builds pass real-device accessibility and performance checks.
- Store declarations match the product’s actual data collection and target audience.
Current boundary: the private preview is for adult evaluation with invented information. It is not open for public child accounts or real child information.
Responsible disclosure
Do not put child data, passwords or security details in a public report. Use the private support route so the team can respond without exposing sensitive information.
Open support guidance