Website analytics and privacy
Wenbo loads traffic and experience analytics only on public website pages. Account, password, MCP-key management and feedback form pages do not load these scripts.
First-party analytics uses separate random website and installation IDs. Extension analytics can be disabled on sign-in or in Settings. Authenticated actions are associated with the verified Wenbo account. Event detail is kept for 90 days, followed by daily totals and deduplicated first-use timestamps. Successful MCP tool calls are counted separately.
Traffic analytics and URL handling
Google Analytics 4 measures public page views, referrers and extension download clicks. Event URLs omit query strings and fragments; titles use fixed public labels and external referrers retain only their origin. Account email, passwords, MCP keys, drafts and platform cookies are not sent.
Experience analytics and masking
Microsoft Clarity uses strict masking with default cookies disabled. Pages with queries, fragments or sensitive referrers skip Clarity. Navigation into account flows loads a new document, unloading analytics scripts.
Browser preferences and third-party services
The website respects Do Not Track and Global Privacy Control. Local development and preview domains do not send production analytics. Blocking analytics does not prevent downloads or account use.
Google Privacy Policy · Microsoft Privacy Statement
Extension and MCP data boundaries
This page describes website analytics. See the FAQ for local extension content, platform sessions and the MCP relay. Platform cookies stay out of the relay; text and images sent through MCP pass through it.
Data and security FAQLast updated: · Wenbo