Privacy Policy

Montessori Tracker ("the Service") is operated by [Operator legal name]("we", "us"). The Service helps schools and childcare programs manage classroom records and communicate with families. Because it holds information about children, we hold ourselves to the strictest reading of the rules that apply: FERPA, COPPA, and — where applicable — GDPR and state privacy laws.

What we collect

• Account data — your name, email address, phone number, and role at a school.
• Child records entered by the school — name, date of birth, classroom, allergies and medical notes, immunization records, attendance and check-in/out events, daily-care logs, learning progress, observations, incident reports, photos (only when the school records parental consent), and family contact information.
• Billing records — invoices, payments, and tuition plans the school manages. Card payments are processed by Stripe; we never store card numbers.
• Technical data — session cookies needed to keep you signed in, and device push-notification tokens if you enable notifications.

We do not sell personal information, we do not use it for advertising, and we do not profile children. There are no third-party analytics or advertising trackers in the app.

Children's data and COPPA

Children never use the Service directly and no accounts exist for children. Information about a child is entered by their school under agreements with the child's parent or guardian, and is visible only to that school's authorized staff and to the child's own linked guardians. Photo storage and sharing require a recorded consent choice from a parent or guardian, which the school can change or revoke at any time.

Who can see what

Access is enforced per school and per role at the database level. School staff see only their own school; teachers and assistants see only their assigned classrooms; parents see only their own children. Directory contact details are shown only as each member chooses.

Where data lives

Data is stored with Supabase (Postgres and object storage) and the application is hosted on Vercel. Data is encrypted in transit and at rest. Payment processing, when enabled, is handled by Stripe under its own privacy terms.

Your rights: access, export, deletion

• Access & portability — schools can export a complete per-child record at any time, supporting FERPA inspection and GDPR access/portability requests.
• Account deletion — every user can delete their own account from the Account page inside the app. Deletion is immediate and removes your profile, memberships, messages, and notification tokens.
• Child record deletion— schools can permanently erase a child's records, including stored photos, to honor a family's deletion request, subject to any records the school is legally required to retain.

For any request you can't complete in the app, contact us at [privacy contact email].

Retention

Records are retained while a school's account is active. Each school can set a retention window in its settings; when set, an archived child's records — including stored photos — are permanently and automatically erased once they have been archived longer than that window. Housekeeping data (old read notifications, expired invitations) is purged automatically for all schools. Licensing rules in some jurisdictions require schools to retain certain records (e.g. incident reports) — those obligations rest with the school, which should export what it must keep before records are erased.

Changes and contact

We will post any changes to this policy here and update the effective date. Material changes affecting children's data will be announced to school owners directly. Questions: [privacy contact email].