Data deletion
Data deletion
This page explains the difference between disconnecting a Threads account and requesting deletion of your threads-ai application data.
1. Disconnecting Threads
Use Disconnect Threads from your account page when you want to stop using the connection. This immediately removes the usable encrypted Threads credential, invalidates existing MCP access, and ends the current browser session. It does not delete the entire account record or the operational records needed to describe past threads-ai-created objects.
2. Deleting content on Threads
Use the threads_delete_post MCP tool or Threads directly to remove public content before requesting full data deletion. The tool can only delete posts and replies that threads-ai recorded as having created. A data-deletion request removes threads-ai application data; it does not by itself remove content from Threads, copies, caches, or other services.
3. Requesting full application-data deletion
To request deletion of data associated with your Threads account, use Meta's data-deletion controls for the Threads AI app. Meta sends threads-ai a signed request. After verifying that signature, we delete the matching D1 account, Threads connection, published-object, and idempotency records. The request is safe to repeat if Meta sends it again.
4. Confirmation
After a verified request, threads-ai returns a confirmation URL and code to Meta. The code is random, is not an account credential, and is retained for up to 30 days only to confirm the request was received.
5. Need help?
If you cannot use Meta's controls or have a question about deletion, contact support@lessontwo.co. To protect account data, we may need information that lets us verify the relevant Threads account before acting on a request.