Privacy Policy

Last updated 2 October 2026. ClipLab is operated by Nyptid ("we", "us"). Contact: omatic657@gmail.com.

The short version. We collect your email, the videos you give us, and the YouTube data you connect. We use it to make your clips and to improve what we pick for you. We do not sell it, we do not use your videos to train anyone's AI models, and you can delete all of it by asking.

1. What we collect

Data	Why we have it
Your email address	To create your account and sign you in. Sign in uses either a one time email link or Google sign in.
Videos you upload, and videos we download from links you paste	To produce clips. This is the core function of the product.
Transcripts we generate from your audio	To find the strongest moments and to write captions, titles and descriptions.
Your YouTube channel data, if you connect it	Video list, titles, view and engagement counts, and retention figures. Used to rank which of your videos to clip and to improve future picks.
Google OAuth tokens	Stored so we can upload and read on your behalf without asking you to sign in every time.
Billing records	Your plan, its status, your subscription's renewal date, and a payment reference from Stripe. We never see or store your card details. Stripe handles the payment directly. Subscriptions started on Square before the switch keep billing there until they lapse or you cancel.
Basic usage logs	Job history, errors, and timestamps, so we can support you and fix bugs.
Free Short checks	If you make the free Short: your email address, the network address it was requested from, and an id for your browser, so each person gets one free Short. Nothing else is done with them.

What we do not collect

No third party analytics scripts and no advertising trackers following you around the site. The one exception is ad measurement, described below. Cookies: one that keeps you signed in, one that tells your browser apart from others while you are signed out, and, if you arrive from a referral link or a Google ad, one that remembers that link or ad click. We do not ask for your platform passwords, ever.

Google Ads measurement

We advertise on Google. To know whether an ad is worth paying for, ClipLab may tell Google Ads two things: that a new account signed up, and that an account bought its first plan, with the plan's price. This happens once each, on the page you see right after, using Google's tag on that page only. Google receives an order number (your ClipLab account id for a signup, the subscription id for a purchase), never your email, your videos or your channel data. If you came from a Google ad, the ad's click id is kept in a first party cookie so the two can be matched. Ad blockers stop all of this, and ClipLab works the same either way.

2. Where your data goes

We use a small number of processors, and only these:

Who	What they receive
Anthropic (Claude API)	Transcript text and channel statistics, so Claude can score moments and write titles, descriptions and captions. Anthropic does not train its models on data submitted through its API.
Google / YouTube	Only what is needed to publish, and only when you tell us to publish.
Stripe	Payment handling and recurring subscription billing for new checkouts. We receive only your subscription's status and renewal date, never your card details.
Square	Recurring billing for subscriptions started on Square before we moved checkout to Stripe. We receive only status and renewal date, never your card details.
fal.ai	The audio track of your video, for transcription. We send audio only, never the video itself, and only to produce the transcript your clips and captions are built from.
Google Ads	A signup or first purchase event with an order number and, for a purchase, the plan's price, as described under Google Ads measurement.
Contabo	The server that hosts ClipLab, located in Germany.

Your video file never leaves our server. We extract the audio track and send that to fal.ai for transcription, then the resulting text is sent to Claude to score moments and write titles. The video itself is only ever processed on our own server.

We do not sell your data. Apart from the Google Ads measurement above, we do not share anything with advertisers. We do not use your videos, transcripts or channel data to train any AI model, ours or anyone else's.

3. YouTube API Services

ClipLab uses YouTube API Services. By connecting your channel you also agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

We request three permissions, and nothing more:

youtube.upload so we can publish or schedule the shorts you approve.
youtube.readonly so we can list your videos and rank which ones to clip.
yt-analytics.readonly so we can read performance and improve future clips.

We cannot delete your videos, change your other uploads, or read your private messages. You can revoke our access at any time at myaccount.google.com/permissions, and you can disconnect inside ClipLab, which deletes the stored tokens immediately.

4. Other platforms

If you use the optional X posting feature, the browser that posts runs on your own computer, under your own login. ClipLab never receives your X password and never stores your X session. We only send your machine the clip and the text to post.

5. How long we keep things

Source videos: cleared after export. If a job is not exported, its source is removed when the 30-day project retention period expires.
Project files: clip metadata, previews, and rendered exports are deleted 30 days after the project's latest update. Download anything you want to keep.
Account-level learning: channel learning and other account settings are kept while your account is open, because this is what makes your results improve over time.
Account and billing records: kept while your account is open, then as long as tax and accounting rules require.
Backups: retained for 14 days, then overwritten.

6. Your rights

You can ask us to show you your data, correct it, export it, or delete it. Email omatic657@gmail.com and we will action it within 30 days. Deleting your account deletes your videos, transcripts, tokens and channel learning. If you are in the UK, EU or California, you have these rights under law, and you can also object to processing or complain to your local data protection authority.

7. Security

Traffic is encrypted in transit with HTTPS. Access to the server is restricted to key based administrator login. That said, no service is perfectly secure, and we will tell you promptly if a breach affects your data.

8. Children

ClipLab is not for anyone under 16. We do not knowingly collect data from children.

9. Changes

If we change this policy in a way that matters, we will email account holders. The date at the top always reflects the current version.