Privacy Policy

1. Information we process

• Account information: your email address, display name, role in your workspace and how you sign in (password, email link, or your organization's single sign-on). Passwords and two-factor secrets are held by our authentication provider, not by us.
• Application details: when you apply, the email, display name, channel links, average viewer count and the kind of install you asked for.
• Stream audio and video: the engine listens to and watches your live stream to find moments worth clipping. It transcribes speech, and it detects where faces are in the frame so a vertical clip can be framed around them. It does not identify who anyone is and does not build face or voice prints.
• Clips and previews: the clips generated from your stream, a smaller preview copy for review, and each clip's title, description, hashtags, scores and your approve or reject decisions.
• Transcript excerpts: the words spoken around each clip, used to write titles and to explain why a clip was chosen.
• Your rules and ratings: the lore rules, ratings and review notes you and your team add.
• Connected platform accounts (YouTube, TikTok, Meta): the access and refresh tokens the platform issues when you connect, your account id and name on that platform, the ids of posts we publish for you and their view counts.
• Link clicks: when someone opens one of your clip or bio links, we count the click. See section 6.
• Devices: the phones and PCs you pair, their push notification tokens, and for the desktop agent a hardware report (GPU model, video memory, driver, CPU, memory, free disk space) and status readings such as GPU temperature.
• Billing: your plan, subscription status and the customer and subscription ids from our payment processor. We never receive or store card numbers.
• Security records: an audit log of security-relevant actions in your workspace (for example sign-ins with emergency access, SSO changes and audit exports).
• Technical logs: request logs (IP address, user agent, address requested, time, result) and, when error reporting is switched on, error reports with emails, tokens, transcript text and file paths removed.

2. How we use it

• To run the service: find clips in your stream, render them, show them for review, publish the ones that are approved to the accounts you connected, and show you how they perform.
• To keep the service safe: stop clipping at once when the kill switch is used or an emergency keyword is heard, enforce rate limits, investigate abuse and secure accounts.
• To bill you for your plan and to send you messages about your account, your application and security.
• To improve how clips are chosen for your workspace, using your own ratings, rules and decisions.

We do not sell personal information, we do not show advertising, and we do not let third parties serve content or advertising in Clip Harness.

3. How long we keep it

4. How we protect it

• Platform access and refresh tokens are encrypted with AES-256-GCM. The encryption keys are themselves protected by Google Cloud Key Management Service (or, for air-gapped installs, by the operating system's credential store). Tokens are never written to logs.
• Phones and PCs are paired with codes and tokens that we store only as SHA-256 hashes.
• All connections use TLS (HTTPS); database and cache connections are encrypted in transit.
• Payments are handled on pages hosted by our payment processor, so card numbers never reach us.

5. Who we share it with

We share information only with the service providers that run Clip Harness for us, and with the platforms you tell us to publish to:

• Google Cloud: hosting, storage, encryption keys and logs.
• Our authentication provider (Supabase): sign-in, email links and two-factor authentication.
• Our payment processor (Stripe): subscriptions and invoices.
• Apple and Google push notification services: a wake-up notice that a clip is waiting, with no title, account or other personal information in it.
• Our email provider [name, once chosen under HITL B5]: application and account emails.
• Error reporting (Sentry), only when it is switched on, with personal information removed first.
• A language model server that writes clip titles from transcript excerpts. We run it ourselves; on local installs it is the one you configure.
• YouTube, TikTok and Meta: the clips you approve, with their titles, descriptions and hashtags, posted to the accounts you connected.

We may also disclose information when the law requires it, or to protect people from harm.

6. Clip and bio links

Your clip and bio links go through our link redirector so you can see how many people open them. For each click we keep only an anonymous count. To avoid counting the same visitor twice in a day, we keep a one-way hash of the visitor's details, made with a secret that changes every 24 hours, so hashes cannot be linked from one day to the next. We store no personal information about viewers on YouTube, TikTok or Meta. The raw request log of each click (IP address, user agent, time) is kept for 7 days to investigate abuse and then deleted; it is never copied into our database.

7. YouTube

Clip Harness uses YouTube API Services. When you connect a YouTube channel we use YouTube API Services to upload the clips you approve and to read their view counts. By connecting YouTube you agree to be bound by the YouTube Terms of Service. Google's handling of your information is described in the Google Privacy Policy.

You can stop our access at any time by disconnecting YouTube in Settings → Connections, which deletes your YouTube tokens and the YouTube data we stored within 24 hours. You can also revoke our access on the Google security settings page; we then delete the YouTube data we stored. YouTube data other than tokens and view statistics is refreshed or deleted at least every 30 days.

8. TikTok and Meta (Facebook and Instagram)

When you connect TikTok, Facebook or Instagram we receive your account id and name and permission to post the clips you approve, and we read their view counts. We use this only to publish for you and to report results to you. Disconnecting in Settings → Connections deletes the tokens and the data we stored from that platform within 24 hours. For Meta you can also remove Clip Harness in your Facebook settings; Meta then tells us, and we delete your Meta data and give you a confirmation code to check the status of the deletion.

9. Cookies and storage on your device

The dashboard keeps your sign-in session and your light or dark theme choice in your browser's local storage. The phone app keeps its pairing and sign-in details on the phone, and the desktop agent keeps its device token in the operating system's credential store. We do not use advertising or tracking cookies, and we do not let third parties place them.

10. Your choices and deleting your data

• Disconnect a platform at any time in Settings → Connections.
• Remove a paired phone or PC in Settings → Devices.
• Workspace owners can export the audit log in Settings → Security.
• To ask for a copy of your information, to correct it, or to have it or your whole workspace deleted, email [privacy contact email]. We answer within [30] days. Deleting a workspace removes its data within 30 days, as in section 3.
• Depending on where you live, you may have further rights under the law (for example to object or to complain to a data protection authority). [Jurisdiction-specific rights, lawful bases and international transfer terms to be added on legal review.]

11. Children

Clip Harness is for streamers and their teams and is not directed to children. [Minimum age to be set on legal review.]

12. Changes to this policy

If we change how we use information, we will update this page and tell you before the change applies. We will ask for your consent before using information from your connected accounts in a new way.

13. Contact

Questions or complaints about privacy: [privacy contact email], or write to [postal address].