Secrets stay secret
Credentials such as a Wi-Fi password are stored encrypted. They are never placed in the agent’s instructions, never spoken aloud, and shown only to a verified stay.
Security and
data handling.
What the platform does today, in specific terms — and what we agree with you before launch.
Fig. 01 — Who can see what
Illustrative
01 / In the platform today
Controls that exist now.
Behaviours we can point to, not slogans.
Customer access is verified
A customer reaches only their own information. In hotels, a guest proves a current stay with a code; access tokens are stored as hashes, locked after repeated wrong codes, and end at checkout or departure time.
Staff and customer are separate
Private staff notes are stored separately and there is no path for a customer to read them. A customer sees only their own requests.
Honest states
A request is shown as sent only after it is recorded. Services you switch off are refused everywhere, including through the API.
Change control
Setups are versioned. A quality check and an approval come before anything goes live, and earlier versions can be restored.
Separated by organization
Each organization’s data is kept separate from every other organization’s. Requests keep a history of status changes and who made them.
02 / Agreed at scoping
What we decide with you.
Some answers depend on your law, your policies and your systems. We do not assume them for you.
- Where data is hosted, and how long it is retained
- Whether voice conversations are transcribed or recorded, who can review them, and for how long
- Which systems VOCA may connect to, with which permissions
- Who configures, reviews and approves changes
- Which requests always go to a person, and the time they have to respond
Certifications. We do not claim formal security or compliance certifications today. If your procurement requires them, we will say plainly what we have and what we do not.
Next step
Bring your requirements.
We will go through them in the demo and write down what is agreed.