Privacy at EOSL.ai

There are no user accounts, no logins, no passwords and no payment of any kind on this site. When you check part numbers in the bulk checker, each part number is recorded as an anonymous sighting, so coverage follows real demand: a matched part as the identifier from our own catalogue, and an unmatched one as typed, because an unmatched part is usually a product worth adding. A pasted export can also carry hostnames, serial numbers, IP addresses and asset tags: serial numbers, MAC addresses, IP addresses and hostnames are dropped before anything is stored, and an email address is kept as typed, so it is clear which organisations use the tools. The checker also offers a pre-filled email for untracked parts, if you want to add detail. What is deliberately NOT collected is what would make any of this dangerous: no IP address, no account, and no record of which parts were checked together. Each sighting stands alone, and an email address in a paste is stored on its own record, never linked to the part numbers around it, so an inventory cannot be reconstructed from this data even by EOSL.ai. The checker's share link keeps the part list in the URL fragment, which browsers do not transmit, so EOSL.ai never holds a copy of your list. Part-level sightings are used internally to steer coverage and are not published; the public usage report shows client types and surfaces only.

This site uses Google Analytics 4 to count visits and see which pages are useful. That sets cookies and collects the ordinary things a web analytics tool collects — pages viewed, approximate region, device and browser type, and the referring site. It is used in aggregate to decide what to build next. It is never used to identify you, and no analytics data is sold or shared with anyone. You can block it with any ad or tracker blocker, and the site works identically with it blocked.

Most pages also load Microsoft Clarity, which records how a page is used (scrolling, clicks, and what the page showed) so layout problems can be found and fixed. It runs in Clarity's no-consent mode, so Clarity sets no cookies on eosl.ai, and this site's settings ask it to give each page view its own ID. Its loader still contacts Microsoft's servers (clarity.ms and c.bing.com), and Microsoft's clarity.ms domain sets its own cookies (CLID, MUID and SM) in browsers that allow third-party cookies. Blocking third-party cookies or using a tracker blocker stops that. Text typed into any box is masked by Clarity before anything is sent, and the forms on this site are masked as well. Clarity is not loaded on the bulk checker, so a pasted inventory is never recorded. Microsoft processes this data under its own terms; like the analytics above, any tracker blocker stops it.

Terms typed into the site search box in the header are recorded once you finish a search: the term, how many results it returned, and whether you picked one. That is how coverage gaps get found: a part number that returns nothing here is a product worth adding, and there is no other way to learn it, because a product this site does not cover never appears in search-engine reports either. They go to the analytics above and to EOSL.ai's own store, where each term is kept as a separate record for the day (no IP address, no cookie, no session), so two searches cannot be linked to each other, and the only way a search is tied to you is if you type your own email address into it; that store is never published and its records expire after 120 days. An email address typed into the box is kept in that store as typed, and is never sent to the analytics above. Anything shaped like a serial number or MAC address is discarded, because those identify one physical device. This applies to the header search box only; see below.

The request form keeps what you send: the type of request, your message, the page you came from, and your email address if you give one. It does not keep your IP address or set a cookie. Each request is emailed to our inbox, and if you give an email address you get a confirmation email. Requests are never published or sold, and are deleted after 400 days.

This site is served by Cloudflare Pages. Like any web host, its infrastructure processes requests and may retain standard technical logs. That is Cloudflare's processing, under Cloudflare's terms, not something EOSL.ai configures or reads.

The public API, the MCP server and the open dataset need no key and no registration. What their requests record: which part numbers get asked for, and whether each was found — in aggregate, with no IP address, no User-Agent string and no identity attached. That log exists for one reason: a part number people ask for that this site does not track is the coverage backlog naming itself, and there is no other way to learn it. It appears publicly, still in aggregate, in the usage report.

You can request a free key that attributes your API and MCP usage to you — that attribution is its only function; nothing is gated with or without it. If you do, EOSL.ai stores the email you gave, the key, and the part numbers looked up with that key. Publicly, your activity appears only as an anonymous key-****** bucket; the email is never published and never shared. Don't want that record? Simply don't attach the key — an unkeyed request is aggregate-only, as above. To delete a key and its history yourself, send the key to DELETE /api/register (for example curl -X DELETE https://eosl.ai/api/register -H "X-EOSL-Key: your-key"); the key, its email and the part numbers attributed to it are deleted at once, with no one to ask.

The lawful basis for the aggregate analytics above is legitimate interest in understanding whether the site is useful. There are no accounts, so with one exception EOSL.ai holds no personal record it could look up, correct or delete — nothing is keyed to you. The exception is the optional API key register above: if you requested a key, the email you gave is stored with it; to delete both, send the key to DELETE /api/register (for example curl -X DELETE https://eosl.ai/api/register -H "X-EOSL-Key: your-key"); the key, its email and the part numbers attributed to it are deleted at once, with no one to ask. To stop analytics collection entirely, block it in your browser.

EOSL.ai is a personal project, operated by one individual rather than a company. You can write to [email protected], but please treat it as unmonitored: no reply is promised and none should be relied on.