What YouChop processes, and why.

Operator and scope

YouChop is operated by Adam Pangelinan, also known as Adam Pang, through Anchor Marianas LLC. The public website does not require an account. The application code does not build advertising profiles or sell personal information.

Information the web tools process

• Public video inputs. When you use Chapterize or Channel to Text, the browser sends the YouTube URL, video ID, playlist ID, channel handle, language choice, or related public query to YouChop's same-origin server endpoints.
• Transcript and chapter content. The server may process public video titles, authors, transcript text, timestamps, and generated chapter labels to return the requested output.
• Operational request data. Vercel, the hosting provider, may process IP addresses, user-agent strings, request times, response status, and security or diagnostic logs needed to deliver and protect the service.

YouChop does not currently load a visitor analytics script. Its application code does not create a first-party account or marketing cookie.

Browser storage

The Chapterize page stores the first successful activation time, the associated public video ID, and a local chop count in your browser's local storage.

The Channel to Text page stores up to 30 recent extraction-history entries in local storage. Those entries can include public video metadata and the full transcript output. You can delete individual entries or clear the history from that page. Clearing site data in your browser also removes this local data.

Service providers

Depending on configuration and the requested feature, YouChop may send public video identifiers or transcript content to the following processors:

• YouTube and YouTube oEmbed for public pages, captions, thumbnails, and video metadata.
• Apify, Supadata, TranscriptAPI, or youtube-transcript.io to retrieve public transcript data. The server tries only providers that are configured.
• Anthropic for chapter generation when the Anthropic-backed chapter engine is enabled. In that path, transcript text and basic public video metadata may be sent to Anthropic. Otherwise, YouChop uses its local heuristic chaptering path.
• Vercel for site hosting, server execution, delivery, and operational security.
• Google Fonts to deliver the typefaces used by the public pages. A font request can expose standard network request information to Google.
• Stripe when you choose the creator-service payment link. The payment happens on Stripe's site, and YouChop does not receive your full card number.

Each provider handles data under its own terms and retention practices. YouChop cannot delete copies controlled solely by those providers.

Browser extension

The extension first attempts to read public YouTube transcript data locally in the browser. A server fallback sends the public video ID and requested language to youchop.app. Chapter generation sends extracted timestamp rows and basic public video metadata to YouChop's server and may use Anthropic as described above.

The extension requests Chrome permissions for clipboard writing, local extension storage, downloads, the active tab, and script injection on YouTube. Its host access is limited to youtube.com and youchop.app.

When extraction fails, the extension stores up to 50 diagnostic records in Chrome's local extension storage. A record can include the date, extension version, public video ID, title, page URL, error message, and diagnostic trace. The extension popup includes a control to clear those records.

Retention and your choices

The application has no user-profile database. Request content is processed to answer the request, while Vercel and configured providers may retain operational records under their own policies. Browser and extension records remain on your device until you clear them or browser storage is removed.

You can use the public information pages without submitting a video, decline the Stripe handoff, clear local history, uninstall the extension, or contact YouChop about a privacy question.

Contact

For a privacy request, visit the contact page and put "Privacy" in the email subject. Do not include passwords, API keys, private videos, or payment-card details.