Your data stays in your tools.
Our workflows connect to your inbox, CRM, and documents. Here is exactly where they run, who holds the keys, and what happens when we leave.
Questions answered in writing before any build. Get your recommendation →
Workers run in your accounts
Every worker runs on Rivet, which is open source, on a server or cloud account in your company’s name. It plugs into the n8n, Make or Zapier flows you already have instead of replacing them. It is all yours, and it keeps running if we stop working together.
Your API key, your account
Rivet calls Claude with an API key created in your own Anthropic account. We never route your data through a shared account of ours, and you can rotate or revoke the key at any time.
We do not copy your data
Workflows read and write through your existing tools. We do not keep a copy of your CRM, inbox, or documents on our systems. Testing uses sample or test records wherever possible.
Every run is logged
Rivet writes one line per run to an audit log you own: what came in, every action and its outcome, the decision, and which model answered. Held actions wait in an approval queue, so any decision can be traced afterwards.
Least-privilege access
We ask only for the access a build needs, through named user seats rather than shared passwords, and we list that access in the proposal.
Access removed when the work ends
At handover, or when a care plan ends, we remove our seats and hand you a list of every connection and credential the workflow uses.
You decide how much the workflow does on its own.
Every first build launches at Level 2: the workflow does the work, and a person approves anything risky. It moves up only when the monthly numbers support it.
- L4 Handles exceptions Selected edge cases are handled automatically, under rules you set.
- L3 Acts on its own Approved work runs without a person. Unclear items still go to review.
- L2 Acts with approval The workflow does the work. Risky steps wait for a person. Every launch
- L1 Suggests The workflow recommends. A person acts.
- L0 Manual A person does everything.
Data residency, an NDA, a data processing agreement, or a vendor questionnaire: ask before the build, and we will answer in writing.