Privacy Policy

• Account data. Username, hashed password (bcrypt — we never see the plaintext), and an optional email address you choose to provide.
• OAuth tokens. If you connect Kick or Discord we store the access & refresh tokens issued by those platforms, encrypted at rest, used solely to act on your behalf (read your channel, post to your Discord, etc.). You can disconnect at any time from Settings.
• Your monitoring config. The channels you ask us to watch, the keywords you track, your detection thresholds, your priority channels, and the streams you’ve subscribed to in the pool.
• Data we derive from public broadcasts. For each monitored channel we store the hype-score time series, detected hype events, short clip files, ~3-minute transcripts of clip audio, visual keyframes of clips, and ±90-second windows of the public chat around each event. This data is derived from publicly broadcast content and is associated with the user who asked us to monitor that channel.
• Operational logs. Standard request logs (IP, user-agent, path, status, timing) retained for up to 7 days for debugging and abuse mitigation, plus error logs for up to 30 days.
• Claude MCP connector usage. When you connect ClipSnipe as a custom connector in Claude.ai, Claude sends tool calls to our MCP endpoint over OAuth. We log which tools were called and at what time, scoped to your user account, for the same retention windows above. The content of Claude’s prompts is never sent to us — only the structured tool arguments.

• We do not collect payment information — ClipSnipe currently has no paid tier.
• We do not collect device fingerprints, browsing history outside of our site, location data, or tracking beyond what is required to operate the service.
• We do not sell, rent, or trade your data to anyone, ever.

• Account & derived data: kept while your account exists.
• Request logs: ≤7 days; error logs: ≤30 days.
• Delete your account: email privacy@clipsnipe.com from the address on file. We action deletion within 7 days — your account row, OAuth tokens, monitoring config, scores, events, transcripts, chat snapshots, and keyframes are removed. Aggregated and anonymized operational metrics may persist.

• Twitch / Kick. We call their public APIs and ingest their public chat & video. Your OAuth tokens are sent back to them when authenticating you.
• Discord. If you connect a Discord webhook or install our bot, we post clip notifications and routing decisions to the channels you configured.
• Anthropic (Claude). Only if you install ClipSnipe as a Claude connector. Claude.ai exchanges OAuth with ClipSnipe and sends tool calls to our MCP endpoint over HTTPS. Your prompts inside Claude are governed by Anthropic’s privacy terms; ClipSnipe only ever sees the structured tool arguments and returns the requested data.
• Cloudflare. Used for R2 object storage (keyframes) and as a CDN. Cloudflare may process request metadata according to its own policy.
• DigitalOcean. Hosts the production droplet and database.

We do not share data with advertisers or analytics brokers.