Subprocessors
Effective: September 8, 2026
Verbato is a service operated by Versa Studio LLC, a Wyoming limited liability company. To run it we rely on other companies — to store your files, to turn speech into text, to take payments, to send email. Where one of those companies handles personal data on our behalf, it is a subprocessor, and it is listed on this page.
This list is public and it is complete. Every service named here is one we actually use; every service we use that reaches personal data is named here. It is a factual disclosure of who is involved in delivering the product — not a certification, and not a claim about any of these companies.
Infrastructure
These services are involved in running Verbato for every account. Your recordings pass through the storage, transcription and generation services below as a matter of course.
| Service | What it does | Data it reaches | Processing location |
|---|---|---|---|
| Microsoft Azure — Container Apps | Runs the Verbato API and the background workers that process your recordings. | All application data, in memory while it is being processed. | United States (East US) |
| Microsoft Azure — Database for PostgreSQL | The application database. | Account records, project metadata, transcripts, generated documents, and channel identities you have linked. | Canada (Canada Central) |
| Microsoft Azure — AI Speech | Speech-to-text transcription and speaker separation. This is the default engine for recordings processed by Verbato. | The audio and video content of your recordings. | United States (East US) |
| Microsoft Azure — OpenAI Service | Generates the documents Verbato derives from a transcript. | Transcript text and the instructions attached to your project. | United States (East US) |
| Microsoft Azure Monitor | Backend logging, tracing and alerting, so we can see when something breaks. | Request metadata and error diagnostics, including account identifiers that appear in logs. | United States (East US) |
| Cloudflare R2 | Stores the audio and video you upload, and the files Verbato produces from them. | Audio and video files, transcript and document exports. | Eastern North America |
| Cloudflare DNS | Domain name resolution for verbato.io. | Connection metadata, including IP address. | Global network |
| Vercel | Hosts and serves the Verbato web application. | Request logs and IP addresses. | Global edge network |
| Clerk | Account sign-in, sign-up and session management. | Email address, name, and authentication and session data. | United States |
| Stripe | Subscription payments, top-up purchases and billing records. | Email address, billing details, and subscription and payment records. Card numbers are collected by Stripe directly and never reach Verbato. | United States |
| Resend | Sends transactional email, and receives audio sent to the Verbato email intake address. | Email address, email content, and any attachments you send in. | United States |
| PostHog | Product analytics and browser error reporting. | Usage events and device information. Accounts that switch analytics off are excluded entirely. | United States |
| Telegram (operations) | Delivers operational alerts to the Verbato team — for example, that a payment succeeded or a job failed. | Alert context, which can include an account email address. | Global |
Reached only in specific circumstances
These services are not part of the ordinary path. A channel receives your data only if you link it to your account. A fallback transcription or generation service receives your data only when the default one is unavailable.
| Service | What it does | Data it reaches | Processing location |
|---|---|---|---|
| AssemblyAI | Transcription with speaker separation, used when the default engine is unavailable. | The audio and video content of your recordings. | United States |
| OpenAI | Transcription where word-level timing is required, and document generation when the default generation service is unavailable. | Audio content, or transcript text, depending on which task it serves. | United States |
| Telegram (Verbato bot) | Sends recordings to Verbato and delivers transcripts back — only if you link the channel to your account. | Your Telegram user ID, the audio you send, and the transcripts and documents returned to you. | Global |
| WhatsApp (Meta) Not currently active | Would send recordings to Verbato and deliver transcripts back, in the same way as the Telegram channel. | No data reaches Meta today. When the channel is activated this page is updated before it carries any traffic. | — |
What is not on this list
When you paste a podcast link, Verbato asks that platform for the episode's public audio file. Those services receive a link or a show name and nothing about you, so they are not subprocessors and are not listed here.
Payment card numbers are collected by Stripe directly and never reach Verbato, so there is no other party in that path to name.
How this list changes
Adding, replacing or removing a subprocessor updates this page and its effective date at the same time. The date at the top changes only when the list changes, so a date that has not moved means the list has not moved.
We keep this list in one place precisely so it cannot drift. If you rely on it and would like to be told when it changes, write to privacy@verbato.io.
Data Processing Agreement
If you are evaluating Verbato for an organisation and need a DPA, ask for one at legal@verbato.io. It names this page as the authoritative subprocessor list rather than freezing a copy that would drift.
Related
What we collect, how long we keep it, and the rights you have over it are covered in the Privacy Policy. The terms governing your use of Verbato are in the Terms of Service.