How Drumtap handles your data

What Drumtap collects

To reconcile what you billed against what your GC paid, Drumtap ingests your accounting exports (QuickBooks Online and equivalents); CSV exports from GC portals (project text + photos); photos of signed POs, change orders and daily logs; and PDFs of unpaid invoices. Drumtap does not currently hold OAuth connections to QuickBooks, Square, or any GC portal — secure connector flows are planned and not active.

To deliver the subscription we also collect your account profile (name, email, company, hashed password), billing metadata handed to us by Stripe, and basic device/log data needed to keep the service secure and running.

Bank access:Drumtap does not currently connect to any bank; banking-feed verification is planned and not active today. Drumtap does not store bank credentials at any tier and never moves funds. No tier currently auto-marks invoices "cleared" based on a payment notice — clearing sits in your books.

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 moves funds at any tier today and has no bank-side connector live.

How we use it

We use the data you load into Drumtap for one purpose: matching each invoice you sent the GC against each payment they actually released, and surfacing the gap. Aggregated, de-identified metrics may inform product direction (for example, "GCs in this vertical pay on day N"), but never in a way that re-identifies your workspace.

We do not sell, rent, or otherwise trade your data. We do not train third-party AI models on it. We do not run advertising against it.

Where it's stored and who sees it

App data is stored in a managed Postgres instance operated by Drumtap's hosting provider. Every connection is served over TLS; the database is disk-encrypted and snapshotted daily. Secrets — connector tokens, session secrets — live in environment-managed storage, never in source.

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.

Authorised Drumtap personnel can access raw data only to act on a support request you opened or to investigate a security incident, and access is logged. See Security for the operational detail.

Stripe and other sub-processors

Drumtap uses a small set of trusted sub-processors: Stripe for subscription billing (their checkout collects the billing details and the card — we never see the card); the platform's email proxy for transactional mail sent on your behalf; the platform's managed Postgres + hosting provider for storage.

Today Drumtap does not hold OAuth connections to QuickBooks, Square, or any GC portal — secure connector flows are planned and not active. Every accounting + portal row Drumtap reads arrives as a CSV export uploaded by the customer.

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. A signed GC-portal sub-token expires on its own clock and leaves no further record of its contents after that.

We keep aggregate, de-identified usage statistics (page hits, error rates) for up to 24 months to keep the product healthy.

Your choices and data-subject requests

Email us at drumtapsupport@gmail.com to export every record Drumtap holds about your workspace, or to erase it. We acknowledge within five business days and complete deletion within thirty.

For data-subject requests that can't be handled from the app (access requests from a former account, corrections on closed data, opt-out requests from a GC the dispute page reached), email us using the address on the Contact section of the Terms. We acknowledge within five business days and complete within thirty.

Changes to this policy

When we change this policy in a material way we email the account contact and post a note on the in-app dashboard. Non-material changes (typo fixes, clarifications) are rolled in silently with a bumped effective date above.

This policy is paired with the Terms and the Acceptable Use policy; together they describe the contract you accept when you subscribe.