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
Section 6 β Consent & Notice π΄
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
| Category | Risk Level | Potential Impact |
|---|---|---|
| Sensitive data concentration | Critical | Highest density of sensitive data of any platform |
| Family member consent | Critical | Third-party data submitted without their consent |
| Caste/religion data | Critical | Explicitly protected categories |
| Post-marriage data retention | High | Sensitive profile retained indefinitely |
| Data deletion integrity | High | Are photos and sensitive data truly purged? |
The Sensitive Data Concentration Problem
No other platform collects ALL of these about a single person:
| Data Category | DPDP Sensitivity | Matrimony Platform Practice |
|---|---|---|
| Religion | High | Required field |
| Caste/sub-caste | Very High | Required field |
| Income | High | Required field |
| Disability | Very High | Optional but encouraged |
| Diet (veg/non-veg) | High (religious indicator) | Required field |
| Complexion | High (discrimination risk) | Common field |
| Family background | High | Detailed β parents, siblings |
| Horoscope | High (belief system) | Common field |
This creates the single richest sensitive data profile of any Indian digital platform.
Recommendations
- Implement family member consent β Before publishing parentsβ/siblingsβ data, require their verification or consent
- Create post-marriage data policy β βUpon marking βmarriedβ: profile data anonymized within 30 days; photos deleted within 7 days; sensitive categories purged immediatelyβ
- Add sensitive data protections β Caste, religion, and disability data should have enhanced encryption and access controls
- Build match data transparency β Show users exactly what data was shared with each match/family
- Deploy progressive disclosure β Donβt share full sensitive profile upfront; reveal data progressively as match interest increases
- Implement deletion verification β Allow users to confirm that their photos and sensitive data are truly purged