Draft · for launch review

Privacy information

This is the current technical description for the test deployment, not the final commercial privacy notice.

Staff and school account records

School setup saves the school name, the organiser’s signed-in identifier and email, membership roles and dates, licence status, and staff invitations. Invitations save the invited email, a hashed invitation token and expiry. Sign-in uses a short-lived code emailed to your address. My Day does not ask for an email-account password. Sign-in emails are delivered through Resend. Short-lived code records, request limits and hashed session tokens are stored to protect accounts.

Classroom routines

The existing board saves routines and check-in selections in browser storage on the classroom device. There is no cloud pupil profile or cross-device routine sync in this version. Avoid entering children’s names or identifying details in school account fields.

Payments

No live payment collection is enabled. Stripe handles card information. My Day stores Stripe resource identifiers, subscription status, access expiry and processed webhook event identifiers; it does not store card numbers.

Before commercial launch

The operator’s legal identity, contact details, lawful bases, retention periods, deletion process, hosting/subprocessor information and applicable international transfer safeguards must be confirmed. The school’s own policies and responsibilities also need to be considered before use with pupils.