Who we are
This policy covers Transit Ops, which runs the Transit Ops live map, performance reports and operator tools at transitops-qld.vercel.app. We follow the Australian Privacy Principles in the Privacy Act 1988 (Cth). Where a bus operator we work for is a contracted service provider to the Queensland Government, we also follow the Queensland Privacy Principles for the information we handle for that operator.
Questions or complaints: dunncr@me.com.
Who this policy is about
- Visitors to the public live map, performance reports and website.
- People who use the operator tools: controllers, administrators and other staff of a bus operator ("operator users").
- Bus drivers who use the driver screen on their phone. Drivers also get a shorter driver privacy notice at sign-on.
- People whose email address is added to receive summaries or alerts.
What we collect
| Who | Information | Why |
|---|---|---|
| Public visitors | Nothing that identifies you. Your browser connects to our host and loads map tiles and fonts from other providers, which receive your IP address. | To show the map and reports. |
| Operator users | Name, email address, role, operator, a hashed access code, sign-in times, the pages you open, the actions you take (for example acknowledging an exception, recording a fix, changing a setting), and your IP address and browser type. | To sign you in, keep each operator's data private, and keep an audit trail your operator can review. |
| Drivers | Name, email address, sign-in details, answers to the sign-on fitness and vehicle check (including whether you are under the influence of drugs or alcohol, and whether you are fatigued), bus number, speedometer readings, defect reports and photos, the trip you connect to, your phone's location and speed while connected to a trip, late reasons, help requests, messages and acknowledgements, passenger counts, voice commands as recognised text, your end-of-shift summary and feedback. | To run the driver screen, let the control room support you, record fitness-for-duty and vehicle checks for your operator, and keep the bus off the road when it isn't safe. |
| Email recipients | Email address and which emails you receive. | To send the daily summary, alerts and bus count notices. |
Some of this is sensitive information under the Privacy Act, in particular answers about drugs, alcohol and fatigue. We collect it only for the driver's operator, with the driver's consent at sign-on, and only so the operator can meet its safety and fitness-for-duty obligations.
We don't collect voice recordings. When a driver turns the microphone on, speech recognition is done by the phone's own browser (Google on Android, Apple on iPhone) under that provider's privacy terms; Transit Ops receives only the recognised words of commands that start with “Transit”.
Vehicle positions, timetables and delays come from TransLink's open real-time data. They describe buses, not people.
How we use it
- To provide the service to the bus operator: the control room, driver screen, analysis and reports.
- To keep the service secure, investigate problems, and keep the audit trail.
- To bill the operator, using the agreed peak bus count (which is about buses, not people).
- To contact operator staff about their account, the service, or changes to these policies.
We don't sell personal information, use it for advertising, or use driver information to make decisions about a driver's employment. Those decisions are for the operator.
Decisions made by the system
Some steps happen automatically, and could significantly affect a driver's work on the day:
- If a driver answers yes to being under the influence of drugs or alcohol, the driver screen stops them connecting to a trip that day and tells them to report to a supervisor. A supervisor at the operator can stand the driver down, but can't clear them to drive that day.
- If a driver reports being fatigued, or the bus isn't fit to depart, the driver waits until a supervisor at the operator clears them or stands them down.
- While the bus is moving above about 8 km/h, the driver screen can't be tapped or typed on, and our server refuses input from a moving bus, except a few voice commands.
These use the driver's own answers and the phone's location and speed. A person at the operator makes every decision about whether a driver works.
Who can see it
- Your operator. Each operator sees only its own users, drivers and data. Operator administrators can see the audit trail for their operator.
- Transit Ops, to provide, support and secure the service.
- Our service providers, listed below, only as needed to run the service.
- Anyone the law requires us to disclose to, or where disclosure is otherwise permitted by the Privacy Act (for example to lessen a serious threat to someone's safety).
Public performance reports show results by operator and route. They contain no personal information.
Where it is stored, and overseas providers
The database is in Sydney, Australia (Neon, on Amazon Web Services). The website and its server code run on Vercel, which processes requests in the United States. Email, once switched on, is sent by Resend, in the United States. Map tiles come from CARTO and fonts from Google. These providers may see personal information, or your IP address, as it passes through them. We choose providers that protect information to a standard similar to the Australian Privacy Principles and bind them by their terms of service. See security and data handling for the full list.
How long we keep it
We keep an operator's data for as long as the operator uses Transit Ops, and delete it within 90 days after the subscription ends unless the operator asks us to return it first or the law requires us to keep it longer. A driver's live location is overwritten every few seconds while connected; only the position at the moment of a late reason or help request is kept with that record. Feed data about vehicles is kept for up to 90 days (positions) or about 13 months (road speeds). More detail is on the security and data handling page.
Accessing or correcting your information
You can ask for the personal information we hold about you, or ask us to correct it, by emailing dunncr@me.com. If you are an operator user or driver, your operator controls your account and records, so we may pass your request to them and work with them to answer it. We'll respond within 30 days.
Security and data breaches
We protect information with encrypted connections, hashed access codes, role-based access, and an audit trail. If a data breach is likely to cause serious harm, we will tell the affected operator promptly, and notify affected people and the Office of the Australian Information Commissioner as the Notifiable Data Breaches scheme requires.
Complaints
Email dunncr@me.com and we'll reply within 30 days. If you aren't satisfied, you can complain to the Office of the Australian Information Commissioner. For information handled for a Queensland government contract, you can also contact the Office of the Information Commissioner Queensland.
Changes
We'll post changes here with a new date, and tell operators by email before a significant change takes effect.
Questions about this privacy: dunncr@me.com