Privacy & Student Data Protection

Milestone Pass purchases

Stripe processes card and payment details. For delivery and support, Milestone Teachers stores the buyer email, Stripe transaction identifiers, offer, amount, payment status, accepted terms version and file-delivery record. We do not ask for student information to purchase a pass. Unpaid pending checkout rows are deleted after 30 days. Completed transaction records are kept for seven years after the latest payment, refund or dispute activity, unless a longer legal hold applies.

Privacy at a Glance

• Data minimization: no student emails required, no student accounts required for TeacherLens resource creation, and class-level prompts by default.
• Teacher review: student-facing drafts, report-card comments and IEP-style supports stay teacher-reviewed before sharing.
• Lesson Capture: lesson recording is not currently offered as a public tool. For any captures an account already holds, raw audio is not kept after transcription, and transcripts and analysis stay teacher-controlled.
• No sale or targeted advertising: student/class data is not sold, shared for ads, or used to build advertising profiles.
• Class-level memory: optional profile memory stores teacher-approved preferences and class-level signals, not private student records.

Regulations We Design For

Privacy laws vary by country, province, state, school board, and district contract. The list below is the practical compliance map we use for TeacherLens. It is not a substitute for your board or district legal review, but it gives reviewers the operating commitments we follow.

• PIPEDA Accountability, limited purposes, consent-aware collection, access/correction/deletion paths, safeguards, retention limits, breach response, and openness.
• Ontario MFIPPA + Education Act TeacherLens is designed to keep school-board records class-level unless a school-approved workflow requires more. We avoid OSR-style records, medical details, and private IEP files in normal prompts.
• Quebec Law 25, Alberta PIPA, BC PIPA We use purpose limitation, clear notices, access/deletion support, service-provider controls, and no sale/share for advertising.
• FERPA + PPRA When used by a school, student education-record data is used only to provide the school-requested service. Sensitive survey-style data is not requested for TeacherLens resource generation.
• COPPA TeacherLens is teacher/school-facing, not a child-directed social app. Where school consent is relied on, data is used only for educational purposes, never behavioral ads.
• CCPA/CPRA and other U.S. state consumer privacy laws We provide notice, access, correction, deletion, opt-out posture for sale/share, and non-discrimination for privacy requests where those rights apply.
• GDPR and UK GDPR We support transparency, data minimization, purpose limitation, processor/subprocessor disclosure, access/correction/deletion, and regional routing review before EU/UK school deployment.

What We Collect

Teacher and account data

Name or email used for login, subscription/billing records, support messages, saved settings, optional TeacherLens profile preferences, and usage/security logs.

Class-level teaching data

Grade band, subject, curriculum region, class-level readiness notes, timetable blocks, resource prompts, lesson transcripts, and teacher-reviewed analysis.

Limited student data when a teacher chooses it

Some legacy classroom tools may use first-name initials or private aliases, class codes, progress, or teacher-entered roster data. TeacherLens asks teachers to avoid names and private records unless their school has approved that workflow.

Technical data

Device/browser data, IP-derived region, authentication/session logs, CSRF/security events, payment status, and aggregate product analytics.

• Do not enter private student records into open prompts. That includes full names, addresses, medical details, diagnoses, report-card marks, private IEP files, OSR records, family contact details, or discipline records unless your school has approved the use and you have a lawful basis.

AI, OpenRouter, and Model Routing

TeacherLens uses AI to draft resources, summaries, suggestions, visuals, lesson insights, report-card drafts, IEP-style supports, and planning notes. Our backend routes AI work through OpenRouter so we can choose appropriate models for the task while keeping provider details out of student-facing exports.

• We do not intentionally enable OpenRouter input/output logging or OpenRouter use of inputs/outputs for improving OpenRouter with student or class data.
• OpenRouter and model providers may still process request metadata and may have their own retention rules. We review provider policies and can tighten routing for school or enterprise contracts.
• Prompts and outputs are not used to train advertising profiles, sold to data brokers, or used for targeted advertising.

Lesson Capture (Not Currently Offered) and Memory

• Lesson Capture, a lesson-recording feature, is not currently offered as a public tool. The rules below cover any captures an account already holds.
• Raw audio is not kept after the transcription request; provider retention depends on the routing configuration. Unreviewed captures are scheduled for deletion after 24 hours by default; a configured or written school policy may set another deadline. Reviewed captures remain until the teacher deletes them or a written school-pilot retention schedule requires earlier deletion.
• TeacherLens memory is optional. If enabled, it stores class-level preferences such as curriculum region, timetable blocks, language supports, and planning style.

No Sale, Ads, or Non-Educational Profiles

No sale or targeted advertising means we do not sell student data, share student data for cross-context behavioral advertising, target ads to students or families based on classroom data, or create non-educational student profiles. Product analytics are used to operate, secure, and improve Milestone Teachers and TeacherLens.

Storage, Transfers, and Subprocessors

Data may be processed in Canada, the United States, or other locations used by hosting, database, authentication, payment, email, analytics, AI, and support vendors. Cross-border processing is protected through contractual, technical, and organizational safeguards. School or district deployments can require a data processing agreement, approved subprocessors, retention schedule, breach notice window, and regional routing review.

Access, Correction, Portability, and Deletion

Teachers can request access, correction, export, or deletion of account/profile data. Parents, guardians, students, schools, or districts may request access or deletion through the school or directly through our Privacy Officer where applicable. We aim to respond to privacy requests within 30 days unless a law, school contract, identity-verification step, or security need requires a different process.

Retention and Deletion

• Teacher account and billing records are retained while needed to provide the service and meet legal/business obligations.
• TeacherLens profile memory is opt-in and can be cleared or changed.
• Classroom/roster data is retained while the class or school workflow is active and can be deleted according to teacher, school, or contract controls.
• Limited exceptions are handled separately: backups and security records may persist for their normal deletion cycles, and billing, contract, or legally required records may be retained for their applicable periods.

Security and Breach Response

We use HTTPS/TLS, authentication controls, CSRF protections, access boundaries, audit-friendly logs, server-side privacy checks, and role-aware routes. If a breach creates a real risk of significant harm or triggers a school/district notice obligation, we will notify affected customers and regulators as required by applicable law and contracts.

Contact Our Privacy Officer

For privacy questions, data access requests, deletion requests, school procurement reviews, DPA requests, subprocessor questions, or AI routing questions, contact us:

If you are in Canada and are not satisfied with our response, you may contact the Office of the Privacy Commissioner of Canada or the relevant provincial privacy commissioner. U.S. schools should also use their district privacy/procurement channel for FERPA, PPRA, COPPA, and state student privacy review.

• Location: Ontario, Canada