01
Privacy by design.
We collect the minimum data needed to make learning work. Student records are scoped to the schools that own them. We do not sell student data. We never will.
School trust posture
Built with school trust at the forefront.
aHasnap! is designed to support FERPA-aligned school deployments and COPPA-aware child privacy practices from day one. Privacy, security, and compliance are core requirements, not retrofits.
02
Security as default.
Encryption in transit and at rest. Server-side validation. Audited deletion paths. Hosted on enterprise-grade cloud infrastructure. Security treated as a release requirement, not a feature.
03
School compliance readiness.
FERPA-aligned data handling. COPPA-aware consent posture. State student privacy law alignment. The documentation and trust artifacts schools expect from a serious vendor.
How we think about school trust.
FERPA-aligned deployments
aHasnap! is built to operate as a school-official service provider under FERPA. Student records remain under school control. Data access follows least-privilege principles.
COPPA-aware practices
For children under 13, we operate under COPPA-aware consent frameworks. Schools may consent on behalf of parents under the educational-purpose exception when appropriate.
Encryption and audit logging
All data is encrypted in transit (TLS) and at rest (AWS RDS encryption). Audit logs track sensitive mutations. Incident response posture documented for school IT teams.
Minimal data collection
We collect only what is needed for the learning experience to work. We do not build third-party advertising profiles. We do not sell student data to any party.
Right to delete
Schools can request full deletion of a child’s record. Deletions cascade through every linked table. Consent records of deletion are preserved for audit.
Documentation on request
Privacy impact assessments, data flow diagrams, SOC posture summaries, and student data sub-processor lists are available to schools considering aHasnap!
A note on language
We say what we mean.
We say FERPA-aligned, not “FERPA certified.” There is no such government certification. We say built to support rather than overclaiming certifications we have not yet completed.
If you are evaluating aHasnap! for a school deployment and you need specific compliance documentation that is not yet listed here, get in touch and we will get you what you need.
Talk with us about school trust.
Send your district’s privacy or technology officer to a quick conversation. We will walk through every question you have.