User Flow Mickael Rutembya · Flow Atlas

Privacy Policy

Visitor reviews how personal data is collected, stored, and protected under applicable regulations.

User intent

What the visitor is trying to do

« I need to understand what personal data is collected and how it is used. »

Entry points

Element	Destination
Footer link Privacy	`/privacy/`
Contact form Consent reference	`/privacy/`
Direct URL Typed by visitor	`/privacy/`

Flow

Adjacent routes — click a node to open it.userflow

flowchart LR Start(["Visitor"]) --> Direct["/privacy/"] Direct --> Home["/"] Direct --> Contact["/contact/"] Direct --> Legal["/mentions_legales/"] Home --> End(["Privacy understood"]) Contact --> End Legal --> End click Direct "https://mickael-umt.com/privacy/" "Open Privacy" click Home "https://mickael-umt.com/" "Open Home" click Contact "https://mickael-umt.com/contact/" "Open Contact" click Legal "https://mickael-umt.com/mentions_legales/" "Open Legal" click End "https://mickael-umt.com/contact/" "Open Contact"

Screen inventory

ID	Screen	User task
P0	Privacy Policy	Understand data collection, rights, retention
P1	Contact	Submit form knowing data handling
P2	Legal	Check identity and hosting

Flow scenario

Scenario LG4

Prospect audits data protection before outreach

Trigger

Visitor clicks privacy from footer before submitting contact form
Wants to confirm GDPR/CNIL compliance

Experience

Privacy page loads with data controller, purposes, retention.
Visitor reviews rights and contact for requests.
Returns to contact form with confidence to submit.

Trust and safety rules

Privacy policy must align with actual data processing activities.
Data controller identity must be clearly stated.
Rights access and contact must be accurate.

Interaction rules

Static read-only content, accessible from footer.
Contact form references this policy in consent notice.
No cookies or tracking beyond site analytics.

Result states

State	What the visitor sees	What happens next
Read	Privacy policy details	Visitor returns to contact or leaves