District & IT
ClassSeats is designed to be local-first and privacy-first: no ClassSeats accounts required, no ClassSeats servers storing student data, and optional Google Drive sync that stores files in the educator’s own Drive.
Quick summary (the part you can paste into an IT ticket)
- Data storage: on the user’s device and/or the user’s Google Drive (optional).
- No ClassSeats servers used to store student data.
- Google Drive scope:
drive.file(file-level access only for files the app creates or the user selects). - Authentication: Google OAuth (only if Drive sync is enabled by the user).
- Network dependency: Core app works offline; Drive sync requires internet.
1) Data model & file format
ClassSeats stores classroom data in a single JSON file per class. The file is owned and controlled by the educator (or district, depending on your Google Workspace configuration). The application is built to avoid silent reinterpretation of old files.
- Files are saved locally by default.
- If Drive sync is enabled, the file is stored in the user’s Drive and synced across devices.
- ClassSeats does not copy those files to any ClassSeats database.
2) Google Drive access
Drive sync is optional. When enabled, ClassSeats uses the Google Drive API with the drive.file scope.
That scope limits access to files the app creates or that the user explicitly selects via the picker/open flow.
- ClassSeats does not request broad Drive access (no “read all files” scope).
- ClassSeats cannot browse or access unrelated Drive content.
- Disconnecting Drive stops Drive access immediately; the app continues using local storage.
3) FERPA / student privacy posture
ClassSeats is intentionally designed to avoid becoming a “student data custodian.” The goal is to keep data under the teacher’s (or district’s) existing controls:
- Data stays on the educator’s device and/or their Drive.
- No student data is transmitted to ClassSeats servers (because there aren’t any for storage).
- District policy controls still apply (device security, account access, Drive sharing restrictions, etc.).
4) Deployment notes
- Web/PWA: Can be used in a browser and installed as a PWA where supported.
- Desktop: A desktop build may be available depending on your rollout approach.
- Offline use: Core functionality works offline. Sync requires internet.
5) Security & control questions (and direct answers)
Can we block Google Drive?
Yes. If you block Drive access or OAuth consent in your environment, ClassSeats still works locally; users simply won’t be able to use Drive sync.
Can we audit what gets stored?
Yes. The data is stored as JSON files (local and/or Drive). Districts can apply their normal controls for Drive file retention, sharing, and DLP policies.
Does ClassSeats run analytics on student data?
No. ClassSeats is built to avoid ingesting student content into third-party analytics systems.
6) Support
For district questions, pilot discussions, or rollout planning:
Email: support@classseats.com