Sub-processors
Last updated: August 2026
To run Verso we rely on the third parties below. Each receives only the data needed for its function. This list may change as the product evolves; we will keep it current.
| Sub-processor | Purpose | Data processed | Region |
|---|---|---|---|
| Anthropic (Claude) | Generating drafts, clarifying questions, research and grammar; sorting messages sent through the contact form or in-app feedback | Your prompts and the relevant knowledge-base context for a request, or the text of a contact/feedback message | United States |
| Voyage AI | Embeddings that make your knowledge base searchable | Text from your knowledge documents and queries | United States |
| OpenAI (optional) | Alternative embeddings provider, if configured | Text from your knowledge documents and queries | United States |
| ElevenLabs | Speech to text for dictation, and the live voice call (speech recognition, turn-taking, and the spoken reply) | The audio you dictate or speak during a call, the resulting transcript, and the reply spoken back to you, which may quote your knowledge base. Audio is streamed for processing and is not stored by Verso. Dictation also sends a short list of recurring technical terms taken from your own uploaded documents (for example product names or acronyms), so that speech recognition spells the words you actually use correctly. | United States |
| Stripe | Payments and subscription billing | Billing identifiers and payment details (handled by Stripe) | United States |
| Resend | Transactional email (for example, team invitations) | Recipient email address and message content | United States |
| Sentry | Error monitoring, so we can detect and fix faults quickly | Diagnostic error reports and technical request context (no knowledge-base content) | European Union |
| Publishing a post when you choose to publish it, and importing your name and profile photo if you sign in with LinkedIn | The post content you publish, and the profile details LinkedIn returns. Nothing is sent to LinkedIn unless you connect the account and press publish. | United States | |
| Sign-in providers (Google, Microsoft, Apple) | Signing you in, only if you choose social sign-in instead of an email and password | Your name, email address and account identifier at that provider | United States |
| Vercel | Hosting and running the application, plus cookieless Web Analytics (page views and referrers, no cookies and no cross-site tracking) | Every request to the site, and the technical metadata that comes with it such as IP address and browser | United States / EU |
| Neon (Postgres) | The database that stores your account and your content | All account and content data; sensitive fields, including knowledge-base content and connected-account tokens, are encrypted before they reach the database | United States |
Embeddings provider depends on configuration; a self-hosted local model can be used instead, in which case no embedding data leaves our infrastructure.
One further recipient is worth naming even though it is not our sub-processor. When you dictate, we use your browser’s built-in speech recognition to show words as you speak. In most browsers that feature is not on-device: Chrome sends the audio to Google, and Edge sends it to Microsoft, under that vendor’s own privacy policy rather than a contract with us. We never receive that audio ourselves. If you would rather your speech did not reach your browser vendor, type instead of dictating.
For more on how we handle your data, see our Privacy Policy.