How SchoolKit Protects School Data
Last updated: September 5, 2026
The Short Version
SchoolKit tools run entirely in your browser. Your school data never leaves your device. There is no server-side storage of tool-entered information. This is not a policy choice — it is a technical architectural fact.
Tool Data Flow
At no point does any data leave your browser. No network requests are made to our servers with your tool data.
Community Data Flow
Community features are the only part of SchoolKit that uses server-side storage. Your identity is not linked to your votes or opinions.
What We Store
On Your Device
- Student names and rosters
- Attendance records
- Exam timetables
- Fee calculations
- Parent contacts
- Bus routes
- Teacher evaluations
- Communication drafts
On Our Servers
- Community votes (pseudonymous)
- Community opinions (pseudonymous)
- Country derived from IP (country code only)
- Device fingerprint hash (one-way, for dedup only)
Verify It Yourself
Don't trust us. Verify us. Here's how:
- Open any SchoolKit tool (e.g., the Attendance Register)
- Open your browser's Developer Tools (F12)
- Go to the Network tab
- Enter some data and generate output
- Watch the Network tab — you will see zero requests to our servers with your data
You can also disconnect from the internet entirely and confirm that every tool still works. They will — because they run entirely in your browser.
Open Architecture
SchoolKit is built with client-side JavaScript. The code running in your browser is inspectable — you can view source, check network requests, and confirm our architecture claims independently. We believe this transparency is more trustworthy than any privacy policy.