How Drumtap handles your sensitive data

What we collect

Drumtap ingests your accounting exports (QuickBooks Online and equivalents); CSV exports from GC portals (text + photos); photos of signed POs, change orders and daily logs; and PDFs of unpaid invoices. Drumtap does not currently hold OAuth connections to any accounting or GC portal — every portal and bookkeeping row arrives as a CSV upload.

Banking connection: banking feeds are planned and not yet live. Drumtap does not currently connect to any bank and does not store bank credentials at any tier — planned banking-feed verification will be read-only and Drumtap will never move funds.

On every shipped tier (Starter today; Pro and Auto planned — Coming next), you upload CSV exports from your accounting software and from the GC portal. Drumtap never queries a bank account at any tier today — and Drumtap never moves funds at any tier. No tier currently auto-marks invoices "cleared" based on a payment notice — clearing sits in your books.

Encryption in transit and at rest

Every connection is served over TLS. App data is stored in a managed Postgres instance with provider-managed disk encryption and daily snapshot backups. Secrets — connector tokens, session secrets — are kept in environment-managed storage, never in source.

Access is scoped to your workspace

Every database query is scoped by where: { userId: user.id } — one user can never read another user's records, and there is no shared cross-tenant account. Sub-tokens used by GC portal dispute pages are signed, single-use and time-boxed, so a forwarded link stops working after its job is done.

Connector credentials

Drumtap does not currently hold OAuth connections to QuickBooks, Square, or any accounting or GC portal — secure connector flows are planned and not active. Every row Drumtap reads arrives as a CSV export uploaded by the customer. When the connector path ships, it will go through each vendor's own OAuth consent screen; Drumtap will store encrypted access and refresh tokens, never account passwords, and will never see the credentials you used to log into the accounting platform itself.

Retention and deletion

Closing your account triggers a soft-delete that purges personally identifying data; financial records are kept only as long as the workspace is active, and backups roll off on the same schedule.

Subprocessors

Drumtap uses a small set of trusted subprocessors: Stripefor subscription billing (Stripe's checkout collects the billing details and the card — Drumtap never sees the card); the platform's email proxy for any transactional mail Drumtap sends through the in-app draft and approval queue; and the platform's managed Postgres + hosting provider for storage.

See the full Privacy Policy or the Terms.