What is the short answer?
Before meeting, a dating product should collect only what it needs, show only what helps respectful matching, and keep sensitive details private by default.
Who is this for?
This is for adults who want real connection but do not want a dating profile to expose legal identity, exact location, boundary details, trusted contacts, safety plans, or private reflections.
What should stay private?
- Legal identity and identity documents.
- Exact birthdate and exact live location.
- Trusted contacts and safety plans.
- Private boundary details and sensitive reflections.
- Reports, moderation notes, and support history.
Verification can support accountability without turning legal identity into public dating identity.
What can be public?
Public profile data should be limited to what helps mutual fit: display name, age or age range, city-level location, optional pronouns, intent, pace, communication style, prompts, and optional green-flag badges.
Why does this matter for trust?
Privacy is not only a compliance obligation. It is a product feature. The less a platform collects too early, the less it can expose, mishandle, or force people to explain before they are ready.
What is not live yet?
This package does not process real identity verification, collect real waitlist data, store private member data, or connect analytics. Those steps require legal/privacy review, provider approval, retention rules, deletion/export workflows, and explicit owner approval.