ctbubbles — Privacy Policy

Applies to the ctbubbles browser extension and website. Last updated: 4 September 2026.

ctbubbles is a browser extension that overlays public analytics (follower growth, an authenticity score, engagement and content signals) onto X (Twitter) profiles. This policy explains, in plain terms, exactly what the extension does and does not do with data.

In one line: we only ever process public information about the profiles you look at and aggregate statistics you ask us to compute. We never touch your passwords, your login cookies, your Direct Messages, or your private data — and we never sell anything.

What the extension accesses

Public profile data of the X account you are currently viewing — handle, display name, avatar, follower/following/post counts, and recent public posts. This is read through your own logged-in X session, exactly the same data X already shows you on the page.
Your own followers / following lists, only when you explicitly press the “follower quality” or “ghost following” button, and only to compute aggregate percentages (e.g. “4% likely bots”). This runs inside your browser.

What we send to our servers (ctbubbles.com)

The public identity of profiles you view: handle, numeric account ID, display name, avatar URL, and follower/following/post counts. We use this to show analytics and to build a public history of @handle / display-name changes.
Aggregate quality percentages (share of bot / inactive followers) — numbers only, never the underlying list of accounts.

The follower/following lists themselves, and the “ghost following” results, stay in your browser and are never uploaded.

What we NEVER do

Never collect, store, or transmit your passwords, cookies, or authentication tokens. Your X session credentials stay on x.com and are only used to talk to X directly.
Never access your Direct Messages, bookmarks, drafts, email, or phone number.
Never sell or share your data with third parties.
Never use data for advertising, credit, or lending purposes.
Never load or execute remote code — all extension logic ships inside the package.

Local storage

The extension uses chrome.storage only to remember your own preferences (such as your chosen inactivity threshold). This never leaves your device.

Data retention

Public profile snapshots and @handle-change history are retained to power the product’s analytics and history features. You can request removal of any account record by contacting us.

Permissions, explained

host access to x.com / twitter.com — to read the public profile you’re viewing and draw the analytics card on the page.
host access to ctbubbles.com — to fetch analytics for that profile from our own backend.
storage — to save your local preferences.

Contact

Questions or data-removal requests: Telegram @h3uih8y.

ctbubbles is not affiliated with, endorsed by, or sponsored by X Corp. “X” and “Twitter” are trademarks of their respective owners.