Health Movement for Organizations

Student Data Privacy Agreement

Effective October 18, 2026

This agreement is between Health Movement, LLC (“Health Movement”, “we”) and the school, district or other local education agency that creates a school organization (the “School”). It is part of the Health Movement Organization Terms and Data Processing Agreement and controls over them for student data. It is written to meet Utah Code 53E-9-309 (as amended effective July 1, 2026), Utah Admin. Code R277-487, the Illinois Student Online Personal Protection Act and similar state laws. Where the School’s state requires terms not here, section 12 applies.

1. The service and the students it is for

Health Movement Steps (and, when the School chooses it, Health Movement Daily) runs voluntary step and habit challenges. Students 13 and older join from the public app on their own device, under our consumer Privacy Policy and Terms of Use, which they or their parents accept in the app. Students under 13 may not be invited; the School confirms this. The School sees aggregate participation and totals only, plus the Members list described in section 2.1.

2. Student data we collect, and what we do not

2.1 Collected from the student in the app: daily step totals or active minutes recorded by the phone or watch, habit check-ins, a display name the student chooses, an optional photo, birth year, challenge and team membership, and answers to a three-question anonymous survey about the challenge. Collected from the School: the School’s name and the names and work email addresses of the staff who administer the account. The School’s administrators can also see, on the Members list, the name and email of each student who joined the School’s organization, and nothing about what the student did. The School never gives us a roster, grades, student identifiers or any education record, and we do not ask for one.

2.2 Not collected from students: location, contacts, heart rate, sleep, workouts, weight or body measurements (our apps never ask anyone under 18 for weight), health conditions, free-text about a student’s health, or any family information. Hourly step detail stays on the phone.

2.3 Outside the challenges they join, students 13 to 17 are shown to people who are not their friends only in participant counts, never by name, photo or progress, and can add friends only by code. Compare with friends and the activity-sharing switch are not available to anyone under 18. Inside a challenge, teammates see what the challenge is scored on (display name, team and daily score), and in large teams a pod of about five teammates sees first names and which days each checked in. School admins never see pods or any individual’s activity.

3. How we use student data

We use student data strictly to provide the service: to run the challenges the School sets up, to show the student their own progress and their team, to produce aggregate reports for the School, to keep the app secure and to meet the law. We do not use student data to build a profile of a student for any purpose other than the service, to target advertising, or for any purpose the School has not agreed to in this agreement. We do not sell student data, and we will not rent, trade or give it to anyone to use for their own purposes.

4. Who we share with

Only the subprocessors listed in the Data Processing Agreement (Annex 3), each bound by written terms, and only to provide the service. We will not share student data with any other person except as the law requires, in which case we will tell the School first unless the law forbids it. We do not share student data with the School beyond aggregates and the Members list: the School never sees any individual student’s steps, check-ins or survey answers, and no plan or payment unlocks that.

5. Security

We protect student personally identifiable information against unauthorized access and redisclosure using the measures in our Security Overview (Annex 2 to the Data Processing Agreement): row-level security, role-checked database functions, an audit log, encrypted connections, encryption at rest, no passwords stored by us, no advertising SDKs. We maintain written security policies aligned with industry standards and will document our information security program and disclose our precautions to the School on request. We will update the School if a material change reduces protection.

6. Breach notice

We will tell the School within 72 hours of confirming a breach of security that affects student data of its students, and in no case later than 30 calendar days after determining that a breach occurred. The notice will say what happened, what data and roughly how many students are affected, what we have done, and a contact. Costs: each party bears the cost of its own legal duties; where a breach is caused by our failure to meet this agreement, we reimburse the School’s reasonable, documented cost of notices the law required it to send, up to the liability limit in the Organization Terms.

7. Audit and assurance

The School may satisfy its audit requirement by asking us, once a year, to complete a self-assessment or questionnaire, provide our Security Overview and any third-party audit report we then hold (we do not yet hold a SOC 2 or SOC 3 report and will say so), or, by written agreement, conduct an onsite or remote audit under confidentiality at the School’s cost.

8. Deletion, return and retention

8.1 At the School’s request, or when this agreement ends without renewal, we delete or de-identify within 90 days all School data (admin accounts, challenge settings, aggregate reports, audit entries), we end every student’s membership in the School’s challenges, and we delete the data held in connection with the School’s challenges (membership, team and pod records and challenge scores), without waiting for a request. We certify deletion in writing on request. Aggregate reports are exportable as CSV before closing. Where the School sends us the SDPC National Data Privacy Agreement, its 60-day deletion clock applies instead.

8.2 Student accounts are the student’s own consumer accounts, created and controlled by the student (or parent) under our Privacy Policy, and remain after the School leaves unless the student deletes them; what remains is the student’s own step history and profile, which the School never held. On the School’s written request naming a student by the display name or email the student used, we will delete that student’s challenge membership and any data held in connection with the School’s challenges, and will tell the student we did so. Deleting the whole account is the student’s or parent’s choice; it removes the data from live systems immediately and from backups on the timeline in our consumer health data policy. We will keep school-linked data past the end of this agreement only if a student’s parent gives written consent.

8.3 We keep student data no longer than needed to provide the service and meet the law.

8.4 Misuse, notice and termination. If the School discovers that we have used student data in a way this agreement or the law does not allow, it will tell us within 30 days of discovery. If we do not remedy the problem to the greatest extent practicable and put in place steps to prevent it from happening again, the School may end this agreement no sooner than 30 days after that notice, and we will not impose a fee, seek damages or assert any other financial liability against the School for ending it on that ground.

9. FERPA and parental rights

9.1 To the extent the School discloses any education record to us (it is not expected to), Health Movement acts as a school official with a legitimate educational interest under FERPA, is under the School’s direct control for that record, uses it only for the authorized purpose of providing the service, and does not redisclose it.

9.2 Parents may see what the app does at healthmovement.com/steps/parents/ and may ask us to correct or delete their child’s data through the app or at support@healthmovement.com. The School is responsible for any parental notice or consent its policies or state law require before inviting students; we will provide a parent letter template on request.

10. Student rights and the join screen

Joining is voluntary. The School must not require any student to join, must not grade, discipline or disadvantage a student for joining or not joining, and must not ask students whether they joined. The join screen tells students this, tells them that the School will only ever see group totals, and tells 13 to 17 year olds that a parent can see what the app does and that the School may ask their parent for permission.

11. Public disclosure

Our Privacy Policy, consumer health data policy, Security Overview and this agreement are published on our website so the School can meet any duty to disclose material information about our collection, use and disclosure of student data, and the School may publish this agreement on its own website.

12. State riders and the SDPC National DPA

12.1 Illinois. For a School in Illinois: this agreement is the written agreement required by 105 ILCS 85/15(4); the categories of covered information are in section 2; the product is in section 1; Health Movement is acting as a school official and is using covered information only for an authorized purpose (section 9); breach costs are allocated in section 6; deletion and its time period are in section 8; breach notice is given within 30 calendar days of determination (section 6); and the School must publish this agreement on its website (section 11).

12.2 Utah. For a School in Utah: sections 2 to 8 are the requirements and restrictions on collection, use, storage and sharing, the description of persons we may share with, the deletion terms, the secondary-use prohibition and the audit rights that Utah Code 53E-9-309(2)(a)(i) requires; section 8.4 is the notice, termination and no-fee provision that 53E-9-309(2)(a)(i)(F), (2)(a)(ii) and (iii) and (2)(b) require; section 8.1 is the return or deletion on non-renewal that 53E-9-309(5) requires, with the parent-consent exception in section 8.2; and sections 5 and 7 are the security and audit terms that R277-487-7 requires. We acknowledge that anyone may report a suspected violation to the Utah State Board of Education’s student data privacy team and that the team may audit or investigate us under 53E-9-309(2)(c).

12.3 Other states. Where the School’s state law requires terms not in this agreement, the School may send us its state’s Student Data Privacy Consortium National Data Privacy Agreement (NDPA, Standard Version 1.0, with the state exhibit), and we will sign it; where the NDPA and this agreement differ, the NDPA controls for that School (its 60-day deletion on request and 72-hour breach notice included). We will sign the NDPA’s General Offer of Privacy Terms (Exhibit E) so that other schools in the same state may rely on the same terms. We may ask for a short rider where the NDPA’s standard clauses describe data flows (for example rosters or education records) that do not exist in our product.

13. General

This agreement lasts as long as the School has an organization account and for the deletion period after. It is governed by the law of the School’s state. For public schools, the Government Customer Addendum also applies. Liability is as in the Organization Terms, except that nothing limits our liability for a breach of sections 3 or 4 caused by our willful misconduct. A signed copy is available on request.

School: ______________________ Signed: ______________________ Title: __________ Date: __________

Health Movement, LLC: ______________________ Date: __________