Cookies Policy

Last updated: 12 June 2026

This policy explains how cookies and similar technologies are used in connection with the Overclaud website at overclaud.dev.

1. The short version

We use the Meta (Facebook) Pixel to measure visits and the effectiveness of our advertising. This is the only tracking technology on the site, and it sets a small number of cookies. Aside from the pixel, browsing overclaud.dev sets no cookies of our own. We do not sell your data, and we do not use fingerprinting.

2. What cookies are

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.

3. Cookies and trackers we use

The Meta Pixel (a piece of code provided by Meta Platforms, Inc.) loads on our pages and records a "PageView" when you visit. 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.

Browsing overclaud.dev otherwise — reading the page, viewing pricing, reading these policies — does not place any other cookie on your device from us.

4. Other third-party services

Two further third parties are involved when you use the site. Neither sets cookies simply from you viewing our pages:

Stripe (payment). When you click "Get Overclaud", you are taken to Stripe's secure checkout page (hosted on Stripe's own domain). To process your payment and prevent fraud, Stripe sets its own strictly necessary cookies on that page. These are essential to completing a purchase and are governed by Stripe's cookie policy. We do not control them and we receive none of their data.
Google Fonts. Our pages load the Inter typeface from Google Fonts. This causes your browser to request the font files from Google, which may log the request (including your IP address) but does not set a cookie. If you prefer to avoid this, you can block third-party font loading in your browser.

5. Cookies and the product

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.

6. How to control these cookies

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.

7. Changes to this policy

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.

8. Contact

Questions about cookies? Email [email protected].