Korea-Facing Consent in Event Payloads
Carry consent state as a first-class property so analysts can filter without rebuilding pipelines.
- privacy
- korea
Collect only properties that feed decisions you actually make. Unused fields add QA noise and legal surface area.
Separate identity keys from content payloads. Prefer hashed identifiers where possible, and write retention periods for raw stores into the same handbook as your dictionary.
Surface consent states on events so analysts can build compliant cohorts without asking engineering for a special export.
Review vendor SDK auto-collection before the first production release. Turning toggles off after a questionnaire arrives is already late.