You can request deletion of personal data held by DripDM, including data received from Instagram and Facebook. You do not need a paid plan or access to your DripDM account to make a request. Disconnecting an account, deleting a contact, closing a workspace, and canceling billing are different actions.
1. Request account, workspace, or associated-data deletion
- Email privacy@dripdm.com with the subject Delete my data. If possible, use your account email; if you no longer have access, explain that in your request.
- Identify your account email, workspace name or ID if known, and the relevant Instagram handle or Facebook Page. Say whether you want to delete an entire workspace, an account's personal data, or data about a particular contact or conversation. You can ask for a copy before deletion and identify any exports or integrations involved.
- If you are a message recipient rather than a DripDM customer, identify the business or Page you interacted with and your relevant handle or identifier. You can also ask that business directly. You do not need to create a DripDM account.
- Support may need to verify identity or authority and clarify shared workspace data. Ask for confirmation of the agreed scope, any records that cannot be removed and why, and completion status. Keep your correspondence and follow up by email if you have not received a response.
Do not send passwords, access tokens, payment-card information, or unnecessary identity documents. There is currently no self-service button to delete an entire DripDM account or workspace. These requests require support handling; this page does not promise an automated purge or a fixed completion time. Applicable legal requirements still apply.
2. Stop the connection to Instagram or a Facebook Page
- Open Dashboard → Connected Accounts and choose Disconnect for the Instagram account or Facebook Page.
- You can also remove DripDM from the relevant Meta account's authorized apps or business integrations settings. Meta labels and menus can vary. If you cannot access DripDM, describe that in your email request.
Disconnection inside DripDM clears the stored tokens for that connection, marks it disconnected, disables its automation rules, cancels scheduled or held messages and scheduled nudges, and removes pending gates and captures. It does not delete past messages, contacts, delivery or event history, the account record, or the workspace. After that disconnect, you can connect the same Instagram account or Facebook Page in another workspace. Messages and contacts already stored in the first workspace stay there.
Removing authorization in Meta is not a confirmation that DripDM has deleted stored data. DripDM does not currently implement an automated Meta deauthorization or data-deletion callback. Email support to request deletion and confirmation rather than relying on app removal alone.
3. Disconnect an AI assistant
- Open Dashboard → AI apps and choose Disconnect for that assistant.
- Remove the connector inside the assistant when you also want the server URL gone from that app.
Disconnect revokes that assistant's access on the next call. It does not disconnect Instagram or Facebook, disable automation rules, or delete messages, contacts, or rules. Other assistants stay connected. DripDM stores the assistant token as a hash. The assistant does not receive your Instagram or Facebook token.
4. Delete an individual contact
- An authorized workspace member can open Contacts, find the relevant contact, choose Delete, and confirm.
- This removes the captured contact record and associated sync logs. For a contact with a platform identifier, it also removes matching pending captures and recipient-linked short links and click attribution.
- For related conversations, webhook payloads, delivery records, or other personal data, send a scoped support request as described above.
Hashed suppression identifiers remain to prevent recapture of the deleted contact. Contact deletion is not a general message opt-out or erasure of every related record. Tell the workspace business if you want messaging stopped, and include that request when contacting support.
5. Deletion scope, external copies, and confirmation
A workspace request can cover account and membership data, connected Meta identifiers and tokens, contacts and captured leads, conversations and messages, automation configuration, next-post attachment notices, tracked links, and associated delivery and event records. Support must establish the actual scope and confirm what was removed. Shared workspaces, queues, logs, backups, and suppression records need separate consideration; there is no fixed public retention or backup-rotation schedule on this page.
- Deleting DripDM data does not recall messages already delivered through Meta or delete Meta's own records.
- Previous CSV downloads, Google Sheets rows, or copies uploaded elsewhere remain with their holders. Disconnecting Sheets stops new sync but does not erase existing rows.
- Stripe handles its own payment records. Records required by applicable law or a specific legal obligation may need to remain; request the reason and scope of any exception.
- Cancel any paid subscription separately in Billing and confirm the cancellation in Stripe. Include billing issues in your support request if you cannot access the portal.
This page is an instruction page, not a deletion-status lookup. Ask privacy@dripdm.com for the status and completion confirmation of your request. See the Privacy policy for data handling and rights, and the Terms of service for subscription and account responsibilities.