How it works
From request to accountable decision.
ConsentKey is designed to sit between a digital request and the information, credential, permission, access, or action being requested.
It does not replace authentication. It evaluates whether an authenticated request is authorized for this purpose, at this time, within this scope.
Incoming request
Person, application, vendor, device, workflow, or AI agent asks for data, proof, permission, access, or action.
Decision boundary
Approve, limit, challenge, review, or deny
Authentication confirms identity. ConsentKey evaluates whether this request is authorized for this purpose, at this time, within this scope.
Minimum result
Only the appropriate data, proof, permission, or action passes through.
Decision receipt
An accountable record remains behind for review, expiration, or revocation where technically possible.
Six public steps
A clear executive model for consent-routed authorization.
- 1
Receive the request
Capture what is being requested before information, permission, or action is released.
- 2
Verify the requester
Evaluate the person, application, device, workflow, vendor, or AI agent behind the request.
- 3
Understand context and purpose
Determine why the request is being made, where it is happening, and what business purpose it serves.
- 4
Resolve authority, consent, policy, authentication, and risk
Compare the request against authority, consent posture, policy rules, authentication state, and risk signals.
- 5
Permit only the minimum appropriate result
Approve, limit, challenge, review, or deny the request, then release only the minimum appropriate data, proof, permission, or action.
- 6
Record the decision and manage expiration
Create an accountable decision receipt and apply expiration or revocation where technically possible.
Decision options
ConsentKey may approve, limit, challenge, review, or deny.
The public model stays vendor-neutral and implementation-safe. It describes what the control layer is intended to evaluate without exposing private scoring formulas or protected routing logic.