Data minimisation

Privacy-conscious student movement tracking

LeaveLens is designed to give schools useful lesson-time movement information without requiring staff to collect a detailed medical, personal or wellbeing explanation for every ordinary classroom exit.

Collect what is needed

The core movement record focuses on the student, class, exit, return and duration.

Avoid routine sensitive reasons

Ordinary logging does not need to create a detailed history of private explanations.

Control staff access

Information is presented according to the user’s role and legitimate school responsibilities.

Australian data storage

LeaveLens application data is stored in Australia to support regional privacy and procurement review.

Useful movement data with less intrusion

Schools need to know when students leave lessons, particularly where an absence becomes prolonged or repeated. They do not necessarily need to store the private explanation behind every toilet break, health-related movement or wellbeing visit.

LeaveLens separates the operational movement record from the sensitive reason. The system can document that a student left class at a particular time, returned later and missed a measurable amount of learning without requiring a teacher to enter intimate personal details into the movement log.

What the core record contains

Operational movement information

  • Student identity and school identifier.
  • Scheduled class, subject and timetable context.
  • Date and exit time.
  • Return time where the movement is completed.
  • Staff members associated with the exit and return.
  • Platform used to record the movement.

Information that should stay in specialist systems

  • Medical diagnoses and treatment information.
  • Disability details and adjustment documentation.
  • Counselling or wellbeing case notes.
  • Detailed behaviour incident narratives.
  • Safeguarding reports and investigations.
  • Other information requiring restricted professional access.
Data-minimisation principles in practice

Purpose

Define the operational reason for recording lesson-time movement.

Necessity

Capture the fields needed for visibility and analysis, not every fact that could be collected.

Access

Limit views according to staff role, school structure and legitimate responsibility.

Review

Ensure school procedures, parent communication and retention arrangements remain proportionate.

Role-based access

LeaveLens supports different levels of school access so that information can be aligned with staff responsibilities. A classroom teacher may need a class-focused view, while a year coordinator, head of department or executive may need a broader analytical view.

Role-based access should form part of the school’s implementation review. Schools should determine:

Parent reporting

LeaveLens can support optional weekly parent reporting where enabled by the school. A summary can communicate exit frequency and total time missed without automatically disclosing sensitive reasons.

The school decides whether to enable the feature, which students are included, how family contact data is maintained and how the report is framed within existing communication and support processes.

Australian hosting and school review

LeaveLens application data is stored in Australia using Microsoft Azure infrastructure. Australian storage is an important regional signal, but it does not remove the need for each school, education department, Catholic education office, independent school body or governing organisation to complete its own privacy, security and procurement assessment.

LeaveLens has been assessed through the Safer Technologies 4 Schools program and can provide relevant product information to support school review. Approval requirements and decisions remain with the relevant school or governing body.

Privacy-conscious does not mean privacy review is unnecessary.

Schools should still consider purpose, notice, access, retention, integration permissions, parent communication and local policy requirements.

Questions for a school privacy assessment
  1. What specific educational and duty-of-care purpose will the movement data support?
  2. Which data fields are imported from the school’s existing systems?
  3. Which staff roles can access live and historical information?
  4. How will students, staff and families be informed about the process?
  5. Which school policies govern ordinary movement, medical needs and sensitive support information?
  6. How will accounts and permissions be maintained over time?
  7. What is the school’s process for privacy enquiries, access or correction requests?
  8. Which integrations and third-party approvals are required?
Related information
See LeaveLens in your school context

Review the workflow with your timetable structure, school roles, data source and student movement procedures.