Trust
The vendors behind Rev. Every one, disclosed.
A subprocessor is a third party that processes your data on our behalf. This is the current list, grouped by what each does. We keep it short on purpose.
AI & inference
Model providers that read transcripts and prompts to power Rev. Under our agreements, none of them train their models on your data.
| Vendor | Purpose | Data it receives | Region |
|---|---|---|---|
| Anthropic | Primary language model for Rev's reasoning and analysis | Call transcripts, extracted call intelligence, prompt context | United States |
| OpenAI | Audio transcription and vector embeddings for search | Call audio recordings, transcript text | United States |
| OpenRouter | Model routing to inference providers | Call transcripts, extracted call intelligence, prompts | United States |
Infrastructure & hosting
Where the product runs and where your data lives at rest.
| Vendor | Purpose | Data it receives | Region |
|---|---|---|---|
| Render | API, background workers, and primary PostgreSQL database | All application data at rest, including transcripts and call intelligence | United States |
| Modal | Per-workspace Rev agent runtime | Runtime credentials that grant access to your workspace data | United States |
| Amazon Web Services / Cloudflare | Object storage for call audio recordings | Call audio recordings | United States |
| Vercel | Web application and marketing site hosting | Edge request metadata; renders the authenticated app in transit | United States |
Integrations & data sources
Vendors you connect so Rev can ingest your calls and CRM, or act on your behalf.
| Vendor | Purpose | Data it receives | Region |
|---|---|---|---|
| Salesforce | CRM records mirrored into Rev when you connect it | CRM contacts and opportunities you choose to sync | United States |
| CallRail, Dialpad, Zoom Phone, Five9 | Telephony sources for calls, recordings, and caller details | Call recordings, call metadata, caller phone and name | United States |
| Composio | Tool bridge that connects Rev to the apps you authorize | Your OAuth credentials for connected tools | United States |
| Slack, Telegram | Chat surfaces where Rev delivers summaries and intelligence | Call intelligence, summaries, and quotes you route to a channel | United States (Slack); international (Telegram) |
Account & operations
Vendors handling your account, billing, and notifications — not raw call content.
| Vendor | Purpose | Data it receives | Region |
|---|---|---|---|
| Resend | Transactional email (verification, resets, notifications) | Email address and message content | United States |
| Stripe | Billing and payments | Billing name and email (card data held in Stripe's vault) | United States |
| Sign-in (OAuth) identity | OAuth identity assertion (email, account identifier) | United States | |
| Sentry | Error monitoring (configured with PII scrubbing before use) | Error telemetry that may incidentally include PII in tracebacks | United States |
No-training commitment
The AI providers above read your transcripts to extract structure. Under our API agreements, they do not train their models on your data. Your call history makes yourRev smarter — it is never pooled, resold, or used to improve anyone else's product. More on how the system protects your data is on our security page.
Changes and notice
Before a new subprocessor begins processing your data — especially any new AI provider or any new recipient of call content — we update this list and give notice consistent with your agreement, so you have the chance to review. Questions about a specific vendor, or a due-diligence request? Email security@revenuerep.ai.