Data deletion

1. Disconnect vs delete

Disconnect (Social Connections in the Avexio dashboard) stops Avexio from using that provider connection for the selected business. It removes or burns locally stored OAuth credentials for that connection according to the product implementation and clears related destination selection. It does not by itself delete your Avexio account, generated content, or all historical publication records.

Delete Avexio account/data is a separate request. The product does not currently expose an automated account-deletion control. Email support@avexio.ai to request a copy of your information or deletion of your Avexio account or data. We review requests manually.

2. Google / YouTube

If you connected YouTube, you can disconnect it from Social Connections in the Avexio dashboard for that business. Disconnecting disables the local YouTube connection and removes or burns locally stored Google OAuth credentials for that connection in Avexio. Avexio also attempts Google-side token revocation for that connection. Local credentials are removed or burned even if the Google revocation request fails. Disconnecting YouTube is not the same as deleting your Avexio account, content, or publication history.

Separately, you can revoke Avexio’s Google authorization from your Google Account (for example, Google Account → Security → Third-party access / Your connections to third-party apps). Revoking on Google stops future authorized API use under those credentials. It does not by itself delete Avexio workspace content or historical Avexio records.

Avexio does not currently implement an automated Google/YouTube data-deletion callback. For Avexio account or data deletion requests related to Google/YouTube use, email support as described above.

3. Disconnect Facebook in Avexio

If you connected a Facebook Page, you can disconnect it from Social Connections in the Avexio dashboard for that business.

When you disconnect:

• Avexio removes stored Facebook authorization credentials and access tokens for that connection.
• The selected Facebook Page connection is disabled, and Avexio stops accessing or publishing to that Page through that connection.
• Avexio makes a best-effort request to Meta to revoke the corresponding permissions. That Meta request can fail; disconnect still completes on Avexio.

Disconnecting does not by itself delete Avexio-created marketing content or all historical operational records. See the Privacy Policy for what may be retained.

4. Removing Avexio from Facebook

If you remove Avexio from Facebook (deauthorization), Avexio will stop accessing Facebook and publishing through that Facebook identity for matching connections. Stored authorization credentials are removed, the selected Facebook Page is cleared, and future Facebook publishing through that identity is stopped. Historical Facebook-related records in Avexio (for example Page identifiers, published post identifiers, permalinks, and engagement metrics already collected) may remain. Deauthorization is not the same as a Facebook data-deletion request.

Avexio implements a Meta deauthorization callback. When that callback is configured on the Meta app dashboard and running in a production deployment, Meta can notify Avexio when you remove the app. Until that production configuration is in place, you can disconnect Facebook in Avexio as described above, or contact support@avexio.ai.

5. Facebook data-deletion requests

You may request deletion of Facebook-related data through Meta’s user data deletion process for the Avexio app. That is stronger than disconnect or deauthorization: it removes or anonymizes Facebook-sourced connection data associated with the request.

Avexio implements a Meta User Data Deletion callback. When that callback is configured on the Meta app dashboard and running in a production deployment, requests received through Meta will remove or anonymize Facebook-sourced connection data associated with the request. Meta provides a confirmation link you can use to check status. Until that production configuration is in place, Facebook data-deletion and related privacy requests can also be sent to support@avexio.ai.

6. Facebook-related data Avexio may hold

Depending on how you used Facebook with Avexio, Facebook-related data may include:

• Facebook connection identity
• Connected Page identifiers and names
• Authorization credentials and access tokens
• Meta-derived engagement information for posts Avexio published

Avexio-created content (for example posts, images, and videos generated in your workspace) and appropriate non-Meta operational records may be retained where they are not Facebook-sourced personal or Page data and where retention is described in the Privacy Policy. This page does not add fixed deletion deadlines.

7. Contact

Privacy and deletion requests: support@avexio.ai. You can also use our Contact page.