Security

SOC 2 Type II, the BAA,and who processes the data.

HIPAA compliant, with the BAA e-signed in the app before any patient data moves. One door for the current report and the vendor list.

Trust Center
HIPAASOC 2 Type IIGDPRBAA
In the path

Governance that actually runs.

TCPA and DNC
The calling window and the DNC list fail closed on dispatch.
Evals
An outbound program passes safety evals before it can run.
Live edits
A live edit cannot strip disclosure or TCPA rules.
Encryption
Encrypted at rest with AWS KMS. The region is us-east-2, Ohio.
Permissions
Permissions follow the role. Finance sees payroll. Population health sees the gap list.
MFA
MFA is enforced per org. Sharing defaults to Only you.
Audit
Consent and policy changes are logged for seven years, and every agent action that touches PHI is logged with who, what, and when.
Connector writes
A write to a connected system can require approval before it runs.
Training
Your data never trains anyone else's model.
Governance

Every action runs under TRACE.

Tiered Review, Audit and Controlled Execution. It runs on the server on every call, and the model cannot bypass it.

THE PATH OF ONE ACTION
  1. 01MODEL
    The coworker asks to act.
  2. 02SERVER
    TRACE checks the call.
  3. 03YOU
    The level decides who acts.
  4. 04LOG
    The record is written.
FOUR APPROVAL LEVELS
  1. LEVEL 1
    Auto-run
    WHO ACTS
    Rivvi runs it.
  2. LEVEL 2
    Draft then you approve
    WHO ACTS
    You approve it in the conversation.
  3. LEVEL 3
    Propose only
    WHO ACTS
    A person makes the change.
  4. LEVEL 4
    Never runs
    WHO ACTS
    No one. The tool is off.
01
You can only tighten
An organization can raise a level. Nothing can lower one.
02
Approval binds to the action
What you approved is exactly what runs.
03
PHI clearance on every call
Tool and user must match, or it fails closed.
04
Signed approval for connector writes
A changed payload fails verification.
05
Audit without content
Every call is logged. Prompts and responses are not.
Guardrails

It does not diagnose, prescribe,or override clinical judgment.

ScopeHANDS OFF TO A CLINICIAN
The agent stays inside the job you gave it. It does not give medical advice, and it hands off when a question needs a clinician.
CrisisESCALATES AT ONCE
Distress and crisis signals escalate right away to the person you name, not at the end of a script.
AccessROLE BASED
Who can see and do what is role-based and scoped to your organization.
RecordWRITTEN AUTOMATICALLY
Who touched PHI is written to the log automatically.
Data

PHI stays inside HIPAA-eligible infrastructure.

Protected health information never leaves that boundary and never trains third-party models. Your data is scoped to your organization, and every read and write is checked against that scope.

AWS KMS
Encryption at rest
7 years
Consent and policy change log
Only you
Default share setting
k-anon
k-anonymity on by default

TCPA consent and opt-out run on every outreach path. Quiet hours follow your policy and the patient's locale. GDPR applies where we process personal data of people in the EEA. Status: rivviai.instatus.com.

Questions

Anything else: hello@rivvi.ai

It is e-signed in the app before any patient data moves. You can open the workspace first.

Access follows the role. MFA is enforced per org, and sharing defaults to Only you.

In us-east-2, Ohio, encrypted at rest with AWS KMS.

No. Your data never trains anyone else's model.

Try it on your own data today.

Free to start. Most teams are using it the same day.