Security
Built for teams that handle sensitive data
Decisions the language model does not make on its own, and data that never goes through it.
The data path
Sensitive data never passes through the AI.
The conversation goes to the AI agent. Passwords, taxpayer IDs and confirmation codes go through a secure form of the channel, straight to your system. Your system validates, approves or refuses, with the rules it always had. All inside your cloud.
Checklist
What IT, legal and compliance ask.
The short answers for the first meeting. The technical documentation delivered with the proposal details each one.
- Where does it run?
- In your company cloud, with an installation signed for your key. Conversations, collected data and credentials never leave your environment.
- What can the AI execute?
- Only the operations of your API that your team released in the dashboard. The agent calls; your system validates, approves or refuses with the rules it always had.
- How are credentials stored?
- Encrypted. Whoever configures them types the value once and never sees it again.
- Who accesses the dashboard?
- Company single sign-on (SSO) and roles that separate who configures, who operates and who views.
- Where do the ID, the password and the code go?
- Through a secure form of the channel, straight to your system. The language model never receives that data.
- How long are conversations kept?
- For as long as your company defines. History per customer, to answer access and deletion requests.
- How do we audit what the agent did?
- Every conversation is logged with the operations called; every use case change has an author and a version.
- How do we limit who talks to the agent at first?
- Pilot with a controlled group: only released customers talk to it. Whoever is blocked is logged with the reason.
How we protect it
Six design decisions
- 01
Runs in your cloud
The platform is installed in your environment. Conversations, collected data and credentials do not leave it.
- 02
Sensitive data outside the AI
Passwords, tax IDs (CPF), health data and confirmation codes come in through a secure form in the channel and go straight to your system.
- 03
Encrypted credentials
The credentials of each connection are stored encrypted. Whoever configures them enters the value and never sees it again.
- 04
SSO and roles
Panel access through your company single sign-on, with roles that separate who configures, who operates and who only views.
- 05
Pilot with a controlled group
Only the customers you release talk to the agent. Anyone blocked is logged with the reason.
- 06
Traceability
Every use case change has an author and a version, and every conversation is stored for audit.
LGPD
What the law requires, where the product helps
The contracting company is the controller of its customers' data. OmniAgent provides the mechanisms to meet what the Brazilian General Data Protection Law (LGPD, Law No. 13,709/2018) requires.
Minimization
The agent asks only for the data the use case needs.
Retention set by you
The company defines how long each conversation is kept.
Data in your environment
No shared environment: the data stays where your company already protects it.
Data subject rights
History per customer, to handle access and deletion requests.
Next step
See your use case running
Thirty minutes with the sales team. You bring the request your customers make most; we show the agent executing it. Prefer to ask first? The assistant next to this text answers questions about security, channels and integration, and schedules the demo.
- 01Chat with the assistant: it asks for your details and what you are looking for
- 02The sales team receives your contact right away
- 03Demo with your use case
- 04Proposal and start of the pilot with a controlled group of customers