Cookies

Two cookies, both from Google Analytics.

Read out of a browser after loading this page, rather than copied from a vendor's documentation. The product itself is a separate matter and sets nothing at all.

What is stored

CookieSet byWhat it is forLasts
_gaGoogle Analytics Tells one browser apart from another, so a person who visits twice is not counted as two people.2 years
_ga_<id>Google Analytics Keeps the state of the current visit. The suffix identifies this site's analytics stream.2 years

That is the complete list. Nothing else is written to your browser, and nothing is kept in local storage.

What is loaded, and what it does

Google Tag Manager is a container. On its own it sets nothing; it loads the two things below.

Google Analytics 4 sets the cookies in the table and sends a beacon on each page view: which page, roughly where you are, and what browser you used. We use it to see which pages people read and which ones they leave.

Ahrefs Analytics loads a script from analytics.ahrefs.com and sets no cookie at all. It reports traffic and referrers back to us in aggregate.

What that means if you would rather not

Any content blocker stops all three, as does a browser set to block third-party scripts. Nothing on this site depends on them: every page works identically, and the contact form posts to our own server either way.

Google Analytics also honours the browser-level opt-out Google publishes, and _ga can be deleted from your browser's site settings at any time.

Requesting a script from another company's server tells that company your IP address, the page you were on and your user agent, cookie or no cookie. That is true of any remotely-hosted script, and it is why the fonts on this site are served from our own domain rather than a font CDN.

Working out which company is visiting

Once a page has been open for five seconds, the site tells our own server which page you are reading. The server looks your network address up with two companies: ipapi.is, for the country and city and whether the address belongs to a datacentre, and RB2B, which for business addresses returns the company that owns the range. If it resolves to a company, we get a message saying which company read which pages. We use it to know whether the manufacturers we are trying to reach are finding the site.

Three things worth being exact about. No cookie is involved and nothing is written to your browser: the lookup happens on our server, so neither of those companies receives anything from you directly. Your address is never stored in a form we can read back, only as an irreversible hash, and the record kept against that hash is deleted after 180 days. And it identifies a company, not a person: it can tell that someone at a firm read the datasheet, and cannot tell which person, or anything else about them.

It does not run at all for datacentre or VPN addresses, for anything that identifies itself as a crawler, or for a browser that has been told to opt out.

Switching all of it off

Load any page on this site with ?no_track=1 at the end of the address. From that moment, on that browser, nothing on this page happens: Google Tag Manager is never loaded, so no analytics cookie is set and no page view is sent, and the company lookup does not run either. It takes effect on the page you type it on, not the next one. Undo it with ?no_track=0.

That does set a cookie, for one year, and it is the only one this site will ever set that is not in the table above. It exists to record that you would rather we did not, which is the one thing we cannot remember without storing something.

The product sets nothing

Worth separating, because it is the more important half. The Inplant AI appliance has no telemetry and makes no outbound connections. Nothing about how your plant uses it reaches us, or reaches Google. That is covered in the security policy.

Questions

Write to hello@inplant-ai.tech.