ThreadSnap: Thread Exporter — Privacy Policy

ThreadSnap is designed to protect your privacy. This policy explains what the extension does and does not do with your data.

Summary

ThreadSnap does not collect, transmit, sell, or share any personal data. It does not send your data to the developer or to any server we control. The files you export are generated locally, inside your own browser.

What the extension accesses

• The current X / Twitter thread. When you click the ThreadSnap toolbar button on an x.com or twitter.com thread, the extension reads the posts already rendered as you scroll — their text, author, timestamps, engagement counts, and media — in order to build the file you asked to export. It scrolls the page from the top to reach them, and stops after at most 500 posts per export.
• Posts you list (optional "Specific posts" feature). If you paste post links or IDs into the extension, it automatically moves the tab you have open between those posts, one at a time, pausing a couple of seconds between each (at most 100 per export), reads each post as it renders — together with the posts it replies to, which X draws on the same page, unless you turn that off — and then returns the tab to the page you were on. This is automated navigation, not you clicking each link, so X may treat heavy use as automated activity. The X website itself loads those posts, under your own login, as the tab navigates; the extension does not request posts from X itself and does not use the X API. (The only requests it makes of its own are the media and font downloads from Twitter's content delivery network described below.) If several posts in a row fail to load, the export stops. The list you paste is used only for that export: it is not saved, and it is never sent anywhere.
• Media and fonts from Twitter's content delivery network. To embed the photos and video thumbnails that are already displayed in the thread — and the fonts the thread is rendered with — the extension re-reads those files from Twitter's own servers (pbs.twimg.com, abs.twimg.com, and other *.twimg.com hosts). These requests go to Twitter, not to the developer, and carry no information about you beyond ordinary image and font requests.
• Your export preferences. Your chosen output format, image quality, and whether Evidence mode is on are saved using the browser's local extension storage so your settings persist between sessions.
• A note of how far the last export got. While an export runs, the extension records one line locally — which stage it reached (capturing, building, zipping, finished, cancelled or failed), when, how many posts it had captured, and, if it failed, the error message. It holds no post content. It is how the extension can tell you what happened when the page stops responding mid-export, and each export overwrites it.
• Evidence mode (optional). If you turn it on, each exported image is stamped with the post's link and capture time, and the export includes a manifest file listing each post's link, posting and capture times, SHA-256 fingerprints, the page you exported from, your browser's user agent (its name and version) and its time zone. That file is written into your own export, and a copy of it is kept locally in the extension (below) so you can save it again if its download never landed; it is never sent anywhere. If you share the export, those details go with it.
• A copy of the last Evidence-mode manifest. If you use Evidence mode, the manifest described above is also kept in the browser's local extension storage, because a page cannot see whether a download landed — so ThreadSnap can offer it to you again from the popup ("Save manifest"). The copy holds what the manifest holds: each post's link, handle, posting and capture times, SHA-256 fingerprints, the page you exported from, your browser's user agent and its time zone. It holds no post text and no images. It never leaves your device, and the next Evidence-mode export replaces it.

What the extension does NOT do

• It does not send your exported files, the thread content, or any other data to the developer or any third-party server.
• It does not collect personally identifiable information, credentials, browsing history, or analytics.
• It does not track your activity across sites.
• It does not post, like, follow, reply, or change anything in your X / Twitter account.
• It does not use the X / Twitter API or sign in on your behalf.
• It does not load or execute any remote code.

How your files are created

All exported files (PDF, images, ZIP) are generated on your device from the posts displayed in your browser and saved through your browser's normal download mechanism. They are never uploaded anywhere.

Data storage

Three things are stored, all of them local to your device via the browser's extension storage, and none of them leaving it: your export-preference settings; the one-line note of how far the last export got; and, only if you use Evidence mode, a copy of the last manifest. The first two hold no post content at all. The manifest copy holds the links and times of the posts you exported — no post text, no images — and the next Evidence-mode export replaces it. You can clear all three at any time by removing the extension.

Permissions

• activeTab — grants access to the current tab only at the moment you click the ThreadSnap button, so it can read the open thread (and, if you use the "Specific posts" feature, move that same tab between the posts you listed). No standing access to any site is kept.
• scripting — to inject the capture code into that tab on demand when you start an export.
• storage — to remember your export preferences locally; to note how far the last export got so the extension can tell you what happened if it stops midway; and, in Evidence mode, to keep a copy of the last manifest so you can save it again from the popup if its download never landed.

The extension requests no host permissions. The media and fonts it embeds are readable because Twitter's own content servers permit it (standard CORS headers), using only the access the page itself already has.

Responsible use

ThreadSnap only works with content you can already view in your browser. You are responsible for ensuring your use of exported content complies with applicable copyright, the platform's Terms of Service, other people's privacy, and any laws that apply to you.

Changes to this policy

If this policy changes, the updated version will be published here and the "Last updated" date revised.