QuickBooks Integration · updated 2026-08-22

Security model: how your QuickBooks credentials and data are protected

Everything the integration does to keep your books and your Intuit access safe, in plain language.

1. 1

   OAuth 2.0 with Intuit, never passwords

   Connecting uses Intuit's official OAuth flow: you sign in on Intuit's own page and authorize the specific QuickBooks company. Dumpster Controls never sees or stores your Intuit password. The authorization handshake is protected by a signed, single-purpose state token that expires in 10 minutes and is bound to your company and your user, which blocks cross-site request forgery and cross-company injection.

2. 2

   Tokens encrypted and bound to your company

   Access and refresh tokens are encrypted at rest with AES-256-GCM. The encryption is additionally bound to your company id, meaning a ciphertext moved to another company's record will not decrypt. Tokens are never logged, never returned to any browser, and never visible to staff.

3. 3

   Strict access control

   Only owners and admins of your company can connect, disconnect or read the sync log. The tables holding connections, entity maps and the queue are locked to zero direct client access; every read goes through server-side functions that re-verify your role and your company on each call. Even the connect callback re-checks, at completion time, that the person who started the flow is still an admin.

4. 4

   Country guard

   At connection time the integration verifies that the QuickBooks company country matches your Dumpster Controls company country (US with US, Canada with Canada), preventing a ledger in the wrong tax jurisdiction from ever being linked.

5. 5

   Revocation, both directions

   Disconnect in the app revokes the grant with Intuit and destroys the stored tokens immediately. Revoking from Intuit's side (your Intuit account, My Apps) is detected: syncing stops, the connection is marked as needing attention, and the app shows a reconnect warning. Either way, no orphan access remains.

6. 6

   Blast radius by design

   The integration holds the minimum scope (accounting only), touches only entities it created or explicitly matched, and is one-way in V1: nothing in QuickBooks can modify your Dumpster Controls data. Every sensitive action (connect, disconnect, kill switch changes) is audit-logged.