Features / Consent
Use the current consent answer without losing the decisions behind it.
Each consent change is an event with a class, state, source, evidence version, and time. Knownry also maintains the current state so another product can make a fast, explainable eligibility check.
Campaign email
Marketing granted
- GrantedFrontroom signup · Evidence v3Aug 24
- ConfirmedPreference center · Policy v3Aug 25
In practice
What happens when you use it.
- 01
Define what the choice covers
A consent class names the channel and purpose, including whether it permits campaign email.
- 02
Record the change
Granted, denied, pending, and revoked states arrive with the source reference, evidence version, and occurrence time.
- 03
Answer the next request
Authorized products can read the current state while an operator can still inspect the events that produced it.
A consent change in context
The latest answer stays fast without flattening the history.
A person grants campaign email at signup and later revokes it in a preference center. PostDesk receives the current denial immediately, while the operator can still inspect both events and their evidence versions.
- Current state
- Revoked
- Purpose
- Campaign email
- Evidence
- Two retained events
The record
What Knownry keeps
- The consent class, channel, purpose, and policy version
- Every state change in the order it occurred
- The source product, source reference, and evidence version
- The current state used for communication eligibility
Why that record matters
A single yes or no is not enough when a preference changes. The event trail explains whether the current state came from a signup, preference center, service request, or later revocation.
The line Knownry does not cross
Knownry preserves the recorded choice and applies it to eligibility. It does not invent consent when evidence is missing or treat transactional permission as marketing permission.
Keep exploring