Privacy Policy

1. What we process

Content drafts: title, body, images, cover, summary, category, and tags are stored in the local storage area the browser assigns to this extension (extension storage.local). Video and audio files you select are stored locally in this extension’s IndexedDB.

Platform sessions: the extension uses the cookies permission to read sessions you are already signed in to, identify available accounts, and make authenticated requests to the corresponding platform. Account export files remove sign-in credentials. Account sync also reads the platform nickname, user identifier, avatar and related profile details so you can select an account locally.

Run records: task status and failure reasons are kept locally so you can diagnose failed fills.

Source-page information: when you import a URL or use the context-menu capture, the extension processes the page title, selection or body, resource links, source URL and capture time. These may be stored locally with the draft. This does not collect your entire browsing history.

Comments and reply drafts: supported interaction tools read platform comments and associated account details, links and times when you start collection or enable automatic collection. These are kept locally for organization and reply drafting. Automatic collection follows your settings; you send the final reply yourself.

Optional services: when you actively use a text, image, search, or knowledge service, the relevant writing direction, topic details, reference material, image prompt, or query is sent to the service address you configured and selected. Requests that require authentication use that service’s API key or session credential.

Membership account data: in a build configured with the membership service, active registration or sign-in sends your email, password and optional nickname over HTTPS to Media Publisher’s own account API, backed by its independent Supabase authentication service. Unconfigured builds do not send these requests.

Registration confirmation email: Supabase generates the confirmation email and sends it through this project’s dedicated Resend SMTP configuration, from noreply@mail.publisher.aiking.dev. Resend processes the recipient address, email content containing the confirmation link, and delivery status to deliver the message. Supabase handles the account’s email confirmation status.

Licenses and orders: the independent membership service stores order identifiers, purchase periods, amounts, payment transaction references, license dates and revocations. Before filling, the extension sends a random task identifier, platform names, content type and local account count to verify access and track quota. Article content, images, platform account names and cookies are excluded. This version pauses new orders and payments while retaining historical orders, payment statuses and callback data. Direct enterprise payments are not yet available.

2. What we do not do

We never click a final publish, submit, or review button on your behalf. Every public post is confirmed by you.

We do not upload your article text, images, or platform account data to this project’s servers.

We do not read pages unrelated to content publishing for analytics, profiling, or advertising.

We do not sell personal information, nor share it with third parties for their own marketing.

We do not use or transfer user data for purposes unrelated to the product's single purpose, sell or transfer it outside approved uses, or use or transfer it to determine creditworthiness or for lending purposes.

3. Where data lives and how to delete it

Drafts, account information, configuration, and run records saved by the extension live in its storage area in the current browser profile. Clearing extension data or uninstalling the extension removes this data.

Membership accounts, orders and licenses are stored in Media Publisher’s independent Supabase project. Uninstalling the extension does not delete those server records. Signing out clears the local membership session and requests revocation of that session. Use the contact details below to reach the service provider about account or order records.

When you save an AI service configuration, the extension attempts to write its key to the local credential vault. When the vault and required local permissions are available, the key is stored in the current Windows user’s Windows Credential Manager and can be restored after a browser restart for that same user. If the vault is unavailable or saving fails, the key remains only in the current Chrome session and you are notified. Removing a configuration clears the session key first; if the local vault is unavailable, the native credential may need separate cleanup. Uninstalling the extension or native component does not automatically delete these Windows credentials. After the vault is available again, remove the corresponding model configuration or delete the entry separately in Windows Credential Manager. This storage method is for the current Windows user on the current computer; cross-device key recovery is not guaranteed.

If you enable the local article layout component, it creates temporary article files in the local application data directory and cleans up the files it manages when the session ends normally. An interruption or external changes can leave files behind. You must also delete any backup files you exported separately.

Drafts created on a target platform are stored by that platform under its own rules. Some platforms (for example the Weibo web home composer, or Dedao) keep drafts in that platform’s browser-local storage, so a refresh or a different device can lose them.

4. Third-party platforms and optional services

When you pick a platform and start filling, the extension sends the content needed for that operation to the platform. It may create an editable draft through the platform’s API or fill fields in its editor. Data sent to a platform is subject to that platform’s own privacy policy and terms.

AI, search, and knowledge services you configure may run locally or remotely. Before actively using them, check their addresses and data handling practices. This project does not control how those services retain or delete data they receive.

This policy page is hosted on Cloudflare Pages. The extension account API currently also uses a Cloudflare entry point and Supabase authentication; registration confirmation email uses Resend. Network providers receive the IP address and HTTP technical information needed to deliver these requests and the account API access logs record IP and other request metadata for service delivery, operational security and troubleshooting. This page loads no advertising, analytics scripts, forms or extension drafts.

Optional Windows Studio serves its formatting page on a dynamic 127.0.0.1 port. The extension loads that cross-origin page and scripts supplied with the separate Studio installer in an iframe, and synchronizes the current draft and theme with the local component. The AI credential component stores configured keys for the current Windows user. Both components require separate installation and are not installed automatically with the store extension.

Cloudflare, Supabase, Resend and your chosen platform or AI provider may process relevant data outside your region. Provider processing and retention follow their respective rules. Contact the email below to ask about or request deletion of this product's account or order records.

5. Permissions

storage, unlimitedStorage: keep drafts, platform configuration, and settings locally.

tabs and tabGroups open, locate and organize the assistant and platform editor tabs for the current task. activeTab reads the current page after you choose the context-menu capture.

scripting injects scripts supplied in the extension package for page capture, account reading and draft filling.

cookies: read the sign-in session of a target platform to identify available accounts.

alarms handles task timeouts and schedules comment reading according to your automatic-collection settings.

clipboardWrite: copy content to the clipboard.

sidePanel, contextMenus, notifications: side panel, context menu, and task completion notices.

nativeMessaging (optional): connect to the local article layout component, AI credential vault, or local knowledge service you enable; permission is requested as needed for the feature.

Website access: identify platform accounts, import content, and fill drafts on the corresponding platforms. Optional website access covers service addresses you select, including local 127.0.0.1 services and HTTP/HTTPS services you configure.

identity completes the browser authorization redirect when you choose GitHub sign-in for the independent Media Publisher account. Google sign-in is not generally available. Some platform-matched scripts load with the page for account identification and editor handling, not unrelated advertising profiling.

6. Children

This extension targets content creators. It is not directed at children under 14 and does not knowingly collect their information.

7. Updates and contact

The original effective date is 2026-09-22; this public version was updated on 2026-11-03. Updates are published on this page, with appropriate notice for material changes to data handling.

For questions or data requests, email 642140331@qq.com and mention Media Publisher.