Privacy

Privacy-first by design — clear defaults and strong boundaries.

What we collect

The essentials required to run a matrimonial introductions product (account, profile, preferences, and messaging).

  • Account + authentication details
  • Profile fields you choose to provide
  • Messages within your conversations

How access is protected

Data access is enforced via database policies and application rules.

  • Supabase RLS for read/write boundaries
  • Auth + onboarding enforcement before app access
  • Rate limiting on sensitive actions

Messaging & deletion

Messaging is one-to-one and designed to be fast without polling. Message deletion is privacy-first.

  • Realtime messaging uses broadcast channels
  • Deleted messages are treated as deleted in UI + inbox

Questions or requests

If you have a privacy question or request, contact us and we’ll help.

Note: This page is a product-facing summary. If you want a full legal policy document (jurisdiction-specific), tell me the target country and I’ll generate the long-form version.

Ready to create your profile?

Build your profile once, then see compatibility-ranked introductions.