Why does this field exist?
Name the task, minimum information, source, audience, notice, choice, and any sensitive or unnecessary data the interface should reject.
Personal data board
Give every data decision a visible card and a real owner.
Uruguay personal-data questions may involve purpose, notices, lawful handling, registration, processors, transfers, rights, security, retention, and incidents. The actual product and organisation determine what applies; software should implement the approved model consistently.
Who can touch the record?
List roles, support access, processors, AI tools, automated steps, exports, integrations, and the approval needed for each use.
Where do copies travel?
Place hosting, subprocessors, email, analytics, logs, backups, remote access, transfer questions, and manual spreadsheets on the board.
What happens when a person or incident interrupts the plan?
Define correction, access, deletion, account closure, retention expiry, backup aging, security investigation, escalation, and communication evidence.
Use the interface to prove the policy works.
Test refusal and changed preferences, required versus optional fields, role removal, vendor failure, a rights request, deletion across copies, and incident investigation. A privacy document that cannot be demonstrated in the system is an unfinished decision.
Measurement boundary
This microsite has its own GA4 property.
It records traffic and direct phone or email click events. That separate measurement does not settle notice, consent, retention, transfer, vendor, or user-right questions for this or another product. Extra advertising or profiling tags are not silently included.
Bring to the data session
- Field and event inventory
- Role and permission list
- Vendor and subprocessor list
- Exports, backups, and retention behavior
- Current notice and request workflow
Pick one record and pin every copy.
The URCDP portal is an official starting point; a qualified owner determines applicability.