Privacy Policy

1. Scope

This Privacy Policy describes how sweet-seat.com and SweetSeat support channels handle personal information. It also explains, at a high level, how classroom information is handled by the SweetSeat browser application.

2. Information collected by this website

sweet-seat.com does not include teacher account creation, contact forms, advertising trackers or third-party analytics scripts. SweetSeat uses a first-party aggregate counter for completed seating-plan generations. Try Me uses fixed fictional students and blocks routes that could load or enter a real class list.

sweet-seat.com is hosted using Cloudflare services. Cloudflare may process technical request information such as IP address, browser/device information, request time and security/log information as part of delivering and protecting the site. Cloudflare's own terms and privacy practices apply to that processing.

3. SweetSeat application data

SweetSeat is a self-contained browser application. It does not send class lists, student needs or classroom-plan data to a SweetSeat database or server. Autosave uses local browser storage, and exported files are saved or handled under the teacher's control.

4. Try Me data

The Try Me class is fictional. Visitors can interact with room building, Student Needs, Best Fit, Review & Share and PDF output, but real student names cannot be uploaded or entered. Each stage deliberately reloads/reset its demonstration data, and Try Me does not maintain a classroom record between visits.

5. Contact and support information

If you contact SweetSeat at hello@sweet-seat.com, information you voluntarily provide may be used to respond to the request and maintain appropriate business records. The SweetSeat website itself does not contain a contact form.

6. Cookies and aggregate usage counts

SweetSeat does not set advertising or third-party analytics cookies. After a successful seating-plan generation in the public application, the browser sends a random, per-generation event identifier to a SweetSeat Cloudflare Worker. The Worker records the event identifier and its receipt date (Australia/Melbourne) to prevent double-counting and calculate daily totals. The public homepage retrieves only the aggregate lifetime total. Student names, class lists, room layouts, preferences, seating arrangements and exported documents are never included in these counting requests.

To retry failed event requests, the application may temporarily store random event identifiers in browser local storage. These are not linked to student data, and there is no teacher analytics account. Requests are still processed by Cloudflare, which may handle technical connection metadata for delivery and security. A private owner-only dashboard uses a secure session cookie and a secret-keyed identifier for failed administrator sign-in attempts, periodically removing older records during subsequent sign-in attempts; no raw IP address is stored in SweetSeat’s analytics database.

The application also uses local browser storage to preserve work and remember whether an optional support reminder was shown or permanently dismissed. Cloudflare may use essential platform and security mechanisms independently of the SweetSeat site code.

Optional PayPal contributions

Teachers may choose to open PayPal.Me links to support SweetSeat development. PayPal independently processes payment details under its own privacy terms. SweetSeat does not collect payment card details or transmit student names, classroom plans, seating preferences or files to PayPal. SweetSeat stores only the support reminder timestamp and permanent-dismissal choice locally in the browser, if available.

7. Children and students

The SweetSeat website and product are designed for teachers and school staff. Try Me does not ask children or students to create accounts or provide personal information.

8. Security

SweetSeat takes reasonable steps to protect personal information handled through its support and website operations. Teachers and schools should also protect exported seating files and printouts because those files may contain student information outside the SweetSeat application.

9. Access, correction and complaints

Where applicable, a person may contact the SweetSeat operator about personal information held by the business, request correction or raise a privacy concern. Contact SweetSeat at hello@sweet-seat.com or use the Contact page.

10. Changes

This policy may be updated from time to time. The effective date at the top of the policy will be updated when material changes are made.

11. Australian privacy context

Australian privacy obligations can depend on the nature and size of a business and the activities it undertakes. This policy is intended to provide transparent information even where a particular statutory obligation may not apply. It is not a substitute for legal advice about the circumstances of the SweetSeat business.