"Mandatory disclosure of caste in private admissions and employment perpetuates the very discrimination the Constitution seeks to end." Critically examine in light of recent judicial directions.

The Constitution bars caste discrimination (Arts. 15, 16(2)) and abolishes untouchability (Art. 17). Yet many private application forms still ask for caste. In October 2026, the Madurai Bench of the Madras High Court ruled that private educational institutions and employers in Tamil Nadu cannot mandatorily collect caste details unless a statute requires it [1]. The statement largely holds, but caste data is not discriminatory in itself.

How mandatory disclosure perpetuates discrimination

• Screening-stage bias: caste revealed at the first stage of selection lets prejudice shape shortlisting [1].
• No lawful purpose: private employment has no statutory reservation, so compulsory collection serves no legal need.
• Privacy and dignity: Puttaswamy (2017) placed privacy under Art. 21. Forcing people to disclose a stigmatised identity denies them informational self-determination.
• Data-protection mismatch: the DPDP framework requires purpose limitation, data minimisation and specific, withdrawable consent [2][3]. A compulsory caste box fails these tests.
• International commitment: ILO Convention 111, which India has ratified, prohibits employment distinctions based on "social origin" [4].

Why the statement is overstated

• Data serves social justice: reservation, scholarships and diversity monitoring depend on caste data. That is why the court kept an exception for statute-backed collection [1].
• Uncounted exclusion stays invisible: without data, exclusion of Dalit and Adivasi applicants from private hiring cannot be measured.
• Narrow remedy: surnames and native villages still signal caste. The order covers only forms, only Tamil Nadu and only mandatory fields [1]. An "optional" box may still be filled out of fear.
• Enforcement gap: the PIL was disposed of without naming any enforcing authority [1]. DPDP duties phase in over 18 months from November 2025 [2].

Way forward

• A Tamil Nadu model application form listing the statutes that genuinely require caste data.
• A firewall: collect caste data after selection, or keep it hidden from shortlisting panels [2].
• Data Protection Board guidance treating caste as high-risk personal data [3].
• A central law against caste bias in private hiring, fulfilling C111's national-policy obligation [4].

Mandatory caste disclosure without a lawful purpose turns identity into a filter, so it does risk perpetuating discrimination. The answer is not to stop counting caste but to separate caste data from the selection decision. Collection should rest on law, be limited to its purpose and be shielded from decision-makers. That balances substantive equality with privacy and fraternity, as the Preamble envisions.