Request data deletion.

1. Stop further Meta access

In Banyan, select the correct client workspace, open Connections, and use Disconnect for the relevant Meta connection. A client administrator or the agency owner can do this. If you do not have that access, contact your administrator or the privacy contact above.

This removes the local connection token and disables its accounts. You can also review or revoke the app's authorization in your Meta account's business integration settings. Revocation at Meta and deletion in Banyan are separate actions; neither should be assumed to erase copies already stored by the other service.

2. Request deletion of stored data

Email fran@wildbird.com with the subject Banyan Systems data deletion request. Include:

• The email associated with your Banyan account, if you have one.
• The relevant workspace or business name.
• What you want removed: a Meta connection and its associated data, particular reports or business content, your user account, or your entire authorized workspace.
• If needed to identify the connection, the Meta app name or ad-account ID. Do not include an access token.

You do not need to sign in to send a request. If you cannot access your account or cannot identify the workspace, explain that in the email. Never send passwords, API keys, access tokens or patient information.

3. Verification and handling

Wildbird handles requests manually. Identity and authority over the affected information must be verified before deletion. We may ask for limited additional information through an appropriate verification process. A request about one client does not authorize changes to another client's data.

Handling a verified request includes identifying the relevant connection credentials, account metadata, reports, agent knowledge or revision snapshots, access records and recovery copies within the agreed scope. This page is a request channel, not an automatic deletion service. Deletion status is provided by the privacy contact; reply to the same email thread to follow up. If some requested information cannot be removed, the response should explain the reason and scope.

Important: disconnecting is not erasure

Disconnecting does not automatically erase past reports, account metadata, agent snapshots or audit history. Business records have no automatic age-based purge. Server backups keep the latest 14 encrypted snapshots; manual off-server copies may remain longer. Relevant recovery copies must be considered during a deletion request, and deletion is not represented as complete merely because the live connection was removed.

Information already processed by Meta or the AI provider selected for a run is also subject to that provider's own controls and retention. A Banyan deletion cannot itself guarantee erasure from those independent systems. Contact us to clarify which services were involved in your request.