Collect
State the purpose, minimum fields, audience, notice, choice, and sensitive-data boundaries.
Privacy and data
Follow the Argentina data from collection to deletion.
Argentina's personal-data framework requires project-specific review of notices, databases, processors, transfers, security, access, correction, and deletion.
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 Argentina 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 Argentina context into a workable brief.
Before a stack or schedule is chosen, identify who will use the system in Argentina, who owns each decision, and which assumptions still need local confirmation.