Privacy Policy

The service is currently an owner-operated beta. A public business identity and dedicated privacy mailbox have not yet been activated. Those details must be published before accounts or payments launch. Until then, do not submit personal, confidential, or access-controlled information.

• The YouTube URL or video ID you submit.
• Public video metadata, captions or transcripts, and the summary generated from them.
• A salted one-way hash of the requesting IP address, used to prevent repeated requests from inflating a video's demand count. The raw address is not stored in the application database.
• Operational information such as provider, model, token usage, generation cost, timestamps, and error logs.

Submitted content is used to fetch the transcript, generate the requested notes, return the result, cache completed work, prevent abuse, diagnose failures, and decide which useful summaries qualify for public index pages.

Requests may be processed by Cloudflare for bot protection, TranscriptAPI or Supadata for transcripts, DeepSeek for summary generation, and the infrastructure providers that host the application, database, and encrypted off-site backups. Only the information needed for each task is sent to that provider.

Transcripts and summaries are cached in the service database so a video does not need to be purchased and generated again. Encrypted off-site database backups are retained on a rolling 14-day schedule. Cached public-video content and hashed demand records do not currently have a fixed automatic deletion date; they are removed when no longer needed to operate the service or after manual operational review.

The service currently has no user accounts, advertising cookies, or first-party analytics cookies. Cloudflare Turnstile may process browser and network signals needed to distinguish people from automated abuse under Cloudflare's own privacy terms.

Do not submit private, confidential, or access-controlled material. A public channel for removal or privacy requests is not available yet, so the service cannot currently accept those requests. This is a known beta limitation. A working contact method will be published here before accounts or payments launch.

This policy will be updated when the service adds accounts, payments, analytics, advertising, or materially different data processing. The date at the top identifies the current version.