Skip to content

Cookie notice

This website sets no
analytics or tracking cookies.

This notice covers www.idcheckglobe.com — the marketing website you are reading. It is a set of static pages about a product, and it is not the product: it holds no identity records, issues no credential and runs no authentication, so there is no session here for a cookie to carry.

That distinction matters more on this site than on most. Authentication genuinely does use cookies and tokens — keeping somebody signed in is, mechanically, holding state in a browser. Those belong to the ID Check Globe identity service at https://app.idcheckglobe.com, not to these pages, and the last section says where they are described. Everything else on this page is about the website.

Scope

The website, not the authentication flows.

Said before the headline claim rather than after it, because a flat statement that nothing uses cookies would be read as a claim about the product — and would be false.

These pages are rendered ahead of time and served as files. There is no login here, no tenant, no saved preference and no personalisation, and the site keeps serving when every product host is unavailable. It is a brochure, architecturally as well as editorially.

The identity service is a separate system at https://api.idcheckglobe.com and https://app.idcheckglobe.com. Hosted authentication flows there do hold state in a browser, because that is what a session is. What they set, what it contains, how long it lasts and how it is secured are documented with the service and governed by the agreement with Cloud Granite Limited — not by this page, which has no visibility of them and no authority over them.

So read this notice for what reading this site does to your browser. Read the product documentation for what signing in does. Conflating the two on a site that sells authentication would be the easiest mistake to make here and the worst one to leave standing.

The claim

No cookies for analytics, advertising or tracking.

Not a reduced set. Not an anonymised set. Not a set that activates only after consent. None — and the absences are listed individually, because a reader checking for one specific technology deserves to find that one named.

No analytics or measurement

No analytics tag of any kind, first-party or third-party, and no measurement script. Nothing counts page views, sessions, bounce rates or conversions.

No advertising or remarketing

No advertising pixel, conversion tag, remarketing audience or ad-network identifier. Nobody is building an audience from the fact that you read this page.

No embeds or widgets

No social buttons, embedded posts, video embeds, comment systems or chat widgets. Each of those would load a third party's script and let it set its own identifiers under our domain.

No session recording

No session replay, heatmapping, scroll-depth tracking or mouse-movement capture. Nobody is watching a recording of you reading this.

No testing or personalisation framework

No A/B testing, no feature-flag client and no content personalisation. That is the other common reason a marketing site writes to a browser, and it is absent too.

No consent platform, and no banner

No consent-management platform, because there is nothing to obtain consent for. A banner asking permission for nothing would be theatre, and it would train you to click through the next one that mattered.

No fingerprinting

No device or browser fingerprint, and no identifier computed from your configuration in place of a cookie. That is the trick that lets a site call itself cookie-free while still recognising you, and it is not in use here.

Check it yourself

You do not have to take any of this on trust, which is the point of writing it as a list. Open your browser’s developer tools on any page of this site and look at the network panel and the storage panel. A cookie notice you can verify in a minute is worth more than one you have to believe.

Because nothing non-essential is set, there is no banner on this site and nothing for you to accept or decline. The absence of a banner here is not an oversight and not a dark pattern; it is what a site with nothing to ask about looks like.

Why

Half architecture, half decision.

The architectural half is easy. The pages are static, there is no account, no login, no saved preference and no state to carry between visits, so there is nothing a cookie would be for. A site like this does not need to be careful to avoid setting one; it has to go out of its way to set one.

The other half is a decision, and it is worth naming as one rather than presenting architecture as virtue. We could add analytics tomorrow. Almost every site in this category has it, and the arguments for it are real: knowing which pages are read, which paths lead to a conversation, which paragraph loses people.

We decided against it, and the trade is real in both directions. We do not know how many people read any page on this site, which page brought them here or where they stopped. We write the pages, publish them, and find out whether they worked from the conversations that follow.

What we get in exchange is that there is no store of who read what, so nothing can be queried, correlated, breached or quietly repurposed later. On an identity site, where the whole argument is that data you did not collect is data you cannot lose, that seemed the better side of the trade — and a site arguing for minimisation while measuring its own readers in detail would be arguing against itself.

One qualification

What the delivery layer may set.

The honest footnote to everything above, stated as a section rather than hidden as a footnote — a blanket claim with an unstated exception is how a cookie notice stops being true.

These pages are served through a content-delivery and security layer, and a layer of that kind may set a strictly necessary cookie for its own operation — typically to tell automated traffic apart from people, to apply a rate limit fairly, or to keep a request on a consistent route while it is being served.

A cookie of that kind is not set by us and not set for us. It is not used to identify or recognise you, it does not reach us as analytics, and it tells us nothing about who read what. It exists to deliver and defend the page you asked for, which is the same purpose as the request metadata described in the privacy notice.

Whether such a cookie is in fact set on this deployment, and under exactly what name and lifetime, is the operational item named in the panel at the top of this page. When it is confirmed it will be named here precisely, as the five commitments in the next section require for anything else.

Cookie substitutes

And none of the things used instead of cookies.

A notice that answers only about cookies, strictly defined, leaves most of the question unanswered. Cookie in the heading of this page means all of it.

This site writes nothing to local storage or session storage, creates no IndexedDB database, and leaves nothing in a service worker or cache for the purpose of recognising you. It uses no tracking pixels or web beacons, in its pages or in any email sent from the addresses on it, and it sets no persistent identifier by any other means.

Fonts are served from this site rather than fetched from a third-party font service, which is one of the quieter ways a visit becomes a request to somebody else’s server. The same applies to scripts: the pages carry no third-party JavaScript, so there is no other party in a position to set anything.

The practical summary: a visit to this site leaves nothing behind in your browser that lets this site, or anyone else, recognise you on a later visit.

If this ever changes

Five commitments, in order.

A site that measures nothing today can want to measure something tomorrow — a form that needs a token to resist abuse, a preference worth remembering, an honest attempt to find out whether a page works. The commitment is not that it will never happen. It is how it would happen.

01

This page changes first

Updated, dated, and saying what is to be set before anything is set — not afterwards, and not in a quiet revision indistinguishable from this one.

02

Each cookie is named individually

Its name, whether it is ours or a third party's, what it does, what it holds and how long it lasts. A category heading such as performance or functional is not a description of anything.

03

Consent is asked before it is set

Where the law requires consent for a non-essential cookie, it is asked for before the cookie is written — not on the second page view, and never by treating continued scrolling as agreement.

04

Declining is as easy as accepting

Same place, same prominence, same number of clicks, and a decision that can be changed later without hunting for where it was made.

05

Nothing non-essential arrives quietly

We will not add tracking and leave this page saying there is none. That specific failure — a cookie notice describing a site as it was two redesigns ago — is why notices like this one are widely assumed to be worthless.

Why state this at all

A notice saying only that there are no cookies today is worth very little, because the reader has no way to know whether it describes the site in front of them or the site as it was two redesigns ago. Writing down the process is the part that remains useful after the facts change.

Your controls

Block everything. Nothing here breaks.

There is no preference panel on this site, because there is nothing here to switch off. Your browser’s own controls work regardless of what any site says: every current browser can block cookies entirely, block third-party cookies specifically, clear what is already stored, and open a private window that discards everything when it closes.

Use all of them here freely. No page on this site depends on a cookie to render, so refusing them costs you nothing and loses you no content.

If you send a tracking-preference signal such as Do Not Track or Global Privacy Control, there is nothing on this site for it to turn off. That is a better outcome than honouring the signal, and worth saying rather than claiming compliance with a mechanism this site never engages.

In the product

Where the product's cookies are described.

Not here, and the reason is not evasion: this notice is published by the operator of a website and has no visibility of a customer's tenant configuration.

Cookies and tokens set by the hosted authentication flows and the application are documented with the service and governed by the agreement between the customer and Cloud Granite Limited. Their lifetimes, scope and refresh behaviour are configuration rather than fixed facts about a product, which is exactly why a marketing page is the wrong place to describe them: a sentence here would be out of date for somebody the moment a tenant changed a setting.

If you are an end user signing in to a company that uses ID Check Globe to authenticate you, the notice that covers that sign-in is that company’s, not ours. They decide what is collected and why; Cloud Granite Limited processes it under their instructions. The privacy notice sets out that split, and the trust centre describes the architecture underneath it.

When this notice changes, the changed version replaces this one at the same address. The first change it needs is the review described at the top of the page. Until then it is an accurate description of a website that stores nothing in your browser, and an incomplete legal document — both halves of which are true, and saying only the first would be exactly the kind of unverified claim the rest of this site exists to avoid.

Cloud Granite Limited, part of Haka Tech Ventures Limited, publishes this website. ID Check Globe is a product name and not a legal person.