privacy
What Threads Deleter stores, why it needs it, and how to get rid of it. Last updated September 2026.
What is stored
When you connect your account, this service stores one record for you in a database in AWS ap-southeast-4 (Melbourne):
- Your Threads user ID and username.
- A Threads access token, so deletions can run while you are away.
- The job you set up: whether it covers every post or only posts older than a date, any text filter, and whether it is a dry run.
- Counts of what has been deleted, skipped and scanned, and the IDs of posts the API refused to delete so they are not retried forever.
Post text is never stored. Posts are read, matched against your filter, deleted or skipped, and discarded.
What it is used for
Only to run the deletions you asked for. Nothing is sold, shared, or used for advertising, analytics or training. There are no third-party trackers on these pages.
How long it is kept
The record expires automatically 120 days after it is created. You can erase it immediately from your status page using "Erase my token". If you remove the app in Threads, Threads notifies this service and the record is deleted then.
Who can see it
The record is reachable only through a link signed with a secret key. Access tokens are encrypted at rest by AWS and are never shown in any page or sent to a browser.
Deletion is permanent
Posts this service removes are deleted through the official Threads API. Neither this service nor its operator can restore them. Threads decides how long deleted posts remain recoverable on its side, if at all.
Contact
This is a personal project run by Logan Han. For anything about this policy, or to have data removed, email logan@han.life.