Follower Manager and backup for Threads – Privacy Policy

Why needed: Ensures that your custom settings and task preferences are preserved between sessions, so you don't need to reconfigure the extension each time you use it. Additionally, it enables the storage of extensive task history records for your review and management.

Data handling: All data is stored locally using Chrome's storage API and is never transmitted to external servers.

Why needed: Enables the extension to interact with the Threads web interface, allowing it to display our custom UI elements and perform automated actions (e.g., scraping followers and following lists, exporting profiles) according to your configured parameters.

Scope: Content scripts run solely on Threads pages where you explicitly activate the extension, and they do not access any unrelated websites or tabs.

Why needed: As users may generate extensive task records over time, this permission ensures the extension can maintain a complete history for your reference without data loss or performance degradation.

Data handling: All data remains stored locally in your browser's IndexedDB and is never uploaded to external servers.

Why needed: Threads cookies: Used to authenticate your session with Threads, enabling the extension to perform authorized actions (like scraping and exporting follower data) on your behalf. PingApps cookies: Used to verify your membership subscription status and synchronize your account information with our API server.

Security note: The extension only accesses cookies for the domains explicitly authorized by you. Threads cookies are held temporarily in volatile memory and are never persisted to disk or transmitted externally.

Why needed: When scraping and exporting followers and following data, the extension needs to extract dynamic parameters such as session tokens, CSRF tokens, and request signatures from ongoing network traffic. These parameters are not available via static configuration and vary per session or request. The webRequest permission allows the extension to read and parse these headers and payloads in real time, ensuring that subsequent API requests include the required authentication and state data. Without this capability, the extension cannot properly replicate the browser's native request logic, leading to failed API calls and broken functionality.

Privacy: The extension only inspects requests related to follower scraping and export operations and does not log, store, or transmit any user data or request contents outside the local processing scope. All extracted parameters are used solely for constructing valid follow-up requests and are discarded immediately after use.

Why needed:

Scope: The extension only interacts with these specific domains and does not access any other websites or services. All API communications are encrypted via HTTPS and use minimal authentication data.