How PRESHoshandles your data.
Where agents work on your data, how it is protected, and what is kept on the record.
The detail,area by area.
- Agents work on a copy of your data
- Your live systems stay the system of record
- A person decides what goes back, and when
- Encrypted storage
- Private file access
- Point-in-time recovery
- Google Cloud Secret Manager
- Scoped runtime grants
- Server-side credentials
- Configurable cloud egress
- SSRF safeguards
- Scoped access to MCP servers, APIs and AI models
- Run and tool event traces
- Human approval records
- Actor, action and outcome for each
- For custom enterprise deployments, your data can be hosted in your own infrastructure
Secrets stayin the vault.
Credentials are held in Google Cloud Secret Manager and granted to a run only for the scope it needs. They stay on the server.
Relatedreading.
More on Platform
AI & Automation
AI Works on a Copy: Approval Before Anything Reaches a Live System
Agents can do real work on a working copy of your data while a person approves what goes back. Here is how a digital twin and an approval gate work together.
AI Engineering
Choosing a Model per Agent: Match the Model to the Job
Different agent jobs suit different AI models. Here is how to choose a model per agent, compare options fairly and keep your controls the same throughout.
AI Engineering
Field-Level Permissions for Agents: Control Down to the Field
Field-level permissions decide which parts of a record an agent can read or change. Here is how roles, scopes and fields combine, with a worked example.
Have a data question?
Tell us what your team needs to know about where data lives and who can reach it. We will answer it directly.