Privacy Policy: AI Boost for Threads (Unofficial)

Last Updated: May 30, 2026

We are committed to maintaining robust privacy protections for our users. This Privacy Policy is designed to help you understand how we collect, use, and safeguard the information you provide to us when using AI Boost for Threads (Unofficial) (the “Extension”).

1. Core Commitment to Privacy

This Extension is designed to be completely serverless and offline-first. * We do NOT own or operate any database or backend server. * We do NOT collect, harvest, read, or track any of your browsing history, analytics, personal information, or API requests.

Your data remains 100% yours and never leaves your browser, except when communicating directly with your configured AI model endpoint.

2. Information Stored Locally on Your Device

To provide writing assistance, the Extension stores configuration parameters inside your browser’s secure sandbox environment (via chrome.storage.sync or localStorage).

These parameters include: * OpenAI API URL & API Key: Used to authenticate prompts directly with your chosen LLM provider. * Selected Model Name: The specific model you chose to execute prompts. * User Writing Profile: Your customized Name, Username, and Persona descriptions to align the AI’s writing style with your personality.

[!IMPORTANT] All stored credentials and writing preferences reside strictly locally inside your local Chrome profile storage. They are never transmitted, synchronized, or visible to the developers of this Extension.

3. Third-Party Data Transmission

When you click “Generate Reply” or “Generate Post”, the Extension performs a direct network request (fetch) from your browser to your configured API URL (e.g., OpenAI or OpenRouter).

What is Sent:

  • The raw text of the Threads post you are replying to (parsed locally in real-time).
  • Your local writing profile metadata (Username, Account Name, Persona description).
  • Your custom additional context instructions (from the input textarea).

How it is Sent:

  • This payload is sent directly to the secure endpoint URL you supplied under your own authorization headers (API Key).
  • No middleman, gateway proxy, or secondary servers are used. The transaction is strictly direct between your browser and the configured model provider.

4. No Analytics, Cookies, or Telemetry

  • No Cookies: The Extension does not set or read any cookies.
  • No Analytics: We do not include Google Analytics, Mixpanel, tracking pixels, or any telemetry engines inside the extension source files.
  • No Remote Scripts: In strict adherence to Chrome Web Store Security Policies, the Extension contains no remote hosted code or libraries. Everything runs locally from the unpackaged local files.

5. Your Choices & Controls

  • Key Deletion: You can erase your API credentials and profile settings at any time by opening the extension popup, entering “Edit” mode, clearing the values, or uninstalling the Extension.
  • Bypassing Sync: Chrome’s sync storage coordinates configurations across your own logged-in Chrome devices. If you do not wish to sync configurations across your devices, you can disable Extension Sync in your Google account settings.

6. Compliance with Chrome Web Store Policies

The Extension complies with the Google Chrome Web Store Developer Agreement, including the Single Purpose Policy and the User Data Privacy Principles (Minimal Permissions Principle).

7. Contact & Support

If you have any questions regarding this Privacy Policy or the local data footprint of this Extension, please contact us directly at: [email protected].

Share this page
share link