Your data stays in your accounts

The short version: we never keep a copy of your business data. Everything we build runs inside accounts you own, the logins are created by you, and you can remove our access in one click without asking us first.

Step 1

You own every account

Your website, your GitHub, your Microsoft 365, your AI provider. Each one is opened in your name, on your card. We help set them up. We never buy them for you or sit in the middle.

Step 2

We get our own login, with limits

A named account with only the access the job needs, never a shared password. You can see exactly who we are in your system, and remove us whenever you want.

Step 3

The automation runs in your accounts

It works on your data where it already sits. It is not copied to our servers, because we do not run your automations on servers of ours at all.

Step 4

We leave in writing

At handover you get the code, a list of every credential and where it lives, and a written statement of what access we kept and what we removed.

The details

Where your automations run

Inside accounts you own: your website, your GitHub organisation, your Microsoft tenant, or your own n8n workspace if you want to edit the flows yourself. We do not host your systems and we do not keep a copy of your data.

Your credentials stay yours

Every password, key and token is created by you, in your own account, and kept in your own secure storage. We never put one in an email, a chat message or a file. If we need one while building, it goes through a password manager and our copy is deleted at handover.

Our access

A named account with the least access the job needs. During the build we can see what the automation has to touch, and we work on it where it sits. You can revoke our access in one click, at any time.

What monitoring can see

Agent cover reads status, not content. Each system reports one thing: whether its last run actually worked, and when. No records, no customer details, no documents. A monitored system is not a system that has handed us its data.

When AI is involved

If an automation uses AI, for example to draft a reply or read an invoice, the text it works on goes from your account to the AI provider, under your own key and that provider’s data terms. It does not pass through us, and the usage is billed to you, so nothing runs on an account you cannot see.

When we leave

If you do not keep agent cover, our access is removed on the day of handover and we tell you in writing. If you do keep it, we keep one named login, with the same limits, that you can remove whenever you like.

What we never do

  • Copy your data to our own systems
  • Run your automations on our servers
  • Use a shared login
  • Hold a paid key in our name
  • Send passwords by email or chat
  • Read your data through monitoring

The same rules are written into our terms, and every build is also covered by our 30-day guarantee.

Bring one process you are tired of

Thirty minutes, and you will know whether it can be automated and what it would save.