What we don't do

We are not an audit firm.

The receipt is verifiable by an auditor, the client's, a regulator's or an expert's, without trusting Hummand. We audit no one; we hand the proof to whoever audits.

What the receipt proves is the integrity of the record and what the declared sources sustain. It does not re-run the capture nor judge anything beyond that: reading the case is the auditor's job.

We are not login.

Login is getting into the account; Hummand comes in at an action with consequences, inside the client’s process, without replacing access.

We do not manage the client's user identities, sessions or third-party passwords. An act happens inside the client's process, when there is a consequence; the session remains theirs.

We do not sell KYC.

KYC is the customer due diligence banks and fintechs run when an account is opened.

Civil identity is a plugged source, labelled in the receipt and in accreditation. The lead offer is recurring presence with proof: a living person, the same one as the reference, authorizing something, with a receipt.

We estimate nothing.

No score, risk, probability or age estimation from a face, anywhere in the product. The receipt records what happened, verifiably; the business decision is the client's. It is a written rule of the restructuring plan, not a preference of the moment.

We keep none of it.

A template is the numeric pattern extracted from the face; a hash is a code that identifies a piece of data without revealing it.

In no receipt, and in no table after the act. Captured image and template are discarded at the end of the step; the client reference image stays encrypted only while the act is open and is erased when it ends; the act context stays encrypted and only the hash leaves. Biometrics retained after the act equals false is a product invariant.

Bureaus, fingerprinting, lists, geolocation and behaviour stay out.

A bureau is a credit database; fingerprinting is identifying the device; PEP are politically exposed persons.

Credit bureaus, fraud scores, commercial device fingerprinting, PEP and sanctions lists, geolocation as proof, behaviour as proof, age estimation from a face and third-party biometrics are not in the catalogue. SMS is only the delivery channel for the link, never proof of possession.

No availability promised outside the contract, no guaranteed accuracy, no certification of our own.

Guaranteed accuracy would be promising a hit rate.

The live-presence component is AWS-certified; Hummand is not certified. Availability is what the contract defines, and "post-quantum" is not in the vocabulary. Every capability carries one of three labels: available, in accreditation, target architecture.

Alerts are computed on read; no source is swept in the background.

No source is swept in the background. What runs by itself is what the client schedules: the rounds of the reverification cycle and the team's access review. A vital-status source only triggers an exception proof at the client's request; the proof is still the presence.