Security

Data-flow summary

Customer messages enter approved channels, pass to the chat engine, retrieve tenant-scoped catalogue and policy data, call AI providers when needed, then log response, usage, handoff, and review data.

Tenant isolation and RLS

Client data is keyed by client identifiers and protected with Supabase row-level security where tables are exposed or sensitive.

Secret handling

Service-role keys and provider secrets stay in Supabase/Netlify environment configuration, not browser code.

Rate limits

The public demo and chat engine use session mint limits and per-session message limits to reduce abuse as free LLM access.

What OpsRivo can and cannot see

OpsRivo can see operational data needed to run, debug, review, and improve the desk. OpsRivo cannot see passwords or payment-card data unless a client separately provides it, which should not be sent through chat.

Incident communication

Material incidents are communicated to affected clients with known scope, impact, remediation, and next steps.