> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/list-advertise/meta/how-to-delete-your-meta-facebook-connection.md).

# How to delete your Meta/Facebook connection

Learn how to remove your Meta or Facebook connection in Channable or Facebook.

### Channable’s Meta/Facebook connection

Channable's Meta integration (to be used for A/B testing for Ad Creatives) operates as a real-time API proxy. This means that we do not store your Meta ad data, campaign data, Creatives content, or any personal information from your Meta account.

#### What we do store:

* An encrypted OAuth access token (used to communicate with Meta's API on your behalf)
* Your Meta Ad Account ID (used to identify which ad account to connect to)

This data is stored only for the duration of your active connection and is permanently deleted when you remove the connection.

### Option 1 - Remove the Channable connection in Facebook:

1. Go to **Facebook → Settings & Privacy → Settings**.
2. Click **Apps and Websites** in the left menu.
3. Locate "Channable" and click **Remove**. This immediately invalidates the access token, preventing Channable from accessing your Meta account.

### Option 2 - Disconnect in Channable:

1. Log into your Channable account.
2. Open **Company settings**:

{% tabs %}
{% tab title="Modern version" %}
In the company dropdown, select **Company settings**.
{% endtab %}

{% tab title="Legacy version" %}
In the sidebar while in the company, select **Company settings**.
{% endtab %}
{% endtabs %}

3. Go to **Connections**.
4. Locate the Meta connection.
5. In the ‘Edit connection’ column, click **Edit**.
6. Click the cogwheel icon and select **Delete connection**.

<figure><img src="https://3067532480-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF8GepmoSonQRG6RnHOxJ%2Fuploads%2Fy0DHThHWzSwQiWjA7E5r%2Funknown.png?alt=media&amp;token=74688c4a-3db9-43b7-8779-6121ea226a04" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3067532480-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF8GepmoSonQRG6RnHOxJ%2Fuploads%2Fu0j18jtBAEEBCpymfLay%2Funknown.png?alt=media&amp;token=bbc0797d-b7b6-4832-8532-cbe0d6f87a2b" alt=""><figcaption></figcaption></figure>

### What happens next

* Your encrypted access token is deleted
* We’ve removed your ad account details from our database
* All project links to the connection are cleared
* No data traces of this connection remain in our system and we don’t keep any backups of this data

For more information, see our [Privacy Policy](https://www.channable.com/privacy-policy).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/list-advertise/meta/how-to-delete-your-meta-facebook-connection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.