Privacy Policy

• Account data — your email address, and (if you use Google sign-in) the basic profile information Google shares to authenticate you.
• Payment data — metadata about your transactions (amount, currency, status, provider reference). Payments are processed by NOWPayments and Creem; we do not receive or store your full card number.
• Usage data — your filter presets, your alert rules and where they deliver (an email address, a Discord webhook, a Telegram chat), and any payout reliability reports you submit.
• Push notifications — if you turn them on for a device: the address your browser's push service gives us for it (Google, Apple, Mozilla or Microsoft), its encryption keys, the device's time zone (for quiet hours) and which notifications you want. Turning them off on the device deletes that address.
• Connected social accounts — the handles you link, their platform, and whether verification succeeded. If you switch profit auto-tracking on, we also read those accounts' recent public posts and view counts on a schedule.
• Earnings data — the profit entries the sync writes and the ones you enter yourself, plus any notes and goals you add to them.
• Affiliate data — if you join the affiliate program, your referral code and the conversions credited to it.
• Developer credentials — API keys you create (stored hashed, shown once) and any webhook endpoints you register.
• ClipRadar AI messages — what you type into the assistant, plus the recent messages in that conversation, sent to our AI provider to produce a reply. Conversations are not stored on our servers and end when you close the tab.
• Clip tools — if you use them: the campaign you pick, the YouTube link or video file you give us, the cut lists produced from it, the clips you order and the styling you choose for them, any caption styles and recipes you save, and any logos or banners you upload to put on your clips (kept until you delete them or your account).
• Connected YouTube channels — if you connect one to post clips to it: the channel's ID, name and picture, and the access tokens Google issues for it (stored encrypted), plus the title, description and posting time of each clip you schedule, the ID of the video it becomes, and that video’s view, like and comment counts. See section 3a.
• Connected TikTok and Instagram accounts — if you connect one to post clips to it: the account's ID, username or display name and picture, the access tokens TikTok or Meta issues for it (stored encrypted), the caption, settings and posting time of each clip you post or schedule, the ID of the post it becomes, and that post's view, like, comment and share counts. See sections 3b and 3c.
• Technical data — standard server logs (e.g. IP address, browser type, timestamps) and the strictly necessary cookies described in section 4.
• Analytics data — with your consent where consent is required: which features you use, on what kind of device, and where you drop out of a flow. Collected as categories and counts, never free text. See sections 4 and 5.

• To provide the Service: authenticate you, show your dashboard, deliver alerts, and remember your preferences.
• To analyse the videos you give the clip tools, and to render the clips you order. Clips are rendered on a machine we operate ourselves, which fetches the video from YouTube to cut it.
• To process subscriptions and confirm payments via our payment providers.
• To build and improve community reliability scores from submitted reports.
• To show your tracked earnings to other signed-in members — on the leaderboard, and on your profile page if you have chosen a username. Both sit behind the sign-in wall, both show period totals only (never individual entries, notes, views or campaign names), and both can be switched off from Dashboard → Profile.
• To secure the Service, prevent abuse, and comply with legal obligations.

We do not sell your personal information, and we do not use it for third-party advertising.

We share data only with vendors that help us operate, under agreements that limit their use of it:

• Supabase — authentication and database hosting.
• Vercel — application hosting and delivery.
• NOWPayments — cryptocurrency payment processing. Creem — card payment processing, as Merchant of Record.
• Resend — delivery of confirmation, alert and account emails.
• Apify — reads the public profile and recent posts of a social account you have connected, for account analysis and profit auto-tracking. It receives the handle, never your account with us.
• DeepSeek — powers ClipRadar AI. Your messages are sent to DeepSeek's API and processed on its servers in China. Whether that content may be used to improve their models is governed by DeepSeek's own platform terms and the data setting on our account there, not by a per-request restriction we can apply.
• Google (Gemini API) — watches the video you give the clip tools, together with the campaign's requirements, to choose the moments in a cut list. A YouTube link is fetched by Google directly; an uploaded file goes from your browser straight to Google, which deletes it after 48 hours. For a clip with a cold open, Google also writes the teaser line and picks out who is speaking. We use Google's free tier, under which Google may use what it receives to improve its products and human reviewers may read it, so do not upload a video you are not willing to share on those terms. Google receives the video and the campaign, never your account details.
• OpenRouter — when Google's free tier cannot take a request, the same request for a YouTube link (never an uploaded file) goes through OpenRouter to Google's models on our paid account. It receives the link and the campaign's requirements, never your account details.
• Microsoft (text-to-speech) — reads aloud the teaser line of a clip with a cold open. It receives that one line of text and nothing else. When it is unavailable, Google reads the line instead.
• Microsoft (Clarity) — heatmaps and session replay, used only where you have consented. See sections 4 and 5.
• PostHog — product analytics: which features are used and where people drop out of a flow. Hosted in the EU, used only where you have consented, and it never receives your email, your account id, or anything you type. See sections 4 and 5.

We do not use advertising cookies, and we never sell your data or share it with ad networks. What we do use falls into two groups.

Strictly necessary — always on. A session cookie that keeps you signed in, and a short-lived cookie recording the country your connection came from so we can show the right currency and any regional pricing. These are required for the Service to work and are not used to track you anywhere else.

Analytics and referral credit — only with your consent. Where consent is required (the EEA, the UK and Switzerland) nothing in this group runs until you accept, and you can change your mind at any time from Dashboard → Profile → Product analytics. It covers:

• Our own product analytics — which features get used and where people get stuck. It creates no cookies at all: two random identifiers are stored in your browser (one lasting until you close the tab, one that persists) purely so a sequence of actions can be recognised as one visit. They are not derived from anything about you, are never sent to anyone else, and cannot be linked back to you.
• Microsoft Clarity — heatmaps and session replay, which record how pages are used so we can see where the interface fails. Clarity sets its own cookies (_clck, _clsk). See section 5 for what it is prevented from recording.
• Referral attribution — if you arrived through a ClipRadar member's referral link, a cookie (cr_ref, and cr_ref_src if the link was tagged) records which member sent you, so that they are credited if you later subscribe. It lasts 60 days, holds only that member's referral code and any campaign tag on the link, and is never used to build a profile of you or to show you anything different. Where consent is required this cookie is not set unless you accept.
• PostHog — which features are used, and how one action leads to the next. It sets its own cookies (ph_*) and stores a random identifier for your browser, which is what lets it tell a returning visit from a new one. It is not given a name, an email or an account id, so that identifier is not linked to you.

The same restrictions apply to what leaves us: Google Analytics receives the same categories and counts described above, and never the two random identifiers our own analytics uses — those are stripped before anything is sent, so no persistent identifier of ours reaches anyone else.

One thing in that group does not need the cookie. If you arrived through a referral link and create an account in the same visit, the referral code travels in the web address rather than on your device, and we record against your new account which member introduced you — so they are credited whether or not you accepted anything. That is a record about your account, not a file stored on your computer, and it is covered by section 2 rather than by this one. It holds the referring member’s code and nothing about you.

Declining costs you nothing: every feature works identically either way.

Microsoft Clarity reconstructs pages from their structure, so it is worth being precise about the limits we place on it. The project is configured to mask text by default, and on top of that we mark specific parts of the app as never-record, regardless of that setting:

• Sign-in and sign-up forms in their entirety — your email address, password, and the one-time codes and links we email you.
• API keys, at the single moment a newly created key is shown to you.

Clarity does not record what you type into form fields, and we do not send it your name, email, or any account identifier. Recordings are held by Microsoft under their own retention schedule; their privacy statement covers what they do with the data as a processor for us.

Our own analytics is separately restricted at the point of collection. It transmits categories, counts and states — never free text. A search records the length of what you typed, never the query; a campaign records whether its requirements are complete, never their wording. Your earnings figures, private notes and ClipRadar AI conversations are never included.

We keep your data for as long as your account is active and as needed to provide the Service. When you close your account we delete or anonymize your personal data within a reasonable period, except where we must retain records to meet legal, tax, or fraud-prevention obligations.

A clip you order is kept in private storage for 48 hours so you can download it, and then deleted. A clip you schedule to TikTok or Instagram is kept until it has been posted, and then deleted on the same terms. Cut lists, and the caption styles and recipes you save, are kept while your account is active.

Analytics events are deleted after 90 days. Session recordings are held by Microsoft under Clarity's own retention schedule. PostHog retains events under the retention period set on our project, and any session recordings under its own, shorter one.

Depending on where you live (for example, in the EU/EEA under the GDPR), you may have the right to access, correct, delete, export, or restrict processing of your personal data, and to object to certain processing. To exercise any of these, email support@clipradar.co and we will respond within the time required by applicable law.

Where we rely on your consent — analytics and session replay, and nothing else — you can withdraw it at any time, as easily as you gave it, from Dashboard → Profile → Product analytics. Withdrawing stops future collection and clears the anonymous identifiers from your browser. It does not affect anything collected before you withdrew, and it changes nothing about how the Service works for you.

We use industry-standard measures to protect your data, including encryption in transit and access controls. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

The Service is not intended for anyone under 18, and we do not knowingly collect data from children.

We may update this Policy; material changes will be reflected by updating the “Last updated” date. For any privacy question or request, contact support@clipradar.co.