Trust, privacy & security
SchoolBudi is built for children's wellbeing data. Here's plainly what we collect, who can see it, and how we keep it safe. This page is maintained by us; it is not an independent certification.
What we collect
- A child's first name and a class-scoped 4-digit PIN they can change.
- Mood check-ins (1–5) and which calming tools they tried.
- Optional "request to talk" flags sent to the class teacher.
- Teacher and school admin accounts (email + name) for sign-in.
We do not collect surnames, contact details, or location for children.
Who can see what
- Children only see their own check-ins and toolkit.
- Teachers only see check-ins for classes they own.
- School admins see classes for their own school.
- Lovable platform staff do not browse customer data and access is logged.
Access rules are enforced in the database with row-level security, so the rules apply equally to the app, scripts, and direct API access.
How data is protected
- Encrypted in transit (HTTPS) and at rest in the managed database.
- Writes to check-ins and meeting requests go through audited server functions only.
- Teacher/admin accounts use email + password with optional leaked-password screening.
- Backups are kept by the platform provider and rotated regularly.
Retention & deletion
Check-in data is retained while the class is active. A school admin can request deletion of a class, a child, or the school's full record at any time — get in touch and we'll action it.
Children & safeguarding
SchoolBudi is a wellbeing tool, not a clinical or crisis service. If a check-in flags concern, teachers should follow their school's existing safeguarding process. "Request to talk" is delivered to the class teacher only.
Get in touch
Questions, data requests, or to report a concern: contact your school admin, or reach SchoolBudi via the school account you signed up with.
This page is editable project content and is not an independent certification.