Collect
State the purpose, minimum fields, audience, notice, choice, and sensitive-data boundaries.
Privacy and data
Follow the Denmark data from collection to deletion.
GDPR, Danish cookie rules, processor relationships, and cross-border vendors should be mapped to the real product flow.
Use
Name ownership, access roles, processors, AI use, automated decisions, and data-quality checks.
Move
List hosting locations, vendors, transfers, subprocessors, backups, and remote access.
Keep
Set retention, deletion, account closure, legal holds, audit evidence, and recovery.
Respond
Assign rights requests, security events, breach decisions, escalation, and communications.
Analytics follows the same consent analysis.
The Denmark microsite has its own GA4 property. That separation improves reporting; it does not remove any notice or consent duty that applies to the visitor. Advertising or profiling tags require a separate decision.
Next step
Turn the Denmark context into a workable brief.
Country context should change the plan where it matters, not decorate the proposal. Start with the parts of the Denmark journey that cannot fail.