Security & privacy
Your books stay yours
Handing an AI assistant access to the general ledger is not a decision anyone should make casually. Orvanta QBD is built so that the honest answer to “where does our financial data go?” is: nowhere it isn't already.
Built on Intuit's official SDK
Orvanta QBD uses the QuickBooks Software Development Kit — the integration method Intuit sanctions — rather than automating the screen or touching your file directly.
Independently reviewed
The product went through a full security review in 2026, and every finding raised was resolved before release.
Your file is never copied
Orvanta QBD reads your company file live and returns the answer. It builds no database, mirror or warehouse of your books.
Nothing is installed on a server we run
You hold the software, the keys and the logs. Cancelling changes nothing about your access to your own data.
The controls
What protects the connection
Enough detail for your IT and compliance reviewers, without a security whitepaper.
Your data stays on your infrastructure
Both parts of Orvanta QBD run on machines you control. Requests go from your AI client to your server to your copy of QuickBooks and back. Orvanta operates no service in that path and receives no telemetry about your books.
Encrypted, authenticated connections
Traffic between the Orvanta components is encrypted with modern TLS and authenticated on both ends — using either client certificates or signed API keys. Unauthenticated requests are rejected before QuickBooks is ever touched.
Read-only is enforced, not requested
The read-only setting lives on the QuickBooks machine, not in the AI client. Even if something upstream is misconfigured or compromised, a write request is refused at the door.
Access limited to the people and machines you name
Restrict access to specific IP ranges, issue separate credentials per user or application, and scope each credential to the areas of QuickBooks it actually needs. Rate limits protect QuickBooks from being overwhelmed.
Credentials stored properly
Passwords are stored as one-way hashes and cannot be read back. Keys that must be recoverable are encrypted with Windows' own protection, tied to your specific installation.
An audit trail your accountants can use
Every request is recorded in an append-only log on your machine: who, when, what and the outcome. The log records the activity, never the financial payload — and you decide how long it is retained.
For your reviewer
The five questions a security review always asks
Forward this page. It answers them.
- Where does our data go?
- From your AI client to your Orvanta server to your copy of QuickBooks, and back. Nothing routes through Orvanta.
- What can the AI do on day one?
- Read. Write access is off until an administrator turns it on, and it is enforced on the QuickBooks machine rather than in the AI client.
- How do we limit who can use it?
- Issue separate credentials per person or application, scope each one to the areas it needs, and restrict access to named IP ranges.
- What do we have for an audit?
- An append-only log on your own machine recording who asked for what, when, and whether it succeeded — with retention you control.
- What happens if we stop paying?
- Nothing is hosted by us, so nothing is switched off remotely. Your data, keys and logs stay where they already are: with you.
A note on what your AI provider sees
Orvanta QBD controls the path between your assistant and QuickBooks. It cannot control what happens to an answer once your assistant has it — that is governed by your agreement with whoever provides the assistant. If you have data-handling requirements, check them against your AI provider's terms as well as ours, and use read-only mode and scoped permissions to limit what can ever be asked for.
- Start read-only and widen access only where there is a reason to
- Give each person or application its own credential, not a shared one
- Review the audit log the same way you review any other financial system
Get started
Send this to whoever has to approve it
We are happy to join a call with your IT or compliance team and answer questions directly.