Privacy policy

1. Who handles your data

DripDM is currently operated by an individual service provider, not a separately incorporated company.

The operator of DripDM handles account administration, billing, support, and service security. For contacts, messages, and leads in a customer workspace, the customer determines how that data is used and DripDM processes it to provide the configured service on their behalf. Your relationship with that business is also subject to its privacy notice.

If your request concerns a business using DripDM, contact that business or email us with enough information to identify the relevant workspace. You do not have to be a DripDM account holder to ask about your data.

2. Account, workspace, and billing information

• Name, email, and a password hash for password-based accounts.
• Provider identity, name, and email returned by Google or Facebook when you use an enabled social sign-in.
• Workspace membership, roles, invitations, plan, usage, and onboarding status.
• Session, verification, password-reset, and OAuth authorization records used to secure access.
• Stripe customer and subscription identifiers, subscription status, plan and billing-period information. Stripe handles payment-card details in its checkout and portal.
• Support correspondence and relevant technical, error, and security records.

Social sign-in and connecting a messaging account are separate actions. We do not ask you to give DripDM your Instagram or Facebook password.

3. Instagram, Facebook Pages, and webhook data

Depending on the connection and permissions you authorize, we process:

• Instagram account identifiers, usernames, account type, and available profile information.
• Facebook Page identifiers, names, profile-picture URLs, and the list of eligible Pages used by the connection picker.
• Access tokens, expiry and connection status, and webhook subscription information used to make authorized API calls.
• Sender and recipient identifiers, usernames and profile information returned by Meta, message text, comment text and identifiers, post or story references, and timestamps.
• Attachments or related metadata supplied in webhook events, message echoes, reactions, postbacks, and other supported messaging or comment events.
• Automation rules, templates, knowledge notes, pending actions, delivery records, conversation history, and event-processing records, including received event payloads.

Page-picker candidates and their encrypted tokens can be stored while you choose which Pages to connect; candidate availability expires. Connected Pages are stored for your workspace. Expiry of a candidate does not by itself mean every underlying record has been purged.

Tokens authorize configured actions such as subscribing to events, reading supported account or conversation information, and sending replies. They are not used to obtain your Meta password. Data received from Meta is used within the permissions and platform rules applicable to the connection, not as permission to access unrelated accounts.

4. Contacts and link measurement

Contacts can include captured email addresses, phone numbers, platform identifiers, source automation and media references, and capture or last-seen timestamps. Workspace users can view and export contact data.

Tracked short links record click time, link and automation references, available recipient identifiers, a browser user-agent string, and a salted IP-address hash whose input changes by UTC day. The click table stores the hash rather than the raw IP address. This is pseudonymous measurement, not a guarantee of anonymity: recipient-linked clicks may be associated with a conversation. Servers and network infrastructure still receive IP addresses and may log them separately.

5. Why we process data

• Authenticate users, administer workspaces, and secure authorization flows.
• Run customer-configured automations, manage conversations, deliver replies, and capture contacts.
• Store an in-app notice when a next-post comment rule attaches to a post or Reel. The notice names the rule and that media. It stays on the Automations page until a workspace user dismisses it.
• Measure delivery and link activity and apply plan or usage limits.
• Provide enabled integrations, process subscriptions, and send account invitations, verification, or reset email.
• Respond to support and rights requests, investigate abuse, and meet applicable legal obligations.

Customers must provide required notices and obtain legally sufficient permissions before messaging, capturing contacts, or exporting data. Applicable law determines the legal basis for each processing activity and the rights available to you; contact us about the basis relevant to your data. Use of the service is not blanket consent to unrelated processing.

6. Optional AI processing

Enabled AI replies can send the triggering message, up to ten recent conversation turns, and the rule's goals, instructions, and knowledge notes to the operator-configured chat-model endpoint. AI topic matching sends a topic and message text; preview requests send the sample and instructions you supply. Generated replies can be sent through your automation.

The reply feature calls a model to generate or classify text; it is not a DripDM model-training feature. This does not establish the provider's retention or training practices. Those depend on the selected provider and its agreement and configuration. Ask us for the provider and applicable handling details before enabling AI for personal data. Do not include unnecessary sensitive information in samples or notes.

7. Recipients and integrations

Data is shared as needed for the feature or purpose described here:

• Meta receives authorized API requests and outbound message or comment content for Instagram and Facebook Pages; Meta supplies login and webhook data.
• Stripe processes checkout, subscription management, and payment information; DripDM keeps billing references and entitlement state.
• Google provides social sign-in when configured. If you connect Sheets, sync can write captured email, phone, username, source references, and a timestamp to your chosen spreadsheet.
• Google reCAPTCHA checks password login and account signup. Google receives the check token and related browser data. The Google Privacy Policy and Terms describe that processing.
• Resend delivers account email when configured, receiving recipient addresses and the email content.
• The configured model provider receives the AI inputs described above when those features are used.
• Hosting, database, queue, and operational service providers process data to run DripDM. Contact us for the current providers and locations.
• Authorized workspace members can access data within their assigned role. Recipients and destination services receive the content you send or export.

Direct Meta Ads audience upload is currently disabled. Downloaded CSVs or data you upload elsewhere are separate copies under your control. We do not sell personal data. Disclosures required by law or necessary to address security or platform issues remain subject to applicable law and the restrictions on sharing Meta Platform Data.

8. Cookies and external services

DripDM uses functional cookies for access and refresh sessions, onboarding state, the last login method, and short-lived OAuth authorization checks. Session cookies last up to 400 days. Login, refresh, and loading your account set them again, so an active session continues. The access token is a signed token with that same lifetime. The server checks it with a signing secret that stays in place across deploys. OAuth attempt cookies last up to 10 minutes. Logout clears the session cookies. Blocking these cookies prevents sign-in or connection flows. Browser local storage also remembers your inbox sound preference.

DripDM does not implement advertising or marketing-attribution cookies in these flows. External sign-in, payment, and linked websites may use their own cookies and have separate privacy policies. Password login and signup also load Google reCAPTCHA. Google can set its own cookie during that check. Cookie controls in your browser do not delete records already held by DripDM.

9. Retention and disconnection

Workspace data is retained to provide the service while it is needed for those purposes. DripDM does not currently provide an automatic workspace-deletion job or a fixed public purge schedule. Ask support for the deletion scope and completion confirmation. Log and backup retention depend on operational configuration; no automatic 30-day database purge or 90-day backup expiry is promised here.

Disconnecting an Instagram account or Facebook Page in DripDM clears its stored connection tokens, marks it disconnected, disables related automation rules, cancels scheduled or held sends and scheduled nudges, and removes pending gates and captures. It does not delete the connected-account record, contacts, past messages, delivery history, or the whole workspace, and does not cancel Stripe billing. After that disconnect, the same Instagram account or Facebook Page can be connected in another workspace. Messages and contacts already stored in the first workspace stay there.

Removing DripDM in Meta settings changes permissions on Meta's side; do not treat that action alone as confirmed deletion from DripDM. Disconnect in DripDM where possible and send a deletion request below. Disconnecting Sheets stops new sync and clears its stored refresh token, but leaves rows already written to your spreadsheet.

Some records may need to be retained for applicable legal obligations or claims. Any exception must be assessed for the specific record and applicable rules; it is not a blanket right to retain Meta data. Payment providers and export destinations handle their own copies.

10. Access, correction, deletion, and other rights

Depending on applicable law, you may have rights to access or receive a copy of your data, correct it, request deletion or restriction, object to processing, withdraw consent where processing relies on it, or complain to the relevant data-protection authority. Withdrawal does not undo processing already lawfully performed.

Follow the Data deletion instructions or email privacy@dripdm.com. Include the relevant account, workspace, or Instagram/Facebook handle and what you are requesting. We may need information to verify your identity or authority; do not send passwords or access tokens. Requests are available even if you cannot sign in or are not a paying customer.

Deleting a contact in Contacts removes the captured record, associated sync logs, and matching pending captures and recipient-linked click attribution. Hashed suppression identifiers are retained to prevent recapture. This does not itself erase message history, all event or delivery records, or prior exports. Ask support about associated data and any suppression record as part of your deletion request.

11. Security and processing locations

The connection code encrypts stored Meta tokens and verifies webhook signatures. These measures do not guarantee that every system or transmission is secure. Use secure connections and report suspected vulnerabilities to privacy@dripdm.com without including secrets.

Processing locations depend on the hosting and integration providers used for the service and may be outside your country. Contact us for the applicable locations and transfer arrangements. This policy does not assert that a particular transfer safeguard has been put in place without verification, or treat service use as blanket transfer consent.

12. Children, changes, and contact

DripDM accounts are for business users aged 18 or older. The service is not directed at children. Contact us if you believe a child's personal data has been collected through DripDM.

The date above identifies this policy version. Material changes will be communicated through the app or email as required by applicable law. Questions and rights requests go to privacy@dripdm.com. See also the Terms of service.