Classic Test Prep · Trust Center
Data elements and retention
The inventory below follows the categories of the SDPC agreement's Exhibit B so a reviewer can map it straight onto the DPA. Most rows say 'not collected', which is the point.
Last updated November 12, 2026
Data element inventory
| Category | Elements | Collected | Note |
|---|---|---|---|
| Application technology metadata | IP address, browser type, device type | Collected | Transient request logs; no persistent device fingerprinting |
| Application use statistics | Pages visited, time on task, lesson and practice completions, points | Collected | |
| Assessment | Practice answers, scores, skill ratings, diagnostic results, official practice test results | Collected | |
| Attendance | Lesson attendance recorded by the teacher | Collected | |
| Communications | Support requests a student or teacher sends us | Collected | |
| Conduct | Behavioral or disciplinary records | Not collected | |
| Demographics | Date of birth, race, ethnicity, gender, language | Not collected | |
| Enrollment | School, class or section, teacher, grade level | Roster only | The app stores class membership; grade level only if a roster supplies it |
| Parent or guardian contact | Parent name, email, phone, address | Not collected | |
| Schedule | Student's self-reported exam date | Collected | |
| Special indicators | IEP, 504, free or reduced lunch, English learner status | Not collected | |
| Student contact | Home address, phone number | Not collected | |
| Student identifiers | School email address, name, our account id; district student ID only if a roster supplies it | Collected | |
| Student in-app content | Written answers inside practice (short responses) | Collected | No free-form essays, uploads, chat, or photos |
| Transcript | Course grades, GPA, official exam scores | Not collected | |
| Financial | Payment information | Not collected | School accounts never see pricing or checkout |
"Roster only" means the app never asks a student for it; it exists only if a district chooses to send roster files, and then only the fields the district includes.
Retention and deletion schedule
| Data | Retention |
|---|---|
| School (institutional) account and all study records | Kept while the agreement is active. Deleted within 60 days of termination with written certification, or within 90 days after the district tells us a student has left |
| Individual (consumer) account | Kept while the account is active. Deleted on request, or when the user deletes their account, within 30 days |
| Database backups | Rolling automatic backups by our hosting provider; expire within 35 days. Deleted records fall out of backups on that schedule |
| Support tickets | Kept 2 years after resolution, then deleted |
| Transactional email logs | Kept by the email provider for 30 days, then deleted |
| Error reports | 90 days, personal data stripped before sending |
| Platform request logs | Limited period at our hosting provider; contain no student responses |
| District roster files | Replaced on each sync; prior files deleted. All files deleted at termination |
How erasure works
Erasure is a program, not a promise. Every database table that holds a user reference is discovered automatically and swept; a hand-maintained list could miss a new table, so we do not use one. A district erasure produces a signed certification listing every account removed. Deleted records leave rolling backups within 35 days; backups are never restored to production except in a declared disaster, and a restore would be followed by re-running every erasure logged since the backup.