How Youtubebrief handles data.

Summary requests and reports

When you submit a YouTube URL, the service may store the submitted URL, canonical video URL, video id, processing status, generated Markdown, section notes, timestamp evidence, and KST request/completion timestamps so result pages can be operated and quality issues can be audited.

The operator brief dataset may include a date-scoped HMAC hash of the client IP when available. It is designed not to store raw IP addresses, raw Cookie headers, or user-agent strings.

Free quota data

The free web quota store is separate from the summary store. It uses an opaque anonymous quota cookie, locked timezone, local-day counters, and privacy-preserving IP HMAC auxiliary counts. It must not store raw IP addresses, raw Cookie headers, user-agent strings, YouTube URLs, provider internals, or summary content.

Analytics

Youtubebrief records privacy-safe product events such as landing visits, summary starts, result views, and copy actions. Analytics payloads are designed not to include raw YouTube URLs, titles, transcripts, cookies, IP addresses, user-agent strings, secrets, or provider internals.

Developer beta requests

If you request private developer beta access, Youtubebrief stores your normalized email address, use case, source or UTM labels, status, and timestamps for beta follow-up and operator audit. Beta request forms do not load advertising or third-party analytics scripts and should never include API keys or secrets.

Accounts and Google sign-in

Youtubebrief account records store normalized email addresses, hashed API keys, session records, credit ledger entries, and checkout metadata needed to operate paid CLI access. If Google sign-in is configured and you choose it, Youtubebrief uses Google's OAuth flow to receive your verified email address; it does not collect your Google password.

Cookies and advertising

The app uses a quota cookie for anonymous free usage and may use account/session cookies for signed-in features. Youtubebrief is preparing Google AdSense for advertising. Third-party vendors including Google may use cookies to serve ads and measure ad performance. Users can manage Google personalized ads through Google Ads Settings.

Contact and deletion requests

For privacy questions, report deletion requests, or policy concerns, contact the operator through the contact page or email [email protected]. Include only the public report URL if you are asking about a specific generated brief.