Where the key lives.

The key is not next to the data

Your content is encrypted by the application before it is stored, and the key that unlocks it is held in a separate key service, not in the database. That key cannot be downloaded. Whoever managed to copy the database would still hold nothing they could read.

The key never reaches a browser either. What a signed-in user holds is the right to ask for it to be used, one ticket at a time, and never the key itself.

One key per ticket

Each ticket is sealed with a data key of its own, itself locked by the key in the key service and kept with that ticket. Opening one ticket gives no ability to open the next.

No operation decrypts your whole history

There is no operation that decrypts a store’s entire history: not with a limit, not with a log, not for the store’s own owner. A path that exists with a limit can be abused slowly. One that does not exist cannot be abused at all.

Your reports work anyway, because each case is classified when it is resolved. The text is read once and becomes fields, and Lens reads the fields, not the conversations.

Your credentials are sealed

Your store and helpdesk credentials are encrypted inside your own workspace and are never readable by a Human Node or by any dashboard user, your own team included. They are opened only to carry out an action that has already been authorized, and the secret is never handed back to whoever asked.

We cannot browse your data either

Reading a customer’s data would require a signed, verified and recorded deploy. There is no query, panel or key that gives us that access.

Razviel’s internal admin has no operation that returns customer content and no permission to decrypt anything. What it can do is reversible: suspend and reactivate, pause and resume. Deleting a store’s data for good happens by destroying that store’s key, a scheduled and deliberate step, never a button in a panel.

What reaches an AI model

Before any text is sent to a model, names, email addresses, phone numbers, street addresses and order numbers are replaced by placeholders, and the answer is filled back in afterward, on Razviel’s side. The model does not see who your customer is.

The model providers are contracted to zero data retention: no prompt and no answer is stored beyond serving the request.

What runs is proven before it runs

The service that holds your key is updated only with code that proves where it was built and passes an independent automatic check. A new version reaches a single store first, and rolls itself back if it behaves differently. No person has to approve it, and no signing key is stored anywhere to be stolen.

And every decryption leaves evidence that the running code cannot erase.

In your browser

Our dashboards load nothing from another origin: no outside script, stylesheet, font, image or frame.

Each page is also built so that the browser refuses any script that does not come from Razviel itself, any script written inline, and any attempt to write markup into the page from script.

Where it is written

Keep reading