Security & privacy

How Databookly protects your QuickBooks connection and your clients' data.

Your QuickBooks connection

  • Intuit's official sign-in. You approve access on Intuit's own page, and Databookly never sees your Intuit password.
  • Only what's needed. Databookly asks for QuickBooks Online's accounting permission. It doesn't ask for Payments, Payroll or your Intuit profile. See what Databookly can access.
  • Encrypted at rest. The connection's access tokens are encrypted (AES-256-GCM) before they're stored, and are only ever used for the workspace they belong to.
  • Single-use, short-lived connection links. Each attempt to connect expires after 10 minutes and works once, for the person and workspace that started it.
  • One company, one workspace. A QuickBooks company can't be connected to two workspaces at once.
  • Revoked when you disconnect. Disconnecting revokes Databookly's access with Intuit straight away.

Access to your books

  • Separate workspaces. Every request is checked against the workspace's members and their role. People only reach the workspaces they belong to. See Roles & permissions.
  • Audit log. Connecting and disconnecting QuickBooks and other important changes are recorded with who did it and when. The log is written together with the change itself.
  • Your sign-in. Sign in with Google, or with your work email and a password. New email addresses are verified with a one-time code. If your account has two-step verification turned on, Databookly asks for your code.

AI features

Auto-select and reading your evidence files use Google's Gemini models. Databookly sends what's needed for the task: the bank line's description, amount and date, the evidence file you uploaded, and your Client's business description. To learn what an unfamiliar vendor does, the AI may run a web search on the vendor's name.

AI only fills in suggestions. Nothing reaches QuickBooks until a person posts it and clicks Send to QuickBooks.

On this page