Privacy Policy

The service stores the records a school needs to operate. Depending on which modules a school uses, this can include:

• School account information — the school’s name, code, campus and configuration.
• Student information — name, class and section, enrolment and admission details, and family links.
• Guardian information — parent and guardian names and mobile numbers, used to identify a family and to sign in.
• Employee / staff information — staff names, roles, mobile numbers and employment records held by the school.
• Attendance — daily and per-period registers, and, where a school connects a biometric device, the punch records it sends.
• Academic and results information — marks, exams, report cards and remarks.
• Fees and payment records — demands, receipts, concessions, refunds and reconciliation entries. We do not collect card or bank-account credentials inside the application.
• Photographs — where a workflow uses them (for example a student record, a gate pass, or a message attachment), stored as access-controlled records rather than public files.
• Driver / location data — only where a school enables transport tracking, and only from the driver’s device while a bus run is active, to show the live position of the bus.
• Device / messaging registration — a push-notification token for a device that opts in, so the school can send notices to it.
• Sign-in records — each sign-in attempt, with the network address and a description of the device, kept as a security record.

Information is used only to provide the service to the school: to admit and manage students, take attendance, record marks, raise and collect fees, issue certificates, arrange transport, and communicate with families and staff. It is not used for advertising, and the application contains no advertising software.

There are no passwords. A user signs in with their mobile number and a one-time code delivered on WhatsApp (Meta Platforms). A school may also choose to send notices to families over WhatsApp or as in-app notifications. When a school enables push notifications, delivery uses Firebase Cloud Messaging (Google). A message carries only what is needed to identify the notice; the school controls what is sent.

Location is requested only for the transport driver role. When a driver starts a run, the app shares the device’s location as a foreground service so families can see the bus on its route. Location is not collected for students, guardians, or any other staff role, and is not collected when a run is not active.

We do not sell personal information and do not share it for advertising. Information is processed by the infrastructure and communication providers the service depends on — the school’s hosting, Meta (WhatsApp) for sign-in codes and messages, and Google (Firebase Cloud Messaging) for push notifications — solely to deliver the features above.

A school’s records are retained for as long as the school operates the service, because they are records the school is often legally obliged to keep. A school administrator can correct records within the application. To request deletion of a family’s or a member of staff’s information, contact the school, or contact us through the support page; requests are handled in line with the school’s own obligations.

Access is scoped by role and, where applicable, by class section, so a user sees only what their role permits. Data is transmitted over HTTPS. Sign-in codes are stored hashed, and photographs and documents are served only through access-controlled routes rather than as public files.

The application is used by school staff and by parents or guardians. Information about students is entered and managed by the school; students do not create their own accounts.

For any privacy question, or to request correction or deletion, contact the school that holds the records, or reach us through the support page. This policy may be updated; the date above shows when it last changed.