Skip to content
Built for Class

Built for Class · Assessments & Feedback

Privacy policy

This policy covers Assessments & Feedback on Built for Class and Classwork Lab while a small group of teachers tries it. Teachers sign in with Google. Students join with a preferred name and a class code, without creating an account.

Last updated October 4, 2026.

What we collect

  • Students: a preferred name their teacher will recognize. The join flow does not ask for a full legal name, email address, birthdate, or student sign-in.
  • Teachers: the name, email address, and account identifier provided by Google to create and recognize their teacher account. We never receive their Google password.
  • Classroom work: assessments, questions, rubrics, student responses, scores, feedback, and activity timing. These records connect each student’s work to their preferred name and class session.
  • Technical data: session cookies, internal identifiers, and service logs needed to keep the app working. Requests include technical details such as an IP address, which may be used to limit repeated join attempts.

How we use data and AI

We use this information to run class activities, save work, provide feedback, and maintain the service. We do not sell classroom data or use it for advertising or model training.

AI assistance uses Anthropic’s Claude API for question generation and grading suggestions. Requests include relevant questions, rubrics, settings, and response text. We do not add student names, emails, or account details to grading requests, but personal information typed into a response may be included. Avoid putting personal details in questions or answers. Teachers control how grades are reviewed and released to students.

Services we use

  • Google handles teacher sign-in.
  • Vercel hosts the app and processes web requests.
  • Neon stores account and classroom data.
  • Anthropic processes content for AI assistance as described above.

If enabled, Sentry receives error reports with user details, cookies, request headers, and request bodies removed. Session replay is not enabled.

Keeping data protected

Connections use HTTPS, and the managed database encrypts stored data. Access checks limit teachers to their own classes and students to their own work. Session cookies keep teachers signed in and let students return to their activity on the same browser. On shared devices, sign out or use “Not you?” before another student joins.

During a monitored activity

When classroom monitoring is enabled, the app records events such as leaving the activity tab, exiting fullscreen, or using paste. Clipboard contents are not recorded as monitoring data. These observations provide context for the teacher and are never used to calculate grades. Device or network issues can cause interruptions; an event is not proof of misconduct. Monitoring cannot see phones, other devices, or apps outside the browser; see what monitoring can and can’t do.

Keeping and deleting data

Classroom work and grades are kept until deletion is requested and processed; they are not automatically deleted when an activity or the current testing period ends. Default retention windows are 90 days for operational logs, 365 days for monitoring events, and one day for records used to limit repeated requests.

Questions or data requests

Contact the teacher or colleague who shared these tools with you with privacy questions or requests to access, export, correct, or delete data. They will coordinate with the application operator. See the teacher guide for help getting started.