MediaClaw Privacy Policy

Updated: October 27, 2026 Effective: March 7, 2026

Thank you for using the MediaClaw website and browser extension (collectively, "MediaClaw"). This policy explains how we collect, use, store, and protect your information when you use MediaClaw.

If you do not agree with this policy, please stop using the website and uninstall the Extension.

---

1. Information We Collect

1.1 Account, Activation, and Authorization Information

When you create a MediaClaw website account, we collect the name and email address or mainland China phone number that you provide. A phone number is converted into an internal account identifier so that you can register and sign in with a password; MediaClaw does not send an SMS or treat the phone number as ownership-verified unless a separate verification feature is introduced and disclosed. Your password is processed using a one-way password hash and is not stored in plaintext.

When you enter an activation code or order number in the Extension for authorization, we collect the following information and send it to the MediaClaw backend server:

• Activation code / order number (code): The authorization credential you enter, formatted locally before transmission
• Device identifier (clientUuid): A unique UUID randomly generated locally upon first installation, used to identify the current browser environment
• Environment label (clientLabel): Automatically detected from the browser User-Agent, e.g., Chrome on macOS
• Extension version (appVersion): The currently installed version of the Extension

This information is used to complete license verification and manage device binding (each activation code supports up to 2 independent browser environments by default).

1.2 Lark Base Target Configuration (sent when sync is triggered)

When you configure and initiate a Lark Base sync, the following configuration is sent with the sync request to the MediaClaw backend server:

• Lark Base App Token (feishuAppToken)
• Target table name or table ID (tableId, bloggerProfileTableName, bloggerNotesTableName, keywordNotesTableName)

This configuration is used to write collected data into the Lark Base table you specify. When you save a sync target, the backend stores the target configuration under your membership account or authorization credential for later retrieval and sync.

Note: The extension also caches configuration in your browser. Use the corresponding settings controls to modify or delete cloud sync targets; clearing local collection data does not delete cloud configuration.

1.3 Collected Data (Browser Local Storage)

When you trigger collection on Xiaohongshu, Douyin or TikTok, or authorize a paired local Agent to perform a collection task, the Extension stores the results in your local browser (chrome.storage.local), which may include:

• Note information: Title, link, author nickname, content, hashtags, likes/saves/comments count, publish time, image links, video links, cover image, etc.
• Creator information: Nickname, Xiaohongshu ID, profile link, avatar link, follower count, bio, and other public information
• Search / keyword results: Keywords, search result lists (including note links, cover images, titles, authors, and like counts)
• Comment information: Commenter nickname, commenter profile link, comment content, comment like count

Important notes:

• The Extension does not read the chrome.cookies API and does not actively capture cookies from any platform.
• Collected data is local by default. When you request sync, AI analysis, image text extraction, or video transcription, or authorize an Agent to read and use data, that feature processes or transmits the inputs it needs as described below. Collection alone does not automatically upload the entire data pool.

1.4 Sync History and Runtime State (Browser Local Storage)

The Extension stores the following runtime data locally:

• Sync history: Historical sync records including sync time, sync type, success/failure status, debug links, etc. (completed execution history is periodically cleared after 7 days and is also subject to per-history entry limits)
• Runtime state: Current page type, collection progress, recently active tab ID, etc.
• Authorization information: The authorization credential, local verification state, and last verification time needed to maintain authorization and make subsequent requests. Unbinding in the extension or browser extension-data clearing removes the local credential.

1.5 Download and Export Actions

When you select Excel, CSV, JSON, or Markdown export, or request attachment downloads, the extension generates local files or reads files from their media URLs using browser download capabilities. You explicitly trigger the export, and the files are saved to your device. Locally generated data-export files do not pass through the MediaClaw server.

1.6 Website Analytics and Attribution

When you visit the MediaClaw website or perform key product actions, we collect limited analytics and attribution data, which may include:

• A randomly generated anonymous browser ID and session ID
• Page path, landing page, and referring website origin/path
• Campaign parameters such as utm_source, utm_medium, utm_campaign, utm_content, utm_term, source, ref, and via
• A normalized acquisition channel and attribution confidence
• Key events such as page views, pricing or download actions, registration, checkout, and payment success
• Account ID after you sign in, where needed to connect product activity with registration or payment results

MediaClaw stores first-touch and last-non-direct attribution context in browser local storage and a first-party cookie for up to 90 days. An attribution snapshot may also be stored with an order when checkout begins. This is used to understand product performance and campaign effectiveness, connect acquisition sources with registrations and revenue, prevent abuse, and improve MediaClaw. We do not use third-party advertising cookies for this purpose and do not sell this data to advertisers.

1.7 AI Analysis and Content Extraction

When you request account analysis, note breakdown, writing, image text extraction, or video transcription, the MediaClaw backend processes the text, comments, image or audiovisual links, extracted text, and instructions needed for that task. It sends necessary inputs to the applicable AI or content-processing service. Depending on the feature and configuration, these services currently include Coze, Alibaba Cloud, OpenRouter and the model providers it routes to, Moonshot/Kimi, or DeepSeek. The AI workspace retains generated research, topics, drafts, and task state for later use. Clearing browser collection data does not delete these workspace assets.

1.8 Local Agent Pairing and Data Use

A local host such as Codex, WorkBuddy, or Doubao Work can call the extension only after you enable Agent access and approve the particular device in the extension. Pairing information, device names, and connection state are stored locally. Authorized interfaces can read the data-pool records, local AI workspace assets, and remote workspace assets accessible to your current membership account that are needed for your task. They can also run public-page collection and content extraction within the scope you authorize. These interfaces do not provide activation codes, platform cookies, access tokens, or similar credentials to the Agent.

Results enter the task context of your chosen host, which may send them to its own model service or retain task records according to that service's settings. An approved Agent communicates with the extension through a loopback address on the same computer; this does not give arbitrary public web pages permission to call the Agent. You can disable Agent access or revoke a particular device in the extension. Revocation stops future calls; it does not delete content already retained by the host, which must be managed in that service.

1.9 Comment Filtering and Direct Messages

Comment filtering uses the comment text, public nicknames, profile links, and user identifiers you have collected. When you use the extension directly, you confirm the recipients and message text in the extension. When you use a paired Agent, it first shows the sender account, every actual recipient, and the full message text in the conversation. The Agent may request sending only after you explicitly approve that final plan; you can also revise or cancel it first. Text confirmation in the conversation is relayed to MediaClaw by your chosen Agent. Both entry points use the same extension messaging flow to send through the currently signed-in platform account by operating the page.

Recipients, message text, sender account identifiers, execution state, and send times are stored locally to show progress, prevent duplicate sends, enforce intervals, and handle recovery. The message is transmitted to Xiaohongshu or Douyin and the intended recipient. Stopping a task or clearing local records does not recall a message already sent.

1.10 Notifications and Referral Links

The notification center sends a device identifier, any available authorization credential, extension version, and language to the MediaClaw backend. The backend uses account and membership state, days of use, and aggregate counts of successful operations to select applicable notifications. It sends necessary account context and a hashed account or device identifier to the website notification service. Hashing does not mean that this information can no longer be associated with an account.

The website retains notification IDs, subject identifiers, and timestamps for impressions, reads, dismissals, and action-button clicks to maintain unread state, prevent duplicates, and limit repeated reminders. Store-review invitations record notification interactions; they do not read the rating or review text you submit to the store.

When you request your referral link, the backend verifies that your authorization credential belongs to the website account before requesting that account's invitation code and link. Recipients can see the invitation code when you share the link. Referral relationships, discounts, and commissions are handled by the website referral feature. Notification receipts and website referral records are stored on the server and are not deleted by browser-local cleanup.

1.11 Information We Do Not Collect

• No collection of bank card numbers, payment passwords, or other financially sensitive information
• No collection of login passwords for any platform
• No capture of browser cookies (the chrome.cookies API is not called)
• No recording of full keystrokes, mouse movements, scrolling sessions, or page DOM replays
• No collection of any personal information unrelated to the Extension's functionality

---

2. How We Use Your Information

Information we collect is used only for the following purposes:

• License verification and device management: Verifying activation code validity and managing the number of bound devices per activation code
• Data sync relay: Forwarding collected data from syncs you initiate to the Lark Base table you specify
• Collection feature support: Executing collection logic on Xiaohongshu, Douyin or TikTok pages you authorize and caching results locally
• Export and download: Responding to your explicit actions to generate export files or download attachments locally
• AI and Agent tasks: Analyze, extract, and use selected data within the task you initiate or authorize
• Comment outreach: Execute the recipients and message text you explicitly approve and retain necessary task state
• Notifications and referrals: Deliver applicable notifications, record notification interactions, and verify and generate account referral links
• Troubleshooting: Using local sync history to help you diagnose sync failures
• Product analytics and attribution: Measuring website and product performance and connecting acquisition sources with registrations, orders, and revenue

---

3. Storage and Security

3.1 Local Storage (Browser Side)

The following data is stored in your browser extension's local storage (chrome.storage.local):

The "Clear local collection data" action clears the data pool, collection progress, completed execution records, and related caches. Ongoing tasks may need to finish first. It preserves authorization and settings, AI workspace assets, active tasks, and outreach rate-limit and recipient-history records still within their retention windows. Completed execution history is generally retained for 7 days and outreach send events for a 24-hour window; records required by active tasks are preserved. Periodic history cleanup does not automatically delete the collected data pool.

Local cleanup does not delete exported files, Lark content, website server records, or tasks retained by an Agent host. Browser extension-data clearing or uninstalling the extension can remove its browser-local data. Website, cloud-workspace, and Agent-host data must be managed in the respective service or through a request to us.

The website also stores attribution context in browser local storage and a first-party cookie for up to 90 days. You can remove it by clearing site data for the MediaClaw website.

3.2 Server-Side Storage

We store the minimum information necessary to operate and improve MediaClaw on our backend servers:

• Activation code / order number status (valid / expired / frozen)
• Device UUID binding associations and most recent verification time
• Account profile and login identifier (name and email address or phone-backed internal identifier) plus the password hash required for authentication
• Limited analytics event records, including anonymous/session identifiers, page and campaign attribution data, event type, and event time
• Registration, order, and payment attribution snapshots used to calculate conversion and revenue by source
• AI workspace outputs and task state, notification receipts, and referral relationship and settlement records (see Sections 1.7 and 1.10)

Collected data in a sync request is processed by the backend and workflow service and forwarded to your chosen target. Separately saved Lark target configuration and sync execution logs are retained on the server to support later syncs, status queries, and troubleshooting.

3.3 Security Measures

• Authorization information is stored in browser extension local storage. Agent data interfaces do not provide this credential, and unbinding clears the local authorization state.
• API connections to cloud services use HTTPS. An approved local Agent connects through the loopback address on the same computer.
• The server employs access control and data minimization principles
• We have made reasonable efforts to protect data security, but cannot guarantee 100% security in all circumstances. Data breaches resulting from user-side causes (e.g., device infected with malware, weak passwords, account compromise) are outside the scope of this policy

---

4. Information Sharing and Third-Party Disclosure

We do not sell, rent, or provide your personal information to advertisers or data brokers unrelated to the Extension.

We share necessary information with the following third parties only to the extent required to deliver the Extension's core functionality:

Sections 1.7–1.9 also describe data sent to AI services, your chosen Agent host, and the platform and recipient involved in direct messages.

These parties receive data to provide the corresponding function and also process it under their own service terms and privacy policies.

We will not disclose your information to any other party except in the following legally required circumstances:

• With your explicit consent
• As required by law, judicial authority, or administrative authority
• In the event of a business reorganization (merger, acquisition, etc.), we will require the successor to continue being bound by this policy

---

5. Chrome Permission Usage

The browser permissions requested by the Extension and their purposes are as follows:

---

6. Your Rights

In accordance with applicable laws and regulations, you have the following rights:

• Right to be informed: The right to know how we process your information (i.e., this policy)
• Right of access: You may view locally cached collected data, configuration, and sync history in the Extension at any time
• Right to rectification and deletion: You may modify Lark Base configuration or clear collected data and sync history in the Extension at any time
• Right to restrict processing: You may stop sync, AI, or content-extraction tasks, disable Agent access, and view or export existing collected data locally
• Authorization release request: If device binding slots are exhausted due to a device change or browser reinstallation, you may contact us to manually release a slot
• Right to withdraw consent: You may uninstall the Extension and clear extension data at any time to withdraw your consent to this policy
• Website data controls: You may clear MediaClaw website data in your browser; you may also contact us to request access to or deletion of server-side data that can reasonably be associated with you, subject to legal retention requirements

---

7. Protection of Minors

The Extension is intended for adult users with the appropriate legal capacity, primarily serving content creators, KOL operators, and similar professionals. It is not directed at users under the age of 18.

If a minor needs to use the Extension, they should do so under the knowledge and guidance of a guardian. If we discover that a minor is using the Extension without guardian consent, we will take necessary measures (including restricting use).

---

8. Policy Updates

We may update this policy when product features, legal requirements, or data processing practices change.

• Updated policies will be published on the official website / extension release page, and the "Updated" date at the top of this document will be revised
• For significant changes, we will provide advance notice via in-extension pop-ups or release notes
• If you do not agree with the updated content, you may stop using and uninstall the Extension; if you continue to use it, you are deemed to have accepted the updated content

---

9. Contact Us

If you have any questions, suggestions, or data deletion requests regarding this policy, please contact us via:

• Email: support@mediaclaw.app
• Tutorial / Documentation: The "Tutorial" link in the Extension sidebar

We will respond within 15 business days of receiving your request.