Subprocessors
The service providers Cairnfit shares your data with, where they're located, and what safeguards apply to any transfer outside the EU. Full detail is in our privacy policy; this page is the register behind it.
Last updated 15 August 2026
Every processor below acts on Cairnfit's instructions under a data processing agreement (GDPR Article 28). None of them may use your data for their own purposes, and none of them see everything: each one receives only what its job requires.
Database, authentication and backend compute. This is where your data actually lives: your account, training, physiological data, pain reports, coach conversations and memory, all of it.
Generates your coach's replies (the Claude API). Receives your message plus the training and health context needed to answer it.
Delivers push notifications. Receives your device's push token and, briefly, the visible text of a notification. It does not keep a copy of the notification content once it's delivered.
Checks your subscription status and entitlement. Does not receive your training, pain, or coach data.
Sign-in, only if you choose to sign in with Google. Receives your sign-in identity (email, name, profile picture) and nothing else.
When you subscribe through the App Store or Google Play, Apple and Google process your payment as merchant of record. They set their own terms with you for that payment, collect card and billing details Cairnfit never sees, and are not acting on Cairnfit's instructions the way a processor does. Cairnfit only receives the result, an entitlement, relayed through RevenueCat. Strava and Garmin are listed here for the same reason, though the flow is different. If you connect Strava, Cairnfit sends Strava nothing but the authorisation you granted, and reads back the sport type, start time, duration and distance of your activities. If you use the watch app, your session is recorded on your own Garmin device and saved to your own Garmin Connect account, which is a transfer between you and Garmin rather than one Cairnfit makes on your behalf. In neither case is the company processing your data on Cairnfit's instructions, so neither is a subprocessor. Both are named here because you should know they are involved.