Last updated: 25 October 2026
This policy explains how cookies and similar technologies are used in connection with the Overclaud website at overclaud.dev.
We use the Meta (Facebook) Pixel to measure visits and the effectiveness of our advertising, but only if you accept it in the banner shown on your first visit. It is the only technology on the site that sets cookies. We also use Cloudflare Web Analytics, which counts visits without cookies and without identifying you. Aside from the pixel, browsing overclaud.dev sets no cookies of our own. Unless you decline the pixel, our server also tells Meta about your visit and any purchase, without cookies (see section 3). We do not sell your data, and we do not use fingerprinting.
Cookies are small text files that a website can store in your browser. They are commonly used to remember preferences, keep you signed in, or measure how a site is used. Similar technologies include local storage, pixels (small invisible images used for measurement), and device fingerprinting.
If you accept it, the Meta Pixel (a piece of code provided by Meta Platforms, Inc.) loads on our pages and records a "PageView" when you visit. If you decline, or make no choice, it does not load at all. To do this it stores cookies in your browser — typically _fbp (set on the overclaud.dev domain) and, if you arrive from a Facebook or Instagram ad, _fbc. These cookies contain a randomly generated identifier; they let us understand how many people visit after seeing our ads and help Meta show our ads to relevant audiences. The data is shared with Meta and processed under Meta's Privacy Policy and Cookie Policy. These cookies are not strictly necessary and exist for analytics and advertising purposes.
Events from our server. Unless you decline the Meta Pixel, our server reports your visit to Meta through its Conversions API: each page view and checkout opened (the page address, and the plan and price on checkout), your IP address and browser details, and, if the page address carries a Meta ad's click id, that id. If you buy, it sends one "Purchase" event once your payment completes, with the order value and currency and your email address in hashed (scrambled, one-way) form. Nothing is stored on or read from your device for this. While the banner is unanswered, page events wait until you leave the page. If you accepted the pixel, these events also carry the _fbp/_fbc identifiers from its cookies and the ad click kept in your browser, and Meta counts each event once even when the pixel sent it too. If you decline the pixel, none of these events is sent.
Which ad or link brought you. If you arrive from a link that carries campaign tags (such as utm_source or Facebook's fbclid), we keep those tags in your browser's local storage for up to 28 days and attach them to your order, so we know which ad or link led to a sale. This is not a cookie. Meta receives only the ad click id (fbclid), with the server events above, and nothing at all if you decline the pixel. You can clear it by clearing this site's data in your browser.
Browsing overclaud.dev otherwise — reading the page, viewing pricing, reading these policies — does not place any other cookie on your device from us.
Two further third parties are involved when you use the site. Neither sets cookies simply from you viewing our pages:
Overclaud itself — the configuration you install into ~/.claude — runs locally on your machine and does not use web cookies. Licence validation is performed by a direct, encrypted request from the installer to our API using your licence key; no cookie is involved.
Your choice on this site: loading…
Turning it off stops the pixel loading from your next page view and stops our server reporting your visits to Meta straight away. To remove cookies it already set, clear them for overclaud.dev in your browser.
You can manage or block cookies, including the Meta Pixel's _fbp/_fbc cookies, through your browser settings — most browsers let you block or delete cookies per site. You can also limit ad tracking from within your Facebook ad preferences, and many browsers and extensions block third-party tracking pixels automatically. For the Stripe cookies set during checkout, or cookies set by any other site, the same browser controls apply. General guidance for common browsers is available at aboutcookies.org.
If we introduce further cookies or analytics in the future, we will update this policy and, where the law requires it, ask for your consent first. The date at the top shows when this page was last changed.
Questions about cookies? Email [email protected].
overclaud