MetaPet Schools
Privacy materials
The school deployment uses alias-based local records, short retention, and teacher-controlled exports only. Download the privacy pack for the full artifact set.
Privacy policy
Child-friendly privacy notice
Parent/carer privacy notice
Data inventory
Retention and deletion schedule
Third-party services register
Data retention summary
- What is stored: Teacher-chosen aliases, lesson progress, classroom setup choices, class summary counts and any light evidence a teacher records.
- Where: Classroom record contents stay in this browser on this device during routine use. Routine classroom use does not submit classroom-record contents to B$S. The hosting provider still receives ordinary page requests, and a deliberate teacher export leaves the browser.
- Retention period: After 35 days without use, expired classroom records are removed when a school route next opens; a website cannot erase browser storage while it is closed.
- Immediate deletion: The supervising adult can delete the covered classroom records immediately from the local-data controls or by clearing this site's browser data.
- Student identifiers: No student account, student email, real name, photo or login is required by the classroom build.
How deletion works
After 35 days without use, expired classroom records are removed when a school route next opens; a website cannot erase browser storage while it is closed.
The supervising adult can delete the covered classroom records immediately from the local-data controls or by clearing this site's browser data. Schools should still clear site data when a device or pilot is retired.
Compliance frameworks
- Australian Privacy Act 1988 (Cth) / Australian Privacy Principles (APPs): Routine classroom use does not submit classroom-record contents to B$S. The hosting provider still receives ordinary page requests, and a deliberate teacher export leaves the browser. Whether the Privacy Act and APPs apply, and who is the relevant entity, depends on the operator, deployment and school practice. This is a data-minimisation design, not a legal compliance determination. Review the OAIC Australian Privacy Principles and obtain setting-specific advice where needed.
- COPPA (US) / GDPR-K (EU): Scope depends on where and how the service is deployed and who uses it. Alias-based records, no default classroom sync and short local retention reduce data exposure, but do not establish compliance in another jurisdiction.
- No application-level student-data sharing by default: Classroom routes do not load consumer product analytics or behavioural tracking. No advertising is loaded on MetaPet School classroom routes. Hosting still involves ordinary requests to the deployment provider. The third-party services register documents that narrower, checkable boundary.