Littovia Children's Data Notice
This notice explains why Littovia handles children's information in the California pilot and how access is scoped across schools, teachers, families, and platform operations.
Why we process children's information
We process children's information to support attendance-style workflows, health cards, pickup safety, class feed posts, teacher announcements, family messaging, and audit tracking in normal school operations.
If information is not needed for those core workflows, we do not keep it as a permanent required field by default.
Information scope
Children's information may include names, class assignment, status logs, health and allergy details, pickup contacts, temporary pickup codes, class-feed related images, and student-linked communication records.
Visibility rules
Teachers can access assigned classes. Principals can access their school scope. Platform administrators access data only when operations or security support requires it.
Families can access linked students. After archive, a family keeps a default 30-day visibility window unless the school closes access earlier.
Security measures
Non-parent roles require TOTP. All roles require trusted devices. Sensitive actions are written to audit logs. Notifications and messaging are scoped to the active device and permission model.
Deletion and correction
Families may submit account deletion requests. If a request touches children's records, deletion, correction, or retention decisions are handled against school duties, guardian identity, and applicable law.