Last updated: September 2, 2026
1. What this policy covers
Cookies are small files that a website stores in your browser. This policy uses the word cookies for every comparable technology, including the browser storage that a site can read and write without a cookie file, because the same rules apply to all of them.
This policy covers the Clipido website at clipido.com. The Clipido application itself is covered by our Privacy Policy.
2. When we ask for your consent
Storage that is strictly necessary to deliver the page you asked for does not require your consent, and we use it without asking. Everything else does require consent, and we ask before it runs.
On your first visit we show a banner with two equally available answers. Nothing that requires consent is stored until you have chosen. A few things do run before then, and all of them leave your browser's storage untouched: the cookie-free visit counters described in section 4, and the Google and Microsoft Clarity tags, which run in their vendors' consent modes with every permission denied, so they set no cookies, read no identifiers and send only anonymous, cookieless signals until you allow a category (see sections 5 and 6). Refusing is a real answer that we store, so you are not asked again on every page. A refusal is kept for 24 hours, after which we ask you again; an acceptance stays in place until you withdraw it or clear your browser data.
We record which categories you allowed and when you decided, together with the version of this policy that was in force at that moment. If we add a new category later, we ask again rather than treating your earlier answer as covering it.
3. Strictly necessary storage
This category is always on and cannot be switched off. It holds your own settings and nothing else:
- NEXT_LOCALE, a cookie that remembers whether you are reading the English or the Dutch version of the site.
- clipido.currency, browser storage that remembers the currency you selected on the pricing page.
- clipido.consent, browser storage that records your cookie choice so that we can honour it and do not have to ask again.
None of these are shared with anyone, and none of them are used to profile you or to follow you across other websites.
4. Cookie-free measurement that needs no consent
Two visit counters run on every page without asking for consent, because they work without touching your browser at all: they set no cookies, write nothing to browser storage, and read no identifier from your device.
- Ahrefs Web Analytics, which counts page views, referrers and countries in aggregate. It stores nothing in your browser and cannot recognise you on a later visit. The provider is Ahrefs Pte. Ltd.
- Vercel Web Analytics, which counts the same kind of aggregate visit statistics. It tells visits apart with a temporary hash that is discarded within a day, so it too cannot recognise you across visits. The provider is Vercel Inc., which may process data in the United States under the EU-US Data Privacy Framework.
We use these numbers to know how many people visit the site and which pages they read, across all visitors rather than only those who accept the banner. Our legal basis is our legitimate interest in basic audience measurement: the output is aggregate, no profile is built, nothing follows you to other websites, and none of it is used for advertising. As with any processing based on legitimate interest, you have the right to object; our Privacy Policy explains how.
5. Analytics
If you allow the analytics category, Google Analytics 4 (via the Google tag) and Microsoft Clarity start measuring and set the following cookies:
- _ga, which distinguishes one visitor from another and expires after up to two years.
- _ga_B76YK45D0V, which holds the state of your current visit and expires after up to two years.
- _clck, which Microsoft Clarity uses to recognise your browser on a later visit and expires after one year.
- _clsk, which Microsoft Clarity uses to connect the pages you view within a single visit and expires after one day.
We use this to understand which pages are read, which links are followed and which sources bring people to the site. Clarity additionally records how a page is used, such as scrolling and clicking, so that we can see where pages are unclear. We do not use any of it for advertising, and we do not combine it with the data in your Clipido account.
The providers are Google Ireland Limited and Microsoft Ireland Operations Limited, which may transfer data to Google LLC and Microsoft Corporation in the United States under the EU-US Data Privacy Framework. If you refuse this category, none of these cookies are set. Both tags still load, each in its vendor's consent mode with storage denied. The Google tag keeps no cookie, no client id and no user id, and the pings it sends carry no identifier that could be tied to you; Google uses them only for aggregate, modelled statistics. Clarity likewise sets no cookies and works with a fresh random id on every page view, so it cannot connect two pages you visit, let alone recognise you on a later visit.
6. Marketing
If you allow the marketing category, six tools start. The Google Ads conversion tag (part of the same Google tag) sets the following cookies:
- _gcl_au, which Google Ads uses to recognise that you arrived through one of our advertisements and expires after 90 days.
- _gcl_aw, which holds the click identifier of the advertisement you came from and expires after 90 days.
We use this for one thing only: to see whether a visit that started with one of our Google Ads later turned into a demo request, so we know which advertisements are worth paying for. When you request a demo, a hashed version of the email address you enter is sent to Google Ads to match the request to the click; Google cannot read the address back from the hash. We build no advertising profiles, no remarketing audiences and no personalised advertising from it.
The provider is Google Ireland Limited, which may transfer data to Google LLC in the United States under the EU-US Data Privacy Framework. If you refuse this category, none of these cookies are set, the click identifier from the advertisement is stripped from anything the tag sends, we do not pass your email address to Google Ads, and our advertisements still work exactly the same; we simply cannot see that they brought you here.
The ChatGPT Ads measurement pixel (from OpenAI) sets the following cookie:
- __oppref, which holds the click identifier of the ChatGPT advertisement you came from and expires after 30 days.
We use this for the same thing as the Google Ads tag: to see whether a visit that started with one of our ChatGPT advertisements later turned into a demo request. When you request a demo we send that event to OpenAI so it can be matched to the click. We build no advertising profiles, no remarketing audiences and no personalised advertising from it. The provider is OpenAI, Inc., which stores this data in the United States. If you refuse this category, this pixel is not loaded at all.
A visitor-identification script from lemlist sets no cookies and writes nothing to your browser. It sends the page you are on, which browser you are using, how long you stay and how often you click, together with your IP address, which is part of the request itself.
lemlist uses this to try to identify the organisation behind the visit, and for visitors in the United States it may also identify an individual, so that we can follow up. The provider is lempire SAS, which stores this data in France.
Leadinfo identifies the organisation behind a visit from the IP address that arrives with the request. Company recognition itself uses no cookie. For session analytics it also sets the following cookies:
- _li_id, which Leadinfo uses to tell a new visitor from a returning one and expires after two years.
- _li_ses, which Leadinfo uses to group the pages of a single visit and lasts for the session.
The provider is Leadinfo B.V., which stores this data in the European Union.
Snitcher likewise tries to identify the organisation behind a visit. It sets the following cookie:
- snitcher_device_id, which Snitcher uses to recognise a returning browser and expires after one year. It also writes session information to browser storage.
The provider is Snitcher B.V., which stores this data in Germany.
Apollo likewise tries to identify the organisation behind a visit, and for visitors in the United States it may also identify an individual. It writes the following to browser storage:
- apolloAnonId, which Apollo uses to recognise a returning browser. It also queues the pages of a visit in browser storage.
The provider is Apollo.io (ZenProspect, Inc.), which stores this data in the United States. If you refuse this category, none of these visitor-identification scripts is loaded.
7. What this site does not use
To be explicit about what is absent:
- No retargeting or personalised-advertising cookies. The advertising conversion tags in section 6 measure whether an ad led to a demo request; they do not follow you to other websites. Visitor identification for outreach, also in section 6, runs only if you allow marketing.
- No social media tracking pixels. Our links to LinkedIn and Instagram are ordinary links that load nothing until you click them.
- No externally hosted fonts. Our fonts are served from our own domain, so your browser never contacts a font provider.
- No selling or sharing of website data with data brokers.
8. Changing or withdrawing your choice
Select cookie settings in the footer of any page to reopen the banner and change what you allow. Withdrawing consent takes effect immediately: we delete the cookies that were set and reload the page so that nothing keeps running.
Withdrawing is as easy as giving consent, and it costs you nothing. Refusing analytics does not limit any feature or block any page.
You can also delete cookies and browser storage directly in your browser settings. If you clear the record of your choice, we will ask again on your next visit.
9. Changes to this Cookie Policy
We update this policy whenever we add, remove or change what we store. If the change affects a category you were asked about, we ask for your choice again.
This Cookie Policy was last updated on September 2, 2026.
