Safety & boundaries

Safety

Connection should grow through mutual choice. Recipient control is part of the product model, not a premium feature.

Public expression is not consent

Posting, answering, or maintaining a public profile does not make someone available for dating or unrestricted private contact. Community identity and dating eligibility remain separate even when they belong to one account.

Sensitive dating preferences and eligibility must be explicit, understandable, and evaluated inside the dating context. They should not be casually inferred from public content.

The recipient keeps control

  • A stranger introduction is bounded while the relationship remains unconnected.
  • Ignoring, blocking, or reporting cannot be overridden by payment.
  • A reply or another explicit mutual relationship is required before ordinary conversation expands.
  • Deleted, private, moderated, or otherwise unavailable public content must fail closed.
Visibility may be purchased in a bounded context. Consent cannot.

Operational readiness matters

Product controls alone are not enough. Before a public launch, reporting, blocking, objectionable-content handling, moderation operations, and a maintained support channel must be verified together.

This website describes the product direction. It does not claim that an App Store release, production moderation operation, public-share backend, or Universal Link chain is already live.