Compliance overview
Student data should feel entrusted, not extracted.
Recallhaus is built for the quiet work of K–12 learning: noticing a gap, offering the right five-minute drill, and giving educators a useful signal. We treat the student data inside that loop as entrusted school data — limited, role-scoped, and governed by the district that brought us in.
This is a plain-language overview of our operating posture, not a certification or a substitute for district counsel. The signed DPA and applicable law govern each partnership.
- School-directed learning purpose
- District-controlled access and integrations
- Documented parent and district request paths
FERPA-aligned
School official, district direction.
When a district engages Recallhaus under its data-processing agreement, we operate in the school-official lane with a legitimate educational interest under 34 CFR §99.31(a)(1). We use student data to provide the learning service the district authorized, and we do not re-disclose student PII.
The district controls the roster, roles, and enabled integrations. Access follows the role that needs it: teachers see per-student gap data for their roster, parents and guardians see their own child's information, district admins see aggregate-only dashboards, and support access is scoped, audited, and time-boxed. Return and deletion expectations are set in the agreement and described in detail on our security page.
COPPA-aligned
Minimize first. Make parent paths visible.
Where students under 13 use Recallhaus, school or district authorization may be the appropriate path where the law permits it. The district's counsel, privacy process, and signed DPA govern the details; this page is not a substitute for that review.
Our operating posture is simple: collect the minimum learning signal, never use it for advertising, and keep parents and guardians able to request review, deletion, or revocation of prior consent through the district or Recallhaus. The full request process, timelines, and exceptions are on the data & privacy page.
Ready for the district conversation?
Bring your DPA questions. We'll bring the pilot packet.
Tell us which grades, schools, and systems you are evaluating. We can start with one cohort and make the data boundaries explicit before anyone rolls out.