X Spam Guard Privacy Policy

Overview

X Spam Guard is a Chrome extension designed to help users identify and manage spam accounts on X/Twitter. The extension analyzes visible account names, profile bios, comment text, and related page information to classify potential spam, sync a user-managed blacklist, and assist with block-task execution through a user-configured backend service.

Information processed

Depending on the user's settings and usage, X Spam Guard may process the following data:

• Visible account handles, display names, profile bios, and comment text on supported X/Twitter pages.
• URLs or page context needed to associate a spam report or block task with the visible page.
• Extension settings such as backend server URL, client token, sync status, blacklist cache, and user preferences.
• Spam classification results, rule matches, confidence scores, task status, and user-approved reports.

How information is used

The extension uses this information only to provide its spam detection, blacklist synchronization, and block-task management features. Data is used to score potential spam accounts, request optional AI-assisted review from the configured backend, display reasons for decisions, and keep block-task status in sync.

Data sharing and transfer

X Spam Guard does not sell user data. The extension sends data only to the backend service configured by the user or administrator for the purpose of spam classification, blacklist sync, contribution review, and task status updates. If the backend is configured to use an AI provider, the backend may send the necessary classification payload to that provider according to the user's backend configuration.

Remote code

The Chrome extension does not execute remote JavaScript or WebAssembly. Extension code is included in the submitted extension package. Network requests to a backend API are used for data processing and synchronization, not for loading executable extension code.

Storage

The extension stores settings and operational state locally in the browser, including backend configuration, sync state, blacklist cache, and preferences. The backend may store blacklist entries, reports, classification decisions, and task status so the user or administrator can review and manage spam detection results.

User control

Users or administrators control the backend server configuration, AI provider configuration, blacklist rules, and report review process. Users can disable the extension, remove it from Chrome, clear local extension data, or request deletion of backend records from the administrator of the configured backend.

Security

X Spam Guard is designed to limit data use to its single purpose: spam detection and blacklist management. Admin and client tokens should be kept private. Users should only configure backend services they trust.

Contact

For support or privacy questions, please open an issue on the project repository: https://github.com/YuJiaoChiu/x-spam-guard/issues