Subprocessors
Effective 28 October 2026. Version 2026-10-28.
The companies below process personal data on behalf of Trailwise. Each one is bound by a data-processing agreement, processes data only for the purpose stated, and is listed with its location and the transfer safeguard where data leaves the European Economic Area. We update this page before adding a subprocessor; if you want to be told by email, write to privacy@trailwise.coach.
| Subprocessor | Purpose | Location of processing | Transfer safeguard |
|---|---|---|---|
| Google Cloud (Google Ireland Ltd) | Hosting, database, storage and backups for the whole service | European Union | Not applicable (data stays in the EU); Standard Contractual Clauses for remote support access |
| Anthropic PBC | The language model behind Trailwise; receives the data needed for each answer; contractually barred from training on it; inputs and outputs retained only as long as needed, with limited retention for trust and safety | United States | EU-US Data Privacy Framework certification and Standard Contractual Clauses |
| Stripe Payments Europe Ltd and Stripe Inc | Payments, invoices, subscription management; holds card details so that Trailwise never does | European Union and United States | EU-US Data Privacy Framework certification and Standard Contractual Clauses |
| Resend Inc | Sending transactional email: sign-in links, confirmations, digests, alerts | United States | Standard Contractual Clauses |
| Backblaze Inc | Encrypted off-site copies of the database backups, kept on a daily, weekly and monthly rotation; every copy is encrypted before upload with a key Backblaze never holds | European Union (the Netherlands) | Not applicable (data stays in the EU); Standard Contractual Clauses for remote support access |
| Google Ireland Ltd (Google Analytics 4) | Usage statistics on the website and in the app, only if you allow analytics; in the app, page views only, without the identifiers in the address, plus a pseudonymous identifier for signed-in users; data kept for fourteen months | European Union and United States | EU-US Data Privacy Framework certification |
| Linear Orbit Inc | Support cases and bug reports you send us, with the technical context you attach | United States | Standard Contractual Clauses |
| MapTiler AG | Map tiles for the weather and route pages; receives your IP address and the map area viewed | Switzerland | EU adequacy decision for Switzerland |
| OpenWeather Ltd | Precipitation map layer and forecasts; receives your IP address and the map area or place requested | United Kingdom | EU adequacy decision for the United Kingdom |
| Open-Meteo | Weather forecasts and place search for the location you choose; receives the coordinates or place name | Switzerland and European Union | EU adequacy decision for Switzerland |
| OpenStreetMap Foundation (Nominatim) | Converting a race location name into coordinates; receives the place name only | United Kingdom and European Union | EU adequacy decision for the United Kingdom |
| Apple Distribution International Ltd | Distribution of the iOS app and push notifications on iPhone | European Union and United States | EU-US Data Privacy Framework certification |
| Google Ireland Ltd (Google Play) | Distribution of the Android app and push notifications on Android | European Union and United States | EU-US Data Privacy Framework certification |
Services you connect (not subprocessors)
Strava, Garmin, Google Health, Polar, WHOOP, Oura, Withings, Intervals.icu, Apple Health and the iPhone calendar (through the Trailwise iPhone app), Google Calendar and iCloud Calendar are not subprocessors: they send data to Trailwise on your instruction, under their own terms and privacy notices. Trailwise sends data back to one of them only to provide a feature you use, such as the race days and training sessions it writes into Google Calendar, the race deadlines it adds to Google Tasks if you switch that on, and the planned sessions it sends to your Intervals.icu calendar or, through the Trailwise iPhone app, to your Apple Watch and iPhone calendar. You can disconnect any of them at any time; section 9 of the privacy notice says what happens to the data already received, and section 7 what happens to the upcoming items Trailwise wrote into Google Calendar or Intervals.icu. Files you upload yourself, such as a Garmin export or a FIT file, come from you, not from a connected service. Trailwise also reads public race listings, for example from RunSignup, to build its race catalogue, and sends them no data about you.
Google advertising (not a subprocessor)
If you choose "Allow all" in the cookie banner, Google also uses data about your visits to our public pages for its advertising services: Google Signals, and the Google Ads audiences through which Trailwise shows its own ads to past visitors. For those uses Google Ireland Limited acts as an independent controller under its own privacy policy, not as a subprocessor. Advertising signals are always off in the app while you are signed in, and Trailwise never uses training, health or body data for advertising.
Last updated 28 October 2026.