Privacy Policy

Effective October 23, 2026.

1. Overview

Hide The Annoying ("the Extension", "we", "us") filters a timeline without tracking the person using it. Settings stay on the device. Post text is sent only to classify that post.

2. Information the extension handles

  • Settings on the device. Topics, filter mode, sensitivity, allowlist, blocklist, and cached decisions stay in chrome.storage.local.
  • A key you paste. A TypeSafe key stays in chrome.storage.local and is sent only to the endpoint you set. The free-tier Google session stays on the device too, and is sent only to the free-tier server.
  • Free-tier account. Google sign-in is limited to Gmail. The free-tier server stores your Google account id, email, and a daily classification count. It does not store post text.
  • Posts. On X, the extension reads publicly visible post text, names, and handles. Your own key sends that text to your endpoint. The free tier sends it to our proxy, which forwards it to TypeSafe Jev.
  • What it does not read. The extension does not read your browsing history, search queries, passwords, cookies, or direct messages.

3. Where a post is classified

With your own key, classification goes directly to TypeSafe AI (Jev). On the free tier, a Cloudflare Worker holds the shared key and forwards the same request. Google sign-in is used only to confirm the account is a Gmail address.

The payload is the post text and the username, used to decide politics, soccer, or crypto.

4. How long it is kept

Cached decisions stay in the browser until you remove them. Clear the cache from the extension's settings page.

5. Contact

Questions about this policy can go through the Chrome Web Store support tab for Hide The Annoying.