FIN∫EGRAL
Use cases Coverage Verify Govern Trust Get access
Govern — step 06 of the pipeline

Consent is not a checkbox. It is a record that stays alive.

Every connection can be paused, narrowed, revoked or expired by the person it belongs to — in seconds, from your app or ours. What happened, who did it and what changed is written down permanently, in a form an examiner can read.

Try a live consent record See the security model
{{ v.name }} {{ v.body }} {{ v.timing }}

The consent record

One record. Every state it has ever been in.

This is live. Pause it, narrow the scope, revoke it or let it expire — the state machine and the event log below respond exactly as they do in production.

Consent Guaranty Trust Bank · 2 accounts Granted by A. Okonkwo · for Kobo Lend {{ stateLabel }}

{{ stateExplain }}

Scope — tap to narrow
{{ f.label }} {{ f.value }}
Actions available to the holder
Consent history — append only
{{ e.what }} {{ e.at }} {{ e.detail }} {{ e.actor }}

{{ eventsNote }}

Lifecycle

Four states, and what each one means to your code.

{{ l.state }} {{ l.name }}

{{ l.body }}

{{ l.api }}

Policy, enforced at the boundary

Rules the client cannot talk its way around.

Governance that lives in your application code is a suggestion. These are enforced where the response is assembled, so a mistake in your integration cannot widen what a consent allows.

See the security architecture →
{{ p.name }}

{{ p.body }}

When someone asks

The four questions an examiner always asks.

Each one is answerable from the record itself, for any read, going back the full retention window.

{{ q.no }} {{ q.q }} {{ q.a }}

The pipeline

Govern is the last step, and it governs all the others.

{{ s.no }} {{ s.name }} {{ s.body }}

Ship a consent your compliance team will defend.

Pause, narrow, revoke and expire come with the connection — there is nothing extra to build or buy.