Security and compliance

Enforced in code, not in a policy.

Outbound reaches other people's inboxes and phones, so the rules are built into the code rather than left to good intentions. Here is exactly what runs today, and what does not exist yet.

Before every action

Six checks run before anything sends.

Not a nightly job, not a review queue. A function that runs before every single email and every single call, and records its verdict either way.

Suppression check

Global and account level, inside the same transaction as the send

Voice consent

Published business lines by default. Mobile numbers require recorded consent

Calling hours

Computed from the prospect's own timezone, not yours

Attempt caps

Four call attempts maximum, spread across different parts of the day

AI disclosure

Stated in the opening line of every call, every time

Opt out

Honored immediately, permanently, and across every channel

On AI voice specifically. The FCC has held that calls using AI generated voices fall under the same consent rules as prerecorded robocalls. Revio therefore targets published business lines by default. Calling a mobile number requires that you record prior express written consent for that contact, with a source and a timestamp, and the system will not place the call without it. We build no feature whose purpose is evading spam filters, caller identification, or consent requirements.

Platform controls

How your data is held.

Tenant isolation

Every customer record carries a workspace id, and the tables that hold customer data have Postgres row level security policies. A query without the right workspace returns nothing, so one customer can never see another's data.

Encryption

Everything travels over TLS. Mailbox and CRM logins are encrypted before they are stored, with a key kept outside the database, and they are never written to logs or shown back in the app.

Access control

Five roles: owner, admin, manager, rep and viewer. Each action checks the role before it runs, so a viewer can look but cannot send, connect or export.

Audit logging

Every send, call, setting change and export writes an audit record with who did it, what it touched and when. The app only ever adds to this log; it never edits or deletes it.

Recordings and transcripts

Call recordings stay with the calling provider and are linked from the call record; transcripts are stored with the conversation. Export or delete them with the rest of your data.

Webhooks

Billing webhooks are signed and checked with HMAC before anything is changed. Call results arrive on a secret address, and public tools like the free audit are rate limited.

Current status

What exists today, and what does not.

Security pages usually list aspirations as if they were facts. This one separates them, because you are going to ask in the security review anyway.

Row level tenant isolationIn place
Encryption in transit and at restIn place
Append-only audit logIn place
Data export and deletionIn place
SSO and SCIMEnterprise, on request
SOC 2 Type IINot yet. Planned once we are past our first cohort
Penetration testScheduled before general availability

Security review before the demo?

That is a reasonable order to do it in. Send us your questionnaire and we will answer it directly rather than pointing you at a trust badge.