Private by default.

Humanly Mutual will handle sensitive identity, location, relationship, intimacy, safety, and communication data. The product must collect less, expose less, and give users more control.

Public profile data

Display name, age or age range, city-level location, optional pronouns, intent, pace, communication style, prompts, and optional green-flag badges.

Private by default

Legal identity, exact date of birth, exact location, boundary details, sexual-health-adjacent answers, trusted contacts, reports, safety plans, and private reflections.

Data minimization is a feature.

Before production launch, Humanly Mutual needs legal review, privacy impact assessment, data retention schedule, identity vendor review, and deletion/export workflow.

Privacy controls

Launch requirements

No exact public locationRequired
Trusted contacts hiddenRequired
No AI training by defaultRequired
Delete/export controlsBefore beta
No ad-tech in intimate flowsRequired

This page is a product privacy pledge, not final legal policy. Public launch needs lawyer-reviewed privacy terms for the launch jurisdiction.

Privacy-first dating needs plain language.

The first privacy guide explains what should stay private before meeting and why data minimization is part of the product.

Ready to inspect the privacy boundary itself?

The private beta preview keeps the first step narrow: local-only save, no live send, and a minimal-field review path before any real collection or provider setup is approved.

Privacy can also mean leaving systems off.

In this package, no-send and no-analytics posture are part of the trust design, not just missing implementation. That restraint helps keep intimate flows quieter until the business and privacy case is stronger.