Privacy-first architecture
Student first names are hashed and stored as aliases before ever contacting AI providers, so personally identifiable information never leaves your workspace.
We designed Staffroom around real classroom safeguards: hashed identifiers, role-based access, and privacy-friendly analytics. Here’s how we keep your pupils and staff protected.
Student hashing
Every student name is converted to a deterministic hash and alias (e.g. “Pupil-AB12CD34”). AI prompts never contain raw names.
Data retention
Schools can export or delete reports at any time. Backups are retained for 30 days in encrypted storage.
Analytics without cookies
We use Umami Analytics in anonymised, cookieless mode. No consent banner is required under UK GDPR/PECR.
Security is embedded in the product—from how we store data to how we plan future features.
Student first names are hashed and stored as aliases before ever contacting AI providers, so personally identifiable information never leaves your workspace.
Staffroom runs on Vercel with encrypted PostgreSQL storage. Access is controlled with role-based permissions, audit trails, and automated backups.
Only the teachers and admins you invite can access a class. Memberships are synced with Clerk organisations so you stay in control of who can view pupil information.
We keep a clear data processing log, support subject access requests, and provide downloadable report exports for your own archiving.
We provide signed Data Processing Agreements, full privacy policies, and Safeguarding statements on request.
Have safeguarding templates you already use? Send them over—we’ll complete them within two working days.