Privacy at EOSL.ai

There are no user accounts, no logins, no passwords and no payment of any kind on this site. Nothing you paste or upload into the bulk checker, the refresh plan builder or Stack Monitor is sent to a server. Those tools run entirely in your browser, and Stack Monitor's saved inventory lives in your browser's local storage on your own device. EOSL.ai cannot read it, has no copy of it, and it is gone if you clear your browser data. That is the part worth being categorical about: a hardware inventory says a great deal about an organisation, and this site is not a place it can leak from.

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.

Terms typed into the site search box in the header are included in that analytics data, along with how many results they returned. 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 — a product this site does not cover never appears in search-engine reports either. Terms are recorded on their own, not tied to you or to a session anyone reviews, and anything containing an "@" is discarded before it is sent. This applies to the header search box only — see below.

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 have a key and its history deleted, write to the address below naming the key.

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, and you can have both deleted by writing to the address below naming the key. 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.