BuzzyX

Privacy Policy

Last updated November 13, 2026

BuzzyX ("we", "us") is a workspace for growing on X. This policy explains what we collect when you use buzzyx.com, why, and what control you have. We keep it short on purpose.

What we collect

  • Your X account basics. When you sign in with X we store your X user ID, username, display name and profile picture URL. We use the X user ID as your identity, since usernames can change.
  • X access tokens. X gives us a token so we can act for you. Tokens are encrypted at rest with a key we hold separately from the database. We never send tokens to your browser or to any third party.
  • Posts you publish through BuzzyX. If you enable posting and publish from Compose, we keep the text, the time, and the ID X assigned, so you can see your history. We only publish what you write, when you press the button.
  • Early access and preferences. Whether you joined the early access list and which planned features you said you want.
  • Billing, if you upgrade. Payments are handled by Dodo Payments, the merchant of record. They collect your email, billing address and card details; we never see your card number. We store your Dodo customer and subscription IDs, your plan, and its renewal date.
  • Session cookie. A random session identifier in an HttpOnly cookie keeps you signed in for up to 30 days. It contains no personal data.
  • Usage analytics. We use DataFast to count visits, pages and a handful of product events (for example "joined early access"). DataFast sets a visitor identifier in your browser. We do not send your X identity, username or tokens to DataFast.

AI features

When you use Compose Assist, the draft you are editing and up to eight of your own recent public posts (as style samples) are sent to Anthropic, the maker of Claude, to generate suggestions. Nothing else about your account is sent: no tokens, no username, no identifiers. Anthropic's API does not use this data to train models. Suggestions are only ever drafts; you review and edit them, and nothing is published unless you press Post. We keep a count of your AI usage and token counts for quotas and cost control, not the content.

Free tools

The free tools need no account. Most run entirely in your browser. When you press a lookup button in the username checker, bio tools or shadowban test, we ask X for that handle's public profile (name, photo, bio, follower counts) and reuse the answer for up to 24 hours so repeat lookups are free. The X crush finder also reads that handle's last 100 public posts and keeps only who they replied to and mentioned, as counts, never the posts themselves, for up to 24 hours. Old answers are deleted daily. To enforce the daily limit on lookups we store a one-way hash of your IP address mixed with the date and a secret, never the IP itself, and delete it within three days.

AI agents (MCP)

You can connect an AI app, such as Claude, to your BuzzyX account from Settings. Nothing is shared until you approve that app on a BuzzyX screen and choose what it may do. A connected app can then, when you ask it to: send a draft or a post's text to BuzzyX for writing help (this goes on to Anthropic, the same as Compose Assist, and counts against your monthly suggestions), read the analytics BuzzyX has stored for your account, and save drafts to your account. It cannot post, reply, delete or follow on X. What it reads is passed to that app and handled under that app's own privacy terms. We store the app's name, what you allowed, when it was last used, and a hash of its access token, never the token itself. You can disconnect an app in Settings at any time, which ends its access at once.

Chrome extension

The BuzzyX Chrome extension reads the posts X shows you on x.com while you scroll (author, text, time and public counts) to rank the ones worth replying to. That list stays in your browser's extension storage, is kept for 48 hours, and is never sent to us. When you open someone's profile, the posts of theirs that you scroll are used to work out that profile's stats in your browser; they are kept only until Chrome closes and are never sent to us.

Some actions send data to BuzzyX, using your BuzzyX sign-in in the same browser:

  • Asking for reply ideas on a post sends that post's text and author handle, which go on to Anthropic, the same as reply ideas in Discover.
  • Pressing an AI action on the BuzzyX button in X's post box sends your draft, which goes on to Anthropic, the same as Compose Assist.
  • Scheduling from X's post box sends your draft and the time you picked, and BuzzyX stores it like any other scheduled post.
  • Pressing "Reply on X" while signed in sends the post's id, so Discover can hide posts you already replied to.
  • If you switch on "Let my AI agents read the post I have open" in the side panel (it is off until you do), then when an AI agent you connected to BuzzyX asks, the extension sends the post your x.com tab is showing (text, author, time, public counts and the replies on screen) to BuzzyX, which passes it to that agent. BuzzyX keeps it for a few seconds only. Switching it off, there or in Settings, stops it.

Feeds you create (accounts and keywords) are saved in your Chrome profile and open as an X search in your tab; they are not sent to us. The "You" tab shows your own numbers from your BuzzyX analytics; opening it doesn't call X. The extension never posts, likes, follows or presses anything on X for you: a suggestion only changes the text in X's post box, and you press Post. Removing it from Chrome deletes everything it stored.

What we don't do

  • We don't ask for your email, password or payment details to sign in.
  • We don't sell or rent your data, and we don't run advertising.
  • We don't post, like, follow, or message from your account unless you explicitly trigger it.
  • We don't read your direct messages. We never request that permission.

Permissions we ask X for

At sign-in we request read access to your profile (users.read, tweet.read) and a refresh token (offline.access) so you don't have to re-authorise every two hours. Posting requires a separate permission (tweet.write) that we only request when you turn posting on, and you can turn it off again in Settings. You can also revoke BuzzyX entirely from your X account settings at any time.

Where data lives

Everything runs on Cloudflare's network: the application on Cloudflare Workers and the database on Cloudflare D1. DataFast processes analytics on our behalf, Anthropic processes Compose Assist requests, Dodo Payments processes subscriptions, and Resend delivers our internal daily report to the founder, which can include your X username, display name and account status. BuzzyX never emails you, and we don't use any other hosting or data processors. The walkthrough video in the dashboard is hosted on YouTube: nothing loads from YouTube until you press play, and it then plays in YouTube's privacy-enhanced mode, where Google receives your IP address and browser details like any video you watch.

Retention and deletion

We keep your data while your account exists. Sessions expire after 30 days of inactivity. To delete your account and everything tied to it, email divv@divvlaunches.com from an address you can verify as yours, or message us from your X account, and we'll remove it within 30 days. Revoking BuzzyX on X stops us from accessing your account immediately but does not by itself delete stored data.

Security

Traffic is HTTPS only. Tokens are encrypted, session identifiers are hashed, and state-changing requests are protected against cross-site forgery. No system is perfectly secure; if you believe you've found a problem, please tell us at the address above.

Children

BuzzyX is not directed at people under 13, and X itself requires users to be at least 13.

Changes

If this policy changes in a way that matters, we'll update the date above and, for significant changes, note it on the dashboard.

Contact

divv@divvlaunches.com