# MetaPet Schools Privacy Policy

## Purpose

This policy explains how the `MetaPet Schools` deployment handles information during a school pilot. It is written for school leaders, ICT teams, and families.

## Core position

- The school deployment is designed for alias-based classroom use.
- Student accounts are not required.
- Routine classroom use keeps records on the current device.
- Teachers decide if any pilot evidence is exported.
- Adult-only or experimental Meta-Pet surfaces sit outside the school deployment.

## What the school deployment stores locally

- Learner aliases chosen by the teacher
- Lesson queue and classroom setup
- Local progress status such as `not started`, `in progress`, and `complete`
- Local class summary counts for pilot evidence

## What the school deployment does not require

- Student email addresses
- Student usernames or passwords
- Public profiles
- Social sharing
- Always-on companion check-ins

## How information is used

- To let a teacher prepare and run a short classroom sequence
- To let a teacher review local lesson progress and local pilot evidence
- To support deletion, reset, and short retention expectations

## Disclosure and exports

- Routine classroom use does not require cloud sync.
- Any pilot evidence export should be teacher-initiated and reviewed before it leaves the device.
- Exports should remain alias-based or aggregated unless the school has its own lawful basis and process for identifiable handling.

## Security controls

- Data is stored in the browser on the current device.
- No student account credentials are used in the school deployment.
- The school deployment blocks adult-only and experimental routes.
- Teachers can delete local school data from the runtime.

## Retention

- Local school data is intended to be short-lived.
- The current pilot configuration uses a 35-day local retention window without use.
- Teachers can delete local data earlier at any time.

## Contact and review

- Schools should review this policy together with the child and parent notices, data inventory, retention schedule, and risk assessments before pilot approval.