Privacy Policy — CleanMyX

Extension: “Delete Tweets - Bulk Tweet Deleter for Twitter & X” (CleanMyX)Last updated: 11 July 2026

In plain English: CleanMyX runs inside your own browser. The content of your tweets, replies, likes, retweets and your archive files is read and processed locally on your device and is never sent to us or to any third-party server. The only network requests the extension makes are: (1) to Twitter/X, to carry out the deletions and other actions you ask it to perform on your own account; (2) to our payment processor, only to check whether a Pro license key is valid; and (3) an anonymous one-line uninstall survey. We do not sell data, run ads, build user profiles, or track your browsing.

1. Who we are

CleanMyX (“the extension”, “we”, “us”) is a browser extension that helps you bulk-delete your own posts, replies, likes and reposts, and mass-unfollow accounts, on Twitter/X. For any privacy question, contact: [[email protected]].

2. What the extension accesses

To do its job, the extension reads the following on your device, inside your browser:

Your posts and account content on Twitter/X — tweets, replies, retweets and likes shown on the page, so it can identify what to delete or unlike.
Your Twitter/X archive files (optional) — if you use Archive Deep Clean, the tweets.js / like.js files you choose are read locally to build the list of post IDs to delete. These files are never uploaded anywhere.
Your Twitter/X session token — the extension reads the ct0 cookie (a CSRF token) for x.com/twitter.com so it can send delete/unlike requests to Twitter/X as you, exactly as the website itself does. This token is used only to authenticate those requests and is never stored by us or transmitted anywhere except to Twitter/X.
Your Twitter/X handle — detected from the page so actions are limited to your own account. Stored locally only.

3. What is stored, and where

All extension data is stored locally in your browser (Chrome storage.local) and stays on your device:

Deletion job progress, queues and result logs (so a large run can resume).
Backups of items you delete, which you may export to a CSV file. CSV files are saved by you, to your own computer, and are never sent to us.
Your settings, detected handle, license key (if you buy Pro) and a randomly generated install identifier (a UUID that contains no personal information).

You can clear this at any time by removing the extension or clearing its storage.

4. Data we transmit, and to whom

Recipient	What is sent	Why
Twitter / X (`x.com`, `api.x.com`, `abs.twimg.com`)	The delete / unlike / unfollow requests you initiate, authenticated with your existing session; and public Twitter/X script files (to keep the extension working when Twitter/X updates).	To perform the actions you asked for, on your own account.
Dodo Payments (`live.dodopayments.com`)	Your Pro license key and a random install identifier — only when you activate or validate a Pro license.	To verify your purchase and unlock Pro features. No tweet content or personal profile is sent.
Uninstall survey (Tally)	If you uninstall, an anonymous request containing only: the extension version, whether your plan was free or pro, and whether you had ever run an action (yes/no).	To understand why users leave and improve the product. It contains no account name, no tweet content, and no personal identifiers.

We do not send your tweets, replies, likes, follower lists, archive files, or browsing activity to us or to any analytics/advertising company.

1. Who we are

2. What the extension accesses

3. What is stored, and where

4. Data we transmit, and to whom

5. What we do NOT do