Your data is yours.
Victoria operates on sensitive information from your company. This page explains how it is isolated, who can see it and what we do not do with it.
Are you the head of IT? We can set up a technical meeting with our development team.
Three rules we do not negotiate.
The data belongs to your company
You remain the owner of the information that enters Victoria. We process it to run your service, nothing else.
Minimum necessary access
Each user sees what their role needs in order to work. The rest does not appear, and it does not appear because the server does not return it.
Everything that happens is recorded
Every action on a piece of data is stored with user, date and detail. If something changed, it can be known who changed it and when.
Six concrete measures.
No more and no less than this. Every point can be reviewed with your IT team before signing.
End-to-end encryption
Communications travel encrypted end to end between the channels, the platform and your system.
Automatic backups
Automatic daily backup copies of the information on the platform.
Audit trail of actions
Every action inside the platform is recorded with user, date and detail of what changed.
Granular permissions
Permissions per user and per area: who sees what, who edits what and who has no access.
Data isolated by company
Each company’s information is separate from everyone else’s. No user can reach data from another account.
No use for training external models
Your data is not used to train external models and is not shared with third parties.
Development aligned with the CIS controls and the OWASP Top 10.
The separation is not visual: it is on the server.
Every company that uses Victoria has its own data space. The users of one account cannot see, list or query information from another.
The important difference is where that is decided. It is not enough for the screen not to show a piece of data: every request that reaches the server is validated against the company the requesting user belongs to. If the request points at another company’s data, it is rejected before the database is read.
That means manipulating the interface from the browser does not grant access: the interface is not the control, it is only the view.
A user of Company A who alters a request to query Company B data receives a rejection from the server, not an empty screen.
Who can do what, and what each person did.
Permissions and the record of actions are not a separate module: they are part of how the platform works every day.
With the access closed, the screen does not appear and the server does not return its data either.
You define what each role sees and edits: per module, per area and per user. A sales rep does not reach the administration information unless you enabled it.
What we do and what we do not.
The use we make of your company information is limited to running the service you contracted.
Each party answers for its own part.
Saying who does what avoids misunderstandings when something has to be resolved fast.
Victoria AI
Develops and operates the platform, applies the measures on this page and answers for the operation of the contracted service. Legal name: Victoria AI, Córdoba, Argentina.
Your company
Administers its users, defines the permissions of each role, decides what information it loads into the platform and which actions the agent may carry out without human approval.
The messaging platforms
WhatsApp, Instagram, Facebook and TikTok are governed by their own policies and terms. We operate on their official APIs and within the rules each one defines.
The full conditions are in the Terms and conditions and in the Privacy policy.
What you sign and what you can request.
Do you have to sign this off from IT?
We set up a technical meeting with our development team to review integrations, permissions and data handling, point by point.
Victoria AI · Córdoba, Argentina