Sub-processors
Every party outside your school that touches School Run data, what it touches, and where it sits.
Effective from 24 August 2026.
In short
Five parties can see some part of a school's School Run data. One of them — the SMS gateway — is chosen and contracted by the school, not by Fleetr Edge Technologies Ltd, which is why it has a section of its own.
Two facts on this page are marked pending confirmation rather than guessed. See the last section.
The list
| Party | What it processes | Where |
|---|---|---|
| Fleetr Edge Technologies Ltd The School Run application and its PostgreSQL database | Everything the School puts into School Run: children, guardians, staff, routes, stops, runs, the attendance record, bus positions and the notification log. | Pending confirmation Hosting provider and region — see below. |
| Core Fleetr Operated by Fleetr Edge Technologies Ltd | Vehicle identity and telemetry for the School's buses: position, speed, bearing, ignition state and the time of each fix, plus the driver assigned to each bus. It also serves the live tracking page School Run embeds, and the share links issued from a bus's page. It holds no child or guardian records. | Same infrastructure as School Run. |
| Traccar GPS ingestion inside core Fleetr | Raw position reports from the GPS device fitted to each bus, before core Fleetr forwards them on. Vehicle data only — it never sees a child or a guardian. | Open-source software run by Fleetr Edge Technologies Ltd on the same infrastructure. No separate company receives the data. |
| Linode Object Storage Akamai Technologies | Uploaded files only: children's photographs on a private bucket, school crests on a public one. No database records, no attendance, no contact details. |
Region sg-sin-1
https://sg-sin-1.linodeobjects.com
Outside Kenya. See clause 8 of the DPA.
|
| Email relay Outbound SMTP | The content of emails School Run sends: invitations, password resets, and transport notifications where a guardian has chosen email. A notification names the child, the stop and the time, and is addressed to that guardian. | Pending confirmation Provider and region — see below. |
| Loopy Labs Ltd Software development and infrastructure management | Builds School Run and manages the servers it runs on. Its named engineers hold production access in order to deploy, diagnose faults and restore backups, so they can in principle reach any record in the system. They do not run the service day to day, and have no dealings with schools, guardians or children. | Kenya. Same infrastructure as School Run. |
| Google LLC Maps JavaScript API, Google Fonts | Map tiles for the staff fleet map, and web fonts on every page. Both are fetched by the browser, so Google receives the visitor's IP address and request metadata. School Run sends Google no child, guardian or attendance records. | Google's global infrastructure. |
Your school's SMS gateway
School Run ships with no SMS provider. A school enters its own gateway — the endpoint, the credentials and the message format — in its own settings, and School Run posts to whatever it was given. There is no platform default to fall back on, deliberately: a fallback would spend somebody else's credit and route a child's data through a provider nobody chose.
What this means for the school:
- The provider sees the message. A text alert carries the child's first name, the stop, the time and the guardian's phone number. That passes through the provider the school selected.
- The school is the controller in that relationship, and needs its own written processor agreement with the provider under section 42 of the Act. Its procurement team will be asked for that document, not for this one.
- Fleetr Edge Technologies Ltd gives no notice of changes there and makes no commitment on that provider's behalf. It is not on the list above because it is not a sub-processor of Fleetr Edge Technologies Ltd.
- What School Run does do: encrypt the credentials at rest, keep them out of API output and out of every log line, refuse an endpoint that resolves to a private or internal network address, and never log the message body or the request headers.
A school that has not configured a gateway sends no SMS at all. Email still works.
Not sub-processors
To be explicit about what is not here:
- No analytics or advertising provider. School Run runs no analytics script, no tag manager, no advertising pixel and no session-replay tool.
- No payment processor. There is no payment surface in the application, and no card or bank details are processed anywhere in it.
- No AI or machine-learning provider. No school data is sent to any model, for inference or for training.
- No data broker, and no resale of any kind.
Notice of changes
Fleetr Edge Technologies Ltd gives subscribing schools at least thirty (30) days' written notice before adding or replacing a sub-processor on this list, and a school may object on reasonable data-protection grounds within that period. The mechanism is clause 7 of the Data Processing Agreement.
What is not yet confirmed
Two rows above are marked pending confirmation. They are marked rather than filled in because the answer is not currently recorded anywhere a reader could check, and a plausible guess in a sub-processor list is worse than an admission:
- The hosting provider and region for the application and database. The deployment configures this outside the application, so this page cannot read it.
- The outbound email provider. School Run sends over SMTP to whatever relay the deployment names; no provider is fixed in the software.
A school that needs both answers before signing should ask for them in writing at hello@fleetr.co.ke, and this page will be updated once they are settled.