Privacy & Student Data

Designed to keep classroom information under teacher control.

This page explains the current SweetSeat data model in plain language. It is separate from the formal website Privacy Policy.

Current product model: the SweetSeat v0.9.0-beta.25 application supplied in this package is a self-contained browser application. It has no network requests to a SweetSeat server. Autosave uses browser local storage and exported files are created on the teacher's device.

Does SweetSeat upload my class list?

In the current local application build, no. Student and room information is processed by the browser running SweetSeat. The app does not contain a connection to a SweetSeat database, analytics service, Supabase, Firebase or other remote class-data service.

What does browser autosave mean?

SweetSeat uses the browser's local storage so work can be recovered on the same browser/device. Local browser data can be cleared by the user, browser or device, so exported plan files should be used where a durable copy is required.

What happens when I export?

When a teacher creates a spreadsheet, plan file or PDF, the output is generated for the teacher to save. After export, the school or teacher controls where that file is stored, shared or printed.

What does the Try Me demo collect?

Try Me contains only fictional students. Build Room can be edited temporarily, and the fictional Student Needs matrix/list can be changed, but real student names cannot be loaded or entered. Room changes reset before Student Needs; needs changes reset before Find Best Fit; the demo does not autosave its state into persistent browser storage.

Does SweetSeat create student accounts?

No student accounts are part of the current SweetSeat application or public demo. SweetSeat is designed as a teacher planning tool rather than a student social or communication platform.

What about projected seating plans?

The app provides teacher-controlled presentation options, including hiding names when appropriate. Teachers should follow their school policies when displaying or sharing student information.

School responsibilities still matter

Local processing reduces the amount of student information that needs to leave the teacher's device, but it does not make exported files automatically safe. Schools and teachers remain responsible for handling saved files, printouts and screen displays according to their own privacy, records and safeguarding requirements.

Website hosting is separate

The promotional website can be hosted on Cloudflare Pages. The site build supplied here contains no third-party analytics scripts by default. Hosting providers may still process ordinary request and security information as part of delivering the website. If analytics, forms, payment services or account features are added later, this explanation and the formal Privacy Policy should be reviewed before launch.

Read the formal Privacy Policy