Security & trust

You're handing over bank feeds. Here's how that's treated.

Six practices, stated plainly enough to be held against us — including the one thing we won't claim.

01OAuth, never passwords

QuickBooks and bank feeds connect through official OAuth flows. Your credentials are typed into Intuit's and your bank's own pages — never ours. We couldn't store your password because we never see it.

02Encrypted at rest

Access tokens are encrypted at rest with AES-256-GCM, and everything moves over TLS. Revoking access from your side kills ours instantly.

03Read what's needed, nothing more

The AI reads transaction data — payee, amount, date, memo — because that's what bookkeeping is. It does not read your email, your documents, or anything outside the accounts you connect.

04A human reviews every close

No packet leaves without a person signing off. Automated work with human accountability, not automation instead of it.

05Your books export clean

Cancel and everything remains yours: your QuickBooks stays your QuickBooks, and your history hands off cleanly to whoever comes next. Lock-in is not a retention strategy here.

06Straight answers

We're a young firm and we don't yet hold a formal certification like SOC 2 — and we won't pretend to. Ask us anything specific about our setup and you'll get a specific answer.

Something we didn't cover?

Ask before you subscribe — a person answers, and if we don't do something, we'll say so.

hello@evobookkeeping.com · (435) 500-5796

Comfortable? Then it's a minute.