This summary explains how KULNA handles data during demos, trials and operation. The detailed version and contracts are updated according to the school's country and the agreed service.
Last updated: September 2026School, student, authorized pickup, staff and bus operating data, plus attendance, movement and handover records, depending on the modules the school chooses to enable. We also receive the contact details sent by whoever requests a trial.
The school decides what data it enters, which roles are authorized, how long the service runs and its dismissal policies. KULNA acts as a technical provider that helps the school carry out these instructions, and never gives any school access to another school's data.
To run accounts, link each student to their school and authorized pickups, carry out movement and transport, show status to authorized roles, send required notifications, and for support, protection, auditing and reliability.
We use permissions by role, school and branch, protected sign-in sessions, an audit log for sensitive actions, and logical separation between schools. We never ask a school to publish student data on the public page.
Access is limited to authorized users and to the technical infrastructure providers needed to run the service, under their contractual and security controls. We do not sell student or guardian data, and we do not use it for targeted advertising.
Final retention periods are set in the school's agreement according to the record type and local requirements. By default the notification center keeps items for 90 days, and bus location points are deleted after the period the school chooses. Core student and safety records are never deleted automatically without a documented, agreed procedure. When the relationship ends, export or deletion is carried out, taking backups and records that must be kept into account.
Guardians and staff start with their school, because the school verifies identity and the relationship to the student and decides on correction or access limits. KULNA works with the school to carry out valid technical requests.
These permissions are only used when a feature that needs them is turned on and the device allows it: location for optional geographic checks, the camera for scanning QR codes, and the microphone for recording a local call the school chooses. The school can turn these features off in its settings.
We only enable Google Analytics after the visitor chooses to allow measurement, and only on public pages, to understand visits, the success of trial requests and how the service is presented. This measurement never runs inside a school account, a guardian account or a device screen, and we never send it student names or school operating data. Measurement can be declined without affecting use of the website.
Write to us, and please avoid sending a student's ID number or sensitive documents in the first message.
[email protected]