Privacy

Who we are

This site is operated by Clearfetch. Privacy questions, requests for a copy of your data, and deletion requests go to privacy@clearfetch.ai.

Early-access requests

When you submit the early-access form we store:

• your email address;
• company and role, if you filled them in (both optional);
• the use case you selected, and the free text you can add when you select “Other”;
• the capabilities you ticked in the optional multi-select, if any;
• the utm_source, utm_medium, utm_campaign, utm_term, and utm_content values from the link you arrived on, plus which version of the page you signed up from;
• if you arrive from an ad, the ad platform’s click identifier from the URL ( gclid, gbraid, or wbraid), stored with your request and used to report to the platform that showed the ad that a signup happened;
• a random confirmation token, the time you submitted, and the time you confirmed.

We use that to run the early-access list and to record which problem people came here for. We do not sell it, rent it, or share it with third parties for their own purposes. The confirmation email is sent through Resend, our email provider, which processes your address to deliver that message.

When you confirm, we generate your reserved API key, show it once, and store a SHA-256 hash of it along with its first few characters, so a key you present later can be recognised without us holding the key itself.

Site analytics

Analytics are first-party. Each event we record holds the event name, a session identifier, the page path, the version of the page, the UTM values, a small properties object (for the form, the use case you picked), and the time it arrived. One event is recorded by the server rather than the browser: confirming your email writes a waitlist_verified event carrying the page version and UTM values from your request, with the literal word server in place of a session identifier.

Cookies

We set no cookies, and we use no third-party trackers, advertising pixels, or fingerprinting. The only browser storage we use is sessionStorage: a random session identifier (key cf_anon) and the UTM values from the URL you arrived on (key cf_utm), which keeps attribution intact while you click between pages. Both are scoped to the tab and are gone when you close it. Nothing is written to cookies or localStorage.

Server logs

Our API logs every request it receives. Each log line holds:

• the time, the endpoint, the HTTP method, and the response status;
• a salted SHA-256 hash of your IP address. The raw IP is never written to disk, and the hash cannot be reversed to an address without the salt;
• your browser's user-agent string, the origin, and the referring page;
• whether an API key was presented. If the key presented is a reserved Clearfetch key we issued, the log line also records which early-access record it belongs to;
• for JSON request bodies, the top-level field names only, with any URL value reduced to its domain. Field contents are not logged.

Third-party requests

Fonts, styles, scripts, and images are served from clearfetch.ai. Loading a page here makes no request to any other company, so no third party learns that you visited.

Retention and deletion

We keep this data while the early-access list is open, and delete it when it stops being useful for that purpose. You can ask at any time for a copy of what we hold about you, or ask us to delete it, by writing to privacy@clearfetch.ai from the address you signed up with. A deletion covers your early-access record, any analytics events we can match to it, and the link from any server-log line that carried your reserved key. The log lines themselves stay, holding the hashed IP and the request details listed above, with nothing left in them that ties back to you.

Changes

When this policy changes we update the date above and describe the change here. We hold no security certifications today, and we will not imply otherwise.