Security & your data

Your numbers,
kept where you choose.

Every finance team asks the same five questions before they let anything near the accounts. Here are the answers in the order they usually come up, including the one about AI.

Question 01

“Will our data be used to train an AI?”

No. Your data is never used for training, anonymised or not.

There are two separate things inside a bot and neither trains on your data. The rules (matching, tolerances, posting and approval routing) are fixed and written down, with no AI in them at all. The same input always gives the same output and you can read each rule in plain English.

Where AI helps, such as reading a supplier PDF, suggesting the account for an unfamiliar expense or drafting variance commentary, we use enterprise processing only. The provider is contractually barred from training on customer content and may keep it only for the limited period its terms allow. The provider and the terms are named in your blueprint before you sign it.

Question 02

“Where does our data actually sit?”

Where you choose. It depends on how you work with us.

When we build inside your own systems, the bot runs against your QuickBooks, Xero or NetSuite, your cloud storage and your Microsoft or Google account, with credentials you issue and can revoke. Your data stays in your systems.

Where a step cannot run in your environment, we say so in the blueprint and name exactly what moves, why and for how long. You then approve it or we design around it.

In the FinOps Robotics app, every bill still posts to your own financial system and your workspace chooses what is kept on our side. Hosted with us: the documents the bots read are kept in the FinOps Robotics document store for the retention period (seven years after the end of the tax period in the UAE) unless you connect your own Google Drive or OneDrive. Documents not kept here: no document is kept and nothing is kept beyond what the app’s data card lists.

Question 03

“Who on your side can see our numbers?”

Named people, listed in the engagement letter.

Named individuals rather than “our team”, usually two: your engagement lead and your build lead. Each holds their own credentials under your identity provider, with MFA enforced by you rather than promised by us. You see them in your own user list.

No offshore subcontracting and nobody is added to your systems without your written approval first. Every access we hold is one you granted and can withdraw in a single click without asking us.

Question 04

“What can the bot actually do?”

Only what its scope allows. It never moves money.

Permissions are least-privilege and written into the blueprint object by object. During scoping the access is read-only, because we can size the work without any write rights.

No bot we build ever holds payment initiation rights, user administration or the ability to delete master data. A payment file is prepared for a human to release, through your bank, with your token, on your device.

Least privilege, in practice

What we ask for
at each stage.

Access goes up only when a stage requires it and comes back down when it doesn’t.

StageAccess we holdWhat it cannot do
First sessionfree, ~5 days Read-only reports or exports you send us. Often no login at all. Change a single record
Blueprint1–2 weeks Read-only, plus a sandbox or test company of your own. Touch live data
Build & parallel run2–6 weeks Write access scoped to the named objects in the blueprint, in parallel with your team. Post without your sign-off
Runongoing The bot’s own service account, scoped to its rule set, fully logged. Release a payment
Neverat any stage Payment initiation · user administration · master data deletion · bulk export outside your own systems —
Where AI is used and where it isn’t

Most of this isn’t AI at all.

“AI” is often used loosely to mean any automation. This is how the work actually splits inside every bot we build.

Fixed rules, no AI involved
  • Matching invoices to purchase orders and receipts
  • Tolerance and variance rules
  • Every posting and journal the bot makes
  • Approval routing and threshold rules
  • Duplicate detection and payment screening
  • Intercompany matching and elimination
  • Consolidation, FX translation and the statements

The same input always gives the same output. Each rule can be read, tested and explained to an auditor line by line.

AI-assisted, always checked before it posts
  • Reading a supplier PDF or a photographed receipt
  • Suggesting the account for an expense it hasn’t seen before
  • Fuzzy vendor name matching for duplicates
  • First-draft variance commentary for your review
  • Ranking an anomaly queue by value at risk

Every one of these outputs passes either a fixed-rule check or a person’s approval before it reaches your books. AI never posts anything on its own authority and low confidence routes to a person rather than into the accounts.

Our own house

The controls we run
on ourselves.

We sell control environments, so we run one ourselves.

Access hygiene

MFA on every account without exception. Credentials in a managed password vault, never in email, chat or a spreadsheet. Encrypted devices, no client data on personal machines.

People

NDA signed before the first call, not at contract stage. Access removed the day someone leaves an engagement. No subcontracting of client work without your written consent.

Leaving well

End the engagement and our access is revoked the same day, working copies destroyed and every rule set and document handed over. The bots keep running without us.

What we don’t claim

We are not ISO 27001 certified and we are not SOC 2 audited. Plenty of firms our size imply otherwise with a badge on a footer; we would rather you heard it from us than found out in due diligence.

What we offer instead can be verified rather than certified. When we work inside your own systems, it is under access you control, so your existing certifications and controls govern the data, not ours. In our app, the data card lists everything kept on our side, policy by policy. You choose the policy. Either way you can revoke our access to your systems in one click and check the work yourself during the parallel run before any bot has authority over anything.

If your procurement process requires a certified supplier, tell us in the first session. We will tell you then whether we meet your bar today, rather than waste six weeks of your time.

Bring your security team
to the first session.

It is a shorter conversation at the start than at contract stage. We would rather design around your constraints than discover them later.