Archived analysis

This page is old. Matrimony.com was reviewed on 2026-02-18.

This is a historical, policy-only review. Policies, product behavior and source URLs may have changed since this analysis was published.

For current public evidence from website trackers, policy findings and proof samples, go to State of Privacy 2026.

Matrimony

Matrimony.com

Ready Score 41/100
Sushant Pasumarty
ANALYSIS SUPERVISED BY Sushant Pasumarty
πŸ“… 18 Feb 2026

Discuss this page with an LLM

Matrimony.com collects India's most sensitive personal data categories: caste, religion, income, family background, physical appearance, horoscope details, and disability status. At 41/100, the platform processes data that reveals every protected characteristic under DPDP β€” creating the highest concentration of sensitive data of any platform analyzed.

How To Read This Analysis

This is an archived policy-only review of the company's public privacy policy. It is not a government certification and it is not legal advice.

For current public evidence from website trackers, policy findings and proof samples, see State of Privacy 2026.

We look for:

  • Notice and consent clarity
  • Purpose limitation
  • Data minimization
  • Retention and deletion language
  • Vendor and processor disclosures
  • Data Principal rights
  • Grievance redressal
  • Breach and security posture

Source Check

  • Source policy was reviewed for this archived analysis, but the old policy URL is not linked because public policy locations may have changed.
  • Date reviewed: 2026-02-18
  • Company: Matrimony.com
  • Readiness score: 41/100
  • Policies and product behavior may have changed since review
  • Whether the current source policy still matches this archived policy-only review
  • Whether app, web and product flows match the policy

What To Do With This

If your company has a similar data model, use this analysis as a warning map. Do not copy the score. Map your own data flow.

Ask internally:

  • Do we collect similar categories of personal data?
  • Do we share data with the same number or type of vendors?
  • Can users understand why their data is shared?
  • Can we prove deletion, retention and grievance workflows?
  • What evidence would we show if questioned?

If this analysis resembles your business model, the next step is not a better privacy-policy paragraph. It is a data map and gap analysis.

Book a DPDP readiness call

⚠️ Compliance Gaps

  • No DPDP Act 2023 reference
  • Caste, religion, income, and family background data = most sensitive data
  • Profile photos and biodata shared with potential matches without granular consent
  • Family member data (parents' occupation, siblings) collected without their consent
  • No data retention timelines for profiles post-marriage or deletion
  • Data Protection Board not referenced
  • Third-party matchmaker access to profile data uncontrolled

βœ… Strengths

  • Identity verification for profiles mentioned
  • Security measures described
  • Grievance officer designated
  • Profile visibility controls available

Overview

Matrimony.com (BharatMatrimony, EliteMatrimony, etc.) is India’s largest matchmaking platform. Users create detailed profiles containing virtually every category of sensitive personal data: religion, caste, sub-caste, income, physical appearance, disability status, dietary habits, family background, property ownership, and horoscope details. No other platform collects such comprehensive sensitive personal data.

DPDP Readiness: Section-by-Section Analysis

Matrimony profiles contain:

  • Religion and caste (protected category)
  • Income and property details (financial data)
  • Physical description (height, weight, complexion)
  • Disability status (health data)
  • Dietary habits (cultural/religious indicator)
  • Family details (parents’ occupation, siblings’ data β€” collected without THEIR consent)
  • Horoscope/astrology data (religious/cultural beliefs)

Critical DPDP issue: Family members’ personal data (parents’ names, occupations, siblings’ details) is submitted by the profile creator without any consent from those family members. Under DPDP, each data principal must consent β€” Matrimony.com has NO mechanism for this.

Section 7 β€” Certain Legitimate Uses πŸ”΄

Matchmaking requires sensitive data. But:

  • Profile data used for advertising analytics β€” overreach
  • Behavioral data (who you viewed, rejected, accepted) β€” beyond matchmaking
  • Payment pattern data β€” income indicator beyond stated income

Section 9 β€” Data Retention πŸ”΄

Critical concern: What happens to your profile after marriage?

  • Does Matrimony.com retain your caste, income, and family data after you mark β€œmarried”?
  • Deleted profiles β€” are they truly purged including all sensitive categories?
  • Photos β€” where are they stored after profile deletion?
  • Behavioral data (viewing and rejection patterns) β€” retained for analytics?

Section 11 β€” Rights of Data Principal πŸ”΄

  • Can family members (whose data was submitted) request deletion?
  • Can users selectively delete sensitive categories while keeping the profile?
  • No data portability
  • No nomination rights
  • Profile photos β€” are they used for other purposes after deletion?

Section 12 β€” Right of Grievance Redressal ⚠️

Grievance officer exists. No DPB pathway. No mechanism for complaints about data shared with potential matches’ families.

Risk Assessment

CategoryRisk LevelPotential Impact
Sensitive data concentrationCriticalHighest density of sensitive data of any platform
Family member consentCriticalThird-party data submitted without their consent
Caste/religion dataCriticalExplicitly protected categories
Post-marriage data retentionHighSensitive profile retained indefinitely
Data deletion integrityHighAre photos and sensitive data truly purged?

The Sensitive Data Concentration Problem

No other platform collects ALL of these about a single person:

Data CategoryDPDP SensitivityMatrimony Platform Practice
ReligionHighRequired field
Caste/sub-casteVery HighRequired field
IncomeHighRequired field
DisabilityVery HighOptional but encouraged
Diet (veg/non-veg)High (religious indicator)Required field
ComplexionHigh (discrimination risk)Common field
Family backgroundHighDetailed β€” parents, siblings
HoroscopeHigh (belief system)Common field

This creates the single richest sensitive data profile of any Indian digital platform.

Recommendations

  1. Implement family member consent β€” Before publishing parents’/siblings’ data, require their verification or consent
  2. Create post-marriage data policy β€” β€œUpon marking β€˜married’: profile data anonymized within 30 days; photos deleted within 7 days; sensitive categories purged immediately”
  3. Add sensitive data protections β€” Caste, religion, and disability data should have enhanced encryption and access controls
  4. Build match data transparency β€” Show users exactly what data was shared with each match/family
  5. Deploy progressive disclosure β€” Don’t share full sensitive profile upfront; reveal data progressively as match interest increases
  6. Implement deletion verification β€” Allow users to confirm that their photos and sensitive data are truly purged

Fix these compliance gaps today.

Book 1:1 Consultation >
Book clarity call