Consent

Overview

When a member enrolls in a partner loyalty program, they provide explicit consent to the partner data policy. Otonum stores consent as a versioned immutable snapshot, where each policy version has its own record.

Policy Versioning

Each partner maintains a data policy with a version number and a jurisdictionCode that determines the applicable regulatory framework.

When a policy is updated, a new version is created. Existing members are not migrated automatically. They keep consent under the version they originally accepted until they actively re-consent.

Enrollment and Consent

Consent is captured during enrollment. The enrollment payload includes:

• The policy version accepted by the member
• The partner jurisdictionCode context

Otonum stores the full policy content as a snapshot at consent time so accepted terms remain auditable even after later policy updates.

Consent Withdrawal

A member may withdraw consent at any time. On withdrawal:

• The member is unenrolled from the loyalty program
• New transactions cannot be submitted for that member
• Existing transaction history is retained according to data retention rules

Key Points

• jurisdictionCode is tenant-level metadata and is not provided per enrollment request.
• Always pass the current policy version at enrollment.
• Consent records are read-only after creation.

See Also

• Consent Management: Implementation patterns
• Quick Start: Enrollment overview