ThreadSnap is designed to protect your privacy. This policy explains what the extension does and does not do with your data.
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.
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.
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.
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.
The only data stored is your export-preference settings, kept locally on your device via the browser's extension storage. You can clear it at any time by removing the extension.
activeTab — grants access to the current tab only at the moment you click the ThreadSnap button, so it can read the open thread. 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.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.
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.
If this policy changes, the updated version will be published here and the "Last updated" date revised.