Skip to content

Privacy notice

Privacy for a website
that holds no identity records.

This notice covers www.idcheckglobe.com — the marketing website you are reading, and nothing else. These are static pages that describe a product. They hold no identity records, issue no credential, store no key and run no authentication, and they cannot grant, change or revoke anybody’s access to anything.

The ID Check Globe identity service is a separate system, reached at https://api.idcheckglobe.com and https://app.idcheckglobe.com. What that service does with personal data is governed by a written agreement with Cloud Granite Limited and the data-protection terms that form part of it. This notice is not that document.

Scope

The website, not the service.

The distinction is first rather than buried in a definitions clause, because everything below depends on it.

This website is statically rendered and served as files. There is no sign-in, no tenant, no directory, no verification session and no signing key behind it. It keeps serving when every product host is unavailable, which is the practical test of whether a page is part of a system or merely about one.

The identity service is where identity data lives: records and attributes, registered factors and keys, verification evidence and the outcomes derived from it, authentication and session events. None of that is in this website, none of it is reachable from this website, and none of it is described by this notice. In a normal deployment the customer whose tenant holds those records decides what is collected and why, and Cloud Granite Limited processes them under that customer’s instructions — a split the trust centre sets out in full.

So: read this notice to find out what reading this site involves. Read the agreement and its data-protection terms to find out what the service does. The two are answered in different documents because they are genuinely different questions, and the last section says where the second one is answered.

Controller

A product name cannot be a controller.

Data protection law gives obligations to legal persons. Naming the right one is not pedantry; it is the difference between a notice that binds somebody and a notice that binds nobody.

The operator of this website, and the controller for the personal data described below, is Cloud Granite Limited.

ID Check Globe is the name of a product. It is not a legal person, it cannot be a party to anything, it cannot hold an obligation and it is not the entity you would correspond with, contract with or complain about. Where this notice says “we”, it means Cloud Granite Limited.

Cloud Granite Limited is part of Haka Tech Ventures Limited. The group is named for completeness and because the footer names it. It is not the controller for this website and it is not the counterparty on any agreement for the service.

How to reach us

Questions about this notice, and requests to exercise the rights set out below:

hello@idcheckglobe.com

Reports about the security of this website or of the service, which reach a different queue:

security@idcheckglobe.com

Review item

Registered office and company number: to be completed.

A privacy notice normally carries the controller’s registered address and company registration number so a reader can identify exactly which legal person is speaking. Both are matters of public record, and both will be filled in at legal review from the register rather than from memory.

Collection

The honest inventory is short enough to print in full.

Most privacy notices describe a measurement stack. This one mostly describes absences, so the absences are listed individually — each line is a specific technology a reader might be checking for.

Not present on this site

  • No analytics. There is no analytics tag, no measurement script and no page-level telemetry call anywhere on this site.
  • No tracking cookies. Nothing is written to your browser to recognise you on a later visit.
  • No advertising pixels, conversion tags or remarketing audiences.
  • No embedded social posts, share buttons, video embeds or chat widgets, each of which would load a third party's script and its identifiers along with it.
  • No session recording, heatmapping or scroll-depth tracking.
  • No fingerprinting, and no device or browser identifier computed in place of a cookie.
  • No account, no login, no profile, and no form on these pages that posts data to a database.
  • No sale of personal data, no sharing of it for anyone else's purposes, and no use of it to train a model.

You do not have to take this on trust. Open your browser’s developer tools on any page of this site and look at the network requests and the cookie store. The cookie notice covers local storage and the other cookie substitutes in the same detail.

What is unavoidable: the request itself.

Delivering a page requires a request to reach a server. Each request to this site is handled by a content-delivery and security layer, which processes the ordinary metadata of an HTTP request — the originating IP address, the user-agent string, the page requested, the referring page where your browser sends one, and the time — in order to serve the page and to protect the site from abuse such as denial-of-service traffic and scraping that degrades it for other readers.

The lawful basis for that handling is our legitimate interest in delivering and defending our own website. It is the minimum processing that serving a page can involve, and there is no version of a public website that avoids it.

Those records are operational. They are not joined to anything else, not used to build a profile of you, not used to measure readership and not exported for marketing. One practical consequence is worth stating plainly rather than leaving as an inference: we do not know how many people read any page on this site, and we would rather say so than install something to find out.

The retention period applied to those delivery records, and the identity of the provider that holds them, are review items — see the note at the top of this page.

Enquiries

An email you sent us is not a consent you gave us.

The only personal data this site causes us to hold in any quantity arrives because somebody chose to write to us. The basis for handling it should therefore describe what actually happened.

There is no contact form on this site that posts data to us. The contact route is an email address, which means an enquiry arrives the way any other email arrives, and the data in it is the data you chose to put in it: your name, your email address, usually your employer and your role, and whatever you wrote. We do not enrich it from a third-party dataset, and we do not look you up to fill in what you left out.

We handle it for one purpose: to answer you, and to carry on the conversation that follows. Two lawful bases cover that, and which one applies depends on what you asked for.

Legitimate interests — responding to an enquiry addressed to us is the reason the address is published. The interest is ours and yours at once, the data involved is what you sent, and the handling stops when you ask it to.

Steps towards an agreement at your own request — where you have asked about using the service, discussing scope, architecture and terms with you is a pre-contractual step you initiated rather than one we decided to take.

We do not rely on consent for ordinary correspondence, because an email you sent us is not a consent you gave us, and recording it as one would misdescribe what happened — and would also imply you could be sent things you never asked for.

What does not happen

  • Your address is not added to a marketing list. This site runs no newsletter and no automated email sequence today.
  • Your enquiry is not passed to a lead-enrichment service, a data broker or an advertising platform.
  • Your enquiry is not used as training data for a model.
  • Nothing you write is published, quoted or used as a testimonial. This site carries no customer names at all.

If any of that ever changes, it becomes a separate thing you are asked to opt into, in its own words, and not a box already ticked.

If your enquiry is a security report

Write to security@idcheckglobe.com and say in the first message if you need a secure channel rather than ordinary email; one will be arranged before you send anything sensitive. The scope of that route, and what we commit to in return, are set out in the trust centre.

Processors

Two kinds of third party, both for a named purpose.

The question a reader needs answered is who else can see this. For a static website with an email address on it, the answer is short.

The hosting and delivery layer

Serves these static pages and shields them from abusive traffic. It processes the request metadata described above, and nothing else, because there is nothing else here for it to process.

The email and business tooling

Carries correspondence to and from the addresses on this site, and holds it where our team reads and answers it. An enquiry about enterprise federation is read by people who can answer it, and by no wider audience than that.

Each is engaged as a processor for a named purpose, bound by written terms with confidentiality and security obligations, and given access to nothing beyond what that purpose requires. No advertising network, data broker, lead-enrichment service or audience platform receives anything from this website — which follows from the inventory above, since none of them is present on it to receive anything.

The subprocessors engaged in delivering the identity service are a different and much longer list. It is maintained for the customer agreement and provided to customers and prospective customers who ask, rather than published as a page that goes stale quietly. The trust centre explains why, and asking for the list is a reasonable thing to do early in an evaluation rather than at the end of one.

Retention

Kept while it has a purpose, then not.

Enquiry correspondence is kept while the conversation is live and for a period afterwards, so that a later reply has its own history attached and so that we can show what was actually said if a question about it arises. Correspondence that leads nowhere is deleted. Correspondence that becomes a customer relationship moves into the records of that relationship and is governed by the agreement rather than by this page.

Delivery records held by the content-delivery layer are kept for the operational period that layer needs for security and diagnostics, and are then discarded. They are not archived for analysis, because there is no analysis.

You can ask us to delete your correspondence at any time, without waiting for anything and without giving a reason.

Your rights

Mostly quick, because it is mostly an email thread.

Where data protection law gives you rights over personal data we hold, exercise them by writing to the address in the controller section. In the ordinary case the data in question is a conversation you already have a copy of.

Access
A copy of the personal data we hold about you, which for almost every reader of this site is the correspondence they sent us and the replies we sent back.
Rectification
Correction of anything inaccurate or incomplete, including a name, employer or role we have recorded wrongly in a thread.
Erasure
Deletion of the correspondence we hold about you, subject only to anything we are required to keep or need to defend a legal claim.
Restriction and objection
The right to tell us to stop handling your data where we rely on legitimate interests — including to stop replying to you — and to have that honoured rather than argued with.
Portability
Your correspondence in a structured, commonly used form, where that right applies to it.
Withdrawal of consent
Where we ever rely on consent for something, the right to withdraw it as easily as it was given, with no effect on anything done before.
Complaint to a supervisory authority
The right to complain to a data-protection supervisory authority about how we have handled your data. That right does not depend on raising it with us first, though we would rather hear from you.

How we verify a request

We will not ask you for a passport or any other identity document in order to answer a data request about an email thread. Proving who you are, on a site that holds no identity records, would mean collecting more sensitive evidence than the request itself involves — which is the opposite of the minimisation this page describes.

Writing from the address the correspondence is with is normally enough. Where we genuinely cannot tell who is asking, we will say so and ask for something proportionate instead rather than refuse or over-collect.

If the data is in a customer tenant

If you are an end user of a company that uses ID Check Globe to authenticate you, your identity record sits in that company’s tenant and that company decides what is held and why. Your request goes to them, and our APIs and our support stand behind them in answering it.

Write to us anyway if you cannot work out who to ask. We would rather help you find the right controller than send you away on a technicality.

Transfers

An edge location is not a legal basis.

Static pages are delivered from whichever edge location is nearest the reader, so a request from one country is routinely served by infrastructure in another. Correspondence is read by people, in the places those people work.

Where personal data crosses a border, the transfer has to rest on a documented lawful basis with contractual safeguards. That is a question about the specific providers involved and about where Cloud Granite Limited is established, and both answers belong in this section once they have been confirmed.

They are not in it yet. The mechanism relied on for the delivery and email providers, and the destinations involved, are review items — named in the panel at the top of this page rather than filled in with the mechanism most sites name. We would rather carry a visible gap than a confident sentence nobody has checked.

For the service rather than the website, regional placement is a different and more tractable conversation: where regional deployment is supported, keeping identity records in a particular region is a configuration choice rather than a negotiation, and the transfer detail for the regions you care about is confirmed as part of the agreement.

Children

This website is addressed to developers, architects, security teams and the people who buy software for them. It is not directed at children, it has no accounts and no profiles, and it asks nobody their age because it asks nobody anything. If you believe a child has sent us correspondence, write to us and we will delete it.

Once the service is contracted

Where the product privacy terms live.

Privacy for the identity service is governed by documents a customer signs, not by a page a customer reads. This is where each one sits, so that nobody has to infer it from marketing copy.

The agreement and its data-protection terms. Concluded between the customer and Cloud Granite Limited, and the document that actually binds. It sets out the roles the parties take, the instructions under which identity data is processed, the security obligations, the retention and deletion mechanics and the audit rights. In a normal deployment the customer is the controller for end-user identity data and Cloud Granite Limited is the processor acting on its instructions.

The current subprocessor list. Provided with the agreement, and to prospective customers who ask, naming each processor, what it processes, the purpose and the location. Material changes are notified in advance under the agreement, while they are still a proposal.

Where we hold data for our own purposes. Some data inside the service is ours rather than a customer’s — the account of an administrator who signed up directly, for instance. Cloud Granite Limited is the controller for that, and the privacy terms accompanying the service say so rather than leaving it ambiguous.

Changes

The version at this address is the version in force.

When this notice changes, the changed version replaces this one at the same address, and the change is visible in the page itself rather than announced as a revision number nobody can check against anything. Where a change materially alters what we do with personal data we already hold, we will say so here in words rather than leave it to be noticed.

The first change this notice needs is the legal and operational review described at the top of the page: the controller details, the retention periods, the supervisory authority and the transfer mechanism. Until then it is an accurate description of a website that collects almost nothing, and an incomplete legal document. Both halves of that sentence are true, and saying only the first would be 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.