Privacy Policy

The short version: your original videos never leave your Mac. In cloud mode we send only small still frames for analysis. In local mode, nothing leaves your device. The free online tools normally send only still frames and the audio track, never your video file. We never track or analyze your footage. The website uses optional, consent-based analytics only.

This Privacy Policy explains what data Cliptag and Framepass LLC ("we", "us") collect and how we handle it. It applies to the Cliptag macOS app and the cliptag.ai website.

1. What we collect

We keep data collection minimal. We collect your email address when you purchase a plan, and usage counts tied to your license key so we can enforce monthly clip limits. We do not require an account to use the free tier. If you voluntarily submit your email to our pre-launch waitlist, we use it solely to notify you when Cliptag launches; that form is processed by Web3Forms and the address is deleted once it is no longer needed.

2. What is sent to the cloud

When you use cloud analysis, Cliptag extracts small JPEG frames from your clips and sends only those frames to the AI provider (Google Gemini) for analysis. Your original video files are never uploaded. Frames are used only to generate names and tags and are not used to train models by us. We keep no copy of them: the sampling described in section 4 applies to the online tools on this website only and never to the Mac app.

3. Local-only mode

If you enable local-only mode, all analysis happens on your Mac using an on-device model. In this mode no frames, clips, or metadata are sent to any server. This is the recommended setting for sensitive footage.

4. The online tools on this website

The free tools at cliptag.ai/tools run without an account and without an email address. In the normal case your video file is never uploaded: your browser reads a handful of still frames and the audio track itself, and only those are sent for analysis. For a three-minute clip that is roughly two megabytes instead of a gigabyte.

There is one exception, and the page tells you before it starts. Some camera formats cannot be decoded by any browser. For those we transfer the file to a separate extraction service of ours, which reads the still frames and the audio with ffmpeg and returns them to your browser. That service holds no API keys, writes the file to temporary storage only for the duration of the request, and deletes it immediately afterwards, including when the request fails.

Two processors are involved in the analysis itself, the same ones the Mac app uses: Google (Gemini) receives the still frames and returns a title, scene and tags; Groq receives the audio track and returns the transcript. Both process the data in the United States under standard data-protection safeguards. They do not store your frames or audio after the request, and neither they nor we use them to train models. On our side the audio is never kept; for the still frames see the next paragraph. The renamed clip you download is created by your own browser from the file already on your computer, so it never passes through us at all.

Samples of still frames. To check that the abuse filter is doing its job and to understand what these tools are actually used for, we keep an occasional sample of the still frames. This applies to the online tools on this website only, never to the Mac app. A sample holds the frames plus the title and tags we generated from them. It contains no IP address, no account, and not the original filename of your clip. Audio is never sampled. Samples are visible only to us, are never published or passed on, and are deleted automatically within 72 hours.

We log no filenames and no content. To see whether the tools are actually useful, we count anonymous events (a clip was dropped, which processing path was taken, which export format was chosen) through the same consent-based PostHog setup described below. If you decline cookies, no such events are recorded and the tools work exactly the same.

5. Website analytics

We do not run any analytics inside the app, and we never analyze the content of your footage for any purpose beyond producing the tags you requested. On the cliptag.ai website we use two providers, both strictly opt-in via the cookie banner: Google Analytics (GA4) for aggregate traffic, and PostHog for product analytics (which pages and features are used), including anonymized session replays. Neither loads until you accept — if you decline, no analytics scripts run and no analytics cookies are set. For Google, IP addresses are anonymized and Consent Mode keeps analytics storage disabled until opt-in. For PostHog, all form inputs are masked in session replays and no replays are recorded on your account dashboard. Both Google and PostHog process this data on servers in the United States under standard data-protection safeguards (EU–US Data Privacy Framework / Standard Contractual Clauses). You can withdraw consent any time by clearing the cliptag.ai site data in your browser.

6. Payments

Payments are processed by Paddle, our Merchant of Record. Paddle collects the billing information needed to complete your purchase (such as name, billing address, and payment details) — we do not receive or store your full payment details. Paddle's handling of that data is governed by Paddle's own privacy policy.

7. Data retention

License and usage data is stored in our database (Supabase) for as long as your account is active. You can request deletion of your data at any time by emailing us, and we will delete it except where we are required to retain records for legal or tax purposes.

8. GDPR and your rights

For EU customers, Paddle acts as Merchant of Record and handles compliance obligations for payments, including VAT. The app itself processes no personal data about you beyond your email and license usage. You have the right to access, correct, or delete your personal data — contact us to exercise these rights.

9. Contact

Framepass LLC, Florida, USA
Privacy questions and data requests: hello@framepass.io