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 saved filters, searches, and any payout reliability reports you submit.
• 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.
• 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 process subscriptions and confirm payments via our payment providers.
• To build and improve community reliability scores from submitted reports.
• 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 and Creem — payment processing.
• Email delivery providers — to send confirmation and alert emails.
• OpenRouter — powers ClipRadar AI. Every request is restricted to model providers that do not store or train on the content submitted to them.
• Microsoft (Clarity) — heatmaps and session replay, used only where you have consented. 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 — 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.

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.

Analytics events are deleted after 90 days. Session recordings are held by Microsoft under Clarity's own retention schedule.

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.