Platform trust and governance

LeaveLens security and Australian data hosting

LeaveLens stores application data in Australia using Microsoft Azure infrastructure and combines role-based access, privacy-conscious movement records and school-controlled implementation processes.

Australian data storage

LeaveLens application data is stored in Australia to support regional school review expectations.

Microsoft Azure

The platform uses Microsoft Azure cloud services for application, database and storage infrastructure.

Role-based access

Teachers, coordinators, heads of department, executives and administrators receive different levels of access.

Independent review support

LeaveLens has been assessed through Safer Technologies 4 Schools and can support school privacy and security review.

Australian hosting

LeaveLens application data is stored in Australia. The platform uses Microsoft Azure infrastructure, including cloud application, database and storage services configured for the LeaveLens environment.

Australian data storage can support privacy, procurement and data-governance discussions for Australian and New Zealand schools. It is one element of a school’s assessment—not an automatic approval for every jurisdiction or governing body.

Microsoft documents that regional Azure services allow customers to select the region where customer data is stored and processed, subject to the characteristics and exceptions of individual services. LeaveLens can provide school-specific information about its deployed environment during an assessment.

Security layers relevant to schools

Platform controls

  • Authenticated staff accounts.
  • School-specific account and data boundaries.
  • Role-based views and permissions.
  • Secure web connections for browser access.
  • Managed cloud infrastructure and database services.
  • Logging and telemetry used to investigate application events.

School governance controls

  • Approval of the selected integration and data fields.
  • Allocation and review of staff roles.
  • Prompt disabling of accounts no longer required.
  • Local procedures for movement and follow-up.
  • Staff training and acceptable-use expectations.
  • Management of parent data and optional reporting.
Role-based access model
Role contextTypical access purpose
User / teacherClassroom logging and information relevant to the teacher’s classes or assigned students.
CoordinatorBroader live and analytical information for year, house or pastoral responsibilities.
Head of departmentSubject and faculty-level reporting aligned with curriculum leadership.
ExecutiveWhole-school visibility, snapshots and broader analytical review.
AdministratorConfiguration, account access, data import and school administration.

The exact permissions and role allocation should be confirmed during implementation and reviewed when staff responsibilities change.

Privacy-conscious data model

Security is strengthened by limiting unnecessary data collection. The normal LeaveLens movement record focuses on student identity, class context, exit time, return time and the staff associated with the movement.

The core workflow does not require teachers to record detailed medical, wellbeing or personal explanations for ordinary movements. Sensitive information can remain in the specialist school systems and professional processes designed for it.

Optional features, such as parent reporting, should only be enabled after the school has considered purpose, contact-data quality, communication procedures and local policy.

Safer Technologies 4 Schools assessment

LeaveLens has been assessed through the Safer Technologies 4 Schools program. This can assist education departments, Catholic and independent school bodies and individual schools when conducting their own privacy and security review.

The assessment does not replace the decision-making process of the relevant governing body. Schools may still need to review:

School assessment checklist

1. Data

Identify every data field imported, generated, displayed and optionally communicated.

2. Access

Confirm authentication, roles, account lifecycle and who can view each reporting level.

3. Infrastructure

Review hosting location, cloud services, integrations and continuity arrangements.

4. Governance

Align the platform with policies, notices, contracts, support procedures and staff training.

Shared responsibility

LeaveLens is responsible for operating and securing the platform within its documented service arrangements. The school remains responsible for how it configures and uses the system, including:

Security is a continuing process.

Schools should review users, permissions, integrations and procedures after implementation—not only during procurement.

Related information
See LeaveLens in your school context

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