Privacy Policy - ThreadToBlog Converter
This privacy policy explains how the ThreadToBlog Converter Chrome extension handles data.
Summary
- The extension runs locally in your browser.
- It does not operate any servers.
- It only processes data you explicitly provide (a Twitter/X thread URL or the current tab).
- If you enable AI formatting, the thread content is sent to your configured OpenAI-compatible API endpoint.
Data We Process
Thread content and URL
- When you convert a thread, the extension reads the visible thread content from the page you open.
- This content is used to generate Markdown or HTML output.
API key (optional)
- If you enable AI formatting, you may store an OpenAI API key in Chrome sync storage.
- The key is used only to call your chosen AI endpoint.
Custom Base URL / Model (optional)
- If provided, these settings are stored to configure the AI request.
How Data Is Used
- To extract and format thread content into blog posts.
- To call an AI API only when AI formatting is turned on.
Data Sharing
- The extension does not share data with the developer or any third parties.
- If AI formatting is enabled, the thread content is sent to the API endpoint you configured.
Data Storage
- Settings (API key, base URL, model) are stored in Chrome sync storage on your device/account.
- You can remove them at any time from the Options page.
Children's Privacy
This extension is not directed to children under 13 and does not knowingly collect personal information.
Changes to This Policy
If this policy changes, the updated version will be included with the extension and the effective date will be revised.
Contact
If you have questions, contact the extension publisher through the Chrome Web Store listing.