MetaPet for Schools
Privacy and Implementation Note
Audience: ICT coordinators, digital learning leaders, assistant principals, principals
This note keeps the classroom-facing language simple while giving leadership and ICT teams enough detail to approve a low-friction pilot.
---
Implementation Summary
No student accounts required for the classroom baseline
Local browser storage for classroom record contents during routine use
No advertising or behavioural tracking on classroom routes
Teacher-controlled deletion and export
15–20-minute sessions with normal teacher supervision
No marking workflow added to existing teacher load
No leaderboard, streak pressure, or reward-pressure loops in the school-facing sequence
---
School-Facing Privacy Position
For the classroom baseline, the simplest accurate description is:
> No student account is required. Classroom record contents stay in the browser during routine use and can be cleared by the supervising adult.
That phrasing is suitable for teachers, school leaders and families.
The technical boundary must also describe network requests: the hosting
provider receives ordinary page requests, and a deliberate teacher export
leaves the browser. Routine classroom use does not submit the classroom record
contents to B$S.
---
ICT Note
The app already contains more technical internal language and identity systems than teachers need to see. For school rollout, those internal concepts should remain in ICT review material rather than classroom copy.
For this Australia-wide school package, classroom users only need to know:
the companion runs as a digital system on a device
classroom record contents are stored locally for routine use
the classroom sequence does not depend on cloud logins
classroom routes do not load advertising or behavioural tracking
the supervising adult can delete the covered classroom records
---
Curriculum Note for Privacy and Security
Privacy and security references should stay in the implementation note, not in the teacher-facing hero copy.
Relevant Australian Curriculum V9.0 codes for ICT discussion:
AC9TDI4P09 - identifying what personal data is stored and shared in online accounts and discussing associated risks
AC9TDI6P09 - accessing multiple personal accounts using unique passphrases and explaining the risks of password re-use
These are included here to support leadership and ICT conversations, not to drive day-to-day lesson delivery.
---
Family and Admin Reassurance
For family communication and leadership approval, the simplest points are:
students are using a short classroom sequence, not a high-admin platform
the classroom baseline avoids account setup friction
the sequence supports Digital Technologies and wellbeing learning
evidence collection is light and non-graded
implementation fits within normal school timetables
---
Local Pilot Checklist
Use this checklist before a pilot:
Confirm the devices to be used for the sequence.
Confirm the preferred delivery format: individual or pairs.
Decide which timetable slot fits best: Digital Technologies mini-lesson, STEM block, wellbeing session, or relief lesson.
Choose one evidence tool: student reflection sheet or teacher observation checklist.
Confirm who needs the ICT note and who only needs the classroom overview.
---
Recommended Positioning for Approval
Describe the sequence as:
> a short Years 3-6 digital companion sequence that supports Australian Curriculum Digital Technologies and wellbeing learning through pattern recognition, system rules, reflection and calm classroom use.