Privacy Policy
Last updated: [DATE THIS VERSION IS ADOPTED]
This Privacy Policy explains how [SCHOOL/ORGANISATION NAME] ("the School", "we", "us") collects, uses, stores and protects information through the NCCD App — the system school staff use to log and report student disability adjustments for the Nationally Consistent Collection of Data on School Students with Disability (NCCD).
The NCCD App is staff-facing software: only school staff (teachers, administrators) hold accounts and log in. Students do not have accounts, do not log in, and never interact with the App directly — their information is entered by staff acting in the course of their duties. This Policy covers both: the account information of staff Users, and the student information staff enter on the School's behalf.
This document is a drafting basis prepared for the School to adopt, complete and have reviewed by a qualified lawyer for the School's own jurisdiction before publishing it. It is not legal advice.
1. Who is responsible for this information
[SCHOOL/ORGANISATION NAME] is the operator of this deployment of the App and is responsible for the information described in this Policy, as the school that collects and holds it about its own staff and students. Contact for privacy questions or requests: [PRIVACY CONTACT EMAIL/ROLE, e.g. the School's Privacy Officer].
The App is deployed and hosted by or on behalf of the School (see "Where information is stored" below). The software itself does not send information to its original developer, to any analytics service, or to any advertising network — there is no such integration in the App.
2. Information we collect about staff (Users)
When a staff member is given an account, we hold:
- Name and email address
- A securely hashed password (the plain password itself is never stored — see "How we protect information")
- Role (Admin, Head of Site, or Teacher) and any staff group/supervision assignments used to control what the account can see
- Display preferences (avatar size, whether favourited students are pinned above or below the rest of the list)
- Any private student nicknames the staff member set before that feature was removed (kept on record but no longer displayed or editable)
- A record of adjustments the staff member has logged, and of any of their actions the audit log records (see "Audit trail")
3. Information we collect about students
Students do not create accounts and do not provide information to the App themselves. Staff enter and maintain the following on the School's behalf, for the purpose of NCCD compliance recording and reporting:
- First and last name, and an optional photo, used so staff can identify the right student
- An optional display name (nickname) set by an admin
- Adjustment records: which category and (optional) preset type of adjustment was made, its intensity (1–10) and frequency, the date, free-text notes (up to 2048 characters), and the NCCD level assigned to it (Quality Differentiated Teaching Practice, Supplementary, Substantial, or Extensive — the four official NCCD levels)
- Where used, a Risk Management Plan: a free-text safety plan maintained by admin/supervisory staff and visible (read-only) to staff who can otherwise see that student
- Class and staff-group enrolments, used only to control which staff can see the student
This is the category of information the Australian Government's NCCD framework requires schools to collect about students receiving an educational adjustment on the basis of disability. It is sensitive information. The School's lawful basis for collecting and holding it, and its obligations to families, sit with the School under its own enrolment and privacy arrangements — this App is the record-keeping tool the School has chosen to use, not the source of that obligation.
4. Adjustment notes and Risk Management Plans are encrypted
Adjustment notes and Risk Management Plan content are encrypted at rest (AES-256-GCM) in the database, in addition to standard database access controls. This does not change who can read the content through the App itself — role-based access controls (see "Who can see what") govern that — it protects the content specifically against someone who gained direct, unauthorised access to the underlying database or its backups.
5. Who can see what
Access is role-based:
- Teachers see and log adjustments for the students assigned to them (directly, via a class, or via a staff group), and see only their own adjustment history and their own logged-in account's settings.
- Admins and Heads of Site can review adjustment data across the School for compliance reporting and export, and manage staff accounts and students. Certain settings — school branding, adjustment categories/types, data-retention configuration, and the audit log — are Admin-only.
- A student can be hidden from teacher-facing lists by an admin; this does not remove any existing record, it only stops new adjustments being logged against that student by teachers and removes them from teachers' day-to-day view.
- No student, parent, or guardian has direct App access; requests relating to a student's information should be made to the School directly (see "Your rights").
6. Audit trail
The App keeps an append-only audit log of who did what — e.g. adjustments created or edited, student records changed, staff accounts created, adjusted, or deactivated — for compliance and accountability purposes. The audit log records the change and who made it, but never the encrypted content of a note or Risk Management Plan itself. Audit log entries are retained even if the staff account that made them is later deactivated, so the compliance history stays intact; only Admins can view the audit log.
7. How we protect information
- Passwords are hashed, never stored or logged in plain text.
- Adjustment notes and Risk Management Plan content are encrypted at rest (see above).
- Sign-in uses a short-lived access token plus a rotating refresh token. On the website the refresh token is stored in an httpOnly cookie (not readable by page scripts) sent only to the sign-in endpoints; on the mobile app it is stored in the device's secure hardware-backed keychain (Expo SecureStore), never in plain local storage.
- Refresh tokens and password-reset links are stored as one-way hashes, not as the usable token itself — a database copy alone cannot be replayed as a valid session or reset link.
- The mobile app can additionally be locked behind the device's own biometric/PIN unlock (Face ID, fingerprint, or device passcode) before showing any student information, on devices where the user has enabled this.
- Staff accounts are deactivated rather than deleted when someone leaves, so the compliance and audit history their work is part of remains intact and attributable, while their access is fully revoked.
No system is perfectly secure, and this section describes the controls built into the App, not a guarantee against every possible incident. [SCHOOL/ORGANISATION NAME]'s incident-response and breach-notification process: [DESCRIBE OR LINK TO THE SCHOOL'S OWN PROCESS].
8. Where information is stored
This App is self-hosted software: each school runs its own copy, against its own database, on infrastructure the School (or the School's IT provider) chooses and controls. [SCHOOL/ORGANISATION NAME] hosts its instance at: [HOSTING PROVIDER / DATA CENTRE REGION]. Because the School controls its own deployment, the School — not the App's original developer — determines where this information is physically stored and which jurisdiction's law applies to that storage.
Password-reset emails are sent via [SMTP PROVIDER NAME], which handles the delivery of that one email and does not otherwise have standing access to App data. No other third party receives information from the App.
9. How long we keep information
Adjustment records and the audit trail are compliance records and are kept for as long as the School's NCCD record-keeping obligations and its own records-retention policy require: [DESCRIBE THE SCHOOL'S RETENTION PERIOD]. Staff accounts are deactivated (not deleted) on departure so this history remains valid; student photos and uploaded images are removed if a student record is deleted from the App by an admin.
10. Your rights
Depending on the School's jurisdiction, staff and the families of students may have rights to access, correct, or request deletion of information held about them, and to lodge a complaint about how it is handled. Because this App is School-operated software, requests should be made directly to the School at: [PRIVACY CONTACT EMAIL/ROLE]. A staff member can also view and update their own display preferences and avatar size directly from Settings within the App, and can request a password reset at any time.
11. Changes to this Policy
If this Policy changes, the "Last updated" date at the top will change and, where the change is material, the School will notify staff through [NOTIFICATION METHOD, e.g. a notice at next sign-in or a staff email].