Privacy Policy - Tweet Thread Saver

Last updated: May 12, 2026

What stays on your device

All of your saved threads, settings, and preferences live in Chrome's local storage (chrome.storage.local) on your computer by default. They are never uploaded to our servers unless you explicitly enable Firebase cloud sync.

What we do collect (anonymous analytics)

When the extension is installed, used, or uninstalled, it sends a small product-analytics event to our server. Each event includes:

• A randomly generated device identifier (so we can count unique users without knowing who they are)
• The event type (install, first action, paywall view, conversion, uninstall, etc.)
• The extension version and your browser language
• UTM parameters if you arrived from a marketing link

The events do not include the URL or content of the thread you are saving, your name, or your email.

About thread URLs and content

When you explicitly click "Save thread" on x.com or twitter.com, the extension reads the URL and visible content of that thread to save it. The extension also calls a Twitter syndication endpoint and our tweetthreadsaver.site extract endpoint to fetch full thread data for the thread you chose to save. We do not silently read pages you have not chosen to save.

License and payment

If you upgrade to a paid plan, your device identifier is also used to verify your license. Payments are processed by Stripe; we do not see or store your card details. If you provide an email for a license, we store only that email and your plan.

Third-party services we use

• peakproductivity.online: analytics events.
• tweetthreadsaver.site backend: thread extraction endpoint, license verification, optional server-side analyze endpoint for Pro users.
• Stripe: payment processing for paid plans.
• x.com / twitter.com / syndication.twitter.com: source of the thread content you save.
• Firebase (cloud sync): optional. If you enable cloud sync, your saved threads are stored under your user account in Firestore. Firestore security rules require your authenticated Firebase UID to match the document path, so other users cannot read your threads.
• AI providers you select (Google Gemini, OpenAI, DeepSeek, Ollama, MiniMax, Aliyun DashScope, BigModel/Zhipu): when you ask the extension to summarize or translate a thread, the request goes directly to the provider using YOUR OWN API key. We do not see or store the request or response.

Permissions and why we ask for them

This extension declares only the permissions it actually uses. Each is listed in the Chrome Web Store entry, and the reason is documented there.

Data we do NOT collect

• Pages you visit outside of x.com and twitter.com
• Threads you read but never click "Save" on (we do not silently scrape your timeline)
• The content of your AI prompts or responses (these go directly to the provider you chose)
• Your name, address, or any account information beyond an email if you choose to provide one for a paid plan or cloud sync

Your rights

To request deletion of your device identifier, Firebase sync data, and any associated analytics or license records, email support@peakproductivity.online. We will delete on request.

Changes to this policy

If we change this policy, the "Last updated" date above will change and significant changes will be communicated through the extension's release notes.

Contact

Questions? support@peakproductivity.online.