Your data. Your way out.

If you used the preview form

No deletion request is needed. The form validates the information you send, acknowledges a valid request and discards the submitted values. It does not create a stored waitlist entry or send your information elsewhere. If you have not submitted, close or refresh the page to clear the application’s current form state.

The public form is separate from the protected Meta manager. If you connected Meta in your invited workspace, use its Connections page to disconnect and remove the stored connection, selections and cached platform data. The retained action audit is anonymised.

Revoke platform access

If you have previously granted ADV Pro access through a separate invitation, use the account that authorised it to review the connection:

1. Meta: open your Meta account or business settings and find the business integrations or connected apps area. Locate ADV Pro, review its permissions and remove the connection. Check the affected business and ad account permissions as well.
2. TikTok: open the connected apps or authorisations area for the TikTok account or business account used to approve access. Locate ADV Pro and revoke the relevant permissions.
3. Check that the connection is no longer authorised. Settings names can vary by account type and platform interface. If you cannot find the connection, use the platform’s own help service.

Revocation prevents future access under that authorisation. It does not automatically delete information previously received, and it does not delete your campaigns or account inside Meta or TikTok.

Request removal of connected-service data

If your team received a separate ADV Pro invitation, use the verified support channel or contact person who provided that invitation. Ask for “ADV Pro data deletion” and identify the workspace, the authorising work email, and whether the request concerns Meta, TikTok or the entire workspace. Include an ad account identifier only when needed to distinguish accounts.

Do not send passwords, access tokens or identity documents with the initial request. The service operator should verify your authority using the least information necessary and explain any additional verification before requesting it. Ask for confirmation of the request, its scope and the expected completion date through that same channel.

Deletion of connected-service data should cover retained platform account and campaign information, imported performance data, derived reports and associated connection credentials within the confirmed scope. Any information that must be retained for a specific legal obligation, and any backup expiry period, must be explained by the operator. The manager includes a signed Meta deletion callback and a receipt page showing whether a valid request has been processed. These work when the operator configures the Meta app and deployment.

Before any account connection opens

A verified deletion contact, operating entity and documented deletion timeline must be published before ADV Pro starts collecting connected-account data. The implemented Meta callback must be registered and verified for this deployment before connection access opens. This page does not assert platform approval.

More about privacy

The Privacy notice describes what this site processes today. For questions about a separate invited workspace, use the verified contact accompanying that workspace rather than entering sensitive information into this preview form.