← Privacy center
Extension privacy notice

CleanerX — X (Twitter) Bulk Cleaner

bulk delete your posts and reposts, remove likes, unfollow accounts, and block or mute a list of accounts through your own signed-in X session.

Last updated
September 14, 2026
Platform
X (formerly Twitter)
Chrome Web Store ID
efkdbehpkfaiehogkiokbiecjdbiebgi
Local processingRuns in your browser
No content collectionYour social content is not sent to us
No data saleYour personal data is never sold

About this notice

CleanerX — X (Twitter) Bulk Cleaner is a browser extension developed by Vladyslav Verbytskyi, an individual software developeras part of CleanMySocial. CleanMySocial is a product name, not a separate company or legal entity. It works on X (formerly Twitter). This notice explains exactly what the extension accesses and where that data goes.

Data the extension accesses

  • 01

    Your signed-in X account's numeric id, handle, display name, profile image URL, and available post, following, and follower counts, used to identify the account in the side panel. The profile card is cached locally in Chrome.

  • 02

    Identifiers, types, timestamps, and text for supported posts, reposts, and likes returned by X. Text and timestamps are processed to apply your keyword and age filters; the cleanup queue retains matching item identifiers rather than post text.

  • 03

    The account identifiers in your following list when you choose mass unfollow, and the usernames you paste when you choose block or mute. Active-job inputs and minimal outcomes may remain in local extension storage until cleared or replaced.

  • 04

    The ct0 CSRF value and numeric account id from the twid cookie, plus X's normal authenticated request headers. These are used only for requests sent directly to X and are never included in reports to CleanMySocial.

  • 05

    Your local workflow state and choices, including selected category, keywords, age filter, safe-test setting, backup-step choice, queued item ids, progress cursors, action outcomes, timestamps, totals, rate-limit state, and review-prompt preferences.

  • 06

    A validated purchased license key stored in Chrome sync, the local daily action count, and the entitlement result CleanMySocial returned when you clicked Activate. That result is checked locally and lapses one hour after the license's expiry; the extension never re-checks it in the background. An empty key slot means free access and makes no license request.

  • 07

    A random installation identifier, created on install and stored only in this browser. It is sent with the milestone and error reports described in this notice so repeated deliveries are not counted twice and so one installation reporting an error fifty times is not mistaken for fifty affected users. CleanMySocial hashes it before storing it, and it is never used for licensing, never synced between devices, never sent with a license check, and never attached to X data.

  • 08

    Six anonymous product milestones, each recorded at most once per installation: that the extension was installed, that a first cleanup action was started, that a first cleanup action succeeded, that the free daily allowance was reached, that you opened the Pro page from inside the extension, and that you opened the Chrome Web Store review page. Each is a name and a timestamp — no X data, no counts of what you removed, and no record of a review being written.

  • 09

    When you uninstall the extension, Chrome opens the CleanMySocial uninstall page and any milestones that had not yet been sent travel in that page address, along with the installation identifier and, if one is pending, the code of the most recent error. Chrome gives a removed extension no way to run code, so this is the only way a last report survives removal. It carries names and timestamps only.

  • 10

    CleanerX does not read or upload the X archive you request from X. The archive link opens X's own settings, and any archive file stays on your computer.

Permissions & why they are needed

scripting

Runs the X requests you initiate inside an open x.com or twitter.com tab, where X accepts requests from your existing signed-in session. It may also read your displayed account name and avatar for the connection card. Nothing is injected until you connect or start an action.

tabs

Finds or opens an X tab to relay requested actions and confirms that the relay tab remains on X. Opens the CleanMySocial installed page once after a fresh install, and opens X archive settings, the Chrome Web Store review page, the Pro page, or CleanMySocial only when you choose those links. Other tabs are not inspected.

storage

Stores your workflow and filter choices, cached X profile card, current job, queue, progress, per-item outcomes, lifetime action count, daily successful-action count, whether you clicked the review card, the entitlement cache, discovered X query identifiers, the installation identifier, and the short queue of milestone and error reports waiting to be sent. A short-lived session record suppresses duplicate error reports. Chrome sync contains a purchased license key only after you paste it and the server validates it.

unlimitedStorage

Allows a large cleanup queue and its minimal result log to survive side-panel closure, service-worker suspension, browser restarts, and X rate-limit pauses without exceeding Chrome's normal local-storage quota.

cookies

Reads the ct0 CSRF cookie and the numeric account id from the twid cookie so X can authenticate the actions you request and CleanerX can target the signed-in account. No cookie is modified or sent to CleanMySocial.

alarms

Wakes a long-running cleanup after Chrome suspends the service worker, resumes work when an X rate-limit waiting period ends, and wakes the extension about a minute after a milestone or error report is queued so the batch is still delivered if Chrome stopped the background worker in the meantime.

notifications

Notifies you when a background cleanup finishes or pauses because X requires your attention. It does not send promotional notifications.

sidePanel

Displays account connection, backup guidance, cleanup filters, confirmations, progress, pause or stop controls, block and mute tools, and locally stored results beside X.

Network access

https://x.com/* and https://twitter.com/*

Reads your own profile and supported timelines and sends the delete, undo-repost, unlike, unfollow, block, or mute actions you request directly to X through your existing session.

https://api.x.com/*

Reads the signed-in account's screen name so the panel can clearly identify which account will be cleaned.

https://abs.twimg.com/*

Downloads X's public web bundle as text to discover current GraphQL operation identifiers when X changes them. The downloaded bundle is searched, not executed by CleanerX.

https://pbs.twimg.com/*

Loads the profile image returned by X for the connected-account card.

https://cleanmysocial.com/*

Opens the product, installed, and uninstall pages, and lets the CleanMySocial installed page ask the extension to open its side panel. That exchange carries only a protocol name and a yes/no answer — no X data, license key, or page content.

https://cleanmysocial.com/api/telemetry

Receives two kinds of anonymous report in one batched request, roughly a minute after they occur: the product milestones described under “Data the extension accesses”, and privacy-filtered technical error reports (error type, stable code, extension version, workflow source, locale, platform, browser version, time, and a repeat count). Neither contains post text, handles, X account identifiers, cookies, CSRF values, session tokens, page addresses, or your license key.

https://cleanmysocial.com/api/license

Validates a license key only when you paste it and click Activate. The request contains only the key and public product slug, never your X account, posts, handles, cookies, or session values. Rejected keys are not stored, and no license request is made when Chrome starts or the panel opens.

https://cleanmysocial.com/api/report

Sends a closed, non-identifying failure code when CleanerX detects that X changed a supported API workflow. It contains the product slug, extension version, and locale—no account or post data.

Good to know

  • CleanerX is free to use with a local daily action allowance. Optional monthly or lifetime Pro access adds unlimited actions and Super Speed. No CleanMySocial account or X-account sign-in is sent to CleanMySocial.
  • X normally exposes only a limited recent timeline through these interfaces, so CleanerX may not be able to reach older content. X also applies rate limits and account-level caps; the extension backs off, saves progress, and can resume later.
  • Safe test mode stops after 10 matching items so you can inspect the result before starting a larger run.
  • Deleting or undoing account activity can be permanent. CleanerX asks for confirmation before destructive cleanup and lets you pause or stop a run.
  • The Chrome Web Store review page opens only when you click the review card or a review prompt. A click records only that the page was opened, never that a review was written.
  • Known X breakage reports contain only the extension slug, closed failure code, version, and locale. Milestone and error reports are retained for a limited operational period — 90 days by default — and are read only in aggregate.
  • The extension contains no advertising and no third-party tracking, and it does not profile you. It does report the six anonymous product milestones described above to CleanMySocial, which is first-party product analytics; nothing it sends identifies you, your X account, or your posts.
  • CleanerX is not affiliated with or endorsed by X Corp.

Payments

Paid plans are processed by Creem, our Merchant of Record. Creem collects and handles your payment and billing details; we receive only a transaction record and a license identifier and never see your full card details.

Sharing, storage & deletion

We do not sell your personal data, and we do not share the content you access through the extension with anyone. Purchase data is shared with Creem solely to process payments.

Operational settings and progress described above are kept in Chrome extension storage on your device. Uninstalling the extension removes its local storage; Chrome may retain values stored in sync according to your Chrome sync settings. We retain purchase and license records only as long as needed to provide access, handle refunds or disputes, prevent abuse, and meet legal or accounting requirements.

Security, children & changes

We use reasonable safeguards for the limited license and purchase data we process. The extension is not directed to children under 13. If this policy changes, the revised text and date will be published on this page.

Your rights & contact

Want to access or delete data?

Email us to request access to or deletion of data associated with your purchase, support request, or technical report. You can also read the product-wide Privacy Policy.

info@verblike.com