Position web as premium beta support/marketing/readiness unless feature parity is proven in code.
Release readiness
Web clarity before beta expansion.
The iOS beta remains the primary member experience while web supports access requests, legal review, support triage, feedback, and release readiness.
Member flow: complete the interview, wait while the dating persona is prepared, let background dates happen, receive progress notifications, then see matches or follow-up needed.
This private beta asks only Man and Woman for gender and introductions are between men and women; there are no pronoun or sexual orientation prompts.
Keep copy aligned to dating persona preparation, background dates, progress notifications, matches, and follow-up needed.
State that this private beta asks only Man and Woman and introductions are between men and women; do not add pronoun or sexual orientation prompts.
Keep legal, privacy, support, and safety routes reachable without member credentials.
Avoid real secrets in examples, docs, screenshots, and tests.
Run audit:prod, typecheck, lint, tests, build, and secret scan before release handoff.
Claim guardrails
Evidence index
Public routes below substantiate the current web role without credentials, private members, or operational secrets.
Credential-independent support aliases and triage expectations are published for private-beta help.
Boundary: Shows support coverage for the controlled private beta, not full customer-success automation.
Trust and safety reporting paths, conduct expectations, and privacy-first principles are visible before sign-in.
Boundary: Explains support escalation paths and member responsibilities without promising guaranteed outcomes.
Feedback prompts collect qualitative readiness gaps without requiring app credentials or personal accounts.
Boundary: Supports private beta learning loops rather than claiming mature analytics or automated decisions.
Release readiness checks document copy, legal, support, safety, build, and scan expectations.
Boundary: Frames web as a readiness surface for beta expansion, not proof of broad launch readiness.
Terms are reachable publicly so prospective members can review responsibilities before requesting access.
Boundary: Provides legal review access while the product remains a controlled private beta.
Privacy policy and contact path are reachable publicly for data-use and deletion questions.
Boundary: Documents privacy practices and legal contact routes without exposing operational details or private data.
Still gated
What remains externally gated
These items are intentionally listed as dependencies rather than implied as done by the web surface.
Cohort expansion approval
Invite volume should follow operator review of support capacity, safety coverage, and qualitative feedback.
Requires: Requires beta operator sign-off before any larger cohort is invited.
Native app distribution review
The web surface can describe the beta boundary, but distribution readiness depends on native release checks.
Requires: Requires external App Store or beta distribution review outside this web repository.
Legal and policy review
Public terms, privacy, safety, and marketing copy should be reviewed before broader promotion.
Requires: Requires external legal review and approval before expansion messaging changes.
Operational coverage window
Support and safety aliases should only be promoted when humans can monitor and respond appropriately.
Requires: Requires operator staffing confirmation for the next beta window.