Hummand

Human identity
infrastructure.

Overview

Position

Hummand stands in the path of every human act with consequences: policy per act, source orchestration, a receipt for the act.

It confirms that the right person is present and authorized, and leaves a record the auditor checks alone.

What we don't do
At Hummand

Who it is, is present, authorized what.

  1. 0.1Policy per act

    The client declares the guarantee level; the policy turns it into steps.How much certainty the request demands, and the steps the person completes on their phone to reach it.

  2. 0.2Source orchestration

    Native live presence; civil identity and signature as plugged sources.Live presence confirms a real person in front of the camera, now; the other confirmations come from external services, and the receipt says which one was used.

  3. 0.3Receipt for the act

    Signed, chained per client, verifiable without Hummand.The record of what happened, which any auditor checks alone.

Sectors
Companies and government: financial, technology, life sciences, public sector
Offer
Presence, identity and mandate, with a receipt
Guarantee
Signed receipt, verifiable without Hummand
0.4

How we speak

[ Act 1 ]
Everything
the client asks,
with type and level
[ Policy 2 ]
Type and level
become steps;
version in the receipt
[ Receipt 3 ]
Signed,
chained,
hashes only

Meet the

Human guarantee

Illustrative demonstration of the target architecture. Live presence available; civil identity in accreditation; document in target architecture; agent mandate available.

tipo
onboarding.identidade
consentimento_geral
v1 · accepted
consentimento_biometrico
v1 · accepted
ts_criado
2026-09-07T14:31:40Z
ref_cliente_hash
sha256:8a1e…f07c
contexto_hash
sha256:c4d2…91ab
etapa presenca
ok
etapa match
ok
fonte
hummand.presenca
fonte
hummand.match
humano_vivo
true
mesma_pessoa_da_referencia
true
identidade_civil
true
fonte
serpro.datavalid
fonte
ocr.documento
imagem
discarded
biometria_retida
false
retencao
by policy · crypto-shred
formato
humanproof/1
nivel
3
resultado
positivo
mandato_ref
ato_01J…7Q · agent · 30 d
ts_concluido
2026-09-07T14:32:07Z
kid · alg
hp-2026-09 · ES256
prev_hash
sha256:3f9a…c21e

The receipt the act leaves: humanproof/1 format, real fields, fictitious values.

Live presence and civil identity in a policy per act, with a receipt that
any auditor verifies.

Progress

Where the proof is a receipt.

  1. 0.5Chained receipt

    Every finished act generates a signed receipt, chained to the same client's previous one.A receipt removed or altered in the middle of the series shows.

  2. 0.6Hashes only

    No receipt contains an image, a template or client content.Whatever refers to the person goes as a hash, a code that identifies the data without revealing it.

  3. 0.7Active challenge

    A passive signal collapses against a competent replay; what resists is the live response.A replay is a recording shown again to the camera; the live response is the reaction to a challenge on the screen, during capture.

* Honest labels on every capability: available · in accreditation · target architecture. A step that does not execute yet responds as unavailable; nothing is simulated.Available is in production today; in accreditation is ready in the code and waits for a third party; target architecture is designed and not yet in production.

Go to Labs
1.0 Evidence
Empirical results with date, method and source declared. Citable.
See Labs
2.0 Verify a receipt
Paste the JSON and the public key. No account, nothing sent: it runs in your browser.
Open the verifier
3.0 Talk to us
A technical conversation, straight with the people who build it, no sales script.
Contact
4.0

Security by design

Centralized custody, declared: KMS envelope per record, per-client isolation in the database, erasure by crypto-shred.Each record has its own key, and destroying it makes the data unreadable for good.

See Security
5.0

Data and LGPD

Consent per step, with versioned text recorded in the receipt. No image or template persists after the act; erasure on request, on record.

See LGPD
6.0

Integration

An acts API with a TypeScript client generated from the contract, signed webhooks, and the dashboard that generates the journey by link, with no code.

See Docs