Privacy policy

Last updated 29 September 2026

This policy covers ClipKit, the desktop application operated by OverclipHQ to produce and publish short-form video clips. It explains what data ClipKit accesses, why, where it is stored, and who it is shared with.

ClipKit is not a public service. It runs on hardware controlled by OverclipHQ and is used only by OverclipHQ to publish to channels OverclipHQ owns. There are no user accounts and no sign-up.

Google user data

ClipKit connects to one YouTube channel owned by OverclipHQ, through Google's OAuth 2.0 flow. It requests two scopes:

Scope	What it is used for
`youtube.upload`	Uploading a finished video file to the connected channel, with a title, description and privacy setting. This is the only scope Google offers that permits an upload.
`youtube.readonly`	Reading back view counts and audience retention for videos ClipKit itself uploaded, so the application can learn which clips performed and improve its selection.

What ClipKit does not do

It does not delete, edit, or unlist any existing video.
It does not change channel settings, branding, playlists, or comments.
It does not read, collect, or store data about any channel other than the connected one.
It does not access Gmail, Drive, Contacts, Calendar, or any other Google service.
It does not use Google user data for advertising, profiling, or credit assessment.
It does not sell, rent, or transfer Google user data to anyone.

Storage and security

The OAuth refresh token issued by Google is stored in Windows Credential Manager on a single computer, encrypted by the operating system and readable only by the Windows user account that authorised it. It is never written to a plaintext file, never committed to source control, and never sent to any server other than Google's.

Statistics retrieved through youtube.readonly — view counts and retention for ClipKit's own uploads — are stored in a local SQLite database on that same computer. They are not transmitted anywhere.

ClipKit has no backend server. There is no hosted database, no analytics service, and no telemetry. Nothing about the connected Google account leaves the local machine except the API calls made directly to Google.

Retention and deletion

The refresh token is kept until it is revoked or the application is uninstalled. Access can be withdrawn at any time from the Google Account permissions page at myaccount.google.com/permissions, which immediately and permanently ends ClipKit's access. Removing the stored credential from Windows Credential Manager has the same effect locally.

Locally stored video statistics can be deleted by deleting the application's data directory.

Limited use

ClipKit's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Other data

ClipKit also connects to Twitch, Kick, Meta and TikTok using credentials issued to OverclipHQ. Those credentials are stored the same way and are used only with their own platform's API. No data from any of those platforms is combined with Google user data.

The transcription ClipKit performs runs entirely on the local machine. Transcript text is sent to Anthropic's API to choose and title clips. That text comes from publicly broadcast livestreams; it contains no Google user data.

This website itself sets no cookies, runs no analytics, and collects nothing from visitors.

Content and attribution

Clips published by OverclipHQ credit the streamer whose broadcast they came from, and where a moment was first marked by a viewer's clip, the person who made it. Rights holders who want a clip removed can write to the address below and it will be taken down.

Changes

If this policy changes materially, the date at the top of this page will be updated. Because ClipKit has no users other than OverclipHQ, there is no notification list.

Contact

Questions about this policy, about data handling, or about a clip: contact@overcliphq.com