Removal request
Every service below is shown to everyone, because this site looks nothing up. Work down the list in order. The first one does most of the work.
Put your name into the letters
Typed here, used here. What you type is substituted into the addresses and letters below by your own browser and is never sent to this site. You can confirm that: disconnect from the internet after this page loads and it still works.
Three steps, and there is no fourth
- Delete at the source. On X, in the order given below.
- Check each holder. One link per service, opened by you.
- Send the requests. Our text, your send button.
There is no verify step. This side counted nothing to begin with, so it has nothing honest to compare against.
8 services, in the order worth doing them
The source every other copy was made from. More of the remedy lives here than anywhere else.
- Edit or overwrite a post before deleting it, wherever the app lets you. A plain delete leaves the original wording intact in anything that already copied it.
- Delete the posts you want gone. This is what stops the research datasets below from reproducing them.
- Check your media and replies separately. They are easy to miss and were copied the same way.
- Consider making the account private while you work. It removes nothing already taken, but it stops new copies.
- Delete the whole account last, if at all. See the caveat.
Worth knowing. Deleting the account is irreversible, it is not needed for any of the steps above, and doing it first takes away your ability to do them. On some services it also changes who a post appears to belong to rather than removing it.
What this covers. Deleting here does not touch a snapshot someone already saved to a web archive. Those need their own request, further down.
Typical response time: Unknown. Route last checked 2026-08-10.
Holds snapshots of specific pages that a person or a crawler chose to save. It is not a list of everything you posted, and it cannot be searched that way. You check the addresses it might hold.
Subject: Request to remove archived pages Hello, I am writing to ask that you remove archived copies of pages from the X (formerly Twitter) account @yourhandle, which I control. The pages are at these addresses: https://twitter.com/yourhandle https://x.com/yourhandle [add the specific snapshot addresses you found] I controlled this account during the period the snapshots were taken. Please exclude the archived copies covering [state the dates]. Thank you for your time. [your name]
If what you are dealing with is an intimate image shared without your consent, there is a separate and faster route. Read that instead.
Worth knowing. The Internet Archive states that it makes no guarantee beforehand about the outcome of a request. Naming the exact addresses and the period you controlled the account is what gives one the best chance.
What this covers. This covers pages that were actually snapshotted, not your whole account. Most posts were never saved by anyone.
Typical response time: Unknown. Route last checked 2026-08-10.
Keeps readable copies of threads that somebody asked its bot to unroll. If you wrote threads and anyone asked for them to be unrolled, copies may sit here. The removal story is the best of any operator on this page.
- Log in there with your X account and delete the stored threads directly. This is the fastest route and needs nobody's permission.
- Post the exact text @ThreadReaderApp BLOCK ME from your account to opt out of future unrolling. It is case sensitive.
- Deleting a thread on X also removes it here, because the service syncs deletions. The operator states this can take up to 24 hours.
- Write to hello@threadreaderapp.com if something is still there after that.
Worth knowing. Opting out stops the bot unrolling your threads in future. Someone can still ask, and the app replies that the author declined.
What this covers. Only threads somebody actually asked to unroll are here. Most accounts have none.
Typical response time: Unknown. Route last checked 2026-08-10.
Sells bulk datasets of X posts and profiles collected from public data. Unlike the archives on this page it is a company, which means it has legal obligations a hobby archive does not.
Subject: Data subject request, deletion Hello, I am making a request regarding personal data you hold about me. I am the holder of the X (formerly Twitter) account @yourhandle. I understand you collect and sell datasets of public X posts and profiles, which may include mine. I am requesting: 1. Confirmation of whether you hold personal data about me. 2. A copy of that data, if you do. 3. Deletion of that data. Please confirm receipt and tell me what you need from me to verify my identity. [your name] [your country of residence]
Worth knowing. Named because it publishes a self-service tool and a clear process, not because it is the only one. It is one of a class, and there is no list of every company reselling X data. Deletion can also be refused where a legal exception applies. Expect an identity check.
What this covers. There is no way to see what a broker holds about you without buying access, so this is a request made without knowing the answer. Rights are strongest in the EU, the UK and California.
Typical response time: Unknown. Route last checked 2026-08-10.
Holds manual snapshots of individual pages, including posts, and is built to resist removal.
There is a report form on each snapshot and there are contact addresses for the operator, but there is no reliable process behind them. Removal is done by hand by the maintainer, requests are expected to come from someone who owns the site the page was on rather than the person in it, and they are frequently ignored. No turnaround is published.
If a snapshot of yours is there and it matters, a lawyer in your country is a better next step than the report form.
Route last checked 2026-08-10.
Maps an X handle to the previous handles and account numbers it has used. It holds no posts. It holds the trail that connects an old name to a current one.
There is no published opt-out and no removal form. The only route is writing to the operator directly, and the project is built for research rather than to process removals.
If your plan was to rename the account and move on, this is the kind of service that defeats that plan.
Route last checked 2026-08-10.
A paid lookup service for X handle and profile history. Same shape of problem as memory.lol, behind a payment.
No documented removal or opt-out route of any kind. Named so you know it is there.
Route last checked 2026-08-10.
Large public datasets of X posts, published by universities and researchers. There are many, and you cannot enumerate them.
X's rules let these datasets share only post identifiers, never the text. A researcher turns an identifier back into a post by fetching it from X. Once you have deleted the post, the identifier resolves to nothing and it cannot be reassembled.
So deleting at the source neutralises every one of these at once, and there is nothing for you to send to anybody. It is the one place on this page where the first step finished the job.
Worth knowing. The limit: a researcher who already fetched the content and kept their own private copy still has it, and no removal process anywhere reaches that. It is a real gap, but it is not a channel with a route, so there is nothing to file.
Route last checked 2026-08-10.
Services people still look for
Both died after X removed the access they ran on, which is the same event that shaped this whole page. Listed so you do not spend an evening looking for a way to contact them.
- Nitter. A privacy front end that mirrored X. The public instances collapsed during 2024 after X removed guest access. There is nothing left to file against.
- Politwoops. Archived politicians' deleted posts. Shut down in 2023 after losing API access.
Nothing here is a guarantee. This tool prepares requests. A person at each service decides whether to act, and may decline.