Account control

Disconnect and data deletion

Revoke Google access

Open Google Account connections, select AdCtrl and remove its access. In the local prototype, Disconnect & revoke requests Google revocation and then deletes AdCtrl's encrypted token file after Google confirms success.

Request deletion of retained records

Email kc@mondaybrew.dk with the subject “AdCtrl data deletion”. Identify the Google or Meta account email you used and the records you want removed. Do not send your password, access tokens or financial account credentials. We will verify the request using the account contact details and confirm what information was removed or must be retained under applicable law.

Revoke Meta access

In the business portfolio that authorized AdCtrl, open Settings > Business settings > Integrations > Connected apps and remove AdCtrl. This revokes that business integration. The Meta workspace’s Check authorization control can verify whether access still works. Remove local connection deletes the encrypted token, review resource identifiers and its operation receipts on the computer or review server running that instance; it does not revoke Meta authorization by itself. Active-file deletion does not establish removal from infrastructure backups. No application-level token backup is configured; infrastructure retention must be established before customer use. Revoke the provider integration as well. Meta business integration tokens can have no scheduled expiry, so revocation is a separate step.

Meta account and performance results are displayed for the authorized tester and are not retained in a reporting database. Separately authorized test recordings, screenshots and sanitized API qualification evidence may be retained in restricted Google Drive or private GitHub storage for provider-review preparation. Removing the active connection does not remove this separate evidence. Include review recordings or qualification records in your deletion request if you want those records removed. We will confirm deletion and explain any applicable retention limitation; active-file deletion is not a promise of immediate erasure of infrastructure or service-provider backups. AdCtrl is still preparing customer-permission review; public customer onboarding is not available.

What disconnection changes

Revoking AdCtrl removes its authorization. Advertising campaigns, products, analytics properties and containers remain in their original Google or Meta accounts. Any separate records already held by those platforms are governed by their own controls and policies.

Messenger and Instagram message test cleanup

Stop each Messenger or Instagram message test and verify that its new AdCtrl Page subscription has been removed before disconnecting. The ten-minute test window does not automatically remove that subscription. Disconnecting deletes the active test code, participant ID, matching test events and reply receipt in this instance, but it does not delete messages from Messenger or Instagram. The Instagram test also keeps the selected linked account ID and username in its encrypted state; local disconnection removes those active-file fields. If authorization was already revoked, remove any remaining AdCtrl subscription through Meta’s controls and request assistance before assuming cleanup is complete.

Resources created during review tests

Disconnecting removes the connection file, tokens and local operation receipts; it does not delete objects created at Meta. Archive the test ad, ad set, campaign and native lead form, delete test comments and the test Page post, delete the staged test product and then delete the empty test catalog before disconnecting. Product deletion needs explicit confirmation, a provider acknowledgment and complete independent absence in its parent catalog. Catalog deletion refuses remaining tracked products or an incomplete/nonempty product list, even if the provider count says zero. The synthetic product is staged/out of stock with zero inventory; this review workflow connects no shop or ad. Page posts and comments can remain public until deleted at Meta. For the marked Instagram comment workflow, first Delete the Instagram test reply, then Delete the marked Instagram test comment. Each needs its own explicit confirmation, provider acknowledgment and complete list readback. If content or access changed, reconcile and clean up in Instagram itself. The app refuses image deletion while tracked test comments/replies remain. Then use the separate Delete the Instagram test post action, with its additional permission and explicit confirmation, to remove an image published by this connection. The app verifies its absence in the authorized account’s media list. Existing posts cannot be selected. You can also remove the test post directly in Instagram. Unpublished Instagram containers are governed by Meta’s expiry. Uploaded ad images and creatives may remain in the account library. Retained review recordings and implementation evidence are separate; contact us to request their deletion.