Collect
State the purpose, minimum fields, audience, notice, choice, and sensitive-data boundaries.
Privacy and data
Follow the Estonia data from collection to deletion.
GDPR, Estonian data-protection law, tracking, processors, transfers, retention, rights, security, and public-sector rules should be mapped to the actual service.
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 Estonia 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 Estonia context into a workable brief.
The clearest scope starts with the actual Estonia operation: people, access, content, transactions, deadlines, support, and acceptance.