Privacy & Student Data

Designed to keep classroom information under teacher control.

This page explains how SweetSeat handles classroom information in plain language. It is separate from the formal website Privacy Policy.

Classroom data stays under teacher control: SweetSeat processes class lists, room information and student needs in the browser. It does not send that classroom data to a SweetSeat database or server. Autosave uses browser local storage, and exported files are created for the teacher to save.

Does SweetSeat upload my class list?

No. Student and room information is processed by the browser running SweetSeat. The app does not send class lists or student-needs data 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?

SweetSeat does not create student accounts. It is designed as a teacher planning tool rather than a student social or communication platform, and Try Me uses fictional students only.

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

sweet-seat.com is hosted on Cloudflare Pages. SweetSeat does not include third-party analytics or advertising scripts. Cloudflare may process ordinary technical request and security information as part of delivering and protecting the website. If SweetSeat's data practices change, this page and the formal Privacy Policy will be updated accordingly.

Read the formal Privacy Policy