Privacy Policy

• Account data. Username, hashed password (bcrypt — we never see the plaintext), and an optional email address you choose to provide.
• Google sign-in. If you sign in with Google, Google shares your Google account ID, name, email address and profile picture. We keep only the account ID (to recognize you next time) and the email address. We don’t store Google tokens or access anything else in your Google account.
• OAuth tokens. If you connect Kick, Discord, TikTok, YouTube, Instagram or a Facebook Page 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, post a clip you scheduled, etc.). You can disconnect at any time.
• Posting accounts. For each account you connect in the Scheduler we store what lets you see which account you are posting to:
  • TikTok: user ID, display name, username and profile picture URL.
  • YouTube: channel ID, channel name, handle and channel picture URL.
  • Instagram (professional accounts only): Instagram user ID, the app-scoped ID Meta gives us, username and profile picture URL.
  • Facebook: for each Page you choose to share, the Page ID, Page name and Page picture URL, plus the app-scoped Facebook user ID of the person who connected it. We never post to personal profiles.
• Scheduled posts. For each post you create we store the clip you chose, your caption, the settings you selected (for example who can see it, a YouTube title and “made for kids” choice, or whether an Instagram Reel also shows in your profile grid), the scheduled time, and the result the platform reports (status, post ID and a link to the post). A copy of the clip is kept on our server until it has been published or you delete the post.
• 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.
• Usage analytics. Which pages you open and which features you use inside ClipSnipe, recorded through Amplitude.
• Cookies and local storage. We set cookies to keep you signed in and, for about ten minutes while you connect an account, to protect the connection from forgery. Amplitude (see below) stores an anonymous identifier in your browser. We use no advertising cookies.
• 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, or location data. The only usage tracking is the product analytics described under “Third parties” below.
• 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.
• Disconnect a posting account: use Disconnect on the Scheduler page. We delete the stored tokens and the account’s name, username, picture and platform IDs, cancel anything still scheduled for it, and remove the platform’s post IDs and links from your post history. For TikTok and YouTube we also ask the platform to revoke our access. Your own captions and post times stay in your history until your account is deleted.
• Removing access on the platform: you can also remove ClipSnipe from the platform itself, and we then remove the account the same way:
  • TikTok: in the app, Settings → Security → Manage app permissions.
  • YouTube: your Google Account third-party access page. We notice within 20 days and remove the account 7 days later unless you reconnect.
  • Instagram: Settings → Website permissions → Apps and websites. Meta tells us right away and we remove the account.
  • Facebook: Settings & privacy → Settings → Business integrations. Meta tells us right away and we remove every Page you connected.
• YouTube data is kept fresh. At least every 20 days we re-read the name and picture of each connected channel and drop links to videos you deleted on YouTube, so nothing we keep from YouTube is more than 30 days old.
• Delete your account: email privacy@clipsnipe.com from the address on file. We action deletion within 7 days — your account row, OAuth tokens, connected posting accounts, scheduled posts and their clip copies, 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.
• TikTok. Only if you connect a TikTok account. We read that account’s basic profile and current posting options, and when you post we send the clip, your caption and the settings you chose to TikTok through its Content Posting API. What TikTok does with that content is governed by TikTok’s own terms and privacy policy.
• YouTube (Google). Only if you connect a YouTube channel. ClipSnipe uses the YouTube API Services: we read your channel’s name and picture and the processing status of the videos we upload, and when you post we send the clip, title, description and the settings you chose to YouTube. Google’s handling of that data is governed by the Google Privacy Policy. ClipSnipe’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Meta (Instagram and Facebook). Only if you connect an Instagram professional account or a Facebook Page. We read the account’s or Page’s basic profile and, when you post, send your caption and settings. Instagram fetches the clip from a private link that works only while that post is being published and for at most one hour; Facebook receives the clip directly. Meta’s handling of that content is governed by the Meta Privacy Policy.
• 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.
• Hetzner. Hosts the production server and database.
• Amplitude. Product analytics. We send which pages and features are used (for example a page view, a clip rating, or a setting change), linked to your account, so we can see what is working. We do not send passwords, tokens, or the content of clips, transcripts or chat.

We do not share data with advertisers or data brokers.