Private data needs plain rules.

Security by constraint

• The server decides access, eligibility, and every match deadline.
• Every write request carries an idempotency key so retries cannot duplicate an action.
• Access checks follow relationships, never email addresses or other changeable fields.
• Logs must exclude messages, review answers, tokens, and direct personal data.
• Alerts cover service errors, scheduled jobs, and failed operator notifications.

Protect the most sensitive data first.

Chat, relationship records, safety reports, and verification references require encryption in transit and at rest. One Match must not store government ID images, selfies, or biometric templates.

Photos pass through validation, metadata removal, moderation, and access checks before release.

Account controls

Phone codes use send limits. Sessions expire and refresh. Signing out invalidates the device session. A verified document anchor, rather than an email or phone number, prevents duplicate identities and ban evasion.

Moderation and operator actions require named accounts and an audit record.

Report a security issue

Email hello@onematch.club with “Security report” in the subject. Include the affected page or feature, steps to reproduce, impact, and a safe proof.