Educational Privacy (FERPA Notice)

Last updated: October 12, 2026

1) Overview

The App helps students practice multiplication facts and stores progress and performance data to adapt practice over time. Depending on how the App is deployed and used, student data may be considered an “education record” under the Family Educational Rights and Privacy Act (FERPA).

2) What data the App may process for students

• Student identifiers

  A username (which may be randomly generated) and a backend account identifier. Depending on configuration, an email address may be used for sign-in.

• Learning/progress data

  Multiplication fact performance, review scheduling fields, response-time statistics, and session summaries.

• Content uploads (optional)

  If enabled, students may upload images/assets for custom scenes; these may be stored in Firebase Storage.

• Technical data

  Device/browser information and diagnostic data collected by Firebase and Google Analytics for security, reliability, and product improvement.

3) Roles and responsibilities

Schools/districts are typically the data controllers for student education records. The App operator is a school official acting as a service provider under the school's direct control, processing data only for the school-authorized educational purpose (class practice, class-link sign-in, and home codes that let a student practice at home without a parent account). We remain responsible for our own obligations under COPPA and FERPA for the data we process, including the identifiers described in Section 2.

If a school uses the App with student accounts, the school is responsible for:

• Authorizing use

  Directing the App's use for its students, including issuing class codes or home codes, which we rely on as the basis for school-directed processing.

• Obtaining required consents

  Including any parent/guardian consent required under FERPA/COPPA and local law, beyond the school-authorization basis described above.

• Providing notices

  Providing any required privacy notices to parents/eligible students.

• Account provisioning

  Ensuring student sign-in methods are appropriate for the student population and the school’s policies.

A school may also give a student a home code so the student can practice at home on a device the school does not control, without a parent account. That home practice remains school-directed use: the school authorized the code, and it (or a connected parent) can end the resulting session at any time. See our COPPA notice for what the device stores for that session.

4) Access, correction, and deletion requests

If a school is managing student accounts, requests to access, correct, or delete student data should generally be routed through the school in accordance with its FERPA policies.

Educators and parents who hold a personal account may delete that account and its associated learner profiles, classrooms, and practice history at any time from the Danger Zone on the Profile page.

For operational help, contact us via the in-app Feedback button or email support@mathbuilders.com

5) Data security

We use reasonable safeguards designed to protect student data; however, no system is perfectly secure. Schools should evaluate whether the App meets their compliance, security, and procurement requirements.