#Security

Your agent talks to your customers about things that matter to them: their health, their money, their orders. This page says what Vatio does to protect those conversations, in plain terms. Every line of it is how the product works today.

#Your data

• Encrypted at rest. Conversation text, contacts’ phone numbers and email addresses, what the agent remembers about a person, the arguments of tool calls and the token your site uses to identify a visitor are encrypted in the database, with keys kept outside it.
• Encrypted in transit. Every connection uses TLS: from a browser or an app to Vatio, from Meta to Vatio, and from Vatio to its database.
• AI models that keep nothing. Every call to an AI model goes only to endpoints with zero data retention, which neither store nor train on what they receive. The models in use are listed in Models and data.
• Logs without your customers in them. Sign-in codes, conversation text, email addresses and phone numbers are filtered out of the application logs, and the payloads messaging channels send us are deleted a day after they are processed.
• Each workspace on its own. Every request is checked against the workspace it belongs to, so one workspace never reads another’s conversations. The webhooks Vatio sends to your backend are signed, and the ones Meta sends to Vatio are verified.

#Accounts and sign-in

• Two-step verification. After the emailed code, Google or GitHub, Vatio can ask for a passkey (a phone, a fingerprint reader or a security key), a code from an authenticator app, or one of ten recovery codes. One passkey works on both the inbox and the sign-in at vatio.ai.
• The owner decides whether it is required. A workspace’s owner can require two-step verification for everyone on the team. Until everyone has it, the inbox reminds whoever hasn’t turned it on.
• Codes nobody can guess. Sign-in codes are random, last three minutes and stop working after five wrong attempts, and requests for them are rate limited by address and by email.
• Sessions you can see and close. Account, in the inbox, lists every browser signed in at vatio.ai, inbox device and CLI token signed in to your account, and closes any of them. A vatio.ai browser session ends after 7 days without use and an inbox device after 90; when the owner requires two-step verification, both end after 12 hours without use. CLI tokens expire after 90 days without use, and vatio logout revokes them.
• Confirm it’s you. Deleting a workspace, inviting or removing people, creating keys, and changing roles or security settings ask you to confirm it’s you again.

#Who can see a conversation

• Your team, by role. Developers build and deploy; supervisors read and answer conversations in the inbox; viewers read without changing anything. Any member can be limited to some of your agents.
• Vatio staff, only with your permission. Nobody at Vatio reads a workspace’s conversations or contact details unless its owner grants support access, for 24 hours, 72 hours or 7 days, from the workspace’s Security page in the inbox. In an emergency, such as an outage affecting your agent, Vatio can open access with a written reason, and the owner gets an email right away. Either way, it expires on its own.
• An Activity log of everything. Sign-ins, conversations opened and answered, searches, changes to the team, keys, secrets and deployments, and every read by Vatio staff are recorded with who, when and from where. Every change made in the inbox, on vatio.ai or in the CLI is recorded automatically. The owner sees it on the workspace’s Security page in the inbox, and it is kept for a year.
• A locked-down inbox. The inbox runs under a strict content security policy, so only Vatio’s own code runs in it. On your site, a signed-in visitor’s past conversations are shown only to that visitor.

#Retention and deletion

• You choose how long conversations are kept: until someone deletes them, or 30, 90, 180 or 365 days without a new message, after which they are deleted with their files, together with contacts left with no conversation.
• Export or delete one person. From the inbox or the developer API, an owner or a developer can export everything about one contact, or delete all of it: every conversation, file and note.
• Logs that don’t pile up. Access logs are deleted after 90 days and the Activity log after a year. Backups roll over every 30 days.

The details are in the privacy policy and on data deletion.

#Infrastructure and providers

The privacy policy has the complete list.

#Report a vulnerability

If you find a security problem in Vatio, write to support@vatio.ai with “Security” in the subject. Tell us what you found, how to reproduce it and what it would let someone do. Please don’t access other people’s data or disrupt the service while you test. We answer within a few business days and tell you when it is fixed.