Privacy and student data FAQ

EloNotes depends on trust. Creators should understand what student data enters the workflow and how it is expected to be handled before inviting students.

What data matters most?

The core workflow may involve student account details, chess usernames or PGN uploads, game data, analysis outputs, AI-assisted draft material, creator edits, and published lesson content.

What should creators tell students?

Creators should be clear that lessons are drafted from student games, reviewed by the creator, and may use analysis tools. Students should know what they are submitting and what the lesson workflow uses it for.

What should not go into analytics?

Creator lead names, email addresses, audience details, student game details, and message content should not be sent to analytics. Website measurement should stay focused on page-level launch reporting unless a future privacy review approves more detailed events.

Who reviews the lesson?

The creator review layer is central to the product. EloNotes may draft structure and analysis, but creators should review lesson quality, tone, student fit, and any sensitive context before students receive lessons.

What is still being finalized?

Detailed production retention, export, deletion, and third-party service policies should follow the published privacy policy and current launch-readiness runbooks. If the product adds new services or stores additional student data, the public privacy policy and internal runbooks should be updated before meaningful launch traffic is sent there.