Privacy Policy

Clippin (“we”, “us”) operates clippin.tv and app.clippin.tv. Clippin is run by an individual sole operator based in the United States. For anything in this policy, write to Albo@clippin.tv.

This policy explains what personal information Clippin handles, why, who else sees it, how long it is kept, and what you can do about it. It applies to the marketing site, the Clippin application, our Discord bot, and the background systems that capture, edit and publish clips.

Clippin is unusual in that most of the people whose data it touches are not its users. We would rather say that plainly than bury it.

• Customers and their staff — the people who sign in to Clippin, connect social accounts and edit clips. You have an account with us.
• Streamers being monitored — the broadcasters whose public streams Clippin watches, clips and, where authorised, transcribes. Usually this is the customer themselves or a creator they work for.
• Viewers in public chat — people whose public Twitch or Kick chat messages are captured as the signal that something worth clipping happened, and whose messages can be rendered into a published video. You have no account with us and never interacted with us directly. Section 10 is written for you.

We do not collect payment card details. If you check out, our payment processor hosts that page and handles your card directly.

We use the information above only for the purposes described in this policy. There is no catch-all “other business purposes” clause, deliberately.

• Running the product: detecting moments, cutting clips, rendering and publishing them.
• Signing you in, scoping what you can see to your team, and supporting you.
• Publishing to the accounts you connected, at your instruction, under the permissions you granted.
• Keeping the service working: debugging, retrying failures, and preventing abuse.
• Billing, where you are on a paid plan.
• Meeting legal obligations and enforcing our Terms.

When you connect a social account, you authorise it yourself in that platform’s own consent screen, and we receive a token scoped to the permissions shown there.

• We only act on accounts you connected, and only within the granted permissions.
• Anything we publish goes to an account connected inside Clippin, on your instruction. We never publish your content to a Clippin-owned account, and we do not sell, share or repurpose it. Clippin is operated as a single managed workspace today, so accounts connected by your team are the ones your team’s content publishes to.
• We read basic profile information — account id, display name, handle, avatar — so the app can show you which account is connected.
• A manager or admin on your team can disconnect an account at any time from the Connections page, which deletes the stored credentials immediately. Anyone at all — with or without a Clippin account — can email us and we will do it for them. You can also revoke Clippin from the platform’s own settings, and we recommend doing both.

Clippin uses YouTube API Services. By connecting your YouTube channel to Clippin you agree to be bound by the YouTube Terms of Service. Google’s own handling of your information is described in the Google Privacy Policy.

What we access, collect and store through the YouTube API:

• your YouTube channel id, channel title and channel thumbnail;
• the OAuth access and refresh tokens Google issues for the scopes you granted, so we can keep uploading without asking you to sign in again;
• the ids and titles of recent videos in your channel’s uploads list, read so we can tell whether something we are about to upload is already there, and the ids of videos Clippin itself uploaded — so the app can show whether a publish succeeded and can remove a video it created if you ask it to.
• the title, description, tags, privacy setting and custom thumbnail you chose in Clippin, which we send to your channel as part of publishing — written, not read.

If you also connect Google Drive (an optional backup destination for finished clips), the same Google sign-in additionally gives us your Google account email address, and the narrow drive.file permission — which means Clippin can only ever see the files it created in your Drive, never the rest of it.

How we use and share it: video files are rendered from your own stream footage, stored in our private object storage, and uploaded to the YouTube channel you connected, at your instruction. YouTube API data is never shared with other customers, never sold, never used for advertising, and never used to train AI models. We do not send YouTube profile or channel data to our AI subprocessors. Clippin serves no advertising, allows no third party to serve content or advertisements through it, and sets no advertising or tracking cookies — the only browser storage it uses is the session cookie that keeps you signed in and local storage for interface preferences.

Revoking access. You can revoke Clippin’s access to your Google data at any time from the Google security settings page (also reachable at myaccount.google.com/permissions), or by disconnecting the channel on Clippin’s Connections page.

Retention and deletion. We store the minimum Google and YouTube API data listed above and no more. Stored channel details are refreshed or discarded at least every 30 days, so what we hold is never older than that. When you disconnect a channel we delete its stored credentials and its channel profile details; we keep a record of which videos we uploaded for you — the video id and the outcome — as the publishing history the app shows you, and that is deleted on request. We honour any deletion request within 30 days — see Data Deletion.

• TikTok — where connected, we receive your open id, display name, username and avatar, and hold a token permitting uploads you initiate. See the TikTok Privacy Policy.
• Instagram (connected through Meta’s login) — Clippin connects Instagram professional accounts only; there is no separate Facebook connection. Because Instagram publishing runs through the linked Facebook Page, we receive and store: your Instagram Business Account id, username and profile picture URL; the Facebook Page id and name that Page-based publishing requires; your Meta app-scoped user id (so a deletion request from Meta can be matched to your connection); and the Page access token and long-lived user token that permit the publishing you initiate. See Meta’s Privacy Policy. You can remove Clippin from your account at any time, and we honour Meta’s data deletion callback — see Data Deletion.
• X — where connected, we receive your user id, name, username and profile image, and hold a token permitting posts you initiate. See the X Privacy Policy.
• Twitch and Kick — we read public channel, stream and chat data from their official APIs and from the same public endpoints their own websites use, and we retrieve public VOD footage. Where you connect a Twitch account, we additionally hold a token for the actions you authorised.
• Discord — used to sign you in, and, where you have added our bot, to post clip approval and workflow cards into your own server. Preview cards carry a link that plays the clip inline in Discord; that link works without a Clippin login for as long as it is valid, so anyone it is forwarded to can watch that clip.

We do not sell personal information. We share it only with the service providers below, each of which processes it on our behalf and for no other purpose, and with the platforms you connected.

We may also disclose information where we are legally required to, or to protect our rights, safety, or the integrity of the service. If Clippin were ever acquired, we would tell you before your information became subject to a different policy.

Clippin sends material to two AI providers: audio to AssemblyAI for transcription, and text — transcripts, sampled chat lines, stream metadata and screenshots — to Anthropic to decide which moments are worth clipping and to draft titles, descriptions and summaries.

• We do not send them your connected accounts’ profile data or your OAuth tokens.
• We do not use your content to train any model of our own.
• Our AI providers process this content under their standard commercial API terms, which we rely on rather than a separately negotiated agreement. Those terms do not permit training on customer API content. We have not enabled any additional zero-retention arrangement, so content sent to a provider is retained by that provider under its own terms, which we do not control.

Automated systems decide which moments get surfaced and, where you enable it, which get published without a human review step. These systems make mistakes; you can turn automatic publishing off, and you can review or delete any output before it goes out.

If you have typed in a public Twitch or Kick chat that Clippin monitors, this section is about you, and you are the only group here who never agreed to anything with us.

What we capture: your chat display name, name colour, badges, emotes, message text and its timestamp — all of it already public in that channel’s chat at the time you sent it.

What happens to it: the volume and content of chat reaction is the signal Clippin uses to find a moment worth clipping. Chat is also rendered as an on-screen overlay in the finished video, which means your display name and message can appear in a published clip.

That clip may be published to the streamer’s own social accounts, and it may also appear on Clippin’s own public website at clippin.tv, where archived streams can be watched with the chat replay rendered on screen. Those pages need no login and can be indexed by search engines.

Our lawful basis for this, where UK/EU law applies, is legitimate interests: identifying notable moments in a broadcast and reproducing the audience reaction that made them notable. We do not use chat data to build a profile of you, we do not advertise to you, and we do not sell it.

We keep information for as long as your account is open and we have a purpose for it, and we delete it when you ask us to. We do not run automatic expiry on most categories — the working material is what the product exists to keep searchable — so deletion on request is the mechanism that matters, and we honour it within 30 days. Concretely, today:

• Full VOD archives are deleted from our storage 30 days after the copy on your own channel is confirmed available. Your team can change that window, or turn the automatic deletion off, on the Archives page.
• Raw live audio chunks are deleted as soon as the transcript derived from them is confirmed written.
• Connected-account credentials are held until you disconnect the account or ask us to delete them, and are deleted immediately when you do.
• Clips, transcripts, chat archives and account records are kept for as long as the account is active, because they are the working material and the searchable history the product exists to provide. They are deleted on request.
• Website measurement records are pseudonymous — a salted one-way hash, never a raw IP address — and are used only to produce daily visitor counts.

We also delete information when we no longer have a legitimate business purpose for it, when the product or feature through which we obtained it stops operating, when you close your account, when a platform or a person asks us to, and where a platform we obtained it from requires deletion under its own terms.

• Credentials for connected accounts are held server-side only. They are never sent to your browser and never written to logs.
• Tokens issued by TikTok, Instagram, X and Twitch are sealed with AES-256-GCM, using a per-secret random salt and initialisation vector, before they are written to the database.
• Media storage is a private bucket. Files are reached through short-lived signed URLs; public copies exist only for clips that have been deliberately made public.
• Signing in to the Clippin application requires a Discord account we have pre-authorised; what you can do inside the app is governed by your role.
• Some surfaces are deliberately public because they have to be: a share link carrying an unguessable token, and clips a team has chosen to publish. Those are reachable by anyone holding the link.
• Traffic to and from Clippin is encrypted in transit with TLS.

No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and any regulator we are required to notify, without undue delay.

Whoever you are, and whether or not you have an account with us, you can ask us to:

• tell you what personal information we hold about you;
• give you a copy of it;
• correct it if it is wrong;
• delete it;
• restrict or object to how we use it;
• withdraw consent, where we relied on consent.

Email Albo@clippin.tv, or follow the instructions on the Data Deletion page. We respond within 30 days. We will not charge you, and we will not treat you differently for asking.

We may need to confirm you are who you say you are before acting — for a chat-data request that usually means proving control of the chat account.

If you live in California, Colorado, Connecticut, Virginia, or another US state with a comprehensive privacy law, you have the rights listed in section 13, plus the right to appeal a refusal and the right to be free from discrimination for exercising them.

We do not sell personal information, and we do not share it for cross-context behavioural advertising. We have not done so in the preceding twelve months. There is therefore nothing to opt out of, but you may still exercise every other right above.

We do not knowingly collect or process sensitive personal information for the purpose of inferring characteristics about you.

Where UK or EU data protection law applies, we are the controller for the information described here, and our lawful bases are:

• Contract — running the service for customers who have signed up for it.
• Legitimate interests — detecting notable stream moments, including from public chat; securing the service; and understanding aggregate site traffic. We have weighed these against the interests of the people involved, and section 10 explains the most significant case.
• Consent — where you give it, for example by recording a voice reaction.
• Legal obligation — where we must keep or disclose something by law.

Our infrastructure and service providers are located in the United States and other countries, so your information is transferred internationally. Where required, those transfers rely on Standard Contractual Clauses or an equivalent safeguard.

You have the right to complain to your data protection authority — in the UK, the Information Commissioner’s Office. We would appreciate the chance to put it right first.

The Clippin application sets a session cookie so you stay signed in, and uses your browser’s local storage to remember interface preferences. These are strictly necessary for the app to work.

Every page — public or signed-in — records a single first-party measurement event per visitor per day, as described in section 3. We do not use advertising cookies, and there are no third-party trackers anywhere on the site.

Clippin is not for children. You must be at least 18, or the age of majority where you live, to hold an account. We do not knowingly collect personal information from children. If you believe a child’s information has reached us — including through captured chat — email Albo@clippin.tv and we will delete it.

We will update this policy as the product changes. The “Last updated” date at the top always reflects the current version, and for material changes we will give notice in the app or by email before they take effect.

Privacy questions, complaints, and requests about your data: Albo@clippin.tv.

To delete data, start at Data Deletion. For product help, see Support.