1. Revoke authorization
Remove Goodwin CRM access from the applicable Facebook or Meta settings. Interface labels may change; revocation controls future access.
Revoking Meta authorization stops future access; a deletion request addresses information already held by the service. These are separate actions, and each request must be verified before action is taken.
These steps describe the planned, reviewable process. They do not promise a response deadline or outcome that has not been legally approved.
Remove Goodwin CRM access from the applicable Facebook or Meta settings. Interface labels may change; revocation controls future access.
Provide a name, work email, company, privacy category, and enough non-sensitive context to identify the relevant workspace or Page.
Use the Privacy category on the contact form when delivery is available, or the support route supplied during private-beta onboarding. Never send passwords, tokens, credentials, or customer messages.
The request process verifies identity and authority before a request is fulfilled and may require additional information through a safer channel.
A verified response should explain what was deleted or identify any information that must be retained under a reviewed legal obligation.
The contact form shows whether inquiry delivery is available. If you participate in the private beta, you may also use the support route supplied directly during onboarding.
Include your name, work email, organization, the Page or workspace context that you are authorized to reference, and whether you are asking for deletion, correction, access, or disconnection help.
Do not include a Facebook password, authentication code, access token, API key, credential, full customer conversation, attachment, or regulated information. A reviewer may need to request a safer verification step through a monitored channel.
The privacy notice explains the information used for inquiries, anti-abuse controls, retention principles, and request choices.