Wisdio AI Privacy Policy

Last updated: August 18, 2026

Wisdio AI ("Wisdio", "we", "us") is a browser extension that captures page content and video subtitles, lets you converse with AI models using your own API keys, and helps you manage notes. This policy explains what information the extension handles and what our product analytics feature collects. It applies to the Wisdio AI extension available on the Chrome Web Store and our website at wisdio.org.

Summary

• Pseudonymous product analytics are enabled by default. You can turn them off at any time in Wisdio settings. When disabled, collection stops immediately and unsent analytics are discarded.
• Wisdio does not intentionally send your page content, page titles, subtitles, notes, AI conversations, prompts, clipboard contents, or API keys to Wisdio or PostHog as product analytics data.
• Product analytics contain event names, enum-like result and error categories, coarse size/count buckets, interface and app-version information, timestamps, and a random local installation identifier. PostHog may also process standard pseudonymous technical metadata as described below.
• Feedback is an explicit exception. If analytics are enabled and you write and submit feedback in the settings page, the feedback text you submit is sent to PostHog along with its category. Please do not include personal information or credentials in feedback.

Because the analytics provider may process pseudonymous device/session identifiers and technical metadata, we describe this data as pseudonymous, not as fully anonymous data.

Information processed locally and when content is shared

The following information is handled locally by the extension and is not sent to Wisdio or PostHog as product analytics data:

• Captured page content and subtitles — kept in the extension's local storage and sent only to the AI provider you configure with your own API key when you ask Wisdio to analyze, summarize, translate, or chat about that content.
• Your notes, conversations, and saved prompts — stored locally in the extension unless you explicitly use a feature that sends the relevant content to a service you configured yourself.
• API keys — stored in the extension's local storage and used solely to call the AI provider you selected. Wisdio does not send these keys to Wisdio or PostHog.
• Obsidian-linked notes — written directly to your local Obsidian vault through Wisdio Companion or the Obsidian Local REST API. Wisdio does not upload them to a Wisdio cloud service.

When you invoke an AI feature, the relevant context is sent directly from the extension to the AI provider configured by you. That provider's own privacy policy and terms apply to its processing.

Pseudonymous product analytics (enabled by default, opt-out)

Wisdio uses PostHog as its product analytics provider. Analytics are enabled by default under an opt-out model: a new installation collects analytics unless you explicitly turn off Help improve user experience in Wisdio settings.

Wisdio's custom event fields are designed to be low-detail and low-cardinality. They may include:

• the event name, such as capture_completed or subtitles_extracted;
• enum-like outcomes and stable error categories, such as success, failure, authentication, or rate_limit;
• coarse size, count, and latency buckets;
• the desktop or mobile surface, app version, and event timestamp; and
• a randomly generated installation identifier stored locally, used only to distinguish repeat events from the same installation.

Wisdio does not intentionally include page URLs, page text, page titles, subtitles, notes, prompts, AI replies, clipboard contents, API keys, Obsidian keys, or raw error messages in these custom event fields.

Technical metadata added by PostHog

PostHog may automatically attach standard technical metadata to explicit events. Depending on the browser and provider processing, this may include pseudonymous device, session, and browser identifiers; browser, operating-system, and User-Agent information; screen and viewport dimensions; language and time zone; extension URL or referrer metadata; and a coarse geographic location inferred from the request IP address (GeoIP).

This metadata may be linkable at a pseudonymous device or session level, but it does not contain a direct name, email address, API key, or product content supplied to Wisdio. Wisdio configures PostHog with person profiles, autocapture, pageview capture, and session recording disabled; no PostHog cookies or persistent analytics storage are used; campaign/referrer persistence is disabled; and the transport respects the browser's Do Not Track signal. PostHog is used only to improve Wisdio, not for advertising, advertising profiling, or selling data.

User feedback

The settings page includes an optional feedback form. If analytics are enabled and you click Send Feedback, Wisdio sends the category (feature request, bug report, or other) and the text you submitted, capped at 2,000 characters, to PostHog as a user_feedback_submitted event. This is the only Wisdio analytics event that intentionally carries user-written free text. The form is disabled when analytics are turned off. Please do not submit personal information, API keys, access tokens, or other confidential information in feedback.

Provider, region, and retention

Analytics events are sent to PostHog through its EU-hosted endpoint in Frankfurt. PostHog is provided by PostHog Inc.; see PostHog's privacy policy. Our current project configuration may retain analytics data for up to 13 months. Authorized Wisdio maintainers may access submitted feedback in the PostHog project to review and respond to product feedback.

Disabling analytics stops new collection immediately and discards events that have not yet been sent. Clearing Wisdio's extension storage or removing the extension deletes the locally stored installation identifier and any unsent local analytics state. Events already received by PostHog are subject to the provider/project retention period; contact us below if you have a question about an analytics event or submitted feedback.

No sale or advertising use

We do not sell, rent, or trade your personal data, browsing history, or user-generated content. Wisdio does not use analytics for advertising or cross-site advertising profiling. The AI provider and any other service you explicitly configure are separate services and process data under their own terms.

Permissions and why we need them

• activeTab, scripting, sidePanel, and storage — capture the current page when you ask, show the Wisdio panel, and store settings, notes, conversations, and captured content locally.
• Host access to webpages and supported video sites, including YouTube, Bilibili, Coursera, and Wistia — capture content or extract subtitles when you use those features.
• Host access to AI provider endpoints, including SiliconFlow, DeepSeek, and OpenRouter — call the AI provider you configured with your own API key.
• The PostHog EU analytics endpoint — send the explicit pseudonymous product events described in this policy when analytics are enabled.
• 127.0.0.1 / localhost — connect to the Obsidian Local REST API or Wisdio Companion plugin on your machine.

Your choices

• Keep Help improve user experience enabled (the default), or turn it off at any time in Wisdio settings.
• When analytics are off, the feedback form is disabled and pending analytics are discarded.
• Clear Wisdio's local data at any time by removing the extension or clearing its extension storage. This removes local settings, keys, notes, conversations, and the local analytics identifier; it does not automatically erase events already received by PostHog.
• Contact us with questions about this policy or data handled by the analytics feature.

Children

Wisdio is not directed at children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from children.

Changes to this policy

We may update this policy to reflect product, provider, or legal changes. Material changes will be announced with an extension update, and the Last updated date above will be revised.

Contact

Questions about this policy or your data: [email protected].