Subprocessors
Last updated: July 23, 2026
These are the services that process data on our behalf to run SoleOS. The list is deliberately short, and none of them use your data to train models. When it changes, this page changes first.
| Service | Purpose | Data it receives | Region |
|---|---|---|---|
| Supabase | Database, authentication, encrypted credential storage (Vault), realtime, webhook gateway | All application data, including encrypted provider credentials | United States |
| Vercel | Hosting, edge network, scheduled jobs | Request data, rendered pages | United States / global edge |
| Stripe | SoleOS's own billing | Billing identity; payment details are held by Stripe, never by us | United States |
| Resend | Transactional email — digests, notifications, sign-in links | Email address, metric summaries in email bodies | United States |
| Anthropic | AI insight generation | Aggregated project metrics and project names only — never credentials, raw events, or your customers' identities. API data is not used to train their models | United States |
| Sentry | Error monitoring | Error traces, with personally-identifying data collection disabled | United States / EU |
| Telegram | Optional notification channel — only if you link a chat | Chat id, notification text (metric summaries) | Global |
Connected providers are different
Stripe (as your revenue source), RevenueCat, PostHog, Google (Analytics, Search Console, Play, Firebase), Apple, Microsoft Bing, and Supabase-as-a-source are providers you authorize directly — you hold your own agreement with each, and SoleOS reads from them with the scopes documented on the Connectors page. They process your data as your providers, not as our subprocessors.
Questions or objections
Email support@soleos.app. For the broader picture: Privacy Policy · Security · How SoleOS uses AI.