TrueSit subprocessors
Version 0.1, 2026-10-11. The outside providers that process personal information for TrueSit, what each does, what it receives and where. Each one is bound by a written agreement with protections at least as strong as our Data Processing Addendum. Locations and each provider’s no-training and retention terms are confirmed when the production accounts are opened (the keys round) and before this page is published.
Providers in use
| Provider | Purpose | Data it receives | Location |
|---|---|---|---|
| Supabase | Database, sign-in and file storage | All customer data: accounts, sits, audio, photos, transcripts, reports, voiceprints, exports | United States |
| Fly.io | Our processing servers: upload checks, transcription and analysis jobs, our own voice model, the public API | All customer data while it is processed | United States |
| AssemblyAI | Speech to text and who spoke when | Sit audio; returns the transcript and speaker turns | United States |
| Anthropic | AI analysis and scoring support, Quick recap, Level and Mentor, practice, drafts, the site and help assistants, the Ops agent for support | Transcripts and sit details, Mentor memory, organization patterns, support tickets; public help articles | United States |
| Cartesia | Voices read aloud in practice and on request | The text to be spoken | United States |
| Vercel | Hosting the web dashboard and the website | Page requests and the signed-in session; dashboard pages carry customer data | United States |
| Cloudflare (R2) | Nightly backup copy of recordings | Encrypted recordings and photos | United States |
| Resend | Service email (digests, sit ready, export links, deletion notices, support replies) and incoming support email | Names, email addresses, message content | United States |
| Expo | Delivering push notifications | Push tokens and notification text (for example a sit’s time and street) | United States |
| Apple | Push notifications, Sign in with Apple, App Store purchases | Push tokens and notification text, sign-in identifiers, purchase status | United States |
| Push notifications, Sign in with Google, Google Play purchases, maps on Android | Push tokens and notification text, sign-in identifiers, purchase status, map area viewed | United States | |
| Stripe | Billing for organization plans and Solo web purchases | Billing contact, payment details (kept by Stripe), invoices | United States |
| RevenueCat | Subscription status for Solo purchases in the app stores | App user id, store receipts | United States |
| PostHog | Website analytics, only after a visitor says yes | Random visitor id, pages viewed | United States |
| MapTiler | Map tiles for the visits and territory maps | The map area being viewed and the requesting IP address; no customer records | Switzerland, served from a global network |
| Twilio or Meta (WhatsApp) | Alerts about support requests to TrueSit’s platform owner, by WhatsApp or SMS (one of the two is chosen at launch) | The requester’s name, organization, role and a summary of the request | United States; Meta also processes outside the United States |
Not in use
Our code can also work with these providers. None receives data today; each is added to the table above, with the notice below, before any use: Groq and Deepgram (speech to text), pyannoteAI (who spoke when), Modal (hosting our own speech models).
Not our subprocessors
When an organization connects its own CRM, API client or webhook endpoint, data goes there on the organization’s instruction and is under its control. Those providers are the organization’s, not ours.
Changes
We email every organization admin at least 30 days before adding or replacing a subprocessor, with the provider, purpose, data and location. An organization may object within that period, as the Data Processing Addendum explains. If we must replace a provider at once (a failure or a security threat), we notify as soon as we can. Anyone else may ask for change notices at privacy@truesit.ai.
Last changed: set at launch.