Sub-processors
Last updated: 5 October 2026
To run BetterStep we rely on a small number of trusted service providers ("sub-processors") that process your data on our behalf. Some of that processing happens outside Georgia. This notice lists who they are, what they do, and where your data goes. It supplements, and should be read together with, our Privacy Policy and Consumer Health Data Policy.
Service providers we use
• Our AI model (Gemma), which we run ourselves on a rented GPU server - onboarding and profile analysis, task generation, insights, AI chat and checking Community posts. Receives your free text (journal and reflections, chat messages, onboarding answers), the profile we derive from it, your check-ins, health readings and recovery data, and Community posts, comments and photos. No outside AI company (such as OpenAI, Anthropic or Google) receives it. TO CONFIRM: the country this server is in, and the company that operates it. • Terra (USA) - connects your wearables and health platforms (Apple Health, Fitbit, Garmin, Oura, Whoop, etc.). Receives the biometrics you authorise (heart rate, HRV, sleep, steps, calories, SpO2, temperature, body composition). • LiveKit Cloud (USA) - audio and video for live rooms and calls. Receives your voice and video while you are in a room, the messages you write in the room's chat, your display name, your account ID (or a made-up ID if you join without your name), the room identifier and your IP address. We do not record rooms. • Sentry (EU - Germany) - backend error monitoring. Receives crash and diagnostic data and technical metadata. • Google Firebase (Cloud Messaging, Crashlytics) (USA) - push notifications, and mobile crash reporting only if you turn on "Send crash reports" in Settings (off unless you do). Receives your push token and device and technical metadata; with crash reports on, also where the app failed, device details (such as model, system and app version, memory and battery), a random installation ID and your IP address. The text of errors in the app's JavaScript code is removed on your phone before sending; the message of a crash in its native Android or iPhone code is sent as written. Firebase Analytics and Firebase Sessions are switched off. • Google Sign-In / Apple Sign-In (USA) - social login. Receives your email and basic profile, or Apple's relay identifiers. • SendGrid (USA) - transactional email. Receives your email address and the message content. • ElevenLabs (USA) - text-to-speech for guided exercises. Receives only the scripts we write for them, nothing about you and never your voice (we do not record it). • OpenStreetMap Nominatim and Zippopotam.us - location lookup when you enter your location. Receive the city, country or postal code you type, to place it on the map, and your IP address. • YouTube (Google) (USA) - podcast playback. When you open a podcast, the embedded YouTube player loads from Google, which receives your IP address, device information and playback activity under Google's privacy policy. We do not send it your account or health data. • MongoDB and hosting (EU - Germany) - our own database and servers, rented from Hetzner Cloud in Falkenstein, store and process your data. • sender.ge (Georgia) - text messages (SMS) from clinics. A clinic you are enrolled with can text you, for example an appointment reminder, through its own sender.ge account. sender.ge receives your phone number and the text of the message. Some parts of the app also load photos, country outlines and sample videos straight from other sites. They are listed on the page "Where your data is stored". We do not use third-party product-analytics trackers (Amplitude, Mixpanel, Segment, Google Analytics) or any payment SDK. If we ever add a payment provider, it will be listed here first.
Clinicians
If you choose to enrol with a clinician, that clinician can see your name, email, recovery profile (your progress signal / tier and clean days), daily check-ins (mood, stress, cravings, sleep, slip flag) and any clinical notes. Clinicians are external organisation staff in a separate, role-based access realm, with an access audit log. This sharing is a feature you opt into - not a hidden exception.
International transfers
BetterStep's provider is based in Georgia; storage and our own processing happen in Germany (EU), except for our AI model, which runs on the rented GPU server described in the first entry above. The providers listed above process what they receive in the countries shown next to them (mostly the USA). We transfer your data on the basis of your explicit, informed consent. • TO CONFIRM: the data-processing agreement with each provider, and the legal safeguard for these transfers. • TO CONFIRM: that we do not transfer any user data to China. This depends on where the server that runs our AI model is. • TO CONFIRM: the country shown for each provider above. The countries have not been checked against each provider's contract. • If you are a US resident, we disclose every recipient of your consumer health data and ask for separate consent to share before your health, journal or voice data leaves to any provider (see the Consumer Health Data Policy). • TO CONFIRM: the separate consent to share described in the line above. The app does not ask for it today.
Keeping this list current
Several regulators (and Apple and Google) require this list to be accurate and up to date. We update it whenever we add or remove an integration. If you have a question about any provider, contact us below.