X Post Radar

X Post Radar privacy policy

Effective date:

This policy covers the X Post Radar Chrome extension. There is no X Post Radar server and no user account with us.

What is stored on your device

The extension stores the following in chrome.storage.local in your browser profile:

  • Your settings: signal weights, thresholds, niche keywords, mute keywords, and display options.
  • Local learning data derived from how you interact with posts, and keywords read from your own X profile when you use Auto-setup (Pro).
  • The on/off settings and threshold of the AI-likelihood check and of hiding likely AI posts, whether or not the TypeSafe score is on, and a marker that a one-time settings update has run. If you enable the TypeSafe score: its on/off setting. Your TypeSafe API key, if you enter one, is kept in the extension's own IndexedDB storage, which websites, x.com pages and other extensions cannot read; it is not encrypted on disk.
  • Your license status (xgc_entitlement): plan, status, and when it was last checked.
  • If you use product promotion (Pro): your product profiles and the text read from their landing pages, the posts scored for each product with their scores, your reply drafts, your reply style, your LLM provider settings, and your LLM API key (kept with the TypeSafe key in the extension's own IndexedDB).

The extension reads the posts shown on x.com pages you open, including author handles and follower counts that X has already loaded in the page, to compute scores. This happens inside your browser. Scores and post data are not sent anywhere except as described below.

What leaves your device

TypeSafe score (optional, off by default). If you turn it on and enter your own TypeSafe API key, the extension's service worker sends the text of highlighted posts, their public like, retweet and reply counts and age, and your niche keywords to https://api.typesafe.ai, authenticated with your key, and receives a score back. The AI-likelihood check (its own toggle, off by default) runs in your browser and sends nothing on its own: it looks for common AI-writing patterns in each post. Only if the TypeSafe score is also on is the text of every visible post and reply sent, not only highlighted ones, once per page view, to receive how likely each one is AI-generated; this may increase your TypeSafe usage. Hiding likely AI posts happens in your browser and sends nothing. TypeSafe's handling of that data is governed by TypeSafe's own terms and privacy policy. Turn the toggle off or remove the key to stop it.

Product promotion (Pro, only when you use it). Every request uses your own keys and is billed to your own accounts:

  • Scan reads your product's landing page (and its /llms.txt) from the popup, opening it briefly in a background tab when the page is built by JavaScript, after Chrome asks you to allow that site and its subdomains, then sends the page text and any description you typed to https://api.typesafe.ai and, if you configured one, to your LLM provider.
  • Find leads in the Leads view of the Top posts panel on x.com (once you have allowed api.typesafe.ai in the popup) sends the text of new posts collected on that x.com page, with each of your products' profiles (one request per post and product), to https://api.typesafe.ai. Author handles, names, links and post IDs are not sent.
  • Write draft sends one post's text, your product's details and a short note on that post's lead score (for example "the author is asking for a solution") to your LLM provider: https://api.anthropic.com, https://api.openai.com, or the OpenAI-compatible server address you entered.
  • These providers' own terms and privacy policies govern what they receive. The extension never posts anything on X for you.

Pro purchases (ExtensionPay and Stripe). Payments are handled by ExtensionPay (extensionpay.com), which runs checkout on Stripe.

  • When you buy or restore Pro, a page on extensionpay.com opens in a tab. ExtensionPay learns your email address and payment status; Stripe processes your card details. The extension never sees or stores card data.
  • Nothing is sent to ExtensionPay until you first press Upgrade to Pro or Restore purchase. At that point ExtensionPay creates a random identifier for your install, and the extension stores it in Chrome sync storage.
  • After that, the service worker regularly asks ExtensionPay whether this install has paid. The request contains only that identifier: no timeline content, keywords or browsing data.
  • ExtensionPay's and Stripe's privacy policies apply to the data they hold.

Key tests (only when you press Test). In the popup's Settings tab, Test sends one short fixed test message with the key you are testing to that key's own service: https://api.typesafe.ai for the TypeSafe key, or your LLM provider for the LLM key. No post, keyword or product data is included.

Nothing else is sent. The extension does not use the X API.

What we never collect

  • Your X password, cookies, or session tokens
  • Your browsing history outside x.com
  • Timeline content for analytics, advertising, or training
  • Card or bank details
  • Analytics, telemetry, or crash reports

We do not sell or share data, and do not use it for advertising or creditworthiness decisions.

Retention

Local data stays until you change it, clear the extension's storage, or uninstall the extension (uninstalling removes it). The license status is refreshed on each check; if ExtensionPay cannot be reached, the last verified status is kept for up to 7 days before Pro turns off. Data held by TypeSafe, your LLM provider, ExtensionPay, or Stripe is retained under their policies; to have ExtensionPay purchase records removed, contact us and we will forward the request.

Changes

Changes to this policy are published on this page with a new effective date.

Contact

Email contact@luongnv.com.

Back to X Post Radar