Teacher Beta Privacy Notice

Who handles your information

The teacher beta is operated under the name Lesson Captain. Questions, consent withdrawals, and access, correction, or deletion requests can be sent to beta@lessoncaptain.com.

Information collected

When you apply, Lesson Captain collects:

• your first name and email address;
• teaching format and learner levels;
• optional learner age band, typical class size, teaching platform, and teaching-challenge description;
• your beta-contact consent and its timestamp;
• sanitized campaign labels, the fixed /beta landing path, and a referring website origin and path without query strings or fragments; and
• a salted one-way hash derived from the request IP address for abuse prevention. The beta-attempt table does not store the raw IP address.

If you continue with Google, Google sign-in creates or accesses your teacher account. Lesson Captain connects the beta application only when the signed-in email matches the application email. OAuth tokens are not stored in the beta application record.

During the beta, the application record may also contain account-linking, onboarding, activity, follow-up, feedback, testimonial-permission, classroom-use confirmation, and internal support-note fields.

How the information is used

Lesson Captain uses this information to review applications, operate the Founding Captain cohort, provide onboarding and support, request optional feedback, protect the application endpoint, understand campaign effectiveness, and evaluate whether teachers reach meaningful classroom use.

The required contact checkbox permits beta-access, onboarding, and feedback messages. You may withdraw that permission by emailing the address above. Withdrawal does not automatically delete an account or information needed to handle an existing request; deletion can be requested separately.

Analytics

Lesson Captain uses PostHog for limited teacher-funnel and product analytics. The four beta funnel events contain only the program name, the /beta landing path, and sanitized campaign labels. They do not contain applicant names, email addresses, free-text answers, student identity, or raw referrer query strings.

After teacher sign-in, the teacher account identifier and email may be associated with product analytics. Students are not identified in PostHog, and PostHog session recording is disabled.

Service providers

Lesson Captain uses:

• Google for teacher authentication;
• Supabase for account, application, and beta-program data;
• Vercel for application hosting and infrastructure delivery; and
• PostHog for limited analytics.

These providers may process technical and account information needed to provide their services and may maintain their own security and infrastructure logs under their applicable terms and retention practices.

Retention and deletion

Beta application and related beta-program records are kept for up to 12 months after your application or your most recent beta interaction, whichever is later. They are then deleted or anonymized unless they must be kept longer to address a security incident, legal obligation, or unresolved request.

Abuse-prevention hashes older than 30 days are deleted when the application-attempt limiter next runs. If no later application attempt occurs, an expired hash may remain until the next claim triggers cleanup; Lesson Captain does not describe this as guaranteed deletion exactly on day 30.

To request access, correction, or deletion, email beta@lessoncaptain.com. Lesson Captain may need to verify that the request concerns your application or account before acting on it.

Changes to this notice

This notice will be updated when beta information practices or service providers materially change. The updated date above shows the current version.