User journey

🔵 Research. Three journeys: the creator, the recipient, and retirement.

Journey 1 — the creator

discover  →  onboard as Consumer  →  claim identity  →  build biodata  →  publish  →  share  →  manage  →  retire

Step	What happens	Existing or new
Discover	Ad, a shared biodata they received, a search, or a matchmaker	—
Onboard	Existing individual/consumer onboarding path	✅ Reuse. See Architecture
Claim identity	Choose a slug for My QR Setu	🆕 Identity layer
Build	Guided form: about, family, education, career, expectations, photographs. Or import from an existing PDF.	🆕 Feature
Choose disclosure	What is open, what is on request, what is private	🆕 Feature
Publish	The destination becomes live at its own address	🆕 Feature
Share	WhatsApp with a rich preview, QR, copy link	✅ Preview machinery exists
Manage	See views, approve access requests, respond to interest, update status	🆕 Feature
Retire	Mark finalised; every existing link honours it	🆕 Feature

⚠ The creator is frequently not the subject. A father building his daughter's biodata is the common case. Steps "build" and "publish" therefore involve two people, and the consent model is a prerequisite rather than a later refinement.

⚠ "Import from PDF" is the highest-leverage step in this journey and also the one with the largest privacy surface. It removes the single biggest adoption barrier — "I do not want to fill another form" — and it sends sensitive personal data to an extraction processor. Both facts are true and the second gates the first.

Journey 2 — the recipient

This is the growth loop, and it must never require an install or an account to begin.

WhatsApp link
      ↓
opens in mobile web          ← no install, no login, no wall
      ↓
sees the OPEN tier
      ↓
   ┌──┴───────────────┬────────────────────┐
   ↓                  ↓                    ↓
just looking     wants more          interested
   ↓                  ↓                    ↓
leaves          request access        OTP  ← the FIRST authentication
   ↓                  ↓                    ↓
"create yours"   creator approves      chat opens

"Don't authenticate curiosity. Authenticate intent." Viewing is anonymous. The OTP appears at the first moment identity genuinely matters, which is also the first moment the person is willing to give it.

⚠ Most recipients are relatives, not prospective creators. The create-CTA should therefore be placed where intent concentrates — the interest moment and the closed-proposal page — rather than in every footer. See Growth.

Journey 3 — retirement, which is the success state

proposal finalised  →  status set  →  every existing link now shows "closed"  →  biodata retires
                                                          ↓
                                              account, identity and QR persist
                                                          ↓
                                          next consumer experience (couple, wedding, …)

⚠ This journey is the whole argument for the identity layer. If the account is the biodata, a successful match is a churned user. If the biodata is one card attached to a permanent identity, the account survives its own success — see Lifecycle.

Where the journeys touch the marketplace

At exactly one natural point, and it must be contextual and dismissible rather than a cross-sell campaign: when a proposal is marked finalised, wedding-adjacent vendor categories become relevant on a known timeline. See Marketplace relationship.

⚠ Marital status is PII. Surfacing "this person is getting married" to vendors in any form is a consent decision, not a product default.

Open questions

1. Does identity claiming happen before or after building the biodata? Asking someone to choose a permanent public slug before they have seen any value is friction at the worst moment; asking after means the biodata exists before its address does.
2. What does the subject see? If a parent creates it, does the subject get their own view, their own control, or only a notification?
3. Can one account manage biodata for two siblings? The owner's rule says one active biodata per account. Whether "active" permits a retired sibling's biodata to coexist is unresolved and needs an explicit answer.
4. What happens to shared links when a biodata is deleted rather than retired? Deletion is a DPDP right, and the answer cannot be a broken page that leaks the fact it once existed.