Privacy Policy

Last Updated: March 25, 2026

1. Introduction

TweetClaw ("we", "our", or "the extension") is a browser extension that bridges your X (Twitter) browser session to local AI agents. This Privacy Policy explains how we handle data when you use our extension.

2. Data Collection

2.1 What We DO NOT Collect

TweetClaw does not collect, store, or transmit any of the following:

• Personal information (name, email, phone number, etc.)
• Twitter/X account credentials or passwords
• Twitter/X content (tweets, messages, profiles, etc.)
• Browsing history or behavior
• Usage analytics or statistics
• Device information or identifiers
• IP addresses or location data

2.2 What We Store Locally

The following data is stored only in your browser's local storage and never leaves your device:

• Connection Settings: LocalBridge IP address and port number
• Instance Name: Optional display name for multi-account scenarios
• Twitter API Metadata: QueryID mappings and Bearer tokens (required for API functionality)

This data is stored using Chrome's chrome.storage.local API and remains on your device. You can clear it at any time by removing the extension.

3. Data Processing

3.1 Local Processing Only

All data processing occurs entirely on your local machine. TweetClaw intercepts Twitter's GraphQL API responses in your browser and forwards them to LocalBridge running on your computer (localhost). No data is sent to external servers or cloud services.

3.2 How Data Flows

1. You visit Twitter/X in your browser
2. TweetClaw intercepts Twitter's API responses
3. Data is sent to LocalBridge via WebSocket (localhost only)
4. LocalBridge processes the data locally
5. No data leaves your computer

4. Permissions Explanation

TweetClaw requests the following permissions. Here's why we need each one:

4.1 storage

To save your LocalBridge connection settings (IP, port, instance name) locally in your browser.

4.2 tabs

To manage Twitter/X tabs (open, close, navigate) as requested by AI agents through LocalBridge.

4.3 activeTab

To access the currently active Twitter/X tab to intercept GraphQL API requests and responses.

4.4 alarms

To schedule periodic WebSocket connection health checks and automatic reconnection attempts.

4.5 cookies

To read Twitter's session cookies (specifically the twid cookie) to verify login status and extract user ID. We do not modify, delete, or create any cookies.

4.6 webRequest

To monitor Twitter GraphQL API requests to capture QueryIDs and Bearer tokens required for API operations. We do not modify, block, or redirect any requests.

4.7 Host Permissions

• twitter.com, x.com: To inject content scripts and intercept API calls on Twitter/X
• *.twitter.com, *.x.com: To access Twitter subdomains (API, media CDN, etc.)
• 127.0.0.1:8765: To connect to LocalBridge running on your computer

5. Third-Party Services

TweetClaw does not use any third-party services, analytics tools, or external APIs. The only connection made is to LocalBridge running on your local machine (127.0.0.1).

6. Data Sharing

We do not sell, trade, or transfer your data to third parties. Since we don't collect any data, there is nothing to share.

7. Data Security

All data processing happens locally on your machine. The WebSocket connection to LocalBridge uses localhost (127.0.0.1), which means data never leaves your computer. Your Twitter session remains secure within your browser.

8. User Rights

You have complete control over TweetClaw:

• Access: All stored data is in your browser's local storage
• Deletion: Remove the extension to delete all stored data
• Control: You can disconnect from LocalBridge at any time
• Transparency: Our code is open source and can be reviewed

9. Children's Privacy

TweetClaw is not intended for use by children under 13. We do not knowingly collect data from children. If you believe a child has used our extension, please contact us.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last Updated" date. Continued use of TweetClaw after changes constitutes acceptance of the updated policy.

11. Compliance

TweetClaw complies with:

• Chrome Web Store Developer Program Policies
• General Data Protection Regulation (GDPR)
• California Consumer Privacy Act (CCPA)

12. Open Source

TweetClaw is designed with transparency in mind. Our code can be reviewed to verify these privacy claims. We believe in building trust through openness.