Removal request
Every service below is shown to everyone, because this site looks nothing up. Work down the list in order, starting with X itself.
This is the only donate popup you will ever see from us. If you enjoy this service, please consider donating to help keep it running.
Put your name into the letters
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.
9 services, in the order worth doing them
The source every other copy was made from. Deleting here reaches X itself and the companies bound by X's developer rules, but not copies made outside those rules.
- Do not rely on editing. X only lets Premium subscribers edit a post within an hour of posting, never threads or replies, and anyone can open the earlier versions.
- Delete the posts you want gone, one at a time, since X has no bulk delete. This is what stops ID-only research datasets and X's licensed data customers from reproducing them.
- Check the Replies and Media tabs on your profile too. Each reply is its own post and has to be deleted separately.
- Consider protecting your posts while you work. It removes nothing already taken, but it hides them from search engines, embeds and anyone who does not follow you, though approved followers can still screenshot them.
- Delete the whole account last, if at all. See the caveat.
Worth knowing: Deleting the account is not needed for any step above, and once X completes it after the 30-day deactivation period you can no longer reach your old posts. Your username then becomes free for anyone to register, so copies elsewhere that show it may appear to point to a stranger.
What this covers: Deleting here does not reach copies already made elsewhere, such as web archive snapshots, posts embedded on other websites, and quote posts or pasted text by other accounts. Archives have their own request route further down.
Typical response time: Unknown. Route last checked 2026-10-02.
Holds snapshots of specific pages that a person or a crawler chose to save. It is not a searchable list of everything you posted; 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 or post addresses you found] Please exclude the archived copies from [start date] to [end date]. I controlled this account from [start date] to [end date]. [Optional: one or two sentences on why you are asking.] 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 says it makes no guarantee beforehand about the outcome. It asks for the exact addresses, the dates you want excluded, and the dates you controlled the account.
What this covers: Only pages that were actually saved are there, not your whole account. Many posts were never saved by anyone.
Typical response time: Unknown. Route last checked 2026-10-02.
Keeps readable copies of threads that somebody asked its bot to unroll. It publishes clearer removal options than any other service on this page.
- Log in there with your X account and choose which of your threads to remove. This works without deleting anything on X.
- Post the exact text @ThreadReaderApp BLOCK ME from your account, with BLOCK ME in capitals. This removes your past threads from the site and stops future unrolls.
- Deleting a thread on X also removes it here, because the service checks X for deletions several times a day. Copies held in web caches can take up to 24 hours to clear.
- Write to hello@threadreaderapp.com if something is still there a day later.
Worth knowing: Blocking also stops future unrolls, but anyone can still ask. The app then replies that the author does not want their content there.
What this covers: Only threads somebody asked it to unroll are here, not single posts. Many accounts have none, and the link then shows a not-found page.
Typical response time: Unknown. Route last checked 2026-10-02.
Sells bulk datasets of X posts and profiles collected from public pages. As a commercial data seller it publishes a privacy contact and a process for access and deletion requests.
Subject: Data subject request, deletion Hello, I am making a request regarding personal data you hold about me, under the data protection law that applies where I live [name it if you know it]. 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. 4. That you stop selling or sharing that data while this request is handled. I can show that I control this account in any reasonable way you ask. 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 privacy contact and a request process, not because it is the only company reselling X data. Expect an identity check, and deletion can be refused where a legal exception applies.
What this covers: You cannot browse what a broker holds yourself, so the access request in the letter is how you find out. Rights are strongest in the EU and the UK, and California law excludes much of what you made public yourself.
Typical response time: Unknown. Route last checked 2026-10-02.
Public datasets holding the full text of hundreds of millions of X posts, collected outside X's developer rules and free for anyone to download. Deleting on X does not reach them.
Subject: Privacy request, my X posts in public datasets Hello, I am the holder of the X (formerly Twitter) account @yourhandle. Public datasets on Hugging Face hold the full text of X posts collected without their authors' consent, and they are likely to include my posts, including ones I have since deleted from X. I am asking you to review these datasets under your content policy on third-party privacy, and to remove the records from my account or have the uploaders remove them. The datasets I am concerned about: [add the dataset addresses] I can show that I control this account in any reasonable way you ask. Thank you for your time. [your name]
Worth knowing: The Report button on a dataset opens a public report, so email this instead if you want the request kept private. Hugging Face decides each case and publishes no turnaround.
What this covers: About 670 such datasets were public on 2 October 2026, and some are arranged so that anyone who knows a handle can pull out that account's posts. You usually cannot confirm your own posts are in one, so this is a request made without knowing the answer.
Typical response time: Unknown. Route last checked 2026-10-02.
A paid lookup service for X handle and profile history, which also searches about 1.8 billion archived posts. Its terms say it sells only to licensed investigators and law enforcement.
Subject: Content removal request Hello, I am the holder of the X (formerly Twitter) account @yourhandle. I am asking you to remove everything your service holds about this account, including its username and profile history and any archived posts, from your index and your search results. I am making this request under the GDPR, which your privacy policy says applies to you. I can show that I control this account in any reasonable way you ask. [your name]
Worth knowing: Their removal page promises removal within 30 days, but it is written for their database search and does not say whether the X tools are covered.
What this covers: Profile history covers late 2011 to January 2023, and again from 2026. You cannot see what it holds without paying, so this is a request made without knowing the answer.
Typical response time: Unknown. Route last checked 2026-10-02.
Holds snapshots of single pages, including X posts, saved when a visitor submits them. Its FAQ says pages are kept virtually forever, and the operator removes some only at its own discretion.
Each snapshot has a "report bug or abuse" link and the operator lists webmaster@archive.ph, but it publishes no process or turnaround for removal requests.
If a snapshot of yours causes real harm, a lawyer in your country is a better next step than the report link. For intimate images, the operator says to go through the police.
Route last checked 2026-10-02.
Maps an X handle to the previous handles and account numbers it has used. It holds no posts, only the trail that connects an old name to a current one.
There is no form, but the project's README says some accounts are excluded at the owner's request and that privacy concerns can be raised with the maintainer privately. The contact details are in the README, and no response time is given.
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-10-02.
Research datasets that list X post identifiers rather than the posts themselves, published by universities and researchers. There are many, and nobody can list them all.
X's developer rules let licensed users pass on only post identifiers, not the text, and a researcher turns an identifier back into a post by fetching it from X. Once the post is deleted, that identifier fetches nothing.
So for datasets built this way, deleting at the source has already done the work and there is nothing to send. Full-text copies published outside X's rules are a different case, listed above.
Worth knowing: A researcher who already fetched the content may still hold a copy. X's developer terms require them to delete it once it is gone from X, but nobody can check that, and you cannot ask without knowing who they are.
Route last checked 2026-10-02.
Services people still look for
Both stopped working because of X: Politwoops lost its API access, and the main Nitter services closed after legal action. Listed so you do not spend an evening looking for a way to contact them.
- Nitter: A privacy front end that showed live X pages and stored nothing. The main instances closed in September 2026 after legal action by X, and there is nothing to file against.
- Politwoops: Archived politicians' deleted posts. It stopped collecting in 2023 after an X API change, and only an unmaintained partial snapshot is still online.
Nothing here is a guarantee. This tool prepares requests, and a person at each service decides whether to act, and may decline.
Nothing here is legal advice, and the requests we prepare are a convenience rather than a legal instrument. If you need advice, consult a qualified lawyer in your jurisdiction.