Privacy & Security
Clear answers about student data.
This page summarizes the documented implementation and current limitations. It is not a legal certification or district approval.
Data minimization
No student email, phone number, home address, birth date, precise location or demographic field is required in the reviewed implementation.
School-scoped access
Students access their permitted state; authorized librarians and approved teachers receive scoped school/class views.
No advertising SDK
No application advertising, analytics or session-replay SDK was found in the reviewed code. Hosting providers still process operational metadata.
Common questions
Privacy & security details
Roster/account information such as school/student identifiers, names, grade and teacher/class; reading and quiz activity; saved game/customization state; private creations; and limited operational/security records.
No student email is required in the reviewed student account model.
Students receive their own permitted records. Authorized librarians can access their school's roster and educational records, while approved teacher views are intended to be class-scoped. Ordinary staff views do not expose private drawings.
The production student login gateway is deployed and enforced. Student PINs are stored as bcrypt hashes, student session tokens are stored hashed, origin checks and shared abuse limits are used, and recorded checks deny the direct database login bypass.
Authorized librarian controls support student disable, export and deletion within documented school-scoped authorization. A general retention schedule and final request procedures remain subject to district/policy/legal review.
No runtime model-generation flow is documented. The proposed quiz-drafting workflow is book/source based and does not require student personal information. External development/content tools still require their own provider and policy review.
Readville documents its student-data practices, access controls, deletion/export tools, subprocessors and security approach for school and district review.
Current limitations retained for review
What is still being worked through
- Staff MFA is not currently enforced.
- A general student-record retention schedule is not yet approved.
- Backup availability is documented, but a restore exercise remains outstanding.
- Accessibility work is an initial review, not a conformance claim.
- Provider agreements, processing locations and final district requirements still require review.