Privacy Policy

Account and authentication

• Identifiers: Email address; password if you register with email and password; and authentication identifiers if you sign in with Google.
• Session data: Tokens and session records needed to keep you signed in securely.

Content you submit or generate

• Video context: YouTube video IDs, URLs, titles, and publicly available transcript or caption text you ask us to analyze.
• Analysis outputs: Summaries, outlines, action items, suggested questions, and similar outputs we generate and store for your account.
• Chat: Messages you send in in-product chat, model responses, and related conversation context.

Subscription, billing, and usage

• Plan and status: Subscription tier, renewal dates, and entitlement flags needed to deliver features.
• Usage metrics: Aggregated or event-level records relating to how the Service is used (for example, counts or estimates tied to analyses performed, chat usage, feature access, and billing periods). We use this information to bill where applicable, operate and improve the Service, protect security and integrity, and enforce our Terms (including acceptable and fair use).
• Payments: Payment transactions are processed by third-party payment providers. We do not store your full payment card number.

Voice input (optional)

• If you use the optional microphone feature in chat, audio is processed by your browser's built-in speech recognition (Web Speech API), which may route audio to the browser vendor's servers (for example Google's speech service in Chrome). SkipBait receives only the transcribed text your browser returns, not raw audio.
• Voice input is entirely optional. Your browser will prompt you for microphone permission before it can be used, and you can decline without affecting any other feature.

Technical and security data

• Logs and diagnostics: Server logs, error reports, rate-limit or abuse-prevention signals, and related technical metadata as needed to keep the Service reliable and secure.
• Extension local storage: The Chrome extension caches data in your browser, including settings, session data, recent analyses, outlines, actionables, suggested questions, chat history, and subscription usage state. This data remains on your device until you clear browser extension data or uninstall the extension.

Extension permissions

The SkipBait Chrome extension uses the following browser permissions:

• Storage: To cache analyses, settings, and session data locally in your browser.
• Identity: To facilitate sign-in (for example Google OAuth through your browser, coordinated with our authentication provider).
• Downloads: To save PDF exports you request from the extension.
• Network access: Limited to youtube.com (to read page context when you are actively viewing a YouTube video), our backend service, and our authentication and storage providers. We do not request access to unrelated websites or your browsing history.

Integrity, fraud prevention, and related accounts

Depending on implementation and risk, we may process additional categories to operate anti-abuse and billing-integrity controls described in our Terms, including detection of multiple or related accounts (not every signal is collected or used at all times):

• Payments and subscription integrity: Information from payment processors such as customer or subscription identifiers, transaction outcomes, limited billing metadata, and processor-provided fraud or risk indicators, consistent with those providers' terms and our role as merchant.
• Account and sign-in context: Authentication provider identifiers, email addresses, and patterns that may suggest duplicate or coordinated registrations.
• Network data: For example IP addresses, timestamps, and derived technical metadata from Service requests.
• Device or environment signals: Where relevant, browser or extension instance characteristics (for example to maintain sessions or distinguish abusive automation from ordinary use). We do not use such signals for unrelated marketing.
• Behavioural signals: Usage rates, timing patterns, and product interaction telemetry (including items described under usage metrics) compared with typical workloads, as risk inputs alongside technical limits.

We combine such inputs only as needed for security, fraud prevention, and enforcement of our agreements; automated outcomes are designed to be proportionate, with manual review where appropriate. See our Terms of Service regarding acceptable use and account measures.

AI inference providers - video analysis

We send video transcripts or extracted caption text, titles, and related metadata to AI inference providers (currently DeepInfra, OpenRouter, Nebius, Fireworks, and IonRouter, depending on availability and routing) to generate summaries, outlines, action items, and suggested questions.

OpenAI - chat and translation

We send your chat messages and relevant conversation history to OpenAI to generate follow-up chat responses. When you use summary translation, we may also send summary or outline text to OpenAI for that feature.

Serper - web search

When you ask questions in chat that may benefit from current information, we send search queries derived from your chat messages to Serper to retrieve real-time web results.

Fly.io - application hosting

Our backend API is hosted on Fly.io. Requests from the extension and website pass through this infrastructure; server logs may include IP addresses, timestamps, and related technical metadata described under technical and security data.

Supabase - authentication and cloud storage

We use Supabase for user authentication and cloud data storage. Your account information, saved video analyses, chat history, and subscription and usage data may be stored with Supabase.

Google - sign-in (optional)

If you choose Google sign-in, authentication identifiers are passed to Google's OAuth service (accounts.google.com). SkipBait receives only the resulting authentication token through Supabase; we do not receive your Google password. Email and password sign-in is handled through Supabase without sending your password to Google.

Stripe - payment processing

Subscription billing is handled by Stripe. Payment information and billing details are processed directly by Stripe. SkipBait does not store or access your full payment card number.