People
Humans inside the control system.
The people who touch your tickets, and what they can see. Human Nodes are constrained by design, bound and scoped like every other part of the system.
01
Independent providers
Human Nodes are independent service providers, individuals or their own entities, under contract with Razviel. They are authorized as a category of subprocessor, and each one is individually bound by confidentiality and data-protection obligations before receiving any access.
02
No account in your store
A Human Node is given no login to your store or your helpdesk. They work only inside the Razviel console, with no bulk export, and your credentials are never readable by them.
03
Scoped to the work in front of them
Access is scoped by row-level policy, so a Node reaches only their assigned tickets and the queue of brands they are certified for. The scope leaves out another Node’s tickets, another brand’s tickets, and tickets resolved without a person.
04
On screen, logged, and closed with the module
Access is screen-only, through the console. No customer data is sent to, stored in, cached on or downloaded to any system in the Node’s country. Every access is logged.
Access belongs to the scheduled module, the Node’s block of work, not to the person. It ends the moment that block ends.
05
Bound before any access
Before any access, each Node accepts a confidentiality and data-protection annex. It forbids copying, exporting, downloading, photographing or screenshotting customer data. It limits the use of that data to the assigned ticket, inside the console. It requires the Node to keep their device secure, and to report any actual or suspected incident to Razviel within 24 hours.
06
And your own team
The same discipline applies on your side. Every sign-in, for a Human Node and for your own team, asks for a second factor. What each person on your team may do is set by the role they hold in your workspace, and by nothing else.