How JumpWatch handles your data.

1. What this policy covers

This policy covers the JumpWatch Chrome extension, jumpwatch.cc web app and free tools, the JumpWatch API, and the JumpWatch MCP service. It explains data handled by JumpWatch and where a feature sends data directly to another service you choose.

2. Chrome extension data

Caption reading in the tab

The extension reads available caption tracks, the video identifier, title, channel, URL, duration, and playback position on YouTube. New transcript caches are held in tab memory and discarded when the tab closes. Reading and searching captions does not require JumpWatch cloud processing.

Chrome Sync and extension storage

Preferences, custom prompts, bookmarks, and limited account profile and connection status may be stored using Chrome extension storage. Authentication uses a secure session cookie; JumpWatch does not store your password in extension storage. Extension version 1.3.10 stops recording new watch history. Older versions can save watched-video metadata and viewing times when enabled; transcripts are not part of those history records. Previously saved history remains available to export or clear. Chrome may sync this data between browsers signed in to your Google account. JumpWatch does not operate Chrome Sync.

Summaries, questions, and saved videos

In extension version 1.3.10, selecting Brief, sending an Ask question, or saving to a collection sends the video identifier, title, URL, transcript, and relevant prompt and account identifier to JumpWatch. These actions do not require a separate cloud-processing switch. Reading captions alone does not automatically upload them to your library. The service may store saved videos, transcripts, summaries, chat questions and answers, notes, collections, model choices, and metered usage in your JumpWatch account.

External assistant handoffs

If you choose a separate-tab assistant workflow, the extension asks before sending the video title, URL, transcript, and your prompt to the named service. Supported destinations include ChatGPT from OpenAI, Claude from Anthropic, Gemini from Google, and Mistral. The destination provider controls its conversation history and retention; clearing JumpWatch does not delete data from that provider.

Optional extension analytics

Extension version 1.3.10 disables product analytics, including for previous opt-ins. Earlier releases can send product-usage events when analytics is enabled. Those events include a persistent account or random identifier, feature events, and coarse count, duration, and latency buckets to PostHog in the United States. Extension analytics excludes transcripts, prompts, questions, answers, and video URLs. It is pseudonymous, not anonymous.

3. Website, account, API, and MCP data

Signing in through Google or Apple provides JumpWatch with an account identifier and may provide your name, email address, and profile image. We use this information to operate your account. We do not receive or store your Google or Apple password.

The web app, API, and MCP service process the URLs, YouTube identifiers, transcripts, prompts, notes, collections, saved-library searches, API keys, generated content, usage, and diagnostic information required for the action you request. The free transcript tool sends the submitted YouTube URL or identifier to JumpWatch and may cache public caption text used by public transcript features.

Website analytics may send page URLs, referral information, a persistent browser or account identifier, and product events to PostHog. When you sign in, analytics may be associated with an opaque JumpWatch account identifier and coarse free or Premium plan state. We do not send your name or email address to PostHog as analytics profile properties. We also receive ordinary server and security logs such as IP address, browser information, timestamps, request paths, and errors.

4. Why we use data

• Deliver transcripts, search, summaries, chat, saved libraries, notes, collections, and MCP tools.
• Authenticate accounts, enforce allowances, process purchases, and prevent abuse.
• Maintain reliability, diagnose failures, secure the service, and provide support.
• Understand feature adoption and improve JumpWatch where analytics is active.
• Meet legal obligations and protect users, JumpWatch, and the public.

5. Service providers and transfers

JumpWatch uses providers for infrastructure, authentication, payments, analytics, and AI processing. Depending on the feature and available model configuration, AI processing may involve OpenAI, Anthropic, Groq, Moonshot AI, or Perplexity. Authentication may involve Google or Apple; payments may involve Lemon Squeezy or Stripe; analytics uses PostHog. These providers process data under their own terms and the arrangements applicable to JumpWatch. Data may be processed outside your country, including in the United States.

We may disclose information when required by law, to investigate abuse or security issues, or as part of a merger, financing, acquisition, or sale of assets with appropriate notice and safeguards. We do not sell personal information or extension data.

6. Retention and deletion

Tab-memory transcripts last until the tab closes. Chrome extension data remains until you clear it, disable a control that removes its related data, or Chrome removes it. Account and saved-content records remain while needed to provide the service or until deletion is requested, subject to limited security, billing, legal, backup, and fraud-prevention needs. Operational logs, backups, and processor records expire according to their configured schedules; a deletion request may not immediately rewrite immutable backups.

Self-service account deletion is not yet available. Email care@jumpwatch.cc from your account address to request access, correction, export, or deletion. We may need to verify your identity and clarify active subscriptions or records we must retain.

7. Your extension controls

• In extension version 1.3.10, use Brief, Ask, or Save when you want the corresponding API feature. New watch-history and product-analytics collection are disabled. Older versions retain their separate settings.
• Decline an external-assistant confirmation to prevent that handoff.
• Export documented preferences, prompts, watch history, and bookmarks without exporting account credentials.
• Clear extension storage and queued analytics from the extension. This does not delete server records or external-provider conversations.
• Use your browser controls to remove the extension, site data, or cookies.

8. Chrome Web Store Limited Use

Data obtained through the Chrome extension is used only to provide or improve the user-facing JumpWatch features described here. We do not use or transfer it for targeted advertising, creditworthiness, lending, or sale to data brokers. We do not allow people to read extension data except with the user's affirmative agreement for a specific purpose, for security or abuse investigation, when required by law, or after aggregation and de-identification for internal operations.

9. Security and children

We use access controls, encryption in transit, scoped account access, and operational safeguards appropriate to the service. No system is perfectly secure. JumpWatch is not directed to children under 13, and we do not knowingly collect their personal information. Contact us if you believe a child has provided data to JumpWatch.

10. Changes and contact

We may update this policy as the product or its providers change. The date above identifies the current version. Questions and privacy requests can be sent to care@jumpwatch.cc.