Student Privacy Notice

Students do not create accounts. They do not provide an email address, a password, a date of birth, or any contact information. A student joins a class with two things their teacher gives them: the class ID and a 6-digit PIN. Inside the product, a student is a display name (chosen and entered by their teacher) and an animal avatar within a single teacher’s classroom.

We store the following, and only the following, about a student:

• Roster entry: the display name their teacher entered, an animal avatar, and their class PIN. When teachers import a roster, we keep only the names — every other column (student IDs, grades, emails, birth dates, and so on) is discarded before anything is saved.
• Work product: the prompts a student writes, the conversations they have with the build assistant, the apps it generates, and files they upload to their apps.
• Operational records: a login session (expires after 12 hours, or up to 180 days when a student chooses to stay signed in on their own device — teachers can require daily sign-in for shared-device classrooms), and — for failed login attempts only — the requesting IP address, kept for 30 days to stop PIN-guessing.

No student email address, password, phone number, date of birth, photo, precise location, or demographic information. No third-party ad trackers or third-party analytics run anywhere students work. We do not advertise to students, build profiles of them, or sell or rent any student information — full stop.

Student information is used only to provide the service: running the student’s workspace, letting their teacher see and guide their work, enforcing classroom and safety limits, and keeping the service secure. It is never used for advertising or marketing, and never used to train AI models.

When a student builds with the AI assistant, their prompts are routed through a privacy pipeline: personally identifiable information is detected and tokenized by a scrubbing proxy before the request leaves our serving path, and the model runs on US-hosted, zero-data-retention infrastructure. Our AI providers do not retain student content after the request completes and do not train on it. The providers involved are listed on our Trust & Security page.

Manifest is used by students under 13. Consistent with the FTC’s guidance under the Children’s Online Privacy Protection Act (COPPA), we rely on the school to provide consent on behalf of parents: by creating a classroom and adding students, the school (through its teacher) authorizes our collection of the limited student information described above, strictly for educational purposes and for no commercial purpose. Schools should only grant this consent within their authority to do so.

Where student work product constitutes an education record under FERPA, we act as a “school official” with a legitimate educational interest, under the school’s direct control with respect to that data. The school owns its students’ data; we use it only to provide the service and delete it at the school’s direction. Districts can request our signable Data Privacy Agreement — see the Trust & Security page.

Because students hold no accounts with us and we hold no student contact information, parents exercise their rights through the school. A parent may review their child’s work, request a copy of it, or request its deletion by contacting the teacher or school — teachers can export or permanently delete a student’s (or a whole class’s) data directly from their dashboard, without needing us. Parents may also contact us at privacy@madewithmanifest.com.

Student data lives for the life of the classroom and no longer. Teachers can export everything for a class as a single file, and can permanently delete a class — roster, student accounts, apps, conversations, and files — at any time; deletion is immediate and irreversible. Failed-login IP records are deleted after 30 days, and student sessions expire after 12 hours — or up to 180 days when a student stays signed in on their own device. The full schedule is on the Trust & Security page.

Student data is protected with encryption in transit, database-level access controls, isolated sessions, and login rate limiting. Class PINs are classroom credentials — designed to be read aloud and printed on login cards by teachers — protecting access to an account that contains no student contact information; guessing is bounded by per-classroom rate limits. If a breach affects student data, we will notify the affected schools promptly — see our commitment on the Trust & Security page.

If we change this notice in a way that affects student data, we will post the update here and notify teachers before it takes effect. Questions: privacy@madewithmanifest.com.