Sub-processors
Last updated: 15 October 2026
Sovrnti sells sovereignty, so we publish who we depend on. This is the full list of third parties that process personal data on our behalf.
Most of it stays in France and the EU. Some of it does not. We tell you which, and why.
Where your data lives
| Sub-processor | Purpose | Location | Data reaching it |
|---|---|---|---|
| Scaleway | Application hosting, PostgreSQL, Redis, file storage | France (Paris) | All application data |
| Scaleway | Sherpa's AI models (Generative APIs) | France (Paris) | Your Sherpa prompts and context. Not stored, not used for training. |
| Bunny | Web protection and CDN for graph.sovrnti.io | Slovenia (EU) | Request metadata, including IP address |
| PostHog | Product analytics, support inbox | Germany (Frankfurt) | Usage events, account id, browser type, IP address, support messages |
| Lettermint | Transactional email and the weekly update email | Netherlands (EU) | Recipient address, message content |
| Neo4j Aura | Our product and market database, on Google Cloud | Belgium (EU) | No personal data |
| Google Workspace | Our company email, including support@sovrnti.io routing | EU and United States | Emails you send us |
| Stripe | Payments, tax and invoices | Ireland and United States | Billing identity, address, VAT number, payment method |
| Tavily | Web search for Sherpa | United States | A search query written by the model from your question |
| Mintlify | Hosts docs.sovrnti.io | United States | Visits to our public documentation |
Only if you turn on Sherpa in a chat tool
These four carry your Sherpa conversation only after you switch on "Allow my messages to leave Sovrnti" and link a channel. Sherpa runs in Slack today. We list Teams, Google Chat and email now, before they launch, so this page is never late.
| Sub-processor | Channel | Location | Data reaching it |
|---|---|---|---|
| Slack | Sherpa in Slack | United States | Your messages, Sherpa's replies, your Slack user id and name |
| Microsoft | Sherpa in Teams | United States | Your messages, Sherpa's replies, your Teams user id and name |
| Sherpa in Google Chat | United States | Your messages, Sherpa's replies, your Google Chat user id and name | |
| Resend | Sherpa by email | United States | Your emails to Sherpa and its replies |
Your chat tool already holds these messages, because they are your workspace. The new fact is that Sherpa's replies, built from our data, also travel through it.
The ones we want you to notice
PostHog's reply transport. Support tickets are stored on PostHog's EU instance. When we answer by email, the reply leaves through PostHog's mail provider, Mailgun, a US company owned by Sweden's Sinch group. We chose this over two disconnected inboxes and a slower answer to you.
Tavily, for Sherpa's web search. Sometimes Sherpa needs recent public information. It then sends a short search query to Tavily, a US company. The query carries no name, email or account id. It can carry words from your question. We have switched off Tavily's use of our queries to improve its service.
The chat channels. Slack, Teams, Google Chat and email are US services. We made them opt-in, per person, because moving your conversation to a US processor should be your choice, not ours.
Our own framing calls these Climber trade-offs: approximate the benefit, keep control, state the price. If one matters for your risk assessment, write to privacy@sovrnti.io. We will tell you exactly what a given ticket, query or conversation carried.
What never reaches a sub-processor
| Data | Why |
|---|---|
| Security vulnerability reports | They go to a person at security@sovrnti.io, never to the support inbox |
| Your visit to sovrnti.io and your use of the app | We do not record sessions, on the site or in the app |
| The text of your Sherpa questions and answers, in analytics | Our analytics record token counts and timings, never the words |
| The inputs your AI assistant sends to our tools | We keep only a one-way hash |
Not sub-processors
These handle data as independent controllers, under their own terms:
- Substack runs our newsletter.
- Your AI assistant's provider (for example Anthropic, OpenAI or Mistral AI) handles your conversation with that assistant. We never receive it.
Changes
We update this page before a new sub-processor starts processing data, not after. Adding one is a decision our founder takes, not an implementation detail.
To hear about changes, write to privacy@sovrnti.io and ask to be notified.