Privacy
ClankerBlocker is an evidence-backed fake-follower and bot checker for X (Twitter). It scans Following or Followers up to your plan cap, shows the signal groups behind every risk score, lets you label Keep/Review/Cut, and exports a CSV cut pack. Optional paced unfollow applies to accounts on your latest Following scan when you confirm it yourself. It never posts, DMs, blocks, or mutes.
What we access
Official X OAuth identifies your account and grants only the scopes shown during connection; you never share your X password with ClankerBlocker. Following and Followers scans retrieve list and profile fields through our graph pipeline (a third-party list provider first, with official X API fallback). Graph requests identify the authenticated account and requested list. Profile fields used for scoring include username, display name, bio, public counts, verification, and account-age signals. Optional one-click unfollow uses follows.write only when you run it on Following accounts (confirm; labels independent). We do not request posting, DM, mute, or block scopes. See how bot scoring works.
What we store
Scan snapshots, scores, flags, and your Keep/Review/Cut labels are stored so the portal can show history and Graph Health without re-loading your graph on every page load. Follow Watch stores a follower-ID baseline and follow/unfollow event history for up to 90 days. Notification email is used only after member verification; a public waitlist handle is never used to choose a recipient. Waitlist submissions remain separate and store email and optional X handle until you request removal. Signed session cookies identify you after login. Payment events (if you subscribe) are handled by Stripe; we store plan linkage needed to enforce capacity.
What we do not do
We do not sell your graph data. We never post, DM, block, or mute for you. Default workflow is export-first; optional unfollow is limited to accounts in your latest Following scan when you confirm it. Exports (CSV cut pack) are generated for you to download and use at your discretion. ClankerBlocker is not affiliated with X Corp.
Deletion and contact
Private beta: signed-in members delete via in-app account delete (typed handle + confirm — see Help). Waitlist-only rows: Contact with your X handle and waitlist email. Latest snapshots stay in the portal until you delete or export CSV; the JSON export does not dump every scan-row blob. Product overview: ClankerBlocker home · Docs · pricing: plans.
Privacy FAQ
What X (Twitter) data does ClankerBlocker access?
Official X OAuth identifies your account and grants only the scopes shown during connection. Graph scans retrieve Following or Followers list data and profile fields through our graph pipeline (a third-party list provider first, with official X API fallback). Optional one-click unfollow requests follows.write. We never request posting, DM, block, or mute scopes.
Does ClankerBlocker post, unfollow, block, or mute for me?
It never posts, DMs, blocks, or mutes. Default workflow is labels + CSV export so you act on X yourself. Optional one-click unfollow can unfollow accounts from your latest Following scan — paced, capped, confirm each action, and only when you run it. Labels stay independent.
What do you store, and for how long?
Scan snapshots and scores are stored in your account so the portal can show history and Graph Health between scans. Follow Watch follower-ID snapshots and event history are retained for up to 90 days. Notification email is used only after you verify it. Waitlist records remain separate and are stored until you ask us to remove them. Session cookies keep you signed in after OAuth.
How do I request deletion?
Signed-in members can delete their account from Help / Privacy: POST /api/me/delete with confirm:true and your typed X handle. That wipes account-linked rows (scans, labels, jobs) and signs you out. Waitlist-only people (no account yet) should use Contact with the waitlist email and handle. Latest scan rows are visible and exportable in the portal; the JSON account export omits bulky per-account scan blobs (public X profiles already shown in-app).