Your chat archive stays on your device.

Data processed

To provide page-load controls, a local timeline, search, available branch information, and source navigation, Threadwing reads and processes the current conversation's messages, roles, structure, title, stable message identifiers, and content types on the active ChatGPT, Claude, Gemini, Grok, DeepSeek, Kimi, or Doubao page. Content may include text, code, formulae, tables, image references, and user-generated content.

Local storage and retention

Captured conversation data is stored in the extension's own IndexedDB so the timeline and full-text search can recover after a refresh. storage.local stores settings such as enabled state and retention policy. storage.session can hold draft-recovery information during a safe apply. Verified restoration or identity-bound cleanup removes it; protected failures or unknown reload outcomes may retain it for explicit recovery without overwriting edited input. Its five-minute recovery validity window is checked before use, not a promise of timed physical deletion. Older unpacked development builds can also leave draft-recovery handoffs in storage.local. The revised development-update path writes only a reload acknowledgement; it does not capture drafts, reload chat pages, or replay, overwrite or delete those older handoffs. An extension restart or update does not guarantee deletion of legacy recovery data, nor does updating files alone replace an already-running older worker. Print handoff content uses a separate IndexedDB database, threadwing-print-sessions; reading consumes the record. A later print save removes unconsumed records older than one hour, not an automatic timed deletion. Data is not placed in browser sync.

Network and sharing

Threadwing runs only on chatgpt.com, chat.openai.com, claude.ai, gemini.google.com, grok.com, chat.deepseek.com, www.kimi.com, and www.doubao.com. It does not send conversation content to a Threadwing server and loads no remotely executable code. The browser opens Afdian or Ko-fi only when you explicitly choose a voluntary support option; Threadwing sends them no conversation content. Exported files are saved only to the location you choose.

Context handoff and image exports

When you choose Continue fast or a selected-message handoff, Threadwing fills a new ChatGPT draft with a locally prepared excerpt. The draft is placed in the chat service's page, not kept exclusively in extension storage; that service's privacy policy applies. Threadwing does not automatically submit it. The excerpt may omit older or oversized content, and original images and attachments are not transferred. When you explicitly include supported first-party images in an export, the browser requests those images from their allowed provider origins. Exporting text alone does not request those images.

DOM image URLs stay in the active page route's memory; only opaque image references enter the timeline and local archive. A refresh, route change, purge or teardown retires those URLs; the bounded registry may also evict older locators. An archived or evicted image may need its source conversation reopened and captured again; message text is not pruned. JSON exports omit typed image resolver references and embed only explicitly resolved safe raster data. An archive schema upgrade removes legacy typed image transport URLs without deleting messages or changing their update times. Ordinary links and literal text or code written in a conversation are preserved; this is not a general content scrubber.

Manual version checks

Only when you click Check for updates, the extension requests the public version for its store from threadwing.simplezion.com/api/releases/. It sends no cookies, installed version, account, device identifier, chat content or chat URL. The Cloudflare-hosted service processes the IP address and ordinary HTTP request metadata; the application does not log requests or build user profiles. It queries official public update feeds and returns only the store, version and source-check time, cached for up to 60 seconds. Failed queries do not claim you are up to date. No remote code or configuration is downloaded. Opening the store to install uses that store's privacy policy; the browser controls installation.

Why permissions are used

storage: stores local settings, short-lived recovery information, and the extension's conversation index.
sidePanel / sidebar_action: displays the virtualized timeline of captured messages in Chromium and Firefox.
scripting: injects local packaged scripts and styles only into an authorized document on the same eight chat origins. Eligible versions can reconnect an existing page without refreshing it or reconstructing its draft; this adds no host access or remote code. Updating files alone does not prove an older installed page has reconnected.
Host access: limited to the eight implemented first-party AI-chat origins for provider-aware capture, rendering optimization, history loading, search, navigation, and user-requested export.

Your controls

You can clear the current conversation's local snapshot from the timeline or remove all local data through the browser's extension-data controls. Uninstalling Threadwing removes extension storage. Files you intentionally exported are unaffected.

Policy updates

This page will be updated if the product or its data handling changes. Threadwing will not add conversation uploads, telemetry, advertising, or data sales without clear disclosure.