Security
We read your books. We never move your money.
See what Quidwise can access, how we protect your credentials and when Ada asks for your approval.
In short
- We read your accounting system, the bank statements you upload and your finance email. We never move money, and Ada enters nothing in your books without your approval.
- Connecting your bank directly, by open banking, arrives on 1 January 2027. You will sign in on your bank’s own pages, through a regulated Open Banking provider. We will never see your bank login.
- Ada sends emails you approve or allow through your sending rules. Under signed standing orders, eligible friendly reminders and statements wait 10 minutes by default so you can stop them. How email approvals work.
- Connection credentials are encrypted at rest with AES-256-GCM. Disconnecting a source deletes them at once.
- You sign in with a one-time code sent by email or, if you choose to set one, a password. A password is kept only as a scrypt hash, never in plain text and never in a log.
- Ada prepares the filing figures and supporting working for review. A qualified accountant at CIJ Labs files for you, or your own accountant can. If filing from Quidwise opens, a filing goes to HMRC or Companies House only after an owner approves that exact filing and presses its button. Quidwise never keeps a Government Gateway password: you sign in on HMRC’s own page, or give it once to Staffology by IRIS, which would file the monthly contractor return for you.
- An accountant you add in Settings can see your workspace. A CIJ Labs accountant assigned to a filing case can see the pack and documents the owner shares for that case.
What each connection can do
The permission lists below are printed from the connector code itself, so this page cannot say one thing while the connect flow asks for another.
Bank accounts (Open Banking)
Connecting your bank directly, by open banking, arrives on 1 January 2027. You will connect a bank through an FCA-regulated Open Banking provider, named on the connect screen before you give consent. You will sign in on your bank’s own pages; we will receive read-only access, never your bank username, password or card-reader codes. That access will read account names, balances and transactions. It will carry no payments permission, so it cannot move money, set up a payee or change anything at your bank. Your consent will run for up to 90 days at a time; you will be able to end it at your bank or by disconnecting in Settings.
What the consent covers, read-only: account details, balances and transactions, for as long as the consent runs. No payments permission is asked for.
Until then, the bank lines in your accounting software reach Ada through that connection, and you can upload bank statements. This section describes the bank link as it is built.
Xero
By default we ask Xero for read permissions only, and every one of them ends in .read. We can read your chart of accounts, contacts, invoices, bills, bank transactions, posted journals and the bank summary report, and with a read permission Xero itself refuses a change from us. If writing is turned on for a business, its owner grants one extra permission from Settings, which lets Ada enter and recode bank transactions the owner approves; Ada does nothing in the books without an approval. The code that does this has not run on any customer’s books.
Permissions asked for: openid profile email offline_access accounting.settings.read accounting.contacts.read accounting.invoices.read accounting.payments.read accounting.banktransactions.read accounting.manualjournals.read accounting.reports.banksummary.read
The extra permission, granted only from Settings: accounting.banktransactions
QuickBooks Online
Intuit offers one accounting permission, which covers reading and writing; there is no read-only version to ask for. That permission would let a change through, so our own gate (a server switch, and your approval of each entry) is the only thing between the connection and a change. The code that can enter and recode payments exists, runs only on an approval, and has not run on any customer’s books.
Permissions asked for: com.intuit.quickbooks.accounting
Sage Business Cloud Accounting
By default we ask Sage for its read-only permission. Sage offers one permission that allows writing, full_access; it includes reading and Sage has no narrower one. If writing is turned on for a business, its owner grants it from Settings, which lets Ada enter payments and receipts and recode entries the owner approves; Ada does nothing in the books without an approval. The code that does this has not run on any customer’s books.
Permissions asked for: readonly
The extra permission, granted only from Settings: full_access
FreeAgent
FreeAgent has no read-only permission to ask for: a connection has whatever access the person who signs in has in FreeAgent. Our FreeAgent code reads bank accounts and balances, bank lines, invoices, bills and contacts. The code that can explain a bank line or change a category in FreeAgent exists, runs only on an entry you approve, and has not run on any customer’s books.
Zoho Books
We ask Zoho for read permissions only, one for each kind of record we read. We cannot create, change or delete anything in Zoho Books.
Permissions asked for: ZohoBooks.settings.READ ZohoBooks.contacts.READ ZohoBooks.invoices.READ ZohoBooks.bills.READ ZohoBooks.expenses.READ ZohoBooks.banking.READ ZohoBooks.accountants.READ
FreshBooks
We ask FreshBooks for read permissions only, chosen on our app there, one for each kind of record we read. We cannot create, change or delete anything in FreshBooks.
Permissions asked for: user:profile:read user:invoices:read user:bills:read user:bill_vendors:read user:expenses:read user:clients:read user:payments:read
Gmail
Quidwise asks Google for permission to read and send mail. Ada looks for invoices, receipts, statements, HMRC letters, remittances, reminders and demands. When you ask about a message or document, Ada can also search the connected mailbox and read related threads. Spam and the bin are never searched. Ada’s desk uses the send permission under your email approval rules. The permissions do not allow Quidwise to delete, move, label or change messages. The Gmail section of our privacy policy explains what Quidwise keeps and shares.
Permissions asked for: https://www.googleapis.com/auth/gmail.readonly https://www.googleapis.com/auth/gmail.send openid email
Microsoft 365 and Outlook.com
Read mail and send mail, plus the permission to know whose mailbox it is and to stay connected between visits. Junk Email, Deleted Items and Drafts are never read. We do not ask for the read-write mail permission, so we cannot change your mailbox.
Permissions asked for: offline_access Mail.Read Mail.Send User.Read
Any other mailbox (IMAP)
You give an app password for the mailbox. We test the login before anything is saved, then store it encrypted like every other credential. Junk, Trash and Drafts are never read. Connections use TLS only. Ada sends through the same login over SMTP under your email approval rules.
HMRC: the VAT return and Income Tax updates
To file from Quidwise, an owner signs in to HMRC on HMRC’s own page with the business’s Government Gateway; Quidwise never sees that password. It receives HMRC’s permission instead, encrypted at rest and never shown: HMRC renews it every four hours and ends it after 18 months, or at once when the owner presses Disconnect on the Tax page. For Income Tax, Quidwise also keeps the owner’s National Insurance number, encrypted. A VAT return or an Income Tax update is sent only after an owner has approved those exact figures and ticked the statement HMRC requires, and every sending carries the device and connection details HMRC’s fraud prevention rules require. Filing the VAT return from Quidwise waits for HMRC to approve Quidwise; Income Tax runs against HMRC’s test service only.
Permissions asked for: read:vat write:vat read:self-assessment write:self-assessment
Staffology by IRIS: the monthly contractor return (CIS300)
To file a business’s monthly CIS300, HMRC needs the business’s own Government Gateway user ID and password. Those are held by Staffology by IRIS, an HMRC-recognised payroll provider, which files the return with HMRC for the business. When an owner gives them on the Tax page, Quidwise sends them straight to Staffology in one request and keeps none of them: not in its database, not in its logs. It records only that they were given, when, and by whom. “Remove from Staffology”, on the Tax page or in Settings, deletes them from Staffology; after that, Ada prepares each return and a qualified accountant at CIJ Labs files it for you on HMRC’s own service, or your own accountant can.
Staffology receives the business’s name and HMRC references (its tax reference, Accounts Office reference and PAYE reference) and, for each person or firm paid on the return, their name, tax reference, kind of business and the month’s payments, materials and deductions. Its records also require a date of birth: where the owner has not given one, Quidwise sends a fixed stand-in, 1 January 1980, which is not part of HMRC’s return. Every return is filed only after an owner has approved that exact return and ticked HMRC’s declaration; a change to the figures withdraws the approval. Filing through Staffology is built and not yet open to customers.
Companies House: the confirmation statement
A company’s confirmation statement goes to Companies House through Quidwise only after an owner has approved that exact statement and ticked its three statements. CIJLABS LIMITED is the presenter: Companies House receives the statement from CIJLABS LIMITED’s presenter account, with the company’s authentication code. The company authentication code, and each director’s Companies House personal code and date of birth, are stored encrypted and used only to file what the owner approved. They are never shown again after they are saved, never written to a log and left out of the data download, and they are deleted when the owner removes them (Remove, on the Tax page or in Settings) or when the business’s data is deleted. Filing from Quidwise waits for Companies House to approve Quidwise’s filing software. Until then, a qualified accountant at CIJ Labs files it for you on Companies House’s own service, or your own accountant can.
What we keep from your email
For each email about money we store the sender, the subject, the date, an extract of up to 300 characters, the amount, due date and invoice number found, a one-line summary and the names of the attachments. PDF and Word attachments are read for their figures (statement balances, invoice totals, sums demanded in letters) by fixed rules on our server; each figure is kept with the file name, the email it came from and the words it was read from. An email that matched the search but turns out not to be about money is kept only as a dismissed line (sender, subject, date, extract) so it is not read again. Email that never matches the search is not fetched.
How you approve outgoing email
A business owner can approve an exact draft in the app or by replying YES to the numbered item on WhatsApp. Only owners can approve it, and a second approval cannot send it again.
Signed standing orders can let Ada send eligible friendly reminders and statements. They wait 10 minutes by default so you can stop them, and you can change that wait in Autopilot. Firm reminders and final notices always need separate approval.
For other emails, an owner can switch on “Send without asking me” in Ada’s desk settings. This applies only when the owner enters every recipient’s address.
Ada checks each pound figure against your ledger or your own words before a draft reaches the desk. She also checks instructions like “contact only through my solicitor” at the point of sending.
How your credentials are stored
Bank, accounting and mailbox tokens, and IMAP app passwords, are encrypted before they are written to the database with AES-256-GCM, using a key derived from a secret that lives only in the server’s environment and a fresh random nonce for every value. The server refuses to start in production if that secret, or the one that signs sessions, is missing. When a provider refreshes a token, the new one is encrypted the same way as it arrives. HMRC’s permission, the owner’s National Insurance number and the company’s Companies House codes are encrypted the same way; a Government Gateway password given for the monthly contractor return passes straight to Staffology and is never stored. When you disconnect a source in Settings, its encrypted credential is deleted at once, and a disconnected mailbox’s stored emails go with it.
In transit
The app is served over HTTPS. The sign-in cookie is marked HttpOnly and, in production, Secure, so scripts cannot read it and it is never sent over plain HTTP. Every call to a bank, accounting or mail provider goes to that provider’s HTTPS address; the Outlook connector refuses to follow any link that is not on Microsoft Graph, and IMAP and SMTP connections require TLS.
Signing in: a code, or your password
You sign in with a six-digit code sent to your email address, or with the password you chose. The code is stored only as a hash, expires after ten minutes, is retired after five wrong guesses, and is replaced the moment you ask for a new one. Requests are limited to three codes per address every ten minutes, with a separate limit per network address, and the checking of codes is limited in the same way, so a code cannot be found by trying. In production the code is never shown on screen; it exists only in your inbox.
A password is chosen when you sign up (an account made earlier can add one in Settings). It is hashed with scrypt, with a salt of its own, and is never stored or logged in plain text. After repeated wrong passwords, password sign-in for that address pauses for a while; a code by email still works, and signing in with one lifts the pause. Setting, changing or resetting a password signs out every other session.
A correct code or password gives you a signed session cookie for 30 days, or 90 days if you tick “Keep me signed in on this device”. The session is honoured only while you are still a member of the business behind it: remove someone and their session stops working at once.
What Ada can and cannot do
- She cannot move money. No bank connection carries a payments permission.
- She changes nothing in your books without your approval. Xero and Sage are connected with read permissions by default; writing needs one extra permission that the owner grants from Settings. Nothing has been written to any customer’s books.
- She follows your email approval rules and cannot delete, move or alter your email.
- She never files anything herself. She prepares the supporting figures and working. A qualified accountant at CIJ Labs files for you, or your own accountant can. Sending a filing straight from the app to HMRC or Companies House is not open to customers yet.
- She does not compute figures. Code computes every number from your ledger; a guard checks every pound and percentage she writes against those numbers. How Ada uses AI explains the line.
- She remembers only what you tell her yourself. Text inside an email, a bank line or a document can never become a memory or an instruction to her.
- Messages on WhatsApp are checked. An inbound message is accepted only when the provider’s signature on it is valid; in production an unsigned message is refused.
Who can see your data
An owner can invite an accountant by email in Settings. That accountant can see the business’s workspace and act on the inbox if the owner enables it. They cannot approve anything that leaves the business, and removing them ends their access at once.
If an owner sends a case to the Accountant Desk, the CIJ Labs accountant assigned to it can review the filing pack and documents the owner shares for that case, and files what the owner has approved. Your main accountant is a point of contact. Workspace access requires a separate invitation in Settings.
Workspace pages and API calls check which business the signed-in person or API key can access. Only the owner can change what Ada remembers. CIJ Labs staff access your data for support you request, security or legal requirements, as the privacy policy explains.
Deleting your data
Disconnect any source yourself in Settings: its credential is deleted at once, and a mailbox’s stored emails with it. Disconnect HMRC on the Tax page, and remove the company’s Companies House codes or the Government Gateway details held by Staffology in Settings: each goes at once. Delete anything Ada remembers in Settings under “What Ada remembers”; a deletion there is permanent. To delete your account and all of your business data, email info@cijlabs.com from the address on your account with the subject “Delete my data”; the privacy policy sets out the timescale.
Where it runs
The service runs on Railway, with its database on Railway’s PostgreSQL, behind HTTPS. The health endpoint reports whether the server and its database are up and shows no secrets. There are no advertising or analytics trackers on the site; the only cookies are the one that keeps you signed in and short-lived ones that protect a connection while you link it.
What this page does not say
There is no independent security certification behind this page. It describes what the code does, and we will answer questions about any of it. If something here does not match what you see, tell us and we will correct the page.
Report a concern
Email security@cijlabs.com with what you found and how to reproduce it. Please do not test against other customers’ data.
Quidwise CFO provides financial intelligence and analysis, not regulated financial, tax or legal advice. See also how Ada uses AI, the privacy policy and the terms of service.