Security & privacy
Built to keep student data where it belongs
Schools trust us with information about children and families. We design every part of JadFlow around that responsibility.
Every school stands alone
Each school is a separate tenant. Isolation is enforced inside the database itself, not only in the app, so one school's records can never appear in another's.
Least access by default
Staff are invited into specific roles. A cafeteria worker sees what meal service needs; a librarian sees what circulation needs. Nothing more.
Families see only their own
Guardians gain access through a school invitation and only ever see the children that school has linked to them.
Under the hood
Safeguards at every layer
Protection doesn't rely on a single wall. Each layer checks again.
Database-level rules
Row-level security policies decide what each signed-in person can read or change, on every request.
Encrypted connections
All traffic between your browser and JadFlow travels over HTTPS.
Audit trail
Sensitive actions, including any support access to a school, are recorded with who, what and when.
Scoped support access
JadFlow staff can only open a school's data through an explicit, audited grant for that school.
Clean offboarding
When someone leaves, their access and active sessions are revoked.
Separate environments
Production schools run separately from our beta, so new features are proven before they reach you.
Have a security or privacy question?
We're happy to walk your district or IT team through how JadFlow handles data.
Contact our teamSee JadFlow running for your school
Book a short walkthrough. We'll show you the modules that matter to your team and how your existing rosters come across.