District & IT — ClassSeats™
This page provides technical, deployment, and data-handling information about ClassSeats™, a classroom management application provided by ClassWare Solutions, LLC, for school and district IT teams.
ClassSeats is designed to be local-first and privacy-first: no ClassSeats accounts are required, no ClassSeats servers store student data, and cross-device synchronization is optional and fully user-controlled.
Quick Summary (Paste into an IT Ticket)
- Purpose: Seating charts, attendance, and student groupings for educators
- Data storage: Local on the user’s device; optional sync to the user’s own Google Drive
- Student data servers: None (no ClassSeats-hosted student data servers)
- Google Drive scope (if enabled):
drive.file(file-level access only) - Authentication: Google OAuth (only when Drive sync is enabled)
- Offline use: Core app functions offline; 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 the district, depending on the Google Workspace configuration in use.
- Files are saved locally by default
- If sync is enabled, the class file is stored in the user’s Google Drive and synced across devices
- ClassSeats does not copy or mirror these files to any ClassSeats-controlled database
2) Optional Google Drive Access
Google Drive sync is optional and enabled only at the educator’s discretion.
If enabled, ClassSeats uses the Google Drive API with the drive.file scope, which:
- Limits access to files created by ClassSeats or explicitly selected by the educator
- Does not permit browsing or access to unrelated Drive content
- Operates entirely within the permissions and policies of the Google account used
Additional notes:
- ClassSeats does not request broad Drive access (no “read all files” scope)
- Disconnecting Drive immediately stops Drive access
- When Drive is disconnected or blocked, ClassSeats continues to operate using local storage
3) Student Privacy Posture (FERPA-Aligned Usage)
ClassSeats is designed to support FERPA-aligned instructional usage by keeping student data under existing educator and district controls.
- Student data remains on the educator’s device and/or within the educator’s (or district-managed) Google Drive account
- No student data is transmitted to ClassSeats servers for storage
- District policies continue to apply, including:
Device security requirements
Account access controls
Drive sharing restrictions
Retention and Data Loss Prevention (DLP) policies
For a detailed discussion of student data handling and FERPA alignment, see the FERPA & Student Data Handling page.
4) Deployment Notes
ClassSeats can be used in multiple environments:
- Web / PWA: Runs in a modern browser and can be installed as a Progressive Web App where supported
- Mobile: Mobile-optimized interface available for phones and tablets
- Desktop: A desktop build may be available depending on rollout approach
- Offline use: Core functionality works offline; synchronization requires internet access
5) Security & Control Questions (Direct Answers)
Can we block Google Drive?
Yes. If Google Drive access or OAuth consent is blocked, ClassSeats continues to work locally. Users simply will not be able to use Drive sync.
Can we audit what gets stored?
Yes. Data is stored as JSON files locally and/or in Google Drive. Districts may apply standard Drive controls for retention, sharing, auditing, and Data Loss Prevention (DLP). ClassSeats does not encrypt or obfuscate files beyond standard Google Drive protections.
Does ClassSeats run analytics on student data?
No. ClassSeats is built to avoid ingesting student content into third-party analytics systems and does not run analytics on student data.
6) Support
For district questions, pilot discussions, or rollout planning, contact:
ClassWare Solutions, LLC
Email: support@classseats.com