Protecto masks sensitive data before AI agents read it. Each answer shows real values only for the data types the asker’s role allows, so an AI agent never sees more than the person it works for.
SOC 2 Type II · ISO 27001 · HIPAA, BAA available
Support rep
Maya Shah · <CARD>5Gk2 h8Lw</CARD> · <DOB>q7Zt2W</DOB>
Billing specialist
Maya Shah · 4111 1111 1111 1111 · <DOB>q7Zt2W</DOB>
AIAI agent working for a support rep
Maya Shah · <CARD>5Gk2 h8Lw</CARD> · <DOB>q7Zt2W</DOB>
The model reads tokens only.Synthetic example
How a Fortune 100 company enforced data policies across its AI agents
To enforce policies at a Fortune 100 company
Live enterprise tenants with their own policies at Automation Anywhere
Lower cost than building it in-house, at a SaaS company
A support rep asks an AI agent to sum up a refund dispute. The AI agent pulls the ticket, the customer record and the payment history through a service account that can read everything. The summary shows the full card number and date of birth to a rep who should see neither.
An AI agent shares whatever its own account can read.
One service account serves every user, so every answer gets that account’s access.
Permissions sit in your app or directory. Prompts, vector stores and tool calls never see them.
Each new AI agent adds its own filters, and none of them match.
Each role gets a list of data types it may see in real form. Everything else stays a token, including in what an AI agent writes for that role.
Tap a type to switch it · 3 of 6
What the answer shows
Refund request from Maya Shah (maya.shah@example.com, +1 415 555 0142). Card <CARD>5Gk2 h8Lw</CARD> was charged twice on March 3. Date of birth on file: <DOB>q7Zt2W</DOB>. SSN <SSN>x9Rk-Pq</SSN> was used for the account check.
An AI agent answering for a support rep gets exactly this view. The model itself only reads tokens. Synthetic example.
See this with your own roles.
Your application passes each user’s role with every request, using a Protecto auth key. Change a rule by updating the policy your application passes; agent code stays the same.
Protecto does not replace your identity or agent identity tools. It applies the roles you already manage.
Sign in
A support rep signs in. The role comes from your app, or from AD or Okta groups through Privacy Gateway.
The role travels with each request
Your application calls Protecto with an auth key and the policy for that role.
The AI agent works on tokens
The model and its tools read tokens, so the AI agent cannot pass on what the rep may not see.
The answer is unmasked by role
Protecto restores real values only for the data types the role allows.
Most AI agents start with one service account. Here is what changes when roles decide what each answer shows.
| Capability | Protecto | AI agent service accounts |
|---|---|---|
| Who the AI agent acts as | The role of the person who asked | Its own account, with broad access |
| What the model reads | Tokens, never real values | Whatever the account can read |
| Control by data type | Card, SSN, email and more, per role | Table or document level |
| Changing a rule | Update the role’s policy; agent code stays the same | Change code in each AI agent |
| Adding a team | Add a role to the policy | New account and new checks |
| Separate customers | A policy per tenant | Separate deployments |
| Records for auditors | Event logs for each mask and unmask | Agent logs, if any |
Call Protecto from LangChain, LlamaIndex or your own code. Mask what the AI agent reads, then unmask its answer with the policy for the asker’s role.
One policy per role. Your AI agents call the same API whoever is asking.
AI agent answer, unmasked for a support rep
PUT /api/vault/unmask
{"policy_name": "support-rep", "unmask": [{"token_value": "Refund for <NAME>Kq8 Tz2</NAME>, card <CARD>5Gk2 h8Lw</CARD>"}]}
Response: value
Refund for Maya Shah, card <CARD>5Gk2 h8Lw</CARD>
Synthetic example, shortened. The same call with the billing policy returns the card number too.
Combine roles with the other controls your AI agents need.
Each user sees only the records their source systems allow.
CBAC weighs who is asking, for which task and why, and can rewrite text that is sensitive as a whole.
Platforms that serve many customers give each tenant its own roles and policies.
Reports show where sensitive data flows and how your data policies were enforced.
Six layers where sensitive data moves in agentic AI, and a framework for mapping your own exposure.
Why static roles break down once an AI agent acts for many users, and how to fix it.
Decide access outside the model, mask before the model, and reveal values only to allowed roles.
How Protecto Vault detects, masks, and controls access to sensitive data.
Role-based access control for AI agents decides which data types each role may see in real form, and applies it to everything an AI agent reads or writes. The AI agent works with the role of the person who asked, not with its own broad access.
RBAC answers “which data types can this role see?”. Data access control answers “which records can this user open?”. CBAC adds the task and the purpose. Protecto supports all three, and most teams start with roles.
No. An AI agent takes the role of the person it works for, so a support rep’s AI agent sees what the support rep sees.
Yes, through Privacy Gateway. You keep each user’s masking and unmasking access in AD or Okta groups, and Gateway issues a Protecto auth key with that access at login. If you use Protecto Vault directly, it’s a headless API, so your team can build the integration around it.
Tokens such as <CARD>5Gk2 h8Lw</CARD>. Each token keeps the data type, so the model can still reason about the record. Real values come back only in the answer, and only for the types the role allows.
No. Update the policy for the role. Your application passes the same policy name, and the AI agent calls the same API.
Yes. Each tenant can have its own policies. Automation Anywhere runs more than 5,000 live enterprise tenants this way.
Yes. Event logs record each mask and unmask, so your auditors can see how your policies were applied.
Bring your roles and a sample record, synthetic if you prefer. We will show you what each role and its AI agents can see.
Features that safeguard your data across agents, AI applications, RAG pipelines, MCPs, data lakes, and enterprise systems.
By submitting you agree to Protecto’s privacy policy.
A reference architecture for protecting sensitive data across agent workflows, for architects and AI platform engineers.
By submitting you agree to Protecto’s privacy policy.
A framework for finding where sensitive data moves through your AI systems, before a security review or an auditor finds it for you.
By submitting you agree to Protecto’s privacy policy.