Built to be trusted with conversations, orders, and revenue.
What we can verify today — plainly stated, without a certification we don't hold.
Tenant isolation
Every business's data is isolated at the database layer. One business's conversations, leads, and knowledge base are never visible to another business.
We never call your customers
Revorex.ai never places outbound phone calls or SMS to your customers through any API — no auto-dialer, no robocall, no cold outreach — and never pulls their phone number via an API for any purpose beyond the conversation they started. Every interaction happens inside the chat conversation your customer started, on your terms.
Production data stays in production
Production data never leaves the production environment — no exceptions. Staging and sandbox environments use synthetic or anonymized data only, so a bug never gets tested against a real customer's data.
Credentials and integrations
Payment keys and third-party integration tokens you connect are encrypted at rest. They are never exposed in the admin panel or in any API response, including to Revorex.ai staff — support can confirm a credential exists and is valid, never see its value.
Admin access controls
Access to the Revorex.ai admin console is role-based, requires two-factor authentication, can be restricted by IP allowlist, and every sensitive admin action is written to an audit log.
Ecommerce settlement protection
For ecommerce sales made via AI handoff, payout is held until the customer's return window expires before it's released — protecting both sides of the transaction from a same-day clawback.
Availability and enterprise terms
We don't publish a general uptime guarantee today. Enterprise plans can include negotiated SLA and dedicated-capacity terms — talk to sales about your availability requirements.
Compliance stance
We don't hold or claim SOC 2, HIPAA, or other regulatory certifications today. If your business operates under a specific compliance requirement — healthcare, government, or otherwise — talk to sales before onboarding so we can give you an honest roadmap answer rather than a blanket promise.
Security questionnaires
Evaluating Revorex.ai as part of a procurement or security review? Email security@revorex.ai with your questionnaire and we'll respond with reviewed, accurate answers.
Why Revorex.ai connects to your business tools.
Every integration has a defined operational purpose. You choose what to connect, Revorex.ai requests only the access needed for that workflow, and credentials stay encrypted.
Connect the authorized business mailbox that your team uses for customer communication. The connection currently verifies and displays the selected Gmail account while the read-only workflow completes Google review.
How access is used
Revorex.ai does not send, modify, or delete Gmail messages. During the current pre-launch review, it does not read, import, analyze, or store message content.
Connect a Microsoft 365 or Outlook mailbox so an authorized workspace can use business-email context in customer-support workflows.
How access is used
The current connection verifies and displays the selected Microsoft account. Revorex.ai does not send, modify, delete, or store Outlook messages through this integration today.
Connect the store that fulfills customer orders so the AI employee can use live catalog, availability, order, and tracking context during a conversation.
How access is used
Access is limited to the connected store and is used for product lookup, order support, tracking, and enabled order-placement workflows. Store credentials are never exposed to customers or dashboard users.
Integration tokens are encrypted at rest, used only on the server, and removed when an administrator disconnects the integration. Read how Revorex.ai handles Google user data.
Start the conversation before they leave.
Give every visitor an immediate path to an answer, appointment, qualified lead, or human handoff.
