Terms of Service

These terms are between Fleetr Edge Technologies Ltd ("we", "us") and the school that subscribes to School Run ("the School", "you"). They govern the School's use of the School Run web application at the School's own address, together with the notifications it sends and the integration with the School's core Fleetr fleet-tracking account.

Personal data processed through School Run is governed by the Data Processing Agreement, which forms part of these terms. Where the two conflict on a data protection matter, the Data Processing Agreement prevails.

Guardians and staff use School Run under accounts the School creates. They are not parties to this agreement; their relationship is with the School.

There is no public sign-up. Every account in School Run is created by the School, or by invitation sent from the School. Each school occupies its own address and its own separated data.

The School is responsible for who it invites, for what role it gives them, and for removing access when a person leaves. School Run deactivates rather than deletes people who have history attached to them, because deleting a member of staff would orphan the attendance entries they confirmed.

Account credentials are personal to the account holder and must not be shared. The School must tell us promptly if it believes an account has been compromised.

The School and its users must not:

• use School Run to hold data about anyone the School has no lawful basis to hold data about;
• use it for any purpose other than operating the School's own transport service — it is not a general staff-surveillance tool, and the location data in it is about vehicles, not about tracking a driver's private movements;
• give a guardian access to another family's children, or export the roll to anyone who has no reason to hold it;
• attempt to reach another school's data, probe, scan or interfere with the service, or circumvent any authorisation check;
• upload malware, or content that is unlawful;
• resell, sublicense or white-label the service to a third party without our written agreement;
• configure an SMS gateway endpoint that points at a network the School is not entitled to reach; or
• use automated means to extract data at a rate that degrades the service for other schools.

We may suspend an account or a school's access where use of the service presents a risk to children, to other schools, or to the integrity of the platform. Where the circumstances allow it, we will tell the School first.

• Accuracy. The School enters the children, the guardians, the routes and the stops. School Run reports what it was told. A child linked to the wrong guardian, or a stop entered in the wrong order, produces a wrong notification, and that is a data-quality matter the School controls.
• Notices and consent. The School is responsible for telling families how their data is used and for obtaining any consent it relies on, including for a child's photograph.
• Trackers. The School is responsible for the GPS devices fitted to its vehicles, for its core Fleetr account, and for having them working.
• SMS. The School chooses, contracts with and pays its own SMS gateway, and is responsible for having a written processor agreement with that provider.
• Supervision. Nothing in School Run replaces the School's duty to supervise children on and around its buses.

School Run is an aid to running a school transport operation. It is not a child-safety device, and it is not a guarantee of a child's safety, presence or whereabouts.

Concretely, and without limiting that statement:

• A boarding record means a person on the bus pressed a button saying a child boarded. It is a human record and it can be wrong, late, or missed entirely.
• The absence of a record does not mean a child is absent, and its presence does not mean a child is safe.
• Bus position depends on a GPS device, on the vehicle's power, and on a mobile network. Any of these can fail, and a bus that is not reporting looks the same as a bus standing still. School Run surfaces that gap to staff rather than guessing across it.
• Notifications depend on the School's SMS gateway, on mobile networks and on mail delivery, none of which we control. A message may be delayed, may not arrive, and time-critical alerts are deliberately dropped rather than delivered stale.
• School Run never infers attendance from location. It will not tell you a child boarded because a bus reached a stop.

A concern about a specific child at a specific moment is answered by the School's transport office and by the adults on the bus — never by assuming the screen is complete.

We aim to keep School Run available during Kenyan school-run hours and to carry out maintenance outside them. No uptime percentage is committed in these terms. A school that requires a contractual service level should agree one with us in writing; without such an agreement, the service is provided on a commercially reasonable-efforts basis.

Support is provided to the School's nominated staff contacts by email at hello@fleetr.co.ke. We do not provide support directly to parents; parents contact the School.

We may change or withdraw individual features. Where a change materially reduces functionality the School relies on, we will give reasonable notice.

School Run depends on services listed in the sub-processor list. Two of them are the School's own: its core Fleetr fleet-tracking account and its SMS gateway. We are not responsible for the availability, pricing, message charges or conduct of a provider the School selected, and we cannot make commitments on its behalf.

Fees, billing period and payment terms are set out in the School's own order or subscription agreement with Fleetr Edge Technologies Ltd, not in this document. Billing runs from Fleetr Edge Technologies Ltd to the School.

Parents are never billed by Fleetr Edge Technologies Ltd and never pay it anything. School Run processes no payment card or bank details of any kind — there is no payment surface in the application.

SMS charges are billed to the School by the School's own gateway provider, directly.

Fleetr Edge Technologies Ltd owns School Run — the software, its design and its documentation. The School is granted a non-exclusive, non-transferable right to use it for its own transport operation for the term of its subscription.

The School's data remains the School's. We claim no ownership of the children, guardians, routes, attendance or notification records the School puts into School Run, and we do not use them to train models or to build products for anyone else.

We may use aggregated, fully anonymised statistics — counts and performance figures that identify neither a person nor a school — to operate and improve the platform.

Nothing in these terms excludes or limits liability that cannot lawfully be excluded or limited under Kenyan law, including liability for death or personal injury caused by negligence, or for fraud.

Subject to that, and to the extent permitted by law:

• School Run is provided without warranty that it will be uninterrupted, error-free, or that any particular notification will be delivered.
• Neither party is liable to the other for indirect or consequential loss, loss of profit, loss of business, or loss of goodwill.
• Our total aggregate liability arising out of or in connection with these terms in any twelve-month period is limited to the fees paid by the School to us in the twelve months preceding the event giving rise to the claim.
• We are not liable for a failure or delay caused by something outside our reasonable control, including a GPS device fault, a mobile network outage, a failure at the School's chosen SMS gateway, or a power or connectivity failure at the School.

The limits in this clause do not apply to either party's obligations under the Data Processing Agreement, which carries its own allocation of responsibility.

Either party may terminate at the end of the then-current subscription period by written notice, or immediately on written notice if the other commits a material breach it does not remedy within thirty days of being asked to.

We may suspend access immediately, without notice, where continued use presents a serious and immediate risk to children, to other schools or to the platform. We will tell the School why, as soon as we reasonably can.

On termination, and in this order:

1. Access ends. The School's users can no longer sign in, and inbound events from core Fleetr stop being accepted.
2. The School may take its data. For thirty (30) days after termination, the School may request an export of its data — children, guardians, routes, stops, runs and the attendance record — in a structured, machine-readable format. We provide it at no charge for a standard export.
3. Then it is deleted. After that window, we delete the School's data from live systems, including uploaded photographs and crests. Deletion is confirmed to the School in writing on request.
4. Backups age out. Data in encrypted operational backups is deleted on the ordinary backup cycle rather than being surgically removed from each snapshot. It remains subject to the confidentiality and security obligations in the Data Processing Agreement until it ages out.

A school that wants a different arrangement — a longer window, or immediate deletion with no export — should say so in writing before termination takes effect.

Note: this clause describes a process carried out by Fleetr Edge Technologies Ltd on request. It is not an automated function of the software, and the thirty-day window is a contractual commitment rather than a timer that runs by itself.

We may update these terms. Material changes are notified to the School's administrator contacts in writing before they take effect. Continued use after that date is acceptance; a School that does not accept a material change may terminate at the end of its current subscription period.

These terms are governed by the laws of Kenya, and the courts of Kenya have exclusive jurisdiction. The parties will attempt to resolve any dispute in good faith before commencing proceedings.

Contact: hello@fleetr.co.ke.