Data Deletion Instructions

We hold two kinds of information, and they are deleted in different ways. Everything stored for your account and workspace - your profile, brand settings, drafts, generated images and schedules - is deleted when we process an account deletion request. The encrypted access token for a connected Facebook Page is deleted the moment you disconnect that Page, or when Facebook tells us you have removed the app.

Signed-in workspace owners can delete a workspace or their account from the Privacy and data page without emailing us. The steps below cover both self-service deletion and the Meta/Facebook deletion route.

Disconnect a Page in the app. Open Connected Accounts, choose the Page and select Disconnect. The stored Page access token is deleted immediately and the Page is marked as disconnected. It can no longer be used for anything.

Remove the app in Facebook. In Facebook, go to Settings & privacy → Settings → Apps and Websites, find WePostSocials and remove it. Facebook then sends us a signed deauthorisation request, and we delete the stored Page credentials and disconnect the Pages associated with that Facebook account. This happens automatically when we receive the request; it is not immediate to the second, but it needs nothing from you.

If Facebook sends us a formal data deletion request, we process it the same way and issue a confirmation code. You can check it on the data deletion status page. That page shows only whether a code is valid; it displays no personal data.

Sign in and open the Privacy and data page. Choose the workspace or account you want to delete. You must re-enter your password and type a confirmation phrase. Account deletion is blocked if you own a workspace with other members; transfer ownership or remove them first. You can also contact support with the subject "Data deletion request" if you cannot sign in.

We may ask you to verify that you control the account before deleting anything. A signed-in owner deletion runs immediately; an emailed request requires identity verification. We aim to respond to a deletion request within one month. If the request is complex, we may extend that period by up to two further months and will explain why.

OWNER INPUT REQUIRED — verified privacy contact and support mailbox confirmation.

When we process an account deletion request we delete the account and the workspaces you asked us to delete, together with the content stored for them: brand profile, drafts, generated images and their stored files, scheduled posts, approval history and connected-account records.

Connected Facebook credentials are deleted as part of this, whether or not you disconnected the Page first.

Backups. Deleting records from the live service does not instantly remove them from every backup copy. Backup copies are overwritten on their normal cycle, so a residual copy may exist for a limited period before it is replaced. We do not restore deleted accounts from backups.

Legal and accounting records. If you have paid for a subscription, we keep the invoices and transaction records the law requires us to keep for the statutory period. They do not include your content.

Facebook's own copy. We can only delete what we hold. Posts, photos or Page information that you published to Facebook remain subject to Facebook's own retention until you delete them there.

Analytics and logs. Server logs are kept for security and troubleshooting for a short period and then rotated. They are not used to rebuild anything you have asked us to delete.

If you removed the app but your Page still appears connected, email us with the Page name. It usually means Facebook did not send us a request we could match to a connection - for example because the connection was made under a different Facebook account - and we will remove it manually.

You can also contact us to ask what data we hold about you, or to correct it, as described in our privacy policy.

If you are not satisfied with our response, you may complain to the Information Commissioner's Office at ico.org.uk. Please tell us first so we can try to resolve it.