Request deletion of your Billion data
Account-data deletion is handled manually in the current pilot. There is no self-service Delete account button or automated Meta deletion callback.
- Contact [email protected] with the subject Billion data deletion request.
- Include the email or sign-in method you use, the organization or brand concerned and what you want removed. If the request concerns Meta data, say which connected Facebook Page or Instagram account is involved.
- The operator will need to verify that you are entitled to make the request. Do not send passwords, access tokens or identity documents in your first message.
The operator must assess your request under applicable law and explain the action taken, any necessary identity checks and any information that must be retained. This page does not promise an automatic deletion deadline.
Disconnect Facebook or Instagram
In Billion, open Social connections, select the right brand and use Disconnect on the connected account. An organization owner or administrator can do this.
This removes that brand’s local connection credentials and pending authorizations. It does not delete your Billion account, drafts, uploaded media, review history or publishing receipts. It also does not remove Billion’s authorization from your Meta account. Manage that separately in Meta’s app or business-integration settings.
What a request can cover
A request can cover your account information, connected-account data and personal information held in workspace content. Team or client content may also involve another organization’s instructions or other people’s rights, so deleting a member account is not automatically permission to erase an entire brand.
Content already published on a social network is a separate copy. Removing it from Billion does not remove a live post; use that network’s own controls or an authorized Page administrator.
Records that may need to remain
Some records may need to be retained to meet a legal obligation, establish or defend a claim, or protect the service and reconcile an already-started request. The operator must assess the need for each exception and explain what remains and why. A disconnected account does not authorize another publishing attempt.
The operator’s retention and backup periods are not confirmed in this draft. They must be reviewed before these instructions are used for a public app.
Who handles the request
For the wider data notice, read the Privacy policy.