WeOrdaHow we protect student data.
WeOrda holds children's names, stops and parent numbers on behalf of the operators and schools we serve. Here is what we collect, where it lives, who can see it, and how it leaves. Plain language; the binding terms are in the DPA.
Less to protect in the first place.
The safest data is the data that never rides on the bus, never sits on paper, and never gets collected.
No hardware on the bus
WeOrda runs on the driver's phone. Nothing to install, unplug, or leave behind with data on it.
Location only on the route
Phone GPS is recorded between Start Route and Exit Navigation, and only because the driver allows it. It follows the route, not the person.
Nothing on paper
Route sheets with home addresses, parent numbers and medical notes stop riding taped to the dash.
Need-to-know access
A driver or aide sees the route assigned to them, while it runs. Office staff see their own operation. Parents see their own child.
Only what the trip needs.
Operators upload their own rosters. WeOrda processes the minimum needed to run and verify the route, and never sells any of it.
Name, stop, school and ride schedule, plus the parent or guardian contact, from the operator's roster. A photo only if a parent adds one, visible to that parent.
Name, phone, credentials and expiry dates, the inspections and confirmations they record, and route GPS while a route is running.
A phone number verified by a one-time code, the ride confirmations they send, and location only if they allow it while the app is open.
Encrypted, logged, and in the United States.
Hosted on Google Cloud in the US. The safeguards below are the ones we commit to in the Data Processing Addendum.
Infrastructure
- Encrypted in transit (TLS) and at rest in cloud storage
- Hosted on Google Cloud Platform, United States
- Encrypted backups, rotated out within 90 days
- Every subprocessor listed publicly, 30 days notice before a new one
Access
- Role-based access: driver, aide, office, oversight, parent
- Every account authenticated; drivers and parents sign in with a one-time code
- Multi-factor authentication for administrative access
- Access to production systems logged and monitored; staff access on a need-to-know basis
The operator owns it. We just run it.
What happens to the data at the end of a contract, and who can ask for what.
Questions from your IT or legal team?
Send them to privacy@weorda.com, or bring them to the demo.