DIREKT Consent and Policy Versioning

Records

Store policy ID, version, language, effective date, user, accepted/declined time, method, purpose and withdrawal where applicable.

Separate choices

  • terms acceptance;
  • privacy acknowledgement/consent where required;
  • public premises/location publication;
  • contact sharing per enquiry;
  • optional marketing;
  • analytics choices where required;
  • provider declarations;
  • evidence/field-visit consent.

Bundling optional marketing with service access is prohibited.

Changes

Material changes trigger notice and re-acceptance where legally required. Historical acceptance remains auditable. Backend enforces minimum required versions for affected actions.

Copy

Plain language summary plus accessible full policy. Withdrawal explains functional consequences without blocking unrelated rights.