Privacy Policy

Vidskim does not sell personal data or use transcript or chat content for advertising. This policy explains what is processed when you use the extension, hosted AI, authentication, the website, and the Vidskim connector for AI assistants.

The Vidskim Chrome extension

Transcript and local extension data

The extension first tries to read the available captions of the YouTube video you are viewing in the browser. When that path is unavailable, it may send the video ID and requested language to the Vidskim transcript proxy, which returns public caption text and may cache it temporarily for reliability. Transcripts, recent chat state, preferences, anonymous analytics identifiers, authentication sessions, and any optional AI API key are stored in Chrome extension storage on your device.

Reading, searching, copying, or exporting does not invoke the AI endpoint. A transcript obtained through the fallback proxy has already passed through Vidskim's transcript service; transcript and prompt text is sent to an AI provider only when you actively trigger an AI feature.

Free hosted AI

When you use summary, chat, takeaways, or AI translation without adding your own API key, the relevant transcript text, your prompt, and the requested operation are sent over HTTPS to vidskim.com/api/ai. Vidskim forwards that content to an AI routing service, which sends the request to an AI model provider and returns the response.

Hosted-AI content is processed only to answer the request you initiated. Vidskim does not store raw transcript text or prompts in its application database and does not send transcript, prompt, or response content to product analytics. To avoid paying for and repeating an identical Quick Action, Vidskim may cache the generated response for up to 30 days under a one-way hash of the transcript and request settings. The hash cannot be used to reconstruct the transcript. The AI routing service and the model provider process requests under their own terms and privacy policies.

Authentication and usage limits

Hosted AI uses Vidskim's self-hosted authentication service. Before sign-in, Vidskim creates an anonymous account and session. After the initial free runs, you may sign in with Google. Google provides Vidskim with account information such as your Google account ID, email address, name, and profile image according to the permissions shown during sign-in. Email one-time codes are not currently enabled.

Authentication sessions and tokens are kept in extension storage. Vidskim's hosted-AI server receives the access token, validates it, and uses the resulting user ID and account status to enforce free usage limits and any plan status configured in the service. Vidskim stores authentication records, usage counters, model and token counts, estimated request cost, short-lived concurrency records, and plan-status fields in its database; it does not store transcript or prompt content with those records. If you voluntarily select a 1–5 star rating to claim the one-time daily-limit reward, Vidskim stores that rating and the reward-claim time with the same user ID so the reward cannot be claimed more than once.

Optional bring-your-own-key AI

You can optionally add an API key for one of the supported AI providers. The key is stored only in Chrome extension storage. In this mode, the relevant transcript and prompt are sent directly from the extension to your selected provider; Vidskim's hosted-AI server does not receive the request.

Product analytics and diagnostics

The extension sends product events through vidskim.com/api/analytics to our analytics service to understand feature use and reliability. Events may include actions such as opening the panel, loading a transcript, requesting or completing an AI feature, changing a language, reaching a limit, and signing in or out. The hosted-AI server also records whether a request passed the usage gate, completed, failed, or reached a limit. Events may include a random extension identifier or one-way pseudonymous server identifier, extension version, browser/OS type, interface language, model, routing reason, action type, token and cost totals, counts, cache status, duration buckets, and coarse performance/error metadata.

Analytics never intentionally includes video titles, transcript text, prompts, chat messages, AI responses, API keys, email addresses, or Google account details. The analytics service receives ordinary network metadata such as an IP address and may derive approximate location. These product events are collected when the extension is used.

Extension permissions

  • storage: saves preferences, cached state, optional API keys, the anonymous analytics identifier, and authentication sessions locally.
  • scripting: inserts or refreshes the panel in YouTube tabs already open when the extension is installed or updated.
  • unlimitedStorage: supports bounded local transcript and chat caching.
  • offscreen: gives the Manifest V3 service worker a local extension page used by the transitional billing transport; the paywall UI and all executable code are bundled locally.
  • youtube.com: reads captions and adds the Vidskim panel to the video page you are viewing.
  • vidskim.com: supports transcript fallback, authentication, user-triggered hosted-AI requests, and the analytics relay described above.
  • AI provider domains: sends direct requests only when bring-your-own-key mode is enabled.
  • platform.vidskim.com: loads plan configuration and starts checkout through the transitional billing adapter when you choose to view plans or a plan.

The vidskim.com website and free tools

  • Video URLs. When you use a web tool, the video ID is sent to the server to fetch public captions. Public-video transcripts may be cached briefly so repeat requests are faster.
  • Web summaries. When you request a summary, transcript text is sent to an AI provider to generate it. Vidskim does not intentionally store the submitted transcript or generated summary.
  • Abuse prevention. The website may use short-lived IP-based request counters. Web servers and infrastructure providers also receive ordinary request metadata such as IP address and user agent.
  • Website analytics. If enabled, the site sends page views, referrers, tool outcomes, and a random local-storage identifier to our analytics service. It does not send pasted video URLs, transcript text, uploaded subtitle contents, or filenames. The site respects browser Do Not Track.

The Vidskim connector for Claude, ChatGPT, and other MCP clients

The connector is a remote MCP server at vidskim.com/api/mcp. AI assistants such as Claude, ChatGPT, Claude Code, Cursor, and VS Code call it to read YouTube videos for you. All of its tools are read-only: they fetch public YouTube data and never post, comment, or act on a YouTube account.

What the connector receives

For each tool call, the connector receives the tool's arguments (a video link or ID, a search query, a channel or playlist link, and options such as language, time range, or page), the access token that identifies your account, and standard request metadata such as IP address and user agent. It does not receive your conversation with the assistant, your other messages, or files you share with it, and Vidskim cannot see them. The assistant you use processes the connector's results under its own provider's terms and privacy policy.

Sign-in

The connector uses Vidskim's own OAuth sign-in with your Google account. Google provides your Google account ID, email address, name, and profile image, as described above. Vidskim stores your account, the app you connected (each assistant registers itself automatically), your consent, and its access and refresh tokens. Access tokens expire after one hour and refresh tokens after 30 days. When you approve the connection, the assistant you connect also receives your name and email address, as shown on the consent screen.

Fetching videos

To answer a tool call, Vidskim sends the video ID to its transcript service, which fetches the video's public captions from YouTube, and it fetches public video details, search results, and channel lists from YouTube. When YouTube blocks a direct request, the transcript service may retry through a proxy provider or a third-party transcript provider, which then receives the video ID and requested language. The transcript service caches a video's public captions for up to 7 days so the same video is not fetched again, and the connector keeps a copy in memory for up to 6 hours. Video details are kept for up to 6 hours, search results (keyed by the search query) for up to 30 minutes, channel lists for up to 20 minutes, and channel handle lookups for up to 7 days. None of these caches are tied to your account, and Vidskim does not store transcripts with your account.

Monthly allowance

To enforce the free allowance of videos per month, Vidskim stores your account ID, the month, and the YouTube video ID and the time of each video the connector opened for you that month. No transcript text or questions are stored with these records. They are kept until you ask us to delete your account.

Emails about your allowance

When you use up the connector's free monthly allowance, Vidskim sends one email that month to the email address of your Google account: when the allowance resets and how to reserve Pro. Emails are sent through an email delivery service, which receives your email address and the message, which greets you by first name. Every email has an unsubscribe link, and Vidskim stores that you unsubscribed and the month each allowance email was sent. These records are kept until you ask us to delete your account.

Pro reservations

If you reserve Vidskim Pro on vidskim.com/mcp/pro, Vidskim stores the email address you enter, the optional note about what you would use it for, which page sent you there, and the time. We use the email only to tell you when Pro opens and to give you the founding price. Reservations are not linked to your connector account, are kept until the founding offer ends or you ask us to delete them, and are not shared with anyone. Analytics for this page record page views, whether a reservation succeeded or why it failed, which page sent you there, and whether a note was added, never the email or the note.

Analytics and logs

Each tool call sends an event to our analytics service with a one-way pseudonymous identifier derived from your account ID, the tool name, the outcome (for example success, no captions, or limit reached), the app that called it, your plan, and, for transcripts, the transcript language, whether it was machine translated, and the video length in minutes, plus the type of access token used. These events do not include video IDs, titles, search queries, transcript text, email addresses, or Google account details. The same identifier is used for an event recording whether an allowance email was sent or failed.

Server logs record each request's status, duration, and calling app, each tool call's name and outcome, and, for sign-in requests, the path, status, the start of the browser user agent, and any error message. Operational alerts about outages, such as YouTube blocking our server, name only the tool and the type of error.

Disconnecting

Removing Vidskim in your assistant's connector settings stops it from calling the connector. Tokens that were already issued expire on their own as described above. To delete your connector account and allowance records, contact the support address below.

Retention and deletion

Local extension data can be deleted by clearing the extension's storage or removing the extension. Removing the extension stops future extension analytics events. To request deletion of a signed-in account, including connector allowance records, or associated server-side usage counters, contact the support address below. Cached Quick Action responses expire automatically after up to 30 days. Our service providers (hosting, analytics, AI, email and transcript providers) may process data on servers outside your country, including in the United States. Service providers may retain security, fraud-prevention, or operational records under their own policies and legal obligations.

Contact

Questions or deletion requests: [email protected]. Vidskim is not affiliated with YouTube or Google.