VES addendum

This page explains how consent events may be captured and relied upon as time-fixed evidence under the Veriscopic Evidence Standard (VES). It does not define additional normative requirements. VES.

Consent as Evidence (Reliance Events)

Consent is often treated as a preference toggle. Under VES, consent can be treated as a governance reliance event: a recorded basis on which an organisation relied at a point in time.

What a consent record evidences

The existence of a consent event at a stated time (UTC)
The scope of consent relied upon at that time
The version of terms / notices associated with that consent (where present)
The page or context where consent was recorded (where present)

What a consent record does not evidence

That consent was legally sufficient for any specific purpose
That the individual understood or intended any particular outcome
That downstream processing was compliant or appropriate
That an organisation met broader regulatory obligations

Integrity statement (recommended)

Integrity-only posture

Verification confirms that a consent record has not been altered since it was fixed in time. It does not certify legal sufficiency or compliance.

Consent linkage semantics

Consent records are most valuable when they are linkable to the decisions or processes that rely on them.

Consent → Decision: the decision record may reference the consent record as a reliance input.
Consent → Assessment: an assessment record may reference the consent record as part of its information state.
Consent → DPS: DPS Page 3 may list consent relied upon as part of the information state at the time of judgement.

Example wording (DPS Page 3)