Isolation
One store.
One vault.
Your data stays apart from every other brand’s, and from your other stores. By design, isolation is a whole workspace per store, not a filter on a shared table.
01
The workspace is the unit
Isolation in Razviel is drawn around the workspace, not around a person, an account or an email address. One workspace is one store, and the binding is permanent: it is written by the first verified connection and tied to the store’s own ID, never to its web address.
The question the system asks is never who you are. It is what role you hold in this workspace, and it answers by reading that workspace alone.
02
Eight pieces, none of them shared
Every store gets a slice of its own: its store and helpdesk connections, its own database, its own encryption keys, the part of the system that reads its tickets, the part that decides on them, its own evidence store and its own model key. Knowing the store is enough to know every piece that serves it.
No credential, key, connection or permission serves two workspaces. Anything found twice inside one is treated as a defect, not as a setting.
The providers behind these pieces are not a secret. They are listed, with what each one processes and where, in the Data Processing Addendum.
03
A wall, not a filter
In a shared database, isolation is a rule that every query has to remember. Here the first line is that your tickets and conversations live in a database of their own, which no other store’s query can reach. Row-level policy is the second line, inside it, scoping who reaches which ticket.
One database is shared across Razviel, and it holds identity, plans and Human Node records. It holds no store credential and no customer content.
04
Identity crosses. Access never does.
One person can belong to several workspaces: an agency working for several brands, a brand running several stores. The identity is one. Each workspace still decides, on its own, what that person may do there, and signing into one store opens nothing in another.
It is also why there is no aggregated view across stores. Each one stands alone, and the isolation that keeps them apart is the reason.
05
Nothing crosses between brands
No Customer Data, in any form, crosses from one customer’s account to another. Not raw tickets, not transcripts, not attachments, not customer memory, not identifiers — and not de-identified, aggregated or derived material drawn from any of them. Each Customer’s material stays with that Customer, permanently. Razviel operates no cross-customer improvement.Data Processing Addendum, §6.2
What one brand teaches the system stays with that brand. Your resolved cases improve your own operation: they are retrieved at the moment of answering, only inside your account, and no model is trained or fine-tuned on them.
Changing any of this would take your separate, prior and written consent, asked for on its own. Neither that consent nor that use exists today.
06
Your search index lives with your data
The index that lets the system find similar past cases is built inside your own workspace database, not in a shared one. Direct identifiers come out before a case is indexed, and only they do: the complaint, the tone and the case stay, and the person does not.