Sub-processors
Last Updated: 8 November 2026
FORMD ("we," "us") engages third-party service providers ("sub-processors") to operate the platform. This page lists every sub-processor with access to personal data, what they do, what categories of data they receive, and where they process it. Sub-processors are bound by contractual obligations consistent with our Terms of Service, Privacy Policy, and where applicable our Data Processing Agreement (DPA).
We will notify customers of material changes to this list (additions, removals, or changes in data category) at least 30 days before the change takes effect, except where the change is required by law or addresses an immediate security risk. To subscribe to change notifications, email privacy@tryformd.com.
Current sub-processors
| Sub-processor | Purpose | Data category | Region | Compliance |
|---|---|---|---|---|
| Supabase Supabase, Inc. | Database (Postgres), authentication, edge functions, file storage | Account credentials, profile data, fitness data, race results, athlete-coach relationships | United States (us-east-1) | SOC 2 Type II; HIPAA-eligible (FORMD is not currently HIPAA-scoped) |
| Stripe Stripe, Inc. | Payment processing, subscription billing, customer portal | Payment method (card data is tokenized — never touches FORMD servers), billing address, transaction history | United States, European Union | PCI-DSS Level 1; SOC 1 Type II; SOC 2 Type II; GDPR-compliant |
| Resend Resend, Inc. | Transactional email delivery (welcome, billing, trial expiry, athlete invitations) | Email address, email content metadata, delivery / open / click events | United States | SOC 2 Type II; GDPR-compliant |
| Mixpanel Mixpanel, Inc. | Product analytics (funnel, retention, feature usage) | Account identifier, usage events (including workouts, logged sets, check-ins, and onboarding answers), device / browser metadata | United States | SOC 2 Type II; GDPR-compliant. On the website, loaded only after the user accepts analytics cookies. |
| Google Analytics Google LLC | Website analytics on tryformd.com (which pages people visit and which searches bring them there) | Pages viewed (address without query string; private links as their route pattern), referring page, a random cookie identifier, device / browser metadata, approximate location from IP. No account identifier, name, email, or health data | United States | EU Standard Contractual Clauses; EU-U.S. Data Privacy Framework. Loaded only after the user accepts analytics cookies; Google signals and ad personalization off. |
| Sentry Functional Software, Inc. (Sentry) | Error monitoring and performance tracing | Website: error stack traces, browser version, pseudonymous user ID (no email, IP, or cookies). Mobile App: stack traces, device data, account email, and a screenshot of the screen at the time of an error | United States | SOC 2 Type II; ISO 27001; GDPR-compliant. On the website, error monitoring runs as a strictly-functional service (no PII, no cookies, no session replay); performance tracing loads only after the user accepts analytics cookies. |
| Intercom Intercom, Inc. | In-app customer support messaging | Email, name, account metadata (subscription status, plan and store, trial status, app version, app language, whether a race date is set), support-message content | United States | SOC 2 Type II; GDPR-compliant. Built into the Mobile App; on the website, loaded only for signed-in coaches on the Coach Platform, as part of the service. |
| RevenueCat RevenueCat, Inc. | Mobile subscription lifecycle (App Store and Google Play entitlements) | Account identifier, email, name, referral code, subscription status, store purchase events | United States | SOC 2 Type II; GDPR-compliant |
| OpenAI OpenAI OpCo, LLC | AI training plans, AI coach replies and reading them aloud, voice-note transcription, and workout photo import | Profile and goals, reported physical limitations, recent training and race results, Coach notes, AI coach messages and voice notes, workout photos you choose to import, and the Apple Health and Garmin summaries in Section 6.4 of the Privacy Policy (no HealthKit identifiers or individual samples; no individual Garmin data; no Strava or HUAWEI Health data) | United States | SOC 2 Type II; EU Standard Contractual Clauses; OpenAI does not train on data submitted via the API per their commercial terms |
| Vercel Vercel, Inc. | Web hosting, CDN, edge runtime | All HTTP request data (URLs, IP addresses, user agent strings) | Global edge network | SOC 2 Type II; GDPR-compliant |
| Expo Expo (Expo Go / EAS, by 650 Industries, Inc.) | Mobile push notification delivery, OTA update distribution | Device push tokens, notification content (which can include a preview of a Coach's message), device identifiers | United States (AWS) | SOC 2 Type II; GDPR-compliant; EU Standard Contractual Clauses |
| Cloudflare Cloudflare, Inc. (infrastructure provider to Supabase) | Edge security and request routing for our database and API | IP addresses, request metadata | Global edge network | Engaged through Supabase |
| Apple Apple Inc. | App distribution, in-app purchase, Sign in with Apple, HealthKit data source | Apple ID identifier (transactional only), purchase data, sign-in identifier and email, HealthKit data (with the user's permission) | United States | Apple's published developer terms |
| Google Google LLC | Sign in with Google, address autocomplete for Coach profiles (Places), web fonts (Google Fonts) | Google account identifier and email (sign-in only), address search text, IP address and browser data when fonts load | United States | EU-U.S. Data Privacy Framework |
| AppsFlyer AppsFlyer Ltd. | Routing links in FORMD emails to the right app store or app screen (OneLink) | IP address and device data when a user taps a link in a FORMD email | Global | See the provider's privacy policy |
| DocuSeal DocuSeal | Electronic signature of creator program agreements | Name, email, social-media handles | United States | See the provider's privacy policy |
Note on HYRESULT (public race-result data source)
FORMD's Results feature aggregates publicly available HYROX race results sourced from HYRESULT (hyresult.com), a public race-result index. HYRESULT is a public data source, not a sub-processor — see the Privacy Policy §2.8. FORMD reads HYRESULT's public records; when you search for or import race results, the athlete name you search for is sent to HYRESULT to look them up. HYRESULT does not process data on FORMD's behalf, so it is not listed in the sub-processor table above. If you do not want your public race result displayed in FORMD, email privacy@tryformd.com and we will remove it.
Cookie controls
On the website, Mixpanel, Google Analytics, and Sentry performance tracing set cookies or browser storage and only initialize after you grant consent through the cookie banner. Intercom support chat loads only for signed-in coaches on the Coach Platform, where it is part of the service whatever you choose in the banner. Sentry error monitoring runs from first load as a strictly-functional service — it captures crash diagnostics scrubbed of personal data (no IP, email, or cookies) so we can keep the service working reliably. You can revisit your choices at any time via the "Manage cookie preferences" link in the page footer. See the Cookie Policy for full disclosure.
Questions or objections
If you object to the use of a particular sub-processor, or if you need a copy of our Data Processing Agreement, please contact privacy@tryformd.com. Material objections may, in some cases, mean we cannot provide the relevant service to you — we will explain the consequences honestly before any action is taken.