Twitter Master

Last updated: March 8, 2026

Overview

Twitter Master is a Chrome extension that helps users draft AI-assisted content and automate selected actions on X/Twitter. The extension processes only the data needed to provide the features the user explicitly enables.

Data We Process

• User-provided settings such as AI provider, model, automation limits, schedule preferences, and optional custom endpoint.
• User-provided API keys for the selected AI provider.
• Visible X/Twitter page content needed for enabled features, such as tweet text, profile handles, user lists, and reply composer context.
• User-entered prompts, reply ideas, draft text, and assistant selections used for AI generation.
• Local activity data such as automation status, scraped handles, action logs, daily counters, and voice/profile analysis results.

How Data Is Used

• Generate replies, tweets, threads, and voice/profile analysis through the AI provider selected by the user.
• Run automation features such as follow, unfollow, like, bookmark, retweet, scraping, and keyword monitoring on X/Twitter.
• Store local configuration, usage counters, and session state in chrome.storage.local.

When Data Leaves the Browser

Data is sent out of the browser only when required by an enabled AI feature.

Depending on the provider selected by the user, relevant prompts and context may be sent to OpenAI, Anthropic, Google Gemini, Groq, OpenRouter, or a custom OpenAI-compatible endpoint configured by the user.

No X/Twitter page content is sent to an AI provider unless the user uses an AI feature that requires it.

What We Do Not Do

• We do not sell user data.
• We do not run advertising trackers.
• We do not run third-party analytics inside the extension.
• We do not send user data to the developer for manual review.

User Control

• Users can change or remove API keys and settings at any time.
• Users can clear scraped users and local activity logs from the extension UI.
• Users can uninstall the extension to remove locally stored extension data from Chrome.

Security Notes

API keys are stored locally in the browser profile and used only to call the provider selected by the user. If the user configures a custom endpoint, data sent to that endpoint is governed by the user’s chosen provider or gateway.

Contact / Support

Add your public support email or support URL here before publishing this document at a public HTTPS URL for the Chrome Web Store listing.