Privacy and data minimization

ClassPods is built around the assumption that student data should be collected only when there's a clear classroom reason. This page explains the practical mechanisms — see /privacy and /data-processing-addendum for the formal documents.

Anonymous PIN play

The most common student interaction with ClassPods is a live game joined via a 6-digit PIN. PIN play requires only a nickname and an optional avatar. No email, no password, no account.

Game session data (which questions a nicknamed student answered, in which session) is retained for the session and reporting period only. If a student does not later create a profile and link the session, that data is purged.

Optional student profiles

Students who want progress to follow them across games can create a profile. That requires:

• A display name (student-chosen)
• An email address (used only for sign-in)
• A password

We do not collect age, school name, parent contact, address, phone number, or any other identifier from students. Email is not shared with classmates and is not used for marketing.

Teacher-created class memberships

When a teacher adds a student to a class via class code, the student's profile is linked to that class. The teacher sees the student's display name, in-class progress, and assignment submissions. The teacher does not see the student's email except where required for administrative communication.

No third-party ad tracking

ClassPods does not run third-party ad networks, does not embed ad pixels, and does not sell or share student data with marketing companies. Analytics is privacy-respecting and aggregate.

Data residency

ClassPods runs on Supabase (Postgres) with infrastructure in multi-region hosting. Schools with specific data residency needs should raise this on the provisioning call so we can confirm the right region.

DPA on request

We sign a Data Processing Addendum on request. See /data-processing-addendum for the standing version or email hello@classpods.org for a school-specific variant.