Privacy Policy
Last updated: 2026-08-01
This is an engineering-baseline policy, not a legal document. It accurately describes what this application actually does with data today. It has not been reviewed by a lawyer and is not a substitute for one — see docs/COMPLIANCE.md in this project for the full regulatory context and known gaps before treating this as sufficient for a real commercial launch in any specific country.
No student, teacher, or parent personal data
Kaylisting does not collect, store, or process any individual student's personal data — no student roster, no attendance, no fee/payment records, and no per-student academic or achievement records exist anywhere on the platform. Teachers and parents aren't identified by name or phone number either: a teacher is known only by a school-assigned employee code, and a parent login is a system-generated credential the School Admin issues, not tied to any name, phone number, or specific child. There is no data path that identifies, or links a login session to, a specific person or family beyond the login itself.
What Kaylisting does — and what your school controls
Kaylisting operates the platform: hosting, security, and the technical infrastructure your school runs on. Your school's School Adminis who actually operates your school on it — they have complete administrative access to every record your school holds (teachers, academic structure, homework, notices, and everything else covered below), because running the school day-to-day requires that access. Kaylisting doesn't decide what your school does with that data; your School Admin does.
Kaylisting's own platform staff cannot see your school's records — no homework content, notices, or messages. Every school's data is walled off from every other school at the database level (row-level security), and that wall applies to the platform operator too, not just other schools. What the platform operator can see, for billing and support purposes only, is: your school's name and subdomain, your subscription plan, and any payment reference (UTR) you submit when paying your subscription — needed to verify that specific payment actually went through.
What we collect
School Admin: name, email, phone (optional), and a securely hashed password — someone has to be reachable to actually run the school account. Teacher: email, employee code, and a securely hashed password — no name or phone number is collected. Parent: a school-issued login (a system-generated email and a securely hashed password) with no name or phone number attached at all; after signing in, a parent picks a class and section at runtime and sees read-only notices, events, homework, classwork, and school-wide achievements, with no individually identifying data behind it. Depending on your role, we also hold: leave requests, notices, events, and achievement records. All of this exists to operate the school — there is no data collected beyond what a school actually needs to run its daily operations.
No tracking, no profiling, no advertising
There is no ad tech, no third-party analytics or tracking scripts, and no behavioral profiling of any user. This is true by construction: none of that infrastructure exists anywhere in this application.
How long we keep data
Records are never hard-deleted while your school has any real activity on it — an archived class, a suspended teacher account, and similar are marked as such via a status change, not erased, because schools have real record-keeping obligations that require this history to stay intact. This applies at the whole-school level too: if a school's account is ever suspended and stays inactive, it's archived, not deleted — and stays that way permanently once it has enrolled even one real teacher. The platform operator can only ever permanently delete a school account that was never actually used (an empty registration with no real staff, records, or activity) — never one with genuine data. If you want data corrected, exported, or deleted where that's legally possible, see "Your rights" below.
Your rights
You can request access to, correction of, erasure of, or a portable export of the data we hold about you from your account's security page once you're signed in. A School Admin reviews and responds to every request. Erasure requests are handled case by case — some records can't be fully deleted where retention is legally required (see above).
How we protect your data
Passwords are hashed with Argon2id, never stored in plain text. Optional two-factor authentication (an authenticator app code) is available from your account's security page. Every school's data is isolated from every other school at the database level (row-level security), not just in application code. Changes to sensitive records are logged with who made them and when.
Contact
Questions about this policy or your data should go to your school's administrator, who can also submit or resolve a data request on your behalf.