ReplyGuyX Extension Privacy Policy

The 30-second summary

• We never see your X (Twitter) password or cookies. The extension acts inside your already-logged-in browser session — exactly as if you typed the reply and clicked "Reply" yourself.
• We send our servers: a random per-install device ID and the X handle you're logged in as, in order to match you to your ReplyX subscription and hand back the replies to post. We record the outcome of each one.
• The replies themselves are written by our backend (from the topics, voice, and stance you configured in the BlockAI Mini App) — the extension only posts them.
• We do not sell or share your data with third-party advertisers or data brokers.

What the extension reads from x.com

The extension's content script runs only on https://x.com and https://twitter.com. It reads:

• Your logged-in handle (from the sidebar account button) so we can confirm which subscription this session belongs to.
• The page state of the specific post it has been asked to reply to — whether the reply composer and the "Reply" button are present, and whether the composer cleared after posting (how it confirms success).
• The tweet ID of the reply it just posted, read from the page, so we can log it back to your reply history.

We do not read your direct messages, your timeline/feed contents, other users' private data, or any X authentication cookies or tokens.

What the extension sends to our servers

The extension talks to https://www.blockmm.ai over HTTPS. Requests include:

• Your device ID: a random UUID generated once on first install, stored locally. Used to identify the install.
• Your X handle (the account you're logged in as), so we can match you to your active ReplyX subscription and return only your replies.
• The outcome of each reply task (posted, skipped because the post was too old, rate-limited, or failed) and, when posted, the resulting reply's tweet ID.

In return, our server sends the extension the reply tasks to post — each a target post and the text to reply with, already generated by our backend from the voice, topics, and stance you set up in the BlockAI Mini App.

What's stored locally

In chrome.storage.local on your own device: your random device ID, your last detected X handle, your daily reply counter, and your pause setting. This never leaves your machine except as described above.

Permissions, and why

• storage — keep your device ID, settings, and pause state on your device.
• alarms — schedule the paced, randomized checks that drive human-like posting timing.
• tabs — find your open x.com tab so the extension can act within it.
• Host access to x.com / twitter.com — where replies are posted.
• Host access to blockmm.ai — to fetch your reply tasks and report outcomes.

What we never collect

• Your X password, login cookies, or auth tokens.
• Your direct messages or private account data.
• Your general browsing history or activity on other sites.
• Any data for sale to advertisers, data brokers, or third parties.

Subscription & payment

ReplyGuyX only posts for an active ReplyX subscriber. Subscriptions are purchased in the BlockAI Mini App (Telegram), not in the extension. Payment details are handled by our payment processors (e.g. Stripe) and are never seen by the extension.

Data retention

Reply tasks and their outcomes are retained with your subscription to operate the service and show your reply history. Local data is removed when you uninstall the extension. To request deletion of server-side data tied to your account, contact us below.

Contact

Questions or a deletion request? Email hello@blockmm.ai.