Privacy and deletion rules.
This is the current product baseline for public registration. It is not legal advice for every country.
What is collected
- Account and matching information: a self-declared legal name, email account, password, age, region, language, marital eligibility, relationship goal, education, income band, self-introduction, and optional notes.
- A recent profile photo is stored as part of the closed member record. It is not a government document and does not mean official identity or face verification.
- The service does not currently connect a face-video, selfie-liveness, government-identity, or biometric provider.
Where it is stored
After production configuration is completed, profile and matching records will be stored by the CloudBase function in its configured PostgreSQL database. The profile photo is encrypted with AES-GCM before being written to the private private_evidence table. At the time of this report, the public health check says the database configuration is not complete, so a valid registration cannot yet be saved. The site has no public member directory and does not display member counts or personal records.
Your controls
- After login, you can view and edit your own text profile.
- In the member center, click “Delete my member record” to remove the account, profile, photo, matching conditions, invitations, connections, in-platform messages, and sessions.
- Deletion cannot be undone. Do not send identity documents, phone numbers, passwords, or other sensitive data by email.
Future verification boundary
Any future identity or anti-fraud provider must be reviewed separately and activated only after provider onboarding, subject checks, data-processing terms, a separate page and notice, separate active consent, signed callback verification, deletion and withdrawal handling, and cross-border processing review. No verification badge is issued before that.
Important notice
This page describes the current technical baseline. Before operation in a specific country, the responsible operator must confirm the data controller, lawful basis, retention period, user-rights process, cross-border arrangements, and provider contracts.