Collect
State the purpose, minimum fields, audience, notice, choice, and sensitive-data boundaries.
Privacy and data
Follow the Serbia data from collection to deletion.
Serbia's data-protection law requires current review of purpose, legal basis, notices, processors, transfers, retention, rights, tracking, security, and incidents.
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 Serbia 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 Serbia context into a workable brief.
A useful first conversation covers the users, existing systems, language responsibility, data, payments, timing, and the evidence that will count as done in Serbia.