Student data privacy, for district review
MyMathLearning is a program of Divide and Conquer Math Institute, which operates MyMathLearning.com. This page is written for the technology directors and privacy officers who review classroom tools before adoption. It states how MyMathLearning collects, uses, and protects student data, names our subprocessors, and offers to sign Colorado's standard data privacy agreement.
FERPA & COPPA alignment
FERPA
We treat student education records (names, class placements, responses, and scores) as protected under FERPA. They are used only to provide the educational service a school has authorized — grading, review, and reporting back to the student's teacher. We do not sell student data and we do not show advertising to students.
COPPA
Students under 13 can use MyMathLearning only with school authorization (under COPPA's school-authorization exception) or with parent consent. Students join a class with a join code — no email address or account is required on their end. The optional rewards shop uses earned in-app points, never money, and there are no in-app purchases directed at students.
What data we collect & why
We collect the minimum needed to run the classroom experience. Nothing here is used to build profiles of students or shared for advertising.
| Data | How it's used |
|---|---|
| Student name & display name | Identifies work and submissions to the teacher. Set by the student or teacher; no student email required to join a class. |
| Class & assignment records | Links students to their teacher's class and assigned warm-ups, worksheets, and relays. |
| Student responses & scores | Answers, drawings, graph plots, and auto-grading results, stored so teachers can review and report on mastery. |
| Progress & engagement | XP, streaks, levels, and Math Journey progress used to motivate students and surface class trends. |
| Camera & bubble-sheet grading | Teachers and students can photograph a printed bubble sheet instead of typing answers. The photo is read entirely in the browser — it is never uploaded, stored, or sent to any AI service, and only the answers the app detects and the resulting score are saved to the student's record. Camera or photo-library access happens only when the user taps the capture button; the app never opens the camera on its own. Handwritten-work photos are the exception: those are uploaded deliberately so the teacher can review and analyze them (see the next section). |
| Teacher account details | Name and email to administer the account and (optionally) approve AI-tool access. |
| Standardized math assessment scores (Star Math, CMAS, Illuminate, i-Ready, MAP Growth, or another state test) | Uploaded by a teacher from the district's assessment export. The file is parsed in the teacher's browser and never uploaded or sent to any AI service; only matched results (which test, how the score reads, the score, percentile, performance level, test date) are saved, and no student names from the file are stored. Visible only to the importing teacher, their co-teachers, and site admins — students and parents cannot read them. Used to suggest small-group intervention support (any AI-generated lesson receives only anonymized skill levels, assessment levels, and standard codes). Kept until the teacher deletes it, which they can do at any time — per student, per test date, or for the whole class — from the Import Assessment Scores page. |
Students can use the platform without creating an account of their own — a teacher's join code is enough. Where a student or parent does create an account (for example, the optional home Parent plan), the email is used only to sign in and recover the account.
Subprocessors
These are the third parties that process data on our behalf to deliver the service. We keep this list current; material changes are posted here.
Cloud application platform
Hosts the application and database that run MyMathLearning, and stores student records on our behalf.
AI language-model providers
Power optional AI generators (warm-ups, worksheets, answer keys, intervention plans). See our AI Use page for details.
Stripe
Processes payments for premium plans and credit packs. Card data never touches our servers.
Optional Google sign-in and Google Classroom rostering/assignment posting, when a teacher connects it.
For specifics on how the AI provider handles data, see our AI use & transparency page.
How student data is used with AI features
- Most AI features are teacher-initiated. They generate teaching materials (warm-ups, worksheets, answer keys, intervention plans) and analyze student work only when a teacher clicks Analyze — students are never sent to an AI model during normal practice.
- The one student-initiated AI tool is Socratic hints, which a teacher must enable for a student before it's available. It sends only the teacher-authored question text — never the student's typed answer — to Google's free-tier Gemini model, so no student data leaves the app.
- Handwritten-work analysis is teacher-initiated: the student uploads a work photo, and the AI runs only when the teacher clicks Analyze. It always runs on a no-training provider tier (Anthropic / OpenAI), whose terms do not allow training on customer-submitted data — student work is never sent to a free model tier, and no student names are sent. A district with its own reader has photos sent only to that reader, in a signed request with no student identifiers; if that reader is unavailable the work is queued for it rather than sent anywhere else. The student's upload itself never calls the model.
- When a teacher generates content, only the inputs needed to build it are sent (grade, topic, standard code, and the teacher's prompt). Student names and individual student responses are not sent to the AI provider.
- The student 'My Math Journey' arcade mode is fully procedural — it generates challenges with code, not AI, and sends nothing to any AI provider.
- Assessment imports never touch AI: the teacher's export is parsed in their browser and only matched results are saved. Intervention-plan drafts built from that data are generated from anonymized skill levels, assessment levels, and standard codes only — never student names, emails, or IDs.
- Teachers review and approve every AI-generated item before students see it. Nothing AI-generated reaches students without a teacher's sign-off.
Optional Google integrations
Two Google integrations are available to teachers who choose to connect their own account. Both are optional, off by default, and scoped to the minimum needed. A teacher can disconnect either at any time.
Google Calendar
When a teacher connects their own Google Calendar, the app creates all-day reminder events for assignments that have due dates. Each event contains only the assignment title and class name — no student names or responses are written to the calendar. The app cannot read the teacher's personal calendar events.
Google Classroom
When a teacher connects Google Classroom, the app can list the teacher's courses and post an assignment announcement. Announcements contain only the assignment title, due date, and a link to open the work. The app does not read or import student rosters from Classroom; students still join through the teacher's join code.
Retention, deletion & your rights
Retention
Student records are kept while a class is active and for the school year, so teachers can report on growth. A teacher or admin can delete a class and its data at any time.
Deletion
Any user can delete their own account in the app, and it takes effect immediately — see how it works. Teachers can remove a student from a class; admins can request full deletion of a school or district's data by contacting us.
No sale, no ads
We never sell student data and we never show advertising to students. Data is used solely to provide the service.
We'll sign your data privacy agreement
We will sign the Colorado Student Data Privacy Agreement (the SDPC template used by most Colorado districts), or your district's equivalent. We're also glad to complete a privacy questionnaire or vendor assessment as part of your review.