Privacy Policy

When you use Fieldtest Lab, we intend to collect only what’s necessary to provide the service.

• Account information. Your name and email address when you create an account.
• Lesson content. The text of lesson plans, scripts, or materials you submit for analysis. See Section 4 for how we handle this specifically.
• Usage data. Basic product usage information such as which features you use, how often, and session length. Used to improve the product.
• Grade and subject preferences. The grade band and subject you select, stored to pre-fill your settings on future sessions.
• Practice Mode transcripts. If you use Practice Mode, the dictation transcript from your session, stored only if you choose to save the session.

We do not collect payment information directly. If we introduce paid plans, payment processing will be handled by a third-party processor such as Stripe. We will never see or store your full card number.

We use the data we collect to:

• Provide and improve the Fieldtest Lab service
• Generate archetype simulations and pre-analysis reports from your submitted lesson content
• Save your lesson history and fieldtest results when you choose to save them
• Send transactional emails such as account confirmations and, if applicable, billing receipts
• Understand how teachers use the product so we can make it better

We do not use your lesson content to train AI models. Your materials are your materials.

We intend to be direct about this: teacher tools have a long history of treating user data as a secondary product. We don’t want to do that. If our business model ever changes in a way that affects how we handle your data, we will notify you explicitly and give you the option to delete your account before any change takes effect.

Lesson plans and instructional materials you submit to Fieldtest Lab are treated as confidential. We pass your content to an AI model (currently Anthropic’s Claude) to generate archetype simulations. This transmission is covered by Anthropic’s API terms, which include data handling commitments. We do not pass your content to any other third party.

Your lesson content is yours. You can delete it at any time from your account. When you delete content, we remove it from our active systems within 30 days. Backups are purged on a 90-day cycle.

If you choose not to save a fieldtest session, your lesson content is not stored beyond the duration of the session.

Fieldtest Lab does not collect any data about real students. The student archetypes in our product are simulated characters based on cognitive development research — they are not connected to, and do not represent, any real student.

We strongly recommend that teachers do not include personally identifiable information about students in lesson materials submitted to Fieldtest Lab. If your lesson references a student by name or includes identifying information, please remove it before submitting.

Fieldtest Lab is a tool for teachers, not for students. Students do not create accounts and do not interact with the product directly.

• Saved lessons and sessions. Retained until you delete them or close your account.
• Unsaved sessions. Not stored beyond the session.
• Account data. Retained while your account is active. Deleted within 30 days of account closure.
• Usage analytics. Retained in aggregate, anonymized form for up to 2 years.
• Backups. Encrypted backups are purged on a 90-day rolling cycle.

Regardless of where you are located, we intend to honor the following rights:

• Access. You can request a copy of the data we hold about you.
• Correction. You can update or correct your account information at any time.
• Deletion. You can delete your lesson content, your saved sessions, or your entire account at any time.
• Portability. You can export your saved lessons and fieldtest reports in a standard format.
• Objection. You can opt out of usage analytics while continuing to use the product.

To exercise any of these rights, contact us at the address below. We will respond within 30 days.

Questions about this policy or how we handle data can be directed to: