Skip to content

Contact

Tell us what you are building.

Three routes, each with its own address and its own section below: starting a build, an enterprise or architecture conversation, and responsible disclosure of a security issue. No form, no phone number and no promised response time — just the right address and a note on what makes a first message easy to answer.

General address

hello@idcheckglobe.com

Everything except a security report: starting a build, an architecture conversation, commercial structure, a procurement question, or a correction to something on this site. Put Start or Enterprise in the subject line and it reaches the right people without a forwarding step — the buttons in the two sections below prefill it for you.

Security disclosure

security@idcheckglobe.com

A suspected vulnerability in the identity service, the hosted flows, the published SDKs or this website. This address is separate so a report is never sitting behind a commercial thread, and the scope and commitments are set out in full in the trust centre.

The routes

Whichever link brought you here, the page is the same.

Some buttons on this site carry a topic in the address. This page does not read it: it is statically rendered, so every route is shown to everyone, and nothing is hidden behind a query string that may not match what you actually need.

?topic=start

Where it comes from. Every Start building button on the site, including the header, the footer and the closing panel on most pages.

Where it leads. Starting a build — what to put in a first message about an integration you are planning.

Go to that section
?topic=enterprise

Where it comes from. The Talk to an identity expert buttons, and the requests to see a subprocessor list or to walk through an architecture.

Where it leads. Enterprise and architecture conversations — federation, tenancy, migration, security review and commercial structure.

Go to that section
No topic at all

Where it comes from. The footer contact link, a search result, or a link somebody sent you.

Where it leads. Whichever of the three sections below matches what you need. Nothing is hidden behind a topic value; the whole page is here either way.

The security route carries no topic link, because a disclosure should not depend on having followed a marketing button to find the address. It is published in the trust centre and again at the top and bottom of this page.

Starting a build

Start with what you are building, not with us.

This is the route for a team planning an integration: a product that needs login, an API that cannot tell which system is calling, a credential nobody outside the company can check. Describe the problem and the identities involved, and the conversation can begin at the design rather than at the introduction.

The button prefills the subject line with Start building and nothing else. Everything you write is your own; this page sends nothing on your behalf and collects nothing as you read it.

What makes a first message easy to answer

  • What you are building, in a sentence or two — the product, not the identity feature
  • Which identities it needs to authenticate: customers, employees, partners, applications, machines, AI agents, or some mix of them
  • The flows you have in mind — hosted login, embedded components, direct APIs, enterprise SSO, machine credentials
  • Whether there is an existing identity system in the picture, and whether it is staying
  • Anything already decided for you: a stack, a region, a protocol, a security review you have to pass

None of it is required, and there is no form here that will refuse to proceed without a field. It is simply the detail that turns a first reply into something useful rather than a request for more detail.

A conversation about the integration

The first exchange is about which services you actually need and which flow fits what you are building, rather than a qualification script. Tell us the awkward constraint early; it is usually the thing that decides the design.

The reading that saves a call

The developer portal sets out the API design, the quickstart shape and the standards involved. The platform page walks the architecture from the outside in, including the three places it deliberately stops.

Commercial structure, when it matters

Pricing has two halves — a package for the platform and metered trust work — and the figures are agreed once your identity mix is known. The pricing page describes the whole structure without inventing a number for it.

Enterprise and architecture

The questions that are easier to settle in a conversation.

Federation design, tenancy boundaries, migration, machine and agent identity, the limits of a verification outcome, data placement, and how the commercial model applies to your identity mix. These are the subjects a spreadsheet of yes and no answers handles badly, so they get an architect rather than a questionnaire.

Federation and enterprise SSO design

Organization-aware connections over OpenID Connect and SAML, attribute and group mapping, provisioning with SCIM, and what each of your customers has to configure at their end.

Federation broker

Tenancy, brands and boundaries

Where the tenant edge sits, how environments stay separate inside it, and how several brands or products share one identity foundation without sharing a blast radius.

The tenancy model

Migration from an existing provider

Identity mapping, application connection planning and credential lifecycle. What is involved depends on the source system and the integration you choose, so this one is a conversation rather than a checklist.

Solutions by problem

Machine, workload and agent identity

Cryptographic identities for services, devices and autonomous agents, the operator relationship behind an agent, and the lifecycle for the keys involved.

Machine identity

Verification, credentials and assurance

What a verification outcome asserts and what it does not, how evidence is kept apart from the issued outcome, and where portable credentials fit in a flow you already run.

Identity verification

Security review, subprocessors and data placement

The current subprocessor list, transfer detail for the regions you care about, tenant isolation, key lifecycle and retention. Early is better than at the end of a trial.

Trust centre

The enterprise route

Same address, different subject line. Say which of the subjects above you are there for, who else needs to be in the conversation — security, procurement, the team who will own the integration — and what you are deciding between. Bring security and procurement in while the architecture is still a question rather than a commitment; that review goes better before a trial than at the end of one.

Security disclosure

Found something? Write to the security address.

A reporting route that is easy to find and answered by a person is worth more than a published test report. If you believe you have found a vulnerability in the identity service, the hosted authentication flows, the published SDKs or this website, this is the address — not the general one, and not a form.

Security contact

security@idcheckglobe.com

Include what you found, where you found it, and the steps to reproduce it — a request and response pair, or a short script, saves everyone a round trip. Tell us if you believe the finding exposes data belonging to anyone else, and say in the first message if you need a secure channel rather than ordinary email; one is arranged before you send anything sensitive.

Ground rules

Four things this page refuses to do.

Each is something a contact page is expected to do. Stating the absence is cheaper than being asked, and the last one is the only piece of advice here that could prevent real harm.

No form

This site is statically rendered and holds nothing. There is no form, no lead-capture field, no chat widget and no tracking script waiting to classify you before a person has read a word. An email reaches someone who can answer, and it leaves both sides with a record of what was said.

No telephone number

The site publishes no phone number, because a number is only worth printing if it is answered by someone accountable for the answer. Every route here is a named address instead, and the one that matters most in a hurry — the security address — is the one that is hardest to lose in a queue.

No response-time promise

No target is published here, for the same reason there is no uptime percentage in the trust centre: a number with no measured history behind it tells you nothing, and we would rather be judged on the reply you actually receive than on a figure we wrote on a marketing page.

Nothing sensitive by email

Please do not send credentials, API keys, access tokens, passwords, customer identity records or copies of identity documents to any address on this page. If a conversation needs material like that, say so in the first message and an appropriate channel is arranged before anything is sent.

Who you are writing to.

ID Check Globe is operated by Cloud Granite Limited. Cloud Granite Limited is part of Haka Tech Ventures Limited. The operating company is the party a customer contracts with and the party that carries the obligations in the agreement; registration detail for a counterparty check is provided as part of contracting rather than printed here, where it would quietly go stale.

Worth reading first.

Most of what a first conversation would otherwise be spent on is already written down, including the places the platform deliberately stops.

Questions

Asked before the first message.

What is the difference between authentication and authorization?

Authentication establishes who or what is making a request. Authorization determines whether that authenticated principal may perform a particular action. ID Check Globe focuses on the first. The second belongs to your application or to a dedicated authorization layer, and we are deliberate about not blurring the two.

Can I use ID Check Globe in an existing application?

The platform is designed around standard authentication flows, APIs and SDK integration, so existing web, mobile and backend applications can connect without rebuilding their user experiences.

Can we migrate from another identity provider?

Migration design covers identity mapping, application connection planning and credential lifecycle considerations. What is involved depends on the source system and the integration you choose.

How do I start?

Tell us what you are building and which identities it needs to authenticate. Enterprise teams can begin with an architecture conversation about federation, tenancy and credential lifecycle.

Two addresses. That is the whole directory.

Everything except a security report goes to the general address; a suspected vulnerability goes to the security address. Neither is a queue you have to be qualified into first.

CompanyTrust centrePricingCookie notice