Security & IT
Built so your IT department can say yes.
It runs in a cloud account in your company's name, reads only what you grant, writes nothing back unless you switch it on, keeps a record of everything it did — and can be switched off from your side, any day.
What IT sets up
Three things, once.
- 1
Read-only access to what each part touches
The folders and the mailbox that job needs — not the whole drive, not every mailbox.
- 2
A connection to your systems, the way they allow
The export a system already writes each night, its interface or import if it has one, or its own screens with an account you create and can close. You choose which.
- 3
A cloud account in your company’s name
Created by you, with the credentials held by you. Everything we build lives there from the first day.
No IT department? We do the setup with you, and the keys are still yours.
The questions IT asks
Straight answers.
Where does it run?
The real system runs in a cloud account in your company’s name; your records, documents and the index built from them stay there, not in an account of ours. The examples you send for the demo are kept in our own cloud account, aren’t used to train AI models, and are deleted when you ask.
What can it touch?
Read-only, and only what you grant. Nothing is written back to your systems unless you switch that on — one workflow at a time, with a person approving each entry.
Who can sign in?
Your people, with the work accounts they already use. What each person can see follows the access rules you already have.
What did it do?
Every read, every draft and every approval is recorded, with who and when. The record is yours, and it downloads as a file.
Is our data used to train AI?
No. It stays in your own cloud account, and under the cloud provider’s enterprise terms it isn’t used to train their models or public AI.
How do we switch you off?
Revoke our access from your side, any day, without asking us. Everything you own keeps running; we simply can’t get in.
What IT sees
One page with all of it.
Where it runs, who owns the account, what it read and when, and the button that takes our access away.
Ownership
What you own. In writing.
Ownership isn't a slogan here — it's a schedule in your agreement. Here is the plain-English version:
| What you get | What that means |
|---|---|
| Your deployment | The running system in your cloud account — yours from the first day of the build, not handed over at the end. |
| Your data | Every record, document and index, kept in your own cloud account. |
| Your configuration | The workflows, rules and tuning that make it fit your business. |
| Your credentials | The cloud account and its keys. You hold them; we don't. |
| The code | Everything built for you, down to the source code. If we’re ever not around, your own people or anyone you choose can keep it running. |
| A perpetual license | For the reusable base parts we bring to every job: irrevocable rights to run, modify and maintain them in your build, with anyone you choose, forever. |
For IT, specifically
More questions from IT.
- Do you need admin rights?
- No. Read-only access to the folders, the mailbox and the systems a job needs, granted by you and scoped to that job.
- Does anything get installed on our PCs?
- No. People use it in the browser they already have, signed in with their work account.
- Can it write into our ERP?
- Not unless you switch it on, and then only for the workflow you choose, with a person approving every entry. By default it only reads.
- What if we replace our ERP?
- We connect to the new system instead and match its fields once. The jobs, the rules and the questions above it don’t change.