Legal
Privacy Policy
Last updated: July 2026
Tutela holds children's names, dates of birth, photographs, home addresses, medical notes and their location on a bus. This page says plainly what we do with all of it.
1. Who we are
Tutela AU is operated by Zeus ICT Services Pty Ltd t/a Tutela AU (ABN 47 654 725 434), an Australian company. We are bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles.
2. Who holds the information, and who processes it
This distinction matters more than anything else on this page.
The transport operator — the bus company your child's service runs with — collects children's information and decides what is recorded and why. They hold it.
We process it on their behalf. We provide the software that stores it and shows it to the right people. We do not decide what is collected, we do not use it for our own purposes, and we do not disclose it to anyone the operator has not authorised.
So if you are a parent or guardian and want to know why something is recorded about your child, or want it corrected or removed, ask the transport operator first — they can act on it directly in the platform. If they need us, they will involve us.
3. What is held in the platform
- About children: name, date of birth, school and year, the stop they use, a photograph where the operator uses photo verification, home address where the service is door-to-door, medical or behavioural notes the operator needs a driver to act on, and the record of which bus they boarded and left, when, and where.
- About parents and guardians: name, contact details, relationship to the child, and the notifications they have received.
- About drivers and operator staff: name, contact details, role, licence and medical certificate expiry, child-protection clearances and their expiry, and the record of runs operated and checks performed.
- About the service: vehicles, stops, routes, timetables, pre-start checks, defects, and vehicle compliance documents.
- Technical records: sign-in times, IP addresses, device identifiers for remembered devices, and a log of who viewed which student record.
4. Location data
Where an operator uses live vehicle tracking, the platform records the position of the vehicle during a run. Children are associated with a vehicle by the boarding record, not tracked individually, and no tracking occurs outside an active run.
5. What we do not do
These are architectural commitments, not preferences:
- No third-party services run in the platform. No analytics, no advertising or tracking pixels, no session recorders, no chat widgets, no externally hosted fonts, no third-party map or geocoding services. Every page loads from us and nowhere else. A map tile request would tell a stranger which streets were on screen, and on this platform that is where a child lives.
- We do not sell, rent or share personal information for marketing, profiling or any commercial purpose.
- We do not use children's information to train machine-learning models.
- We do not use it to build products for anyone else, including aggregate products, unless the data has been irreversibly de-identified.
6. Who can see what
Access is limited by role, and the limits are enforced by the software rather than by policy. A dispatcher can see which children are on a bus without being able to open a medical note or an address list. A driver sees today's manifest for their own run and never the student register.
Each operator's data is isolated from every other operator's. Access to a student record is logged — who looked, at what, and when — and unusual bulk access is detected and can suspend the session that is doing it.
Photographs of children are never served from a content delivery network. They are delivered through a permission-checked, short-lived link, are not cached by browsers, and are removed from a driver's device when the run completes.
7. Access by our staff
Our staff do not browse operator data. Access happens only where it is necessary to provide support that has been requested, investigate a fault, or meet a legal obligation — and access to student records is logged in the same way as anyone else's.
8. Where it is stored
Data is stored in Australia, on Australian infrastructure, and is encrypted in transit and at rest. Backups are held in Australia and encrypted. We do not transfer personal information overseas.
9. How long it is kept
Retention is set by the operator, within the limits their accreditation and the law impose.
Safety records are an exception. Boarding and alighting events, pre-start checks and defect reports are append-only: corrections are recorded as new entries that supersede earlier ones rather than replacing them. That is what makes the record worth anything after an incident, and it means these entries cannot be edited or deleted, including by us.
When an operator leaves the platform, their data is retained for 90 days so an export can be arranged, then deleted, unless the law requires us to keep it longer.
10. Your rights
You may ask for access to the personal information held about you or your child, ask for it to be corrected, and complain about how it has been handled.
Ask the transport operator first — the information is theirs to act on and they can do it immediately. If you cannot resolve it with them, or your question is about something only we can answer, write to info@tutela.au. We will respond within 30 days.
If you are not satisfied with our response you may complain to the Office of the Australian Information Commissioner.
11. Data breaches
If personal information is accessed or disclosed without authorisation and serious harm is likely, we will notify the affected operator without undue delay and support their obligations under the Notifiable Data Breaches scheme, notifying the Commissioner and affected individuals where the scheme requires it.
12. Cookies
The platform sets only the cookies it needs to work: a session cookie to keep you signed in, a security token to prevent cross-site request forgery, and — if you choose to remember a device — an opaque token that lets that device sign in again. There are no advertising or analytics cookies, and nothing to consent to, because there is nothing optional to decline.
13. Changes to this policy
We will update this page when our practices change, and will notify operators of material changes. The date at the top shows when it last changed.
14. Contact
See also our Terms of Service.