What we can actually promise.
This page lists guarantees that exist in the code today. Where Relia does not hold a certification, it does not display a badge for one.
Keys are separated, and one of them never leaves the server
The browser receives a publishable key that can boot a widget and resolve a transaction. It cannot read another customer's conversation or change any configuration. The secret key signs identity tokens and receipts, and no client endpoint will accept it.
- Client side
- pk_live_, scoped to public widget endpoints
- Server side
- sk_live_, identity signing and receipt signatures
- Webhooks
- whsec_, signature verification on your side
Workspaces cannot see each other
Tenancy is not a filter applied at the view layer. Every query carries a workspace id, including the ones behind the public widget endpoints, so a leaked publishable key exposes that workspace's public surface and nothing else.
- Conversations
- Scoped by workspace and by customer
- Knowledge
- Scoped per workspace, never shared
- Keys
- Resolved to exactly one workspace
The widget is sealed in both directions
Relia renders inside Shadow DOM. The host page cannot restyle or read it, and it cannot leak styles into the host. That is also why it can sit on a black casino page and a white dashboard and look the same on both.
- Isolation
- Shadow root, no global CSS
- Uploads
- SVG is deliberately rejected, because it can execute script
- Attachments
- Type and size checked before anything is stored
Answers about money are signed
Every chain answer is written with the statement, the network facts at that moment, a timestamp and an HMAC-SHA256 signature over the exact bytes. Anyone holding the link can verify it. Editing the record breaks the signature and the verification page says so.
- Signature
- HMAC-SHA256 with the workspace key
- Verification
- Public, no account required
- Tamper evidence
- Recomputed on every read
Everything an agent does is recorded
Who assigned, who escalated, who resolved, who opened a document, who shared a case file. Sharing a case is a real disclosure, so it is audited like one and the link expires on its own.
- Audit log
- Actor, action, target, address, time
- Delivery log
- Every webhook attempt and its result
- Share links
- Signed, expiring, audited
Data can be exported and deleted, for real
Per customer and per workspace. The export returns everything held about that person. The deletion removes it. This is a working endpoint, not a policy paragraph.
- Export
- Customer or whole workspace
- Deletion
- Removes the record, not just a flag
- Retention
- Attachment limits enforced at upload
Relia tells you when data is not durable
A health endpoint reports the storage mode and whether writes survive a deploy. If they do not, the operator sees a banner rather than discovering it when accounts disappear. That failure is exactly how this check came to exist.
- Health
- Storage mode, durability, database, email, AI provider
- Banner
- Shown in settings when durability is at risk
- Honest by default
- No silent degradation
Relia does not currently hold SOC 2, ISO 27001 or a third party penetration test, so none of those appear anywhere on this site. When they exist, they will be listed here with dates and scope.