Security & data

How we look after your school's data.

Most of what StudentAid holds is about children. This page sets out, plainly, where that data lives, how it is protected, who can see it and how long it is kept. The privacy policy has the full detail.

Where it lives

Hosted, encrypted and backed up every night

hub

Hosted on Google Cloud

Our servers and databases run on Google Cloud in Mumbai, India.

restore

A backup every night

An encrypted copy of the databases goes to Amazon Web Services storage in India every night, locked with a key only we hold. Copies are kept for up to 12 months.

https

Encrypted in transit

Every StudentAid website and app talks over HTTPS, and browsers are told to use nothing else on any StudentAid address.

key

Sensitive numbers encrypted at rest

Government ID numbers are encrypted when stored, shown only as the last four digits, and revealed in full only through one deliberate action that is logged.

lock

Sign-in by one-time code

People sign in with a one-time code sent to a verified phone. Codes are stored hashed and expire in minutes; app sessions can be revoked.

visibility_off

No tracking of parents

The parent app takes one location reading when a parent checks in at pickup, and never asks for background location.

Who can see what

Access follows the job

These boundaries are enforced by the system, not by convention: a request for data outside them fails rather than returning a filtered result.

WhoSees
A parentTheir own children only: the child's plan, journey events and the bus carrying them.
A driverThe children on the trip they are running, and the checks needed to board each one safely.
School staffTheir own school's records, limited further by their role. Only the school's owner sees billing. What each role sees →
A transport operatorTheir own vehicles, drivers and trips.
StudentAid staffOnly what is needed to run and support the service. Access to a school's data is restricted and logged.
Records you can stand behind

Built to be checked later

history

An audit log

Significant actions are written to a log: who approved a driver, who released a child, who changed a setting. It exists so a school can answer questions about its own records.

fact_check

A pickup record that cannot be rewritten

Who collected a child, how and when is append-only. It cannot be edited, and it is not deleted on a timer.

qr_code_2

Cards and passes that cannot be guessed

Each child's boarding card carries a random code that cannot be guessed, and a lost card is cancelled straight away. Collection passes are signed, time-limited and can be withdrawn at once.

verified

Reports anyone can check

Compliance reports carry a reference number and a signature, so a printed copy can be checked against our records.

Data retention

How long we keep it

Our default is 30 days. Information that exists to run a journey is deleted 30 days after it stops being useful, by scheduled jobs that run every night.

WhatHow long
Where a bus was, minute by minute30 days, then permanently deleted.
Location on a pickup check-in or a stop at a family's door30 days, then the location is removed. The check-in or stop itself stays.
A driver's government ID number and ID scans30 days after the driver is rejected or removed. Only the last four digits stay, for the record.
One-time sign-in codesMinutes. Stored hashed, never readable.
Nightly backup copiesUp to 12 months, encrypted, then deleted.
A child's record and journey historyWhile the child is enrolled, and afterwards for as long as the school must keep it. The school decides, and can ask us to delete it.
Who collected each childKept, append-only. A pickup record that erased itself would be worth nothing on the one day it is needed.

The apps show parents and drivers the last 30 days. The school keeps the full record in its portal. When a school stops using StudentAid, its data is made available for export and then deleted, except where the law requires us to keep it.

What we never do

Lines we do not cross

block

No advertising, no sale of data

There is no advertising in the apps and no advertising code in them. We do not sell or rent personal information to anyone.

not_interested

No training on your data

We do not use personal information to train machine-learning models. The optional AI helpers are off unless a school switches them on.

notifications_active

No silencing an emergency

Parents can turn off ordinary notifications, but an SOS cannot be switched off. There is no setting that could suppress one.

No system is perfectly secure. If a breach affects your information, we will act to contain it and tell the affected schools, and you, without undue delay.

Questions

What schools ask about data

Where is our school's data stored?

On Google Cloud in Mumbai, India. An encrypted copy of the databases is made every night to Amazon Web Services storage in India and kept for up to 12 months.

Can another school see our children?

No. Each school sees only its own children, even where one van serves two schools. The boundary is enforced by the system, and a request outside it fails.

How are government ID numbers protected?

They are encrypted when stored, shown only as the last four digits, and revealed in full only through one deliberate action that is logged. A driver's number is deleted 30 days after they are rejected or removed.

Do you use our data to train AI?

No. We do not use personal information to train machine-learning models. The optional AI helpers are off unless your school switches them on.

The full detail: Privacy Policy · Terms of Service · Contact us