How each app handles student data

Where each app keeps its data, how people sign in, and which outside services it talks to. Ask us if your school needs more detail on any of them.

ClassPass

The student roster and the visit log are kept in a Google Sheet your school owns and can open, sort and share.
Student history sits behind a separate reports password.
A cleanup removes log entries older than a set number of days (7 by default, adjustable).
IDs and search terms are checked on the server, and each device's requests are rate limited.

The student roster and the sign-out log are kept in a Google Sheet your school owns.
Every page sits behind a staff login with a secure session cookie, and reports need a separate password.
A cleanup removes log entries older than a set number of days (7 by default, adjustable).
Repeated wrong passwords lock that device out for 15 minutes.

Photos and finished cards are stored on the app's server, in each staff member's own account.
Each person signs in with their own login, so batches from different offices never mix. Admins add and remove users.
Face detection runs on the app's server. Photos are not sent to an outside face-recognition service.
Cards and original photos are kept until you delete them, and can be deleted in bulk.

Runs in Docker with its own PostgreSQL database, on a server your school controls.
Teachers have their own accounts. When an admin turns an account off, access ends right away.
Each teacher connects their own Google account to import from Classroom. Re-syncing never overwrites a teacher's own notes.
When a teacher asks for an AI draft or summary, that student's name, class, term, grades and notes are sent to the AI provider your school chose, using your school's key. Nothing is sent until a teacher asks.
Admins can download a backup ZIP with a folder per student.

Keeps its data in its own PostgreSQL database.
Students and staff sign in with their school Google account, so there are no new passwords.
AI hints and example sentences are written from the word and its meaning only. No student information is sent, and each result is saved so it's made once.
Pictures come from the Pexels photo library, searched by the word.
Admins can turn accounts off or delete them.

Video files and the library database stay on the app's own server.
Users sign in with their school Google account. Each video is visible only to the groups or people it's assigned to, and shared links still require sign-in.
Videos are deleted automatically after 30 days.
Three roles: admins manage everything, content managers add and assign videos, viewers watch what's assigned to them.

Runs as a desktop app on an IT admin's own computer and connects straight to Google's admin tools from there.
It asks for an admin password and uses an encrypted connection.
Bulk jobs ask for confirmation before anything changes.

Reads both systems every four hours and keeps snapshots in its own database. Old snapshots are pruned.
Roster and grade changes are written only after a person approves them. Removals and archives need an extra confirmation.
Staff sign in with their school Google account. Viewers can look, operators can apply plans, admins manage users.
An event log records who applied what, and when.

Ask us about any app, and we'll answer specifically for your school's setup.