Security
Your books are read,
never touched.
Financial data deserves specifics, not badges. Here is exactly how FinOpHQ handles yours, and where the full written policies live.
The rules the product is built on
Read-only, by architecture
Every connection (QuickBooks Online, Jobber) is authorized through that platform's own sign-in with read-only scope. FinOpHQ cannot write, edit, or delete anything in your books. There is no code path for it.
Your credentials never touch us
You sign in at Intuit or Jobber, on their pages. FinOpHQ receives an access token, never your password. You can revoke that token from the platform's own connected-apps page at any time, independent of us.
Sealed per user
The access keys the platforms hand us are stored encrypted, each user's sealed under its own key (not one shared secret) and never shared with any third party.
Accounts walled off from each other
Your data is fenced off inside the database itself, not just by the app's code, so one account can never read another's, even if someone tries to trick the system. For your IT friend: Postgres row-level security, enforced and forced.
A snapshot, not a hoard
Your dashboard is built from a snapshot of your books that is replaced on each sync, not an ever-growing archive. Disconnect an integration and its data is removed; delete your account and everything goes with it.
Two-step verification
Available on every account, and required before a bank account can be connected: enforced at the database layer, not just the sign-in screen.
Controls you hold yourself
Delete everything, yourself. Account deletion is self-serve, inside the app. It removes your account and every stored record, no email thread required.
See what happened. An append-only activity log records the security-relevant events on your account, and you can read it.
Leave without asking permission. Revoke FinOpHQ's access from Intuit's or Jobber's own connected-apps page any time. The disconnect works even if you never open FinOpHQ again.
The policies, in writing
Every claim on this page is backed by a published, versioned policy: the same documents provided to the platforms FinOpHQ integrates with:
- Privacy PolicyWhat's collected, why, and your rights over it.
- Terms of ServiceThe agreement, in readable English.
- Data Retention & Disposal PolicyHow long each kind of data lives, and how it dies.
- Information Security PolicyAccess control, patching timelines, and how often it all gets reviewed, versioned, with its revision history.
Ask the hard question.
If something here is unclear, or your accountant wants specifics, write and you'll get a direct answer, not a ticket number.
michael@finophq.com