How Drumtap handles your data

The information we collect depends on how you interact with Drumtap.

Waitlist and campaign information: If you join a waitlist, we collect your email address and, where the form asks for it, your name. We may also keep campaign attribution such as UTM source, medium, campaign, content, term, the page where you signed up, and a referring URL so we can understand which conversations brought people to Drumtap.

Uploaded intake files and file records: When an owner or authorized workspace user uploads an intake file, Drumtap processes the file content needed for the workflow and keeps associated file records and metadata. Metadata can include the file name, type, size, timestamps, upload status, storage reference, and the workspace or workflow the file belongs to. The metadata is distinct from the uploaded content itself.

Owner, workspace, and operational information: For an owner account or workspace, we may collect account and authentication details, workspace and dashboard records, billing and checkout metadata, support communications, audit history, device and log information, and other operational data needed to provide, secure, troubleshoot, and improve the service.

We use information to provide and secure Drumtap, review whether a waitlist request is a fit, send transactional or welcome email, operate support and billing, maintain audit and operational records, and respond to requests from account owners and authorized users.

With consent where required, we measure marketing and ad-conversion performance. We may also use aggregated or de-identified metrics to understand product usage and improve Drumtap. Workspace data is not used for advertising and is not sold.

Service boundaries: Drumtap does not use workspace records to build advertising audiences, does not sell workspace data, and does not treat uploaded records as public content. Access to workspace data is limited to the service operation, support, security, and other purposes described here.

We use specialized providers to operate parts of Drumtap. They process information only as needed for their role and our instructions.

Managed database and object storage: A managed database stores account, workspace, file-record, billing, support, audit, and operational data. Managed object storage holds uploaded files and related objects when the workflow requires it.

Stripe: If paid services open, Stripe may provide hosted checkout and process payment and billing metadata. Drumtap does not store full payment-card numbers; hosted checkout is disabled pending legal review.

Polsia email proxy: The Polsia email proxy helps send transactional, welcome, support, and other service email. It may process the recipient address, message content, and delivery metadata needed to send and troubleshoot that email.

Meta Pixel: After you accept non-essential tracking, Meta Pixel may receive browser events used to understand marketing and ad-conversion performance. For a consented waitlist lead event, Drumtap may send a one-way hashed version of the submitted email as conversion-matching data. Meta Pixel is not used to advertise against workspace records.

These providers are service providers or processors for the roles above. Drumtap does not sell your personal information.

Drumtap uses browser state for different purposes. Essential session behavior and waitlist attribution are separate from optional marketing tracking.

Consent choice: drumtap_cookie_consent The drumtap_cookie_consent cookie remembers whether you accepted or declined non-essential tracking so the consent banner does not ask on every visit.

Authentication and session cookies: Auth and session cookies help sign you in, keep your session active, and protect your account. They are essential service cookies and do not depend on marketing consent.

UTM attribution: UTM campaign information may be retained with a signup or other submission to understand what brought the conversation to Drumtap. Declining optional marketing tracking does not remove this first-party attribution needed for the waitlist funnel.

Optional Meta Pixel tracking: Meta Pixel and related marketing events load and send only after you accept optional tracking. If you decline, those events stay off. Declining does not turn off essential session behavior or the attribution described above.

We retain each category of information only for as long as needed for the purpose described here, including providing the service, account and file cleanup, security, support, accounting, dispute handling, and legal obligations. We do not promise a single fixed period because the right period depends on the record and the workflow it supports.

When an account, workspace, or file is closed or no longer needed, Drumtap may delete or de-identify the related content and records through the applicable cleanup process. Some limited records may remain for security, accounting, fraud prevention, audit, or legal reasons.

You can ask us to review account, workspace, waitlist, file, or other personal information for deletion by using the contact path below.

Depending on where you live and subject to applicable exceptions, you may have the right to request access to the personal information we hold about you, correction of inaccurate information, deletion, a portable copy, objection to or restriction of certain processing, and withdrawal of consent where processing is based on consent.

California residents may also have rights under the CCPA and CPRA, including the right to know, access, correct, or delete personal information; to opt out of the sale or sharing of personal information or targeted advertising where applicable; and to limit certain uses of sensitive personal information where applicable. Drumtap does not sell personal information.

We will not discriminate against you for making a privacy request. We may need to verify your identity and clarify the scope of a request before completing it.

To make a request, use the contact page or email us at the address below.

For a privacy question, rights request, or deletion request, use Contact or email us at

We may update this policy as Drumtap, its providers, or applicable requirements change. We will post the revised version here and update the effective date. Material changes may also be communicated through the account or contact information we have on file.