DATA RETENTION & DELETION

Keep less. Keep it only as needed.

RSA’s pilot procedures favor data minimization, verified requests, and deliberate deletion rather than indefinite student records.Effective August 29, 2026 · RSA classroom pilot

Current pilot schedule

  • Private coaching transcripts: not stored in RSA’s classroom database. OpenAI’s separate API processing terms apply.
  • One-time teacher codes: expire after 10 minutes.
  • Teacher browser sessions: expire after 30 days or can be signed out sooner.
  • Teacher-approved materials: remain until the teacher removes them or the classroom pilot is closed.
  • Student classroom identifiers, limited study metadata, and deliberately shared requests: retained only for the active pilot and reviewed for deletion when the pilot ends.
  • Student-saved questions: stay only in that browser’s local storage until the student deletes them or clears browser data.

Requesting access, correction, or deletion

  1. A student or caregiver contacts the pilot teacher or school contact.
  2. The teacher contacts RSA through the existing pilot-onboarding channel and identifies the classroom and requested scope.
  3. RSA verifies the requester and previews the records in scope without exposing private coaching content.
  4. A second review confirms the classroom and records before permanent deletion.
  5. RSA records completion without retaining the deleted student content.

Why deletion is reviewed

A public class code alone is not enough authority to erase a student or classroom. RSA requires verification so another student—or anyone who learns the code—cannot delete someone else’s information.