Forms and accounts
Collect only necessary fields, explain the next step, protect transport and restrict administrative access.
Privacy and data
Know the information path before it becomes a system.
A form field can create duties far beyond the screen. We map what is collected, why it is needed, where it travels, who can see it and when it should be removed.
The data route we document
- Every category of personal or sensitive information the service collects.
- The purpose, user notice and consent or other approved basis for each use.
- Every processor, analytics tool, integration, host and human role with access.
- Where information is stored or transferred, including cross-border services.
- Retention, deletion, access correction, incident and account-recovery procedures.
- The named owner who keeps the map accurate after launch.
Design decisions
Privacy becomes architecture.
The answers determine whether a field exists, which vendor is suitable, where a log is retained and how a user request reaches a responsible person.
Analytics and AI
Identify what each tool receives. Keep confidential or personal information out of AI services unless an approved data route explicitly allows it.
Cross-border vendors
Record locations, roles, terms, safeguards and exit options rather than treating a cloud product as a neutral black box.
A compliance page is not a compliance programme.
Notices must match the actual system. The project owner remains responsible for legal decisions, registrations, approvals and operational follow-through.
Trace the real information flow.
Bring current forms, spreadsheets, vendors, roles and retention habits. We can turn them into a visible system map.