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 doWho it is, is present, authorized what.
- 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.
- 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.
- 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
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
- mandato.agente
- consentimentos · geral
- v1-2026-08-en · accepted
- consentimentos · biometrico
- v1-2026-06-en · accepted
- consentimentos · escopo
- v1-2026-09-en · accepted
- sujeito.ref_compromisso
- sha256:8a1e…f07c
- contexto.hash
- sha256:c4d2…91ab
- etapas · presenca
- ok
- etapas · match
- ok
- fontes · hummand.presenca
- aws
- humano_vivo
- true · componente
- mesma_pessoa_da_referencia
- true · componente
- evidencia_tecnica
- no score
- identidade_civil
- null · in accreditation
- fontes · serpro.datavalid
- in accreditation
- sujeito.referencia
- sha256:5b07…e2d4
- biometria_retida
- false
- retencao
- 2031-10-30 · declared basis
- formato · revisao
- humanproof/1 · 2
- nivel
- required 2 · reached 2
- resultado
- positivo
- mandato.concessao
- agent · 30 d
- ts_emitido
- 2026-10-30T14:32:07.412Z
- assinaturas
- emissor · hp-2026-09 · ES256
- prev_hash
- sha256:3f9a…c21e
The receipt the act leaves: humanproof/1 format, revision 2, real fields, fictitious values; civil identity is in accreditation.
Live presence and civil identity in a policy per act, with a receipt that
any auditor verifies.
Where the proof is a receipt.
- 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.
- 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.
- 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- 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
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 SecurityData and LGPD
Consent per step, with versioned, published text; the receipt records the version and the hash of the text shown. No image or template persists after the act; erasure on request, on record.
See LGPDIntegration
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