Invitation-only by design.
Beta access requires a private invitation. Service email uses the configured private delivery channel. Payments, external analytics and network AI are not enabled.
Care, from the beginning
Two separate experiences: invitation-only beta accounts and the original fictional demo. Neither is an emergency service.
Beta access requires a private invitation. Service email uses the configured private delivery channel. Payments, external analytics and network AI are not enabled.
Registration checks the age calculated from a private, self-reported birth date. This does not verify actual age or identity. Independent age assurance is still required before a wider release.
Other accounts can see your chosen profile only when both profiles are eligible and discoverable. Your email, full birth date and password are never part of another person's profile view. Distances use city centres, not your location.
Blocking hides profiles and photos in both directions and deactivates the match. Reports enter a protected staff workflow. This beta does not provide live emergency response.
Beta matches require two separate accounts to like each other. A like can be withdrawn. Date proposals require both people to accept independently.
Protected sessions, login limits, CSRF protection, image sanitization and own-account export and deletion are implemented. This beta has not received an independent production security audit or legal compliance review.
Messages are available only within active mutual matches. Blocking or unmatching disables conversation access and sending. Stored history remains available in each participant's own data export.
Account data and sanitized photos use the configured private storage. Password reset and confirmation messages use the configured private email channel. Account deletion removes live database records; delivery records and backups are managed separately by the operator.
Essential cookies keep your session and language preference. A browser preference remembers the colour theme. Session expiry is configured by the operator; account data stays until you delete it or the documented retention process applies.