Legal
Privacy Policy
Last updated: 4 November 2026
1. What we collect
Depending on your role, the Service may hold: names, email addresses, phone numbers, and login credentials; admission numbers, dates of birth, and gender; national ID numbers and ID photos for staff and guardians; medical information (allergies, conditions, medications, and school clinic visit records) for learners; emergency contact details; attendance and academic records; photos (profile photos, staff signatures) and, where you send them, photo or voice-note attachments in messages, incident reports, homework, and announcements; and, for the driver/minder role only, live GPS location while a transport run is in progress. Where your school uses fees, the Service also holds fee structures, balances, payments and receipts, and — for an M-Pesa payment — the paying phone number, the amount and the M-Pesa transaction reference. We never see or store M-Pesa PINs, bank card numbers or bank logins. For security, we also record sign-in activity (time, IP address and device type) and a history of changes made to records.
2. How it's used
Information is used to operate the Service for your school — running attendance, academic records, communication between staff and guardians, staff administration, transport coordination, and related school operations. It is not used for advertising, and we do not run any advertising or analytics tracking in the app.
3. Who can see it
Access is restricted by role within your own school — for example, a facilitator only sees learners in their own grade, and one school's data is never visible to another school, enforced at the database level, not just in the app. See our access-control design in the product for specifics.
4. Third parties and service providers
We use a small number of service providers to operate the Service, none of whom may use your data for their own purposes: a server host in Kenya that runs the Service and its database; an email provider to deliver notifications; Africa's Talking to deliver SMS notifications where SMS is enabled; Backblaze to store uploaded photos and files and our encrypted nightly backups; Safaricom (M-Pesa), only when a school connects its own paybill or till, to process a payment a guardian chooses to make; Google Maps to display transport maps; your browser's push service (for example Google or Apple) to deliver notifications you've turned on; and Sentry to collect crash reports. Crash reports contain only the error and its stack trace — no names, no account identity, no cookies, no request contents, and nothing else about you or your device. We do not sell personal data, and we do not share it with third parties for their own marketing.
5. Where data is stored
The Service and its main database run on a server in Kenya. Uploaded photos and files, and encrypted backups, are stored with Backblaze in the United States. Files are kept in private storage and are only reachable through the Service by someone with access to them; backups are encrypted before they leave our server. Messages between users are encrypted in the database.
6. Children's data
Learner records necessarily include information about minors, provided and managed by the school on behalf of parents/guardians — Schoohubke is provided to schools as their administrative system, not marketed directly to children, and a learner's account is created and managed by their school. Guardians can access their own children's records through the guardian portal. A school administrator is responsible for ensuring guardian consent is obtained as required by law before a learner's information is entered into the Service.
7. Location data
Only the driver/minder role's device location is collected, and only while actively running a transport route — this powers the live map an admin and affected guardians see during pickup and drop-off. It is not collected from any other role, and is not used for advertising or retained beyond the operational history needed for transport records.
8. Data retention
Data is retained for as long as your school's account is active, or as required by applicable record-keeping obligations. Schools may request deletion of their data on account closure, subject to legal retention requirements. Some operational logs (system activity, notifications) are automatically pruned on a rolling retention window your school administrator controls.
9. Account and data deletion
Because accounts are provisioned and managed by your school, an individual (a staff member, guardian, or learner) requests deletion of their account and personal data through their school administrator, or directly from us via our Contact page — include your name, your school, and the account you're asking about, with the subject line "Account deletion request". A school administrator can request deletion of the school's entire account and all associated data the same way. We'll confirm what will be deleted, any legal retention obligations that apply, and when it will be complete.
10. Cookies and local storage
The Service uses browser storage to keep you signed in and to remember basic preferences. See our Cookie Policy for details.
11. Your rights
Under Kenya's Data Protection Act, 2019 you have the right to be told how your data is used, to access it, to have it corrected, to object to its processing, and to ask for it to be deleted, subject to the school's legal record-keeping duties. Your rights under Kenya's Data Protection Act, 2019 explains each of these in plain language. Requests can be made through your school's administrator or our Contact page.
12. Changes to this policy
This policy may be updated from time to time. Material changes will be reflected here with an updated date.