Service Providers (Sub-processors)
The companies that help run HEAL, what each one does, and what data it can touch.
Draft — pending legal review. This document describes how HEAL intends to operate and will be finalized by qualified counsel before launch. Until then, write to privacy@teleheal.com with any question.
In plain words
- 01Like most online services, HEAL relies on a few specialist companies for hosting, email, live audio, push notifications, network protection, analytics and the website’s chat guide, plus payments and printing for the optional shop and Supporter plans.
- 02Each one handles only the data it needs for its job, only on our instructions.
- 03None of them can read your workbook answers or check-in notes.
- 04None of them may sell your data or use it for their own advertising.
- 05We announce new providers here before they start. Email privacy@teleheal.com to get updates, or to object.
This summary is for convenience. The full text below is what applies.
On this page
01Our current service providers#
These companies process personal information on HEAL’s behalf. The data shown is the most each one can access.
| Provider | What it does for HEAL | Data it handles | Where | Never receives |
|---|---|---|---|---|
| Railway | Hosts the HEAL API, database (Postgres) and job queue (Redis) | All account and app data, stored with workbook answers and check-in notes encrypted | United States | Readable workbook answers or check-in notes. They’re stored sealed, and the key isn’t kept in the database. |
| Vercel | Hosts the website, member web app and staff console | Request logs (IP address, browser), no database access | United States / global edge | Database access, workbook or check-in content. |
| Cloudflare | DNS, network protection, bot checks (Turnstile) and file storage (R2) for avatars, media and private safety evidence | IP address, request metadata, uploaded files | United States / global edge | Database access, workbook or check-in content. |
| Resend | Sends account and notification emails | Email address, display name, email content | United States | Workbook text, check-in notes or mood, who attended a meeting, or meeting and help-request titles (those emails are generic). |
| LiveKit | Real-time audio for live meetings (not recorded) | Display name, avatar, connection metadata, live audio in transit | United States / global edge | Your email, recordings (HEAL doesn’t record), or any workbook, check-in or help-board content. |
| Expo (650 Industries) | Builds the mobile apps and relays push notifications | Push token, notification title and body (never workbook or health content) | United States | Meeting names, workbook or check-in content, or your email. |
| Stripe | Processes shop payments and Supporter plans (card, Apple Pay and Google Pay), fraud prevention, optional sales-tax calculation, receipts and the Customer Portal where supporters manage their card and invoices | Name, email, billing and shipping address, phone if given, card or wallet details (held by Stripe; HEAL never sees full card numbers), amounts, items and plan, device and IP signals for fraud checks. Stripe also uses some payment data as its own controller for fraud prevention and legal compliance | United States / global | Your recovery status, workbook or check-in content, meetings, help-board activity, or anything else from your HEAL account beyond what a payment needs. |
| Printful | Prints, packs and ships shop orders made to order, and handles misprint and damage claims | Recipient name, shipping address, phone if given, and the items ordered. No payment card details and no account or recovery information | United States, with production facilities in other countries; an order may be made at the facility nearest the delivery address | Payment card details, your HEAL account or display name, recovery status, workbook or any other member data. It receives only what an order needs. |
| Google Analytics | Optional website analytics (off with Global Privacy Control, and outside the US until you opt in), plus basic mobile-app usage. Ad storage and ad personalization are always off | Website: pseudonymous cookie id, pages viewed, device and approximate location. Apps: a random install id, app opens, sessions, screen templates, errors and performance only. Shop: completed purchases and refunds (order number, items and amounts), never your name, email or address. Never your account id, and never meeting, help-board, check-in, workbook or crisis-line activity | United States | Your account ID, email or name, anything you typed, workbook or check-in content, help-board text, or app activity that could reveal recovery (meetings joined, help posted, check-ins, crisis lines). No advertising storage. |
| Anthropic | AI model for the website chat guide (primary, when configured) | Chat messages after names, emails, phone numbers, addresses and long numbers are removed, plus the site’s own help text. No account id, IP address or cookie. Messages that look like a crisis, a medical question or an attempt to change the guide’s rules are answered by HEAL without being sent | United States | Names, emails, phone numbers, addresses or long numbers typed into the chat (removed first), messages that look like a crisis or a medical question, your IP address, cookies, or any member data from the apps. |
| OpenAI | Alternative AI model for the website chat guide (used only when Anthropic isn’t configured), and moderation screening of chat messages when configured | The same scrubbed chat messages and site help text as above. No account id, IP address or cookie | United States | Names, emails, phone numbers, addresses or long numbers typed into the chat (removed first), messages that look like a crisis or a medical question, your IP address, cookies, or any member data from the apps. |
Apple and Google deliver push notifications to phones as part of their operating systems. Expo hands notifications to them, with the same generic text. Cloudflare Turnstile’s bot check runs in a frame on our sign-up and sign-in pages.
The website chat guide. The chat on teleheal.com is answered by an AI model: Anthropic’s Claude when it’s configured, otherwise OpenAI, otherwise our own built-in answers with no AI provider at all. Before any message is kept or sent, our server removes names, email addresses, phone numbers, street addresses and long numbers. Messages that look like a crisis, a medical question, a request to pick a treatment center or an attempt to change the guide’s rules are answered by HEAL directly and never reach a model. What is sent is the scrubbed conversation and our site’s own help text, from our server, so the provider doesn’t see your IP address or cookies. The chat is open to anyone and isn’t linked to a HEAL account. We keep the open conversation only for a short time after the last message (or until you end it) and then only anonymous daily counts. When an OpenAI key is configured, OpenAI’s moderation service also screens scrubbed messages.
Stripe processes payments for the shop and for Supporter plans, and hosts the Customer Portal where supporters update their card and download invoices. Card details are entered straight into Stripe; HEAL never receives full card numbers. Stripe runs fraud checks using device and network information, and, where we switch it on, calculates sales tax from the shipping address. For fraud prevention and its own legal obligations, Stripe acts as an independent controller of some payment data under its own privacy policy, which is why it appears here and is also named in our Privacy Policy.
Printful prints, packs and ships shop orders, which are made to order. It receives the recipient’s name, shipping address, phone number (if given) and the items. It may make an order at the facility nearest the delivery address, which can be outside the US, and it hands packages to postal and courier carriers, who see what’s on the label. Printful never receives payment details or anything from your HEAL account. Members who never shop share nothing with Printful.
Google Analytics runs only with advertising storage, ad user data and ad personalization denied. On the website it follows your cookie choice and Global Privacy Control. From the mobile app, our server forwards only app opens, sessions, screen names, errors and performance timings, keyed to a random install ID, never your account ID.
02Why we use service providers#
HEAL is a small, free community. Running our own data centers, email servers or global audio network wouldn’t be safer or sensible. Instead we choose established providers for each job, and design HEAL so that each one sees as little as possible. The most sensitive information, your private writing, is sealed before any provider stores it.
03How we choose providers#
Before we use a provider, we look at:
- whether we can avoid sending them personal information, or send less;
- their security practices, including encryption, access controls, independent audits and their record on incidents;
- where they process data, and whether they’ll accept the contract terms below;
- whether their business model depends on using customer data for their own purposes. If it does, we don’t use them for member data.
We review each provider at least once a year, and whenever its service or terms change materially.
04How providers are bound#
We put a data processing agreement (DPA) in place with every provider that handles member data, before member data reaches them. The agreements require them to:
- process personal information only on our documented instructions, and only to provide their service to HEAL;
- not sell or “share” it, or use it for their own purposes, including advertising or training products;
- keep it confidential and secure, and limit access to their staff who need it;
- tell us promptly about any security incident affecting it;
- help us respond to your rights requests, including deleting your data when we ask;
- bind their own sub-processors to the same obligations;
- delete or return the data when the service ends.
These terms are designed to meet the service-provider and processor requirements of the CCPA/CPRA, Washington’s My Health My Data Act and other state laws, and the GDPR and UK GDPR. Where data leaves the EEA, UK or Switzerland, the agreements include the Standard Contractual Clauses or rely on the provider’s Data Privacy Framework certification. For Google Analytics, we rely on Google’s data processing terms for its analytics products, and for Stripe and Printful, on their data processing terms for business customers.
05What providers never get#
Workbook answers, share-link snapshots and check-in notes are encrypted with AES-256-GCM on our application server before they’re stored. The database host stores only the sealed form, and no other provider ever receives them. Notifications sent through our email and push providers never include workbook text, check-in notes, mood, diagnoses or who attended a meeting.
No provider receives member data to sell or advertise with, and no treatment center or listed provider is ever a recipient of member data.
06How we announce changes#
Before a new provider starts processing member data, or an existing one takes on a materially different role, we update this page. We aim to do this at least 30 days ahead, except where a change is urgent, for example to keep HEAL secure or running after a provider fails. In that case we update the page as soon as we can, and explain why.
Get updates by email: send a message to privacy@teleheal.com with “Subscribe: service provider updates” in the subject. We’ll email you whenever this list changes, and use your address for nothing else. Reply “Unsubscribe” at any time. Significant changes are also announced in the app.
07Objecting to a provider#
If you have a concern about a new or existing provider, email privacy@teleheal.com and tell us why. We’ll answer in writing, explain the safeguards in place, and consider whether we can address it, for example by limiting what that provider receives.
If we can’t resolve it, you can stop the processing affecting you by switching off the related feature (for example, turning off analytics in Cookie settings or turning off notifications), or by exporting and deleting your account as described in Your Data Rights & Deletion.
08Who isn’t on this list#
- People you share with, such as share-link recipients, help-board members and people in a meeting. They aren’t service providers. The Privacy Policy explains what they see.
- Postal and courier carriers that deliver shop orders. Printful chooses and hands packages to them, and they see only what’s on the shipping label.
- Authorities who serve legal process. See our law enforcement guidelines.
- Websites we link to, such as a listed provider’s site or a crisis line, which have their own policies.
- Location lookup: we work out a city-level location from IP addresses with a database file (MaxMind GeoLite2) stored on our own servers. No IP address is sent to MaxMind.
09Questions#
Questions about our providers, or a request for a copy of the relevant contract terms: privacy@teleheal.com.
HEAL is not an emergency service. In danger, call 911. In crisis, call or text 988. Treatment referrals: SAMHSA 1-800-662-4357.