Legal

Privacy policy

Thread Hunter Chrome Extension  ·  Effective: 1 January 2025  ·  Last updated: 13 April 2026

The short version

1. Who we are

Thread Hunter ("we", "our", "the extension") is a Chrome browser extension that allows users to extract content from X (formerly Twitter) — including tweets, threads, articles, bookmarks, and profile timelines — and optionally repurpose that content using Claude AI. This privacy policy explains how the extension handles data.

Thread Hunter is an independent tool and is not affiliated with, endorsed by, or sponsored by X Corp or Anthropic.

2. What data the extension accesses

Thread Hunter reads the following data from your active browser session on x.com or twitter.com. This data is never stored, logged, or transmitted to any server operated by Thread Hunter.

Data type Purpose Stored externally?
CSRF token (ct0 cookie) Required by X's API to authenticate requests from your session No — read once, never saved
Tweet text and metadata Display in extension panel, export to clipboard, or include in AI prompt Local only — cleared on reload
Tweet metrics (views, likes, retweets, replies, bookmarks) Displayed as context alongside extracted content Local only
Author name, handle, and avatar URL Attributed display inside the extraction panel Local only
Article content (X Articles) Full-text extraction via X's article API Local only
Bookmark timeline Batch extraction at your explicit request Local only
Profile tweet timeline Extraction at your explicit request Local only
User ID and follower count Display profile context in the extraction panel Local only
Media URLs (images, videos) Listed as metadata in JSON/Markdown export Local only
Current X page URL Used when you click a Quick Share button for LinkedIn, Facebook, or X Sent only to the share service you choose
How API requests work: Thread Hunter uses X's internal GraphQL API endpoints on your behalf, authenticating with your browser's existing session token (ct0 cookie). This is identical to the requests X's own website makes. Thread Hunter does not create a separate account, proxy your traffic, or intercept credentials.

3. Data we do not collect or store

Thread Hunter does not collect, transmit to Thread Hunter servers, log, or store any of the following:

4. Local data storage

Thread Hunter does not write any data to chrome.storage, localStorage, IndexedDB, cookies, or any other persistent storage mechanism.

All extracted content is held exclusively in JavaScript in-memory variables (e.g. cachedData, cachedBookmarks) within the content script's runtime. This data is automatically discarded when you navigate away from the page, reload the tab, or close the browser. There is no way for Thread Hunter to retain your data between browsing sessions.

5. Third-party services

Thread Hunter interacts with external services only as needed to perform actions you request:

X / Twitter (x.com, twitter.com)
Thread Hunter reads data from X's own GraphQL API endpoints using your browser's active session. This data transfer occurs on x.com's own domain and is subject to X's Privacy Policy. Thread Hunter does not post, modify, or delete any content on X.

Claude AI (claude.ai)
When you click a platform repurpose button (LinkedIn, Facebook, Instagram, or X Thread), Thread Hunter constructs a prompt containing the extracted content and opens claude.ai in a new browser tab with that prompt pre-filled in the URL or page input. This data transfer happens only when you actively click the button. Because the prompt is placed into the Claude page URL or input flow, the prompt may also appear in your browser history or be processed by Claude/Anthropic. The content you send to Claude.ai is subject to Anthropic's Privacy Policy. Thread Hunter has no control over how Anthropic handles this data.

LinkedIn, Facebook, and X share dialogs
When you click a Quick Share button, Thread Hunter opens the selected service's share dialog with the current X page URL or a short share text. This happens only when you actively click a share button and is subject to the selected service's privacy policy.

Thread Hunter does not use Google Analytics, Mixpanel, Segment, Sentry, or any other analytics, error tracking, or telemetry service. No data is sent to Thread Hunter's servers because Thread Hunter has no servers.

6. Permissions justification

Thread Hunter requests host permissions only for the sites where it operates:

Permission Why it is needed
Host: https://x.com/* Thread Hunter only activates on x.com. This restricts the extension to operating on X's domain only — it cannot access any other website.
Host: https://twitter.com/* Allows the extension to work on the legacy twitter.com domain for users who are redirected there.

Thread Hunter does not request activeTab, scripting, tabs, history, cookies (as a global permission), webRequest, storage, identity, or any other broad permission. Access is intentionally scoped to the minimum required to deliver the extension's functionality.

7. Children's privacy

Thread Hunter is not directed at children under the age of 13, and we do not knowingly collect any personal data from children. The extension requires an active X account, which itself requires users to be at least 13 years old under X's terms of service.

8. Data security

Because Thread Hunter does not operate its own external server, the conventional data security risks associated with Thread Hunter-hosted cloud storage do not apply. Your extracted content exists only in your browser's memory for the duration of your current page session unless you explicitly copy it, open it in Claude.ai, or send a share link to a third-party service.

Thread Hunter runs entirely as a Manifest V3 Chrome extension, which means it operates within Chrome's sandboxed extension environment and cannot access data from other extensions, your file system, or other applications on your device.

9. Your rights

Because Thread Hunter does not collect or store personal data on Thread Hunter-owned servers, there is no personal data held by Thread Hunter that requires deletion, correction, or portability. However, if you have questions about your data or this policy, you may contact us at the address below.

You may also uninstall Thread Hunter at any time through Chrome's extension management page (chrome://extensions). Uninstalling the extension removes all associated code from your browser immediately.

10. Changes to this policy

If we make material changes to this privacy policy — for example, if a future version of Thread Hunter introduces Thread Hunter-owned server storage, analytics, or telemetry — we will update the "Last updated" date at the top of this page and, where possible, notify users through the Chrome Web Store update notes.

We encourage you to review this policy periodically. Continued use of Thread Hunter after changes are posted constitutes your acceptance of the revised policy.

11. Contact

If you have questions or concerns about this privacy policy or Thread Hunter's data practices, please contact us:

Thread Hunter Support
Email: threadhunterapp@gmail.com
Chrome Web Store: Thread Hunter on Chrome Web Store

We aim to respond to all privacy-related enquiries within 5 business days.