Trust
Built on Meta’s official API.
You approve DripDM in Meta’s login screen. We do not see your password. Comments, DMs, and Page messages go through the API.
3 minute read
What the connect does
Instagram login grants the access the product needs to read events and send replies. You can remove that access in your Meta settings.
A scheduled send stays inside the messaging window. If the window is closed, the send is held.
What this page is not
This page describes the connection method. It does not claim a badge Meta has not issued to DripDM. If that status changes, this page will say so in plain text.
The route name is not evidence of a badge
This page explains official account authorization and API use. It does not establish a Meta Verified badge, a subscription to that program, certification, endorsement, or a guarantee of enforcement immunity. The legacy route is retained so existing links remain useful, while the page title and copy state the narrower claim. Look at the actual authorization flow and revocation options rather than inferring status from a URL or importing another vendor’s trust language.
A workflow to try
During connection, review the account identity and requested access in Meta’s authorization screen. Connect only accounts you are entitled to manage. After authorization, create a small test rule and verify a fresh eligible event from an independent account. If you no longer need the integration, remove its access through the relevant Meta settings and disconnect it in DripDM. Keep the distinction between revoking account access and requesting deletion of stored workspace data.
Checks before you change the setup
Tokens can expire or permissions can be removed, so a once-successful connection is not a permanent guarantee of delivery. The messaging window, private-reply eligibility, recipient preferences, and Meta rate limits still apply. An AI-enabled plan or scheduled message cannot bypass those checks. If the account is restricted, follow Meta’s notice rather than assuming the API connection proves the restriction is impossible. This review did not verify live app-review status or a newly issued platform badge.
Verify account control and stored-data scope separately
An authorization review asks who granted access, which business identity was connected, and how that access is removed. A data review asks what the workspace retains and what deletion process applies. Keep those questions separate from billing and from any external export. A legacy URL containing verified should not collapse them into a badge claim. If you need proof of a specific platform status, ask for current attributable evidence instead of inferring it from wording. This page’s purpose is to describe a bounded technical connection and its limits, not to borrow another vendor’s verification story or promise that every connected account is safe from enforcement.
Questions
Yes. Remove DripDM in your Instagram or Facebook app settings, and disconnect the account in DripDM.
Not necessarily. Revocation stops the integration’s access; workspace data and billing require their own handling. Follow the published privacy and deletion process for stored information and confirm the requested scope. Disconnecting an account should not be described as proof that every export or backup was erased.
The integration can no longer rely on that access. Check connection state and reconnect through the official authorization flow only if appropriate. Revocation does not automatically establish that stored workspace data or external exports were deleted.