Figbloom
Privacy Policy
Last updated: 13 October 2026
This policy covers the Figbloom school-management apps — the parent, student and driver app, and the teacher app — and the Figbloom web console they connect to (together, the "Service"). Figbloom Digital Group ("Figbloom", "we") builds and operates the Service on behalf of the schools that use it. Each school is the data controller for its own students', parents' and staff's information; Figbloom acts as the school's data processor, storing and transmitting that data on infrastructure Figbloom operates.
Information we collect
| Category | What, and from whom |
|---|---|
| Account & identity | Name, role (parent, student, teacher, driver), a school-assigned login ID (most users sign in with this rather than an email address), and school/class assignment — provided by the school when it enrolls a user. A phone number or email is collected only where the school records one or a feature needs it (e.g. M-Pesa payments use a phone number). |
| Location (driver app only) | Precise GPS location, collected continuously — including while the app is in the background or the phone is locked — for the duration of an active school-bus trip, so the bus's position can be shown to parents and school staff tracking that trip. Location is not collected outside an active trip. |
| Academic & attendance records | Grades, assessment results (including CBE strand/rubric scores), attendance marks, timetables and class assignments, entered by teachers or synced from the school's records. |
| Communications | Messages sent between teachers and parents in-app, and notices/ announcements published by the school. |
| Payments | Fee balances and M-Pesa payment references (phone number and M-Pesa transaction code) when a parent pays school fees in-app. We do not collect or store card numbers. |
| Photos | A profile photo, if a user chooses to upload one. |
| Device & push notification data | A device push-notification token, collected today only from Android users of the parent/student/driver app (not yet from the teacher app, and not yet from iOS — see below), used to deliver school-wide announcements the school has marked for push and school-bus trip updates. |
How we use this information
- To run the core features of the Service: attendance, gradebook, messaging, fee payment, timetables, and — for the driver app — live bus-location sharing during a trip.
- To deliver push notifications where they're currently supported (Android, parent/student/driver app only) — for announcements the school has marked for push, and for bus-trip updates. Teacher-parent messages are delivered in-app and are not pushed.
- To authenticate users and keep each school's data separate from every other school's.
- To maintain and secure the Service, including diagnosing technical issues.
We do not sell personal information, and we do not use it for advertising.
Who can see what
Data is scoped to the school it belongs to. Within a school: a parent sees their own children's records; a teacher sees the classes and students they're assigned to; a driver sees the trips they're assigned to and the location they themselves report while a trip is active; school administrators see the records their role is permitted to see. Figbloom staff can access data only as needed to operate and support the Service, under the school's instruction.
Children's data
Because this is a school platform, it necessarily holds data about children. That data is provided and controlled by the school, not collected by Figbloom directly from children. Parents/guardians should direct requests about their child's data to their child's school in the first instance; the school can in turn ask us to act on that request.
Data retention
We retain data for as long as the school's account with Figbloom is active, plus a reasonable period after a school leaves the Service in case the school requests an export. A school can request deletion of its data at any time, subject to any academic-record retention requirements that apply to it.
Your rights
Depending on where you are, you may have rights to access, correct or request deletion of your personal information, including under Kenya's Data Protection Act, 2019. Requests should go to your school first, since the school controls its own records; the school can escalate to us if needed. You can also contact us directly at the address below and we will route the request to the right school.
Security
We use access controls and encryption in transit to protect data held in the Service. No system is perfectly secure, and we work to improve these protections over time.
Changes to this policy
If we make material changes, we'll update the date at the top of this page and, where appropriate, notify schools directly.
Contact us
Questions about this policy or a privacy request: privacy@figbloom.org.