Privacy and student data

Classroom observations are among the most sensitive records a teacher keeps. The design assumption is that they never leave the organization that owns them.

Open the app API, llms.txt and MCP for agents

What is stored

• Teacher account: name and email from your sign-in provider.
• Organization, schools, classes and rosters your organization creates.
• Observations: an area, an indicator, a valence, a timestamp, an optional note and an optional curriculum expectation.
• Report-comment drafts and learning-skill ratings you generate, until you delete them.

Who can see it

• Access is scoped to your organization and school by row-level security in the database, not only in the interface.
• Teachers see the classes they are assigned to; nothing crosses organizations.
• No student data appears on this website, in its JSON API, in llms.txt or through the MCP server.

Your board comes first

Boards differ on what may be recorded about a student, where it may be stored, and for how long. Follow your board and MFIPPA obligations, and treat anything you write in an anecdotal note as a record that could be disclosed.