Privacy Policy

1. Information we may collect

Account information: display name, email address, password hash (for email registration), email-verification status and account activity. With Google Sign-In, identity information supplied through Google's authorized flow may include a Google account identifier, email and display name; MarryMe3000 does not need your Google password.

Matrimonial profile: optional photograph; approximate age derived from private birth year; country, region, religion, community, education, profession, marital status, family and children preferences, relationship goals, personal description and partner criteria you choose to provide.

Private matchmaking information: preference weights, deal-breakers, relocation expectations, values and optional feedback shared with the AI matchmaker.

Service information: login, verification, security, moderation and interaction records needed to provide and protect the service. If paid features are later introduced, additional transaction records may be necessary.

2. What other people can see

Published profile fields and a chosen profile photo may be visible to people browsing MarryMe3000. Individual profiles are planned not to be indexed by search engines at launch, but a technical policy still needs implementation and testing; do not assume publicly visible information is inaccessible to search engines or other visitors.

Birth year, account email, phone number, private AI preferences and exact address are not intended to appear on a public profile. Free-tier descriptions are designed to remove contact details, although no detection method is perfect. Contact reveal will be off by default and require a deliberate choice if introduced.

Some data, including religious beliefs and family circumstances, can be sensitive. You decide whether to provide optional sensitive profile fields and which information to submit for publication. The appropriate consent workflow and controls must be finalized before launch.

3. Why information is used

The planned purposes include creating and securing accounts, confirming email addresses, enabling profile publication and search, helping members express or respond to interest, moderating misuse, responding to support requests and providing optional AI-assisted profile and match analysis.

AI recommendations should be based on information supplied for matching and should explain uncertainty; they must not be treated as guarantees of outcomes. Marketing messages, if ever offered, should use separate choices where required.

4. Service providers and other members

Some information is shared with other visitors through published profiles or through introductions you explicitly permit. Operating the service may involve hosting, database, email delivery, Google authentication and AI providers. The final policy must name or categorize the actual providers, what they receive, where they process data and what protections govern any transfers outside Mauritius or your country.

MarryMe3000 should not sell private matchmaker preferences or disclose them to other members. AI processing of sensitive details should be limited to what is needed for the action requested. Specific provider retention and training settings must be verified before these features are activated.

5. Your choices and rights

The product is intended to let you edit or pause your profile, control optional fields, express or withdraw consent where applicable, and request account deletion. Access, correction, objection and other data protection rights depend on applicable law and your circumstances. Details about data export, deletion procedures and response timeframes will be finalized before launch.

Withdrawing a profile from public view may not immediately remove copies others saved or information indexed elsewhere. We will explain any retention obligations or necessary exceptions in the finalized policy.

6. Security, cookies and retention

The platform architecture includes hashed passwords, secure session cookies, restricted credential storage, server-side validation, rate limiting and moderated profile publication. Controls must be tested in the deployed application; no internet service can promise absolute security.

Essential cookies support account sessions and security. Analytics, optional cookies and push notifications, if introduced, require separate disclosures and controls where applicable. Personal information should be retained only as long as necessary for defined purposes or legal obligations; exact schedules remain to be established.

7. Responsible operator and privacy contact

Katalume is the proposed Mauritius operator, pending formal registration. The registered name, BRN, address, privacy contact and finalized governing terms remain to be confirmed. The responsible legal entity, postal location, privacy email contact, complaints procedure and finalized effective date are pending confirmation. These must be published before MarryMe3000 accepts public registrations. Mauritius data protection obligations, and rules in other markets served, require review.