User Flow Mickael Rutembya · Flow Atlas

CGV

/cgv/

Visitor reads general terms and conditions of sale for services offered on the site.

User intent

What the visitor is trying to do

« I want to review the terms of sale before ordering a service. »

Entry points

ElementDestination
Footer link CGV/cgv/
Direct URL Typed by visitor/cgv/
Order process Pre-checkout reference/cgv/

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor or buyer"]) --> Direct["/cgv/"] Direct --> Home["/"] Direct --> Legal["/mentions_legales/"] Direct --> Cgu["/cgu/"] Home --> End(["Terms acknowledged"]) Legal --> End Cgu --> End click Direct "https://mickael-umt.com/cgv/" "Open CGV" click Home "https://mickael-umt.com/" "Open Home" click Legal "https://mickael-umt.com/mentions_legales/" "Open Legal" click Cgu "https://mickael-umt.com/cgu/" "Open CGU" click End "https://mickael-umt.com/" "Open Home"

Screen inventory

IDScreenUser task
P0CGVRead sale terms, deliverables, payment
P1HomeReturn to offerings
P2LegalVerify identity

Flow scenario

Scenario LG2

Buyer validates terms before checkout

Trigger

  • Visitor clicks CGV from footer before ordering
  • Wants to confirm deliverables, payment, cancellation

Experience

  1. CGV page loads with pricing principles, scope, liability.
  2. Visitor reviews clauses relevant to their case.
  3. May navigate to legal identity or CGU for full context.

Trust and safety rules

  • CGV is legally binding; wording must match invoicing.
  • No personal data is collected on this page.
  • Pricing and scope are indicative unless a contract is signed.

Interaction rules

  • Static read-only content, accessible from footer.
  • No authentication required.
  • Linked from terms references in checkout and contracts.

Result states

StateWhat the visitor seesWhat happens next
ReadFull terms of sale textVisitor returns to offering or proceeds to order