Public sector

The agency pastes the list of beneficiaries from its spreadsheet, by the reference it already uses, such as the registration number, and sets a common deadline. Up to 500 proofs at once; the links come out in a CSV, to go through the channel the agency already has with the beneficiary.

For periodic proof of life, a reverification cycle opens each round by itself, in the birthday month or on a date, and closes with how many proved it and the value covered and at risk, summed from the value the agency reports.

The beneficiary opens the link on their own phone, reads what the proof is for, consents and answers a live presence challenge on the screen. In the browser, with no app to install and no trip to an office.

The photo on record can be attached to each proof after creation, in the campaign too; with it, presence comes with the comparison.

Every finished proof leaves a signed receipt, chained to the previous one from the same agency: what happened, when and at what assurance level, with no image and none of the beneficiary's data in the clear.

The dashboard shows each campaign's progress, the proofs about to expire and those that expired without renewal. What to do with each pending case is the agency's decision; Hummand delivers the proof, it does not suspend benefits.

The gov.br proof requires the gov.br app and biometrics on file with the driving licence or the electoral court. Whoever has neither is left out of it and goes back to re-registration.

With Hummand, the link opens in the phone's browser, with no app, and the comparison is against the enrolment photo the agency itself attaches.

Each Hummand proof leaves a signed, chained receipt that internal control and the audit court check with the public key, without asking Hummand for anything. The cycle closes in the agency's dashboard with the value covered and the value at risk.

The gov.br account as a plugged source, next to presence. gov.br says the identity was validated at some point; Hummand proves the person is present now. They add up; neither replaces the other.

The receipts leave the dashboard exactly as they were signed. The auditor checks signature and chain in the browser or on the command line, with the published public key, without access to Hummand's systems.

A receipt removed or altered in the middle of the series shows in the verification. A missing proof does not stay invisible: the chain exposes it.

Who opened the evidence of a proof, when and with what declared reason; and what the team did in the dashboard, with filters by period, person and type, and CSV export.

The agency generates a link with a deadline to the dossier of a proof, with the recipient and the purpose declared. The audit court or internal control opens it without an account, and each opening becomes a signed receipt the agency sees in its dashboard. The link can be revoked at any time.

Image and template are discarded after the proof; what stays is the result and the hash of the reference. The beneficiary's reference is keyed with a secret of the agency, never in the clear.

By proof or by the reference the agency itself assigned, by key destruction, with a record of who erased and when.

By contractual agreement, the operation can be entirely national: server, database, backups, keys and live presence itself. Today's installation is described, without omission, in Security.

Live presence plus the government database, when the source accreditation arrives. Only the verdict persists; the raw data never leaves.

The date of each receipt attested by an ICP-Brasil Time Stamp Authority, a third party that is not Hummand. Ready in the code; it goes live with the authority contract.

A death notice from a vital records source, such as SISOBI or the national civil registry, only triggers an exception proof; the proof is still the presence.

Someone who cannot take the proof alone authorizes another person, with scope, deadline and a document, such as a power of attorney or guardianship, all hashed in the receipt. Level 2 since 0.28.0; it rises to level 3 when civil identity is accredited.

Per completed act, approved or rejected, with a minimum allowance in the annual contract and a lower price per act as volume grows. An act that expires or is cancelled without a result is not charged. The amount is set in the contract.

By e-mail, with the agency, the scheme, the approximate number of beneficiaries and how often the proof is due. The answer comes from the people who build the platform.

Security, LGPD, capabilities and what Hummand does not do are published, with the label of each item's state, for the terms of reference and the agency's review. The technical sheet sums up security and LGPD in two pages.

This page on one A4 sheet, for the process and for whoever decides.