Privacy Policy
Last updated: 15 October 2026
The short version
We collect what we need to run Sovrnti and Sherpa, and little else.
Your data lives in France and the EU by default. A few services we use are US-owned. We name every one of them below and on our sub-processor page.
We do not sell your data. We do not train AI models on it. You can see it, export it and delete it.
Who we are
SAS Sovrnti, 16 place des Quinconces, 33000 Bordeaux, France, is the controller of the personal data described here.
Write to privacy@sovrnti.io for anything about your data. We answer within 7 days and act within 30 days.
What this policy covers
- sovrnti.io, our website.
- The Sovrnti app at app.sovrnti.io, including Sherpa, our AI analyst for Sovrnti Starter and Sovrnti Pro subscribers.
- The Sovrnti MCP server and REST API at graph.sovrnti.io. AI assistants such as Claude, ChatGPT and Le Chat connect to them.
- Sherpa in chat tools: Slack today. Microsoft Teams, Google Chat and email when each one launches.
- Support, by email, chat widget or contact form.
Our documentation at docs.sovrnti.io and our newsletter on Substack are covered in "Who receives your data".
What we collect, and why
| What | From whom | Why | Legal basis |
|---|---|---|---|
| Name, email, username, password (hashed), passkeys, two-factor secrets, language, country, industry | you, when you create an account | run your account and sign you in | contract |
| IP address and browser type for each sign-in session | your browser | keep you signed in, detect misuse | contract, legitimate interest (security) |
| Organization name, logo, members, roles, invitee emails | your organization's admins | run team accounts | contract |
| Records of each tool call: who called it, which tool, when, the result status, and a one-way hash of the inputs | the Sovrnti app, the API, or your AI assistant | billing, audit and abuse prevention | contract, legitimate interest |
| Product usage events: which features you use, your account and organization id, browser type, and a shortened IP address. The full IP address when we refuse a request. | the app and the API | understand and improve the product | legitimate interest |
| Your Sherpa conversations, and what Sherpa remembers about your context (organization, role, vendors, decisions) | you, when you use Sherpa | answer your questions and remember context between them | contract |
| Billing name, email, address, VAT number, payment method | you, at checkout | take payment, issue invoices, meet tax law | contract, legal obligation |
| Your name, email and message | you, when you contact support | answer you | legitimate interest |
| Your name and email. The changelog link in the email carries a campaign tag, so we can count visits that come from it. The email has no tracking pixel. | your account | send you one email a week on what changed in the product: New, Improved, Fixed | legitimate interest. It is on by default, and you can stop it in one click |
| Pages viewed, clicks, technical errors and IP address | your browser on sovrnti.io | understand how visitors use the site | consent |
| Name, email, role, country and company size | you, when you join the waitlist | offer you early access | consent |
| Name, email, role, LinkedIn profile URL, your message, and the corrections you submit | vendor employees, through sovrnti.io/builders | let vendors correct data about their products | legitimate interest |
We do not collect special categories of data. Please do not put them in Sherpa or in a support message.
Sherpa, and how AI processes your data
Where the model runs
Sherpa's language models run on Scaleway Generative APIs, in Paris, France. Today they are open-weight models, such as Mistral Small and Qwen. Scaleway does not store your prompts or answers, does not use them for training, and does not share them with model makers.
Sherpa uses a shared Scaleway endpoint. No other customer can see your data, and Scaleway applies zero data retention to it.
Web search: the one to notice
When a question needs recent information, Sherpa can search the web. It sends a short search query, written by the model from your question, to Tavily, a US company. The query does not include your name, email or account id. It may include words from your question. We have told Tavily not to use our queries to improve its service.
What we never do
- We never train or fine-tune AI models on your data. That includes data from Slack, Microsoft Teams and Google Workspace.
- We never sell or rent your data.
- We never use your data for advertising.
Who at Sovrnti reads conversations
Our founder reads a sample of Sherpa web conversations to check answer quality. The reviewer works for Sovrnti and is bound by confidentiality. You can object to this review at any time by writing to privacy@sovrnti.io. We will then exclude your conversations.
No one at Sovrnti reads your Slack, Teams, Google Chat or email conversations with Sherpa. The only exceptions are when you ask us to, to investigate abuse or a security incident, or when the law requires it.
Sherpa in Slack, Teams, Google Chat and email
Today Sherpa runs in Slack. Microsoft Teams, Google Chat and email follow, and this section applies to each one from the day it launches.
These channels are off until you turn them on. In Account settings, Sherpa everywhere, you switch on "Allow my messages to leave Sovrnti". Then you link a channel. We show you which company carries the messages before you link it.
When you use Sherpa in a channel:
- Your messages and Sherpa's replies pass through that channel's provider: Slack, Microsoft, Google, or Resend for email. All four are US companies.
- When someone mentions Sherpa in a thread, Sherpa reads up to 59 earlier messages in that thread to understand the question. Those can include messages from colleagues. Mention Sherpa only in threads where that is appropriate.
- We store your channel user id, display name and the link to your Sovrnti account. Sherpa remembers the conversation in our database in France, as it does on the web.
- Turning the switch off deletes every channel link at once.
Your workspace administrator controls whether Sherpa can be installed in your workspace. The channel provider's own privacy policy applies to messages inside their service.
Google Workspace data. Sovrnti's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google Workspace data to develop, improve or train generalized AI or machine-learning models.
Slack data. We do not use Slack data to train any AI model. Sherpa's model runs on Scaleway in Paris, with zero data retention by Scaleway, as described above.
The MCP server, the API, and your AI assistant
When you connect Sovrnti to Claude, ChatGPT, Le Chat or another AI assistant, that assistant calls our tools on your behalf. It uses a token you approved when you connected it.
What we receive from your AI assistant: the tool's name, its inputs and your token. We also see the assistant's software name and the connection's IP address.
What we do not receive: your conversation with the assistant. We see only what the assistant sends to our tools.
What we keep: a record of each call (who, which tool, when, the result) and a one-way hash of the inputs. We do not store the inputs themselves. A hash lets us match a repeated call without reading it.
What our tools return: data about markets, products, vendors, countries and regulations. Our tools never return personal data.
Your assistant then uses our results inside its own conversation. Its provider (for example Anthropic, OpenAI or Mistral AI) handles that conversation under its own privacy policy. We have no access to it.
When you connect a new assistant, it registers itself with us. We store its name and return address, and we log the IP address of each registration for 30 days to stop abuse.
Who receives your data
We use the providers below to run Sovrnti. Each acts on our instructions under a data processing agreement. The full list, with what reaches each one, is on our sub-processor page.
| Category | Providers | Location |
|---|---|---|
| Hosting, database, storage, AI models | Scaleway | France |
| Web protection for the API | Bunny | Slovenia |
| Product analytics, support inbox | PostHog | Germany (Frankfurt) |
| Transactional email and the weekly update email | Lettermint | Netherlands |
| Product and market data (no personal data) | Neo4j Aura, on Google Cloud | Belgium |
| Payments | Stripe | Ireland and the United States |
| Web search for Sherpa | Tavily | United States |
| Sherpa chat channels, only if you opt in | Slack, Microsoft, Google, Resend | United States |
| Support email delivery | Mailgun, a US company owned by Sweden's Sinch group (PostHog's email provider) | outside the EU |
| Our own email, including support@sovrnti.io | Google Workspace | European Union and the United States |
| Documentation website | Mintlify | United States |
Two parties act as separate controllers, not as our processors:
- Substack runs our newsletter. If you subscribe, Substack's privacy policy applies.
- Your AI assistant's provider, as described above.
We may disclose data when the law requires it, for example a valid court order. We will tell you first, unless the law forbids it.
International transfers
Data sent to US providers leaves the EU. We rely on the EU-US Data Privacy Framework where the provider is certified, and on the European Commission's Standard Contractual Clauses otherwise.
US law can let US authorities request data from US companies. That is the trade-off we accept for these specific services. We tell you about it here so you can decide. The chat channels are opt-in for exactly this reason.
How long we keep it
| Data | How long |
|---|---|
| Account and organization data | until you delete your account or organization |
| A sign-in session | up to 30 days |
| Tool-call records (audit) | 12 months |
| IP addresses logged for rate limits | 30 days |
| Sherpa conversations | until you delete them, or your account |
| What Sherpa remembers about you | until you delete your account |
| Product usage events | up to 7 years, our analytics provider's standard period. We delete them sooner on request, and when we close your account. |
| Support conversations | until you ask us to delete them |
| Billing records and the credit ledger | 10 years, as French accounting law requires |
| Backups | up to 7 days after deletion |
Your rights and controls
You have the right to access, correct, delete, export and restrict your data, and to object to its use. Where we rely on consent, you can withdraw it at any time.
| You want to | How |
|---|---|
| Delete your account | Account settings, General, Delete account. This removes your account, your Sherpa conversations and memory, and your channel links. |
| Delete one conversation | Delete it in Sherpa. It leaves your history at once. Sherpa's memory of it goes when you delete your account. |
| Disconnect an AI assistant | Graph, Connected apps. Its tokens and permissions are deleted. |
| Stop the chat channels | Account settings, Sherpa everywhere: switch off "Allow my messages to leave Sovrnti". |
| Stop the weekly update email | "Unsubscribe" at the bottom of any edition, in one click. Or switch it off in your notification settings. |
| Change cookie choices | "Cookie settings" in the footer of sovrnti.io. |
| Export your data | Write to privacy@sovrnti.io. We send a JSON file within 30 days. |
| Anything else | Write to privacy@sovrnti.io. |
Some records stay after you delete your account. Billing records and the credit ledger stay 10 years, by law. Tool-call records stay until they reach 12 months. These carry an internal id, not your name or email.
If you are not satisfied with our answer, you can complain to your data protection authority. In France, that is the CNIL: www.cnil.fr.
Cookies and similar storage
| Name | Where | Purpose | Needs your consent? |
|---|---|---|---|
| Session cookie | app.sovrnti.io and its sign-in pages | keeps you signed in | no, strictly necessary |
NEXT_LOCALE | all our sites | remembers your language | no |
consent | sovrnti.io | remembers your cookie choice, 30 days | no |
sidebar-collapsed | app.sovrnti.io | remembers your layout | no |
ph_…_posthog cookie and local storage | sovrnti.io | analytics | yes, set only after you accept |
ph_…_posthog and widgetSessionId local storage | app.sovrnti.io | the support chat widget | no, it runs the support you asked for |
On sovrnti.io, nothing for analytics loads until you click Accept. We do not record your visit.
Inside the app, we do not record sessions and do not track clicks in your browser. Usage events are sent from our servers.
We use no advertising cookies and no cross-site tracking.
Security
Data is encrypted in transit with HTTPS. Tokens that AI assistants use expire after 5 minutes. Passwords are hashed. Access to production is limited to the people who run it.
Report a vulnerability to security@sovrnti.io. Security reports go to a person, never to our support tools.
Children
Sovrnti is a professional service for people aged 18 and over. We do not knowingly collect children's data. If you think we have, write to privacy@sovrnti.io and we will delete it.
Changes to this policy
We change this page before a change in how we use data takes effect. For a significant change, we email account holders first. The date at the top tells you when it last changed.
Contact
- Privacy: privacy@sovrnti.io
- Support: support@sovrnti.io
- Security: security@sovrnti.io
- Everything else: hello@sovrnti.io
SAS Sovrnti, 16 place des Quinconces, 33000 Bordeaux, France.