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 CenterIn the path
Governance that actually runs.
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
- 01MODELThe coworker asks to act.
- 02SERVERTRACE checks the call.
- 03YOUThe level decides who acts.
- 04LOGThe record is written.
FOUR APPROVAL LEVELS
- LEVEL 1Auto-runWHO ACTSRivvi runs it.
- LEVEL 2Draft then you approveWHO ACTSYou approve it in the conversation.
- LEVEL 3Propose onlyWHO ACTSA person makes the change.
- LEVEL 4Never runsWHO ACTSNo 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