Security and Trust
Plain-language edition
Written for the person whose job is to say no.
Ace Work sees how your company works. That's the product, and it's exactly why we hold ourselves to a higher bar than a tool that only sees your data. Here's the whole picture.
§ 00 · The short version
01
Your data stays yours
Workflow data is visible to your team only. It doesn't feed benchmarks, and it doesn't train anyone's AI model.
02
Runs in systems you own
Automations run inside your tools, under the access controls you already set. Nothing migrates to us.
03
Humans hold the send button
Nothing acts under your people's names until a human approves it.
04
Autonomy is your dial
Every autonomy decision is yours, per workflow, reversible at any time.
§ 01 · Where your data lives
Your work stays where it already lives.
The automations we build run inside your tools: your Airtable, your Salesforce, your Google Workspace. Your business data stays in the systems you already govern, under the access controls you already set. We don't copy your operational data into a new platform to make things work.
What Ace Work itself holds is the map: interview transcripts, documented workflows, and the numbers around them. That data lives on Neon, a US cloud database provider, encrypted in transit and at rest. It's visible to your team and to the Ace people working your account, and nobody else. It doesn't feed benchmarks with your name on them, and it doesn't train anyone's AI model.
Your systems · your governance
Airtable
Salesforce
Google Workspace
Slack
XeroAutomations run here. Business data never leaves.
Ace Work holds · the map
- Interview transcripts
- Documented workflows
- The numbers around them
Encrypted in transit and at rest. Visible to your team and your account's Ace people. Nobody else.
§ 02 · AI providers, plainly
Your interviews stay yours.
Ace Work uses AI models from providers including Anthropic to run interviews, map workflows, and power the platform. We work with these providers on terms where your data is not used to train their models. Your interviews describe how your company works. They stay yours.
Non-negotiables
Training their models on your data
OffBenchmarks with your name on them
OffEncryption in transit and at rest
On
§ 03 · Who can see what
Private to your company, by default.
Interviews, SOPs, and workflow data are private to your company by default, for the whole engagement. Inside your company, division scoping controls who sees which team's workflows. Inside Ace, access is limited to the people assigned to your account.
When the engagement ends, your data doesn't linger by default. You can export your workflow data, and we honor deletion requests. Ask us for either at any time.
Access · from the inside out
Your team
Interviews, SOPs, and workflow data, private to your company by default, for the whole engagement. Division scoping controls who sees which team's workflows.
Your account's Ace people
Inside Ace, access is limited to the people assigned to your account.
Everyone else, nothing.
§ 04 · The autonomy ladder
No workflow runs on trust it hasn't earned.
Every automation sits on a graduated ladder, and you decide the rung. Moving up the ladder is your call, per workflow, and moving down is instant.
Rung 01
Propose
The workflow drafts everything and executes nothing. A human reviews every run.
Where most workflows start, and stay, until the run history says otherwise.
Rung 02
Spot-check
The workflow runs, and your team reviews samples on a cadence you set.
You choose the sample rate and the rhythm, weekly, per batch, whatever the risk warrants.
Rung 03
Auto
The workflow runs on its own, with every run logged and reported.
Earned by run history, never the default. Moving back down is one click.
§ 05 · Approval gates, concretely
Ace drafts. Your person sends.
"Human approval" is usually a vague promise, so here's the concrete case: automated emails are written by the workflow and wait in the sender's own drafts folder. Ace drafts. Your person sends. Nothing goes out under anyone's name until the person who owns that name says so.
The same pattern applies wherever a workflow would act as one of your people: the action is prepared, the human releases it.
Drafts · sarah@yourcompany.com
1 waitingRe: March client report
Hi Tom, the March numbers are attached. Revenue landed at…
Drafted by workflow · waiting for Sarah
Sends only when Sarah says so
§ 06 · Our people
In your systems, under your controls.
Forward deployed experts work inside your systems, in your accounts, under your access controls. Every builder is vetted and approved before they touch client work. You can see what they're doing because it happens in tools you own, and you can revoke access the same way you granted it.
Granted by you · revocable by you
Forward deployed expert
Your Airtable · your access controls
Workflow builder
Your Google Workspace · your access controls
It happens in tools you own, so you can see it, and shut it off, the same way you would for anyone on your team.
§ 07 · Subprocessors & documents
The full list of subprocessors, and what each one touches, is maintained in our Data Processing Agreement. We keep it current there so there's exactly one source of truth.
Read the DPAQuestions this page didn't answer?
Ask them directly. A real person replies.