Scope
This policy applies to the Chrome and Edge extension WeChat to Markdown (formerly also named 网页归档助手) and wx2md.com. It is provided by independent developer Wangshan and is not affiliated with, authorized by or endorsed by Tencent or WeChat.
Articles and public collections
When you actively use the extension, it reads WeChat articles, public collections or ordinary article pages you have permission to access. It locally creates Markdown, HTML, PDF, images, ZIP archives and library records. Processed fields can include titles, authors, source names, publication times, bodies, image URLs and source links.
This article content is not uploaded to the operator’s servers. You choose where to save generated files. Library bodies, archive collections, filters and knowledge-base directory handles remain in extension-local storage.
Licensing, orders and necessary requests
When you redeem or activate a paid license, the extension sends a license code or email address, a random installation ID and the extension version to the licensing service to verify entitlements and device counts. That service does not receive article bodies, article URLs, titles, images, Cookies or browsing history.
The website has no license-code input. Enter codes only in the installed extension’s activation screen, available from the toolbar popup, article, collection or local library. A single submission redeems the code and activates the current device.
Online purchases use the operator’s NAS Work service to process products, orders, payment amounts, transaction status and associated license codes. WeChat Pay handles payment. The purchase page sends a product ID and random order-access credential to NAS Work and displays the delivered code after payment. The credential stays in the URL fragment, which is not sent to the static website host; queries send it in the body of an HTTPS request to the order service. Anyone holding the complete order link can view its code. Do not share it. Home and pricing pages containing checkout never load third-party analytics scripts. Order-access credentials, license codes and payment-provider transaction credentials are excluded from analytics. Consented order attribution and payment measurement are described below.
If you add the maintainer on WeChat, WeChat processes your account and conversation data. Share only what is needed for troubleshooting; do not post article bodies, Cookies, Tokens, license codes, payment receipts or identity documents publicly.
External feedback form
The support page links to an external Feishu form. Submitted feedback goes directly into the operator’s Feishu Base; the website does not read, store or transmit form answers. Contact details are optional and needed only if you want a reply.
Feishu may process network, device and account information according to its privacy policy. Do not submit article bodies, Cookies, Tokens, license codes, payment receipts or identity documents in the form or public issues.
Optional product and website analytics
Extension analytics
Product analytics are off by default. You may opt in using the toolbar popup’s privacy and usage controls and withdraw at any time; refusal does not affect export or purchased entitlements. When enabled, allowlisted events go to the operator’s NAS Work service to understand installation, daily use, feature completion and failure categories.
Fields are limited to random installation ID, version, distribution channel, platform, optional interface language, feature entry point, export format, count ranges, broad error category, purchase/activation stage, allowance-rule version, new/existing free-install group, allowance source and monthly usage stage. Event IDs deduplicate retries. These fields measure allowance use and activation conversion; activation is not treated as proof of payment. Third-party analytics credentials remain on trusted servers and are not included in the extension package.
Extension analytics exclude article content, URLs, titles, site names, Cookies, email addresses, license codes and Tokens. Failures do not block export, licensing or the local library. Withdrawal stops future events and clears the unsent queue; previously sent records are not automatically deleted, but you can request deletion privately. The random installation ID links events from one installation and is also used for licensing, so it is pseudonymous rather than irreversibly anonymous. Servers may also record IP addresses and request times; these are not used to analyze article content.
Website analytics
Website analytics are disabled by default. After explicit consent, the operator’s NAS Work service receives a website-only random identifier, product and version, language, allowlisted page category, source codes and coarse browser and device categories. This measures page visits, visible plans, purchase-entry clicks, checkout confirmation and displayed payment QR codes. The website identifier is separate from extension identifiers and does not use cross-site fingerprinting. With consent it links to new orders, so it is pseudonymous, not irreversibly anonymous. Earlier visit-only consent does not automatically authorize order linkage; a new choice is required.
Validated UTM or source codes take precedence; otherwise the browser locally classifies a referring site into search, referral or unknown. Raw URLs, query strings, fragments, referrers, User-Agent strings, forms, articles, emails, license codes and order-access credentials are not sent to analytics. Missing referrers may mean direct visits, copied links or browser restrictions, so the real source is unknown. The first source is stored locally for up to 90 days and the latest valid source for up to 30 days. Internal navigation and direct visits do not overwrite an unexpired source or extend its lifetime. New validated source parameters or an external referral update the latest source. Allowlisted surface and trigger values identify coarse extension entry points and provide fixed purchase guidance; arbitrary message text is never read or sent.
Home and pricing pages containing checkout use only first-party analytics and never load third-party analytics scripts. With consent, a new order includes the website random identifier, consent version, source, browser and device categories so NAS Work can associate visits with verified payments. Restored orders and retries do not replace the original source. QR display, activation and reactivation are not proof of payment. Declining does not affect purchasing; unlinked orders are reported separately rather than mixed into consenting-visitor conversion rates.
Pages without checkout may load Google Analytics 4 after consent, sending sanitized page paths, content categories and click positions. Google Signals and advertising-personalization signals are disabled. Only genuine GA client and session identifiers obtained on those pages are cached in this tab for up to 30 minutes. A new order may include that context; when server forwarding is enabled, NAS Work may send a deduplicated transaction identifier, plan, amount and currency after verified payment. It never forwards license codes, order-access credentials, emails or payment-provider transaction credentials. Missing GA context is never fabricated; first-party NAS reporting remains available.
Decline or withdraw using “Analytics settings” at the bottom of any page. Withdrawal immediately stops local analytics and clears website identifiers, sources, GA context and accessible GA Cookies. It also requests server withdrawal for that website identifier; once confirmed, NAS Work stops subsequent analytics and payment forwarding for it. Network failures are shown as pending. Only up to 20 pending website identifiers are retained to retry when online or on a later visit, and removed on success. If more than 20 requests accumulate, only the latest 20 can retry automatically and older requests require private support; the page shows this limitation. Clearing site data also removes unsent withdrawal requests; contact private support if further help is needed. Previously sent records are not automatically deleted, and necessary transaction records remain subject to contractual and legal retention. Choices are stored in this browser; clearing site data prompts again.
Google processing
Only after consent do pages without checkout make HTTPS requests to Google. NAS Work may also forward verified payment analytics when the order has valid, consented GA context. Google may process network and device information under its privacy policy and data-processing terms. Home and pricing pages never load Google analytics scripts. We do not use usage analytics for advertising, cross-site profiling, credit assessment or AI training.
Retention and security
- You store articles in your browser or chosen folders; the operator has no server copy.
- Free allowances, migration bonus markers and unfinished export records are stored locally to prevent duplicate deductions and recover interrupted operations. They do not contain article bodies. Clear extension or website data to remove local settings and checkpoints.
- Uninstalling, clearing browser data, switching browsers or browser profiles may make library data and checkpoints unrecoverable.
- Orders, financial records and licenses are retained as needed for contracts, support and legal obligations.
- Licensing and analytics use HTTPS. Local SiYuan connections contact your configured local address only when you initiate synchronization.
Your choices and rights
You may stop using or uninstall the extension, clear local browser data, withdraw website analytics, disconnect knowledge-base directories and use private WeChat support to request access, correction or deletion of license contact information and linkable analytics records held by the operator. Transaction records required by law may be retained.
Do not paste article bodies, Cookies, Tokens, license codes, identity documents or other sensitive information into public discussions.