Effective October 18, 2026
This Data Processing Agreement (“DPA”) is part of the Health Movement Organization Terms and applies to every Organization that accepts them. Capitalized words mean what they mean in the Organization Terms. Where this DPA and the Organization Terms conflict on data matters, this DPA controls. A signed copy is available at support@healthmovement.com.
1.1 There are two kinds of data in the service, and the roles differ.
Participant data. Data that Participants give us directly in our apps (daily step totals or active minutes, habit check-ins, display name, optional photo, birth year, friends and challenge membership, pulse survey answers) is collected under our Privacy Policy and consumer health data policy. For this data Health Movement is an independent controller (or “business” under California law) and is responsible for it. The Organization never receives it and has no rights in it.
Organization data. The Organization’s account records (Owner and admin names and work email addresses, the names and email addresses on the Members list of people who joined, organization details, challenge settings, drawing settings and results, invoices), and the Aggregate Reports we produce for the Organization (participation counts, group totals and averages, pulse survey aggregates, exports). For Organization data and Aggregate Reports the Organization is the controller (or “business”) and Health Movement is its processor (or “service provider”), acting only on the Organization’s documented instructions, which are the Organization Terms, this DPA and the settings the Organization chooses in the dashboard.
1.2 Nothing in this DPA gives the Organization any right to Participant data, and no instruction from the Organization can require us to process Participant data for it.
2.1 We process Organization data and produce Aggregate Reports only to provide the service, support the Organization, bill it, keep the audit log, meet legal obligations and improve the service in de-identified form.
2.2 We never process data at the individual level on the Organization’s behalf. Every Aggregate Report is produced by database functions that hide any figure derived from fewer than 5 people and never show who has not joined.
2.3 We do not use Organization data or Aggregate Reports for employment, discipline, insurance, underwriting, rating or health-plan decisions, and the Organization agrees not to instruct us to, and not to use them that way itself.
2.4 If we believe an instruction breaks the law, we will tell the Organization and may decline it.
3.1 Participant data (collected by us under our own policy, listed here so the Organization knows what the apps hold): daily step totals or active minutes recorded by the phone or watch, habit check-ins, display name, optional photo, birth year, challenge and team membership, friends, pulse survey answers. Not collected in any organization challenge, and never visible to an Organization: location, contacts, heart rate, sleep records, workouts, weight or any body measurement. (Health Movement Daily offers adults an optional weight screen for their own use; it is never for anyone under 18, is never part of an organization challenge and is never visible to an Organization or a friend.) Hourly step detail stays on the phone and is never uploaded.
3.2 Organization data: Owner and admin name and work email, the name and email of each person who joined the Organization (shown to administrators on the Members list), organization name, address and verification details, plan and billing records, challenge configuration, drawing configuration and draw results, audit log entries.
3.3 Aggregate Reports: participation counts and shares, team and group totals, Fair play and percent-of-baseline averages, pulse survey aggregates, certificates, CSV exports of the same.
3.4 People affected: the Organization’s Owner and admins; Participants, who may be employees, students 13 and older, members or the public, only ever in aggregate (apart from the Members list in 3.2).
4.1 We keep Organization data confidential and disclose it only as this DPA allows. Today, administrative access to the production database is limited to the founder of Health Movement; as staff are added, each person with access will be bound by a written confidentiality duty and given access only to what their role needs.
4.2 We will not disclose Organization data to any third party except subprocessors under section 6, the Organization’s own admins, or where the law requires, in which case we will tell the Organization first unless the law forbids it.
5.1 We maintain the measures described in our Security Overview (available on request at support@healthmovement.com), which is Annex 2 to this DPA and is updated as our controls change. In summary: row-level security on every table so a person can read only their own account and challenges; organization functions that run as trusted database functions checking the caller’s role on every call; an audit log of plan, billing, export and verification actions; plan and people limits enforced by the database; sign-in by Apple, Google or emailed link with no passwords stored by us; payments handled by Stripe with signed webhooks; secrets held outside the code; encrypted connections in transit; encryption at rest and backups provided by Supabase; no advertising or analytics SDKs receiving step data; removal of profile, photo, step history and membership from live systems as soon as a Participant deletes their account, with copies at subprocessors and in backups cleared on the timeline in our consumer health data policy (within 30 days, and from backups within the following 30 days).
5.2 Not yet in place, stated so no one is misled: single sign-on and enforced multi-factor authentication for admin accounts (Google sign-in with its own MFA is available), a read-only reporter role, per-organization retention settings, a SOC 2 report, a third-party penetration test and a formal vulnerability disclosure program. We will update Annex 2 when any of these changes.
6.1 The Organization authorizes the subprocessors listed in Annex 3 (also on the subprocessor page).
6.2 We will give the Owner at least 30 days’ notice by email before adding or replacing a subprocessor. If the Organization has a reasonable objection it may end the Organization Terms before the change takes effect and receive a pro-rated refund of any prepaid period.
6.3 Each subprocessor is bound by written terms that protect the data at least as well as this DPA does. We remain responsible to the Organization for our subprocessors.
7.1 We will tell the Organization without undue delay, and in any case within 72 hours of confirming it, about any breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Organization data or Aggregate Reports, or to Participant data of people in the Organization’s challenges.
7.2 The notice will describe what happened, what data and roughly how many people are affected, what we have done and plan to do, and a contact. We will update it as we learn more and will preserve relevant logs.
7.3 We will cooperate with the Organization’s own notification duties. Where the law requires notice to individuals or regulators about Participant data, we give that notice ourselves, because we are the controller of it, and we will coordinate timing and wording with the Organization where the breach also touches its data. Breach costs are allocated as follows: each party bears the cost of its own legal duties; where a breach is caused by our failure to meet this DPA we reimburse the Organization’s reasonable, documented cost of notices the law required it to send, up to the liability limit in the Organization Terms.
8.1 Participants exercise their rights (access, correction, deletion, withdrawal of consent) directly with us through the apps and our Privacy Policy; deleting a Participant account removes their data from live systems at once, ends any challenge membership, and clears subprocessor copies and backups within the 30 days plus 30 days promised in our consumer health data policy. If a Participant asks the Organization instead, the Organization will point them to us and we will handle it.
8.2 For Organization data, we will respond to the Organization’s instruction to access, correct, export or delete it within 30 days.
8.3 We will provide reasonable help with the Organization’s privacy impact assessments, security questionnaires and consultations with authorities, where our processing is the subject.
9.1 On request, no more than once a year unless a breach has occurred, we will complete the Organization’s security questionnaire or self-assessment, provide our current Security Overview, incident response plan summary and subprocessor list, and provide any third-party audit report we then hold. An onsite or remote audit by the Organization or its auditor is by written agreement, during business hours, at the Organization’s cost, and under confidentiality.
9.2 We do not yet hold a SOC 2 report and will not represent otherwise. Our hosting provider publishes its own security attestations, which we will point to; they describe the provider’s controls, not ours.
10.1 Within 90 days after the Organization’s account closes or the Organization Terms end, we delete or de-identify all Organization data and Aggregate Reports, unless the law requires us to keep specific records (for example invoices for tax purposes), and we will confirm deletion in writing on request. Before closing, the Organization may export its Aggregate Reports as CSV from the dashboard.
10.2 Participant data is not deleted when the Organization leaves. It belongs to the Participant, stays with the Participant’s consumer account, and is deleted when the Participant deletes it. The Participant’s membership in the Organization’s challenges ends, and the Organization’s challenges stop counting them. An Organization should not expect us to delete its employees’ or students’ personal app accounts, and we will not do so at its request.
10.3 Backups of Organization data and Aggregate Reports are overwritten on our hosting provider’s schedule; de-identification or deletion of that data reaches backups within six months. Participant data follows the shorter timeline in our consumer health data policy, not this one.
11.1 California. With respect to Organization data and Aggregate Reports, Health Movement is a service provider under the California Consumer Privacy Act as amended. We will not sell or share that data; will not retain, use or disclose it for any purpose other than the business purposes in this DPA or outside the direct business relationship with the Organization; will not combine it with personal information we receive from others except as the law permits a service provider to; will notify the Organization if we can no longer meet these obligations; and we certify that we understand these restrictions. The Organization may take reasonable steps to stop and remedy unauthorized use. Participant data that we collect directly in the apps is processed by us as a business under our own Privacy Policy, and the Organization is not responsible for it. The Organization is responsible for any notice at collection its own law requires it to give its employees or students about the program.
11.2 Washington, Nevada, Connecticut and other consumer health data laws. We treat Participant activity data as consumer health data under the strictest of these laws, obtain a separate consent before anything of a Participant’s is counted in an Organization’s totals, and honor withdrawal and deletion on the timelines in our consumer health data policy. Nothing in this DPA asks the Organization to collect consumer health data on our behalf.
11.3 Utah and other states with government data privacy laws. Where the Organization is a public body, the Government Customer Addendum adds the terms those laws require.
11.4 We do not sell personal data, and we do not share it for cross-context behavioral advertising, under any state’s definition.
12.1 Public bodies: the Government Customer Addendum is part of these terms and adds public-records, appropriation, venue and Utah Code 63A-19 terms.
12.2 Schools: the Student Data Privacy Agreement is part of these terms for any school organization and adds the student-data terms state law requires. Where it and this DPA differ, the Student Data Privacy Agreement controls for student data.
13.1 This DPA lasts as long as we process data for the Organization. Sections 7, 10 and 13 survive. Liability under this DPA is subject to the limits in the Organization Terms. If a change in law requires a change to this DPA we will update it and notify the Owner; if the Organization needs a signed copy, request one at support@healthmovement.com and we will return a countersigned PDF of this same text.
Subject: operation of voluntary activity and habit challenges for the Organization. Duration: the term of the Organization Terms plus the 90-day deletion period. Nature and purpose: section 2. Data categories: section 3. People affected: section 3.4. Location: United States.
The current Security Overview, available on request at support@healthmovement.com and incorporated by reference, including its list of measures not yet in place.
Supabase (database, sign-in, server functions; United States region). Stripe (payments and billing). Netlify (website hosting). Apple and Google (app stores, sign-in, notification delivery). Postmark (account email). Expo and Firebase Cloud Messaging (builds, push notifications). RevenueCat (consumer subscription management; not used for organization billing).