Revogent is an AI-powered revenue platform for logistics and freight sales teams. Because the product connects to your team's mailboxes and calendars, we hold ourselves to a simple standard: request the minimum access required, act only as the individual signed-in user, and keep a human in the loop on everything that leaves the building.
This Trust Center documents how the platform actually works at a technical level. If your review needs something that is not covered here, email us and we will get you a direct answer from the engineering team.
Quick answers for IT reviewers
- Email sending: Revogent never sends outreach email from its own infrastructure. Every message is sent from the individual user's own Microsoft 365 or Google Workspace mailbox through the Microsoft Graph and Gmail APIs, so SPF, DKIM, and DMARC evaluate exactly as they do for mail sent from Outlook or Gmail.
- Microsoft 365: No app registration is required in your tenant. Revogent is a multi-tenant Microsoft Entra application that uses delegated, per-user permissions only, and access can be restricted to specific individuals with standard Entra controls.
- Single sign-on: Enterprise SSO over SAML and OIDC is supported through our identity layer, including Okta Workforce and Microsoft Entra ID. Under SSO, your identity provider's MFA and session policies apply to Revogent sign-ins.
- Outlook add-in: None. There is no Outlook or Office add-in to deploy or maintain. All mailbox integration happens server-side through Microsoft Graph.
- AI outreach: AI-drafted messages require explicit human approval before anything sends, and platform-wide kill switches can pause all outbound communication instantly.
Security highlights
- Encryption: All traffic is encrypted in transit with TLS. OAuth access and refresh tokens are encrypted at rest with AES-256-GCM using application-managed keys, and API keys are stored only as hashes.
- Access control: A three-tier role model (internal staff, customer admin, customer rep) is enforced server-side on every backend function. Frontend role claims are never trusted.
- Tenant isolation: Every access to organization-owned data verifies record ownership on the server. Automated authorization scanners run in CI and require zero violations before code can merge.
- Audit logging: Security-relevant events, including sign-ins, permission denials, role changes, OAuth connections, data exports and deletions, and admin access, are written to a structured, organization-scoped audit log.
- Rate limiting: Three enforcement layers, from IP-based limits at the edge to per-endpoint and per-mutation limits in the backend.
- Webhook integrity: All inbound webhooks are signature-verified with HMAC, timestamp-checked, and protected by idempotency reservations.
- Human-in-the-loop AI: Outbound AI content requires per-message human approval, with platform-wide kill switches for outbound communications and AI generation.
Subprocessors
Revogent uses the following infrastructure and service providers to deliver the platform. Each is engaged for a specific purpose and receives only the data required for that purpose.
| Provider | Purpose | Data involved |
|---|---|---|
| Vercel | Application hosting and content delivery | Application traffic and request logs |
| Convex | Primary database and backend functions | CRM records, synced email and calendar data, encrypted OAuth tokens |
| Clerk | Authentication and identity management | User identities (name, email), sessions, organization membership |
| Upstash | Rate-limiting infrastructure | Request metadata such as IP addresses and counters |
| Anthropic | AI drafting and analysis | Prompt context from your workspace |
| OpenAI | AI features, including realtime voice | Prompt context and live voice audio |
| AI models (Gemini) | Prompt context from your workspace | |
| MiniMax | Text-to-speech voice synthesis | Script text to be synthesized |
| LiveKit | Realtime voice transport | Live audio streams during voice sessions |
| Apollo.io | B2B contact enrichment | Business contact identifiers (names, companies, work emails) |
| Hunter.io | Email discovery and verification | Business contact identifiers |
| ZoomInfo | B2B contact enrichment | Business contact identifiers |
Data handling and deletion
Revogent stores the CRM data your team enters or imports, email messages synced from connected mailboxes (including message bodies, to power threading, reply detection, and CRM timelines), calendar events, and encrypted OAuth tokens for connected integrations.
- Disconnecting an integration: removes its stored OAuth tokens and stops all sync for that account.
- Deletion and export requests: are honored per our privacy policy, and each export or deletion is recorded as an auditable event.
- Offboarding: when an organization leaves Revogent, workspace data is deleted on request.
Report a security concern
If you believe you have found a security issue in Revogent, we want to hear about it directly and quickly. Email us with enough detail to reproduce the issue and we will respond promptly. We ask reporters to give us reasonable time to remediate before any public disclosure.