Your clients' data stays yours.
Precision AI OS is built for firms that hold sensitive client information. Every firm's data is kept apart, encrypted with keys unique to that firm, and handled by rules written into the system, not into a policy binder.
Your data is isolated from every other firm
Every table in the database carries a firm identifier, and the database itself, not just our application, refuses to return another firm's rows. Row-level security is enforced on every table, and the accounts our services use to reach the database can't switch it off. Only two narrowly scoped database functions can resolve a user's firm, and our tests check that no others exist.
Encrypted with keys unique to your firm
Documents and sensitive data are encrypted with AES-256-GCM using a key for your firm alone, and that key is itself protected by Google Cloud Key Management Service. Encrypted files are sealed so any tampering is detected before they're read, and they're bound to your firm, so a file can't be moved into another firm's space and opened there.
Language models only under zero-retention terms
Language models only run under rules we write into the code. Before a language model can be called, it must be covered by a zero-data-retention agreement with no training on your data, with prompt logging off and fallback to shared providers off. A model that doesn't meet all four conditions can't be called. Providers may hold a prompt briefly in memory to speed up a request. Every model call is recorded: which job made it, which model answered, and what it cost. Reading scanned documents (OCR) runs on Google Cloud's Document AI.
A permanent record of every approval
When your team approves work, the approval is written to a record that can't be edited or deleted during its retention period, even by an administrator, and it's tied to exactly what was approved. Checks for separation of duties are built in, so the person who prepared the work isn't the one who approves it.
Legal hold and controlled deletion
A legal hold stops deletion of anything it covers. Deletion runs as a preview first, so nothing is removed until it's been reviewed. When a firm leaves, its encryption keys are destroyed, so any of its encrypted data that remains can no longer be read. The exit steps are agreed in your contract.
Infrastructure and engineering
Hosted on Google Cloud in the United States.
Database backups are kept daily for 30 days, with point-in-time recovery over the last seven days.
Secrets live in Google Secret Manager, never in code. Every change is scanned for leaked credentials and vulnerable dependencies before it ships.
Production deploys run only from the main branch after every automated check passes, using short-lived credentials instead of stored keys.
A written incident-response process covers detection, containment, recovery and notifying affected firms.
Built toward SOC 2
Our controls are designed against SOC 1 and SOC 2 criteria, with written security policies in place. We haven't completed an audit yet, and we'll say so plainly until we have. Ask for our security packet to see the policies and the controls behind this page.
People stay in charge
Agents prepare work; your people make the calls. We build every agent so that anything going to your clients, and anything it isn't sure about, waits for a person on your team. Every approval is recorded.
Have your IT lead or security reviewer walk through it with us.
Questions
Is my firm's data mixed with other clients' data?
No. Every record carries your firm's identifier, and the database enforces row-level security on every table, so queries can't return another firm's data even if application code made a mistake.
Is our data used to train AI models?
No. A language model can't be called unless it's covered by a zero-data-retention, no-training agreement with prompt logging and shared-provider fallback off, enforced in code. Reading scanned documents uses Google Cloud's Document AI; the terms that apply to it are listed in our security packet.
How is our data encrypted?
With AES-256-GCM using a key for your firm alone, protected by Google Cloud Key Management Service. Encrypted files are tamper-evident and bound to your firm, so they can't be opened in another firm's space.
Where is our data stored?
On Google Cloud in the United States. Backups are kept daily for 30 days, with point-in-time recovery over the last seven days.
Are you SOC 2 certified?
Not yet. Our controls and written policies are designed against SOC 1 and SOC 2 criteria, and we'll publish audit status when it's complete. We can share our security packet during a discovery call.
What happens to our data if we leave?
Offboarding respects any legal hold and follows the exit steps in your contract. Your firm's encryption keys are destroyed, so any encrypted data that remains can't be read, and deletion is reviewed as a preview first.