FERPA & Student Data Handling — ClassSeats™

Overview

This page describes how ClassWare Solutions, LLC handles student data in connection with ClassSeats™, a local-first classroom management application designed for educators to manage seating charts, attendance, and student groupings while keeping student data under the control of the educator and within existing school or district systems.

ClassSeats is intentionally designed without ClassSeats-hosted student data servers. Student information remains on the educator’s device and/or within the Google Drive account chosen by the educator.

FERPA Alignment

ClassSeats is designed to support FERPA-aligned instructional workflows.

• ClassWare Solutions, LLC does not independently collect student information.
• ClassWare Solutions, LLC does not take custody of education records.
• ClassWare Solutions, LLC does not store student data on ClassSeats-controlled servers.
• All student data is entered, stored, and controlled by the educator using the application.
• ClassSeats functions as a teacher-directed instructional tool and operates only at the direction of the educator.

School Official Context

ClassSeats does not operate as a centralized student information system and does not receive or host education records.

When used in a school environment, ClassSeats operates under the authority of the educator and within the permissions of the account and device used. ClassWare Solutions, LLC does not independently access, review, or redistribute student data and does not exercise control over education records.

Data Storage & Control

Local storage

Classroom data is stored locally on the educator’s device by default.

Optional Google Drive sync

If enabled by the educator, classroom files are stored in the educator’s chosen Google Drive account for cross-device use.

No ClassSeats servers

ClassWare Solutions, LLC does not copy, transmit, or store classroom data on ClassSeats-owned servers.

Data ownership

Classroom files are owned and controlled by the educator.

If a district-managed Google Workspace account is used, district policies governing that account (including sharing, retention, and security controls) apply.

Google Drive Access (Optional)

If Google Drive sync is enabled, ClassSeats uses the Google Drive API with the drive.file scope.

This scope:

• 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

ClassSeats does not override or bypass Google Workspace controls applied to the account.

If Google Drive sync is not enabled, ClassSeats operates using local storage only.

Student Accounts & Authentication

• Students do not create accounts in ClassSeats.
• Students do not log in or authenticate.
• Authentication (Google OAuth) is used only when an educator enables Google Drive sync.

Analytics & Redisclosure

• ClassWare Solutions, LLC does not run analytics on student data.
• Student data is not used for advertising, profiling, or secondary purposes.
• ClassWare Solutions, LLC does not redisclose student information to third parties.

Account & District Context

ClassSeats respects the security and governance controls of the account used:

• When an educator uses a personal Google account, data remains under that educator’s control.
• When an educator uses a district-managed Google Workspace account, district policies governing Drive usage, sharing, retention, and device security apply.

ClassSeats does not alter or interfere with these controls.

Summary for Schools & Districts

• No ClassSeats student data servers
• No student accounts
• No analytics or profiling
• Optional, file-level Google Drive access
• Student data remains under educator control and within the account used

For district or IT questions, contact: support@classseats.com