Background Verification Under DPDP: What Employers Can Check, and How
TL;DR
Background verification collects some of the most sensitive data an employer handles: identity documents, education and employment history, addresses and sometimes criminal records. Under the DPDP Act, tell candidates exactly what will be checked and by whom, get their authorisation, check only what the role requires, handle Aadhaar carefully, contract your BGV vendor as a processor and delete verification data once it has served its purpose.
Who this is for: HR, talent acquisition and procurement teams that commission background verification (BGV), and the legal teams that approve it.
Background verification sits where recruitment, security and privacy meet. It protects employers from fraud and misrepresentation, but it also involves collecting identity documents, address proofs, education and employment records, references and sometimes criminal records, often through third-party vendors who contact universities, former employers and police.
Under the DPDP Act, BGV is lawful when it is transparent, proportionate and controlled. This guide covers how.
The lawful basis
Background checks generally rely on documents and information the candidate provides for the purpose of verification, together with their authorisation for the employer or its vendor to verify them with third parties. Checks connected to an offer of employment can also be seen as employment purposes under Section 7(i).
Whatever basis you rely on, two things make it hold up:
- a clear notice before the check, explaining what will be verified, which sources will be contacted, which vendor will do it and how long results are kept
- a specific written authorisation from the candidate, separate from the offer letter's other terms
Check only what the role requires
Proportionality is the core discipline. A blanket package of every available check for every role collects far more than most roles need.
| Check | Typical justification |
| Identity | All roles |
| Education | Where qualifications are a role requirement |
| Previous employment | Most roles |
| Address | Where relevant to the role or legal requirements |
| Criminal records | Roles involving cash, vulnerable people, security, sensitive data, or where a law or regulator requires it |
| Credit checks | Generally only for financial roles where a regulator expects it |
| Social media screening | Rarely justifiable; high risk of collecting irrelevant data |
| Drug or health tests | Only where safety-critical or legally required |
Define a check matrix by role level and function, and apply it consistently.
Handling Aadhaar and identity documents
Aadhaar raises additional legal restrictions under the Aadhaar Act. In practice:
- prefer masked Aadhaar (showing only the last four digits) or offline verification methods
- do not collect or store full Aadhaar numbers unless a law permits it
- do not photocopy identity documents into general HR folders
- restrict access to identity documents and delete copies once verification is complete
Criminal record checks
Criminal record information can seriously affect a person's prospects. Limit criminal checks to roles where they are justified, tell the candidate in advance, keep results in a restricted file, and give the candidate an opportunity to explain an adverse finding before you withdraw an offer.
Your BGV vendor is your processor
The BGV vendor collects data on your behalf, so it is your Data Processor. Under Section 8(1), you remain responsible for what it does. Your data processing agreement should require:
- processing only for the checks you order
- Rule 6 security safeguards, especially for identity documents
- breach notification to you within a short window
- no use of candidate data for the vendor's own databases or products
- deletion of documents and reports after a fixed period
- disclosure of any sub-contractors, such as field verification agents
Retention
Keep the verification outcome, and any records needed for employment or legal reasons, for as long as they are required. Delete supporting documents, detailed reports and unsuccessful candidates' verification data once the purpose is served (Section 8(7)). See HR records retention.
Checklist
Checklist
- Role-based check matrix approved by HR and legal
- Candidate notice explaining checks, sources, vendor and retention
- Separate written authorisation for verification
- Masked or offline Aadhaar verification
- Restricted storage for identity documents and criminal records
- DPA with the BGV vendor covering safeguards, breaches and deletion
- Process for candidates to respond to adverse findings
- Fixed retention and deletion of supporting documents
How ConsentifyAI helps
ConsentifyAI records the notice and authorisation each candidate gives for verification, links the BGV vendor and its contract to the processing activity in your ROPA, and applies retention rules so verification documents are deleted on schedule.
Sources & references
- DPDP Act, 2023 — Section 5, 6, 7(a), 7(i)
- DPDP Act, 2023 — Section 8(1), 8(2), 8(5), 8(7)
- DPDP Rules, 2025 — Rule 6
- Other — Aadhaar (Targeted Delivery of Financial and Other Subsidies, Benefits and Services) Act, 2016
Frequently asked questions
Do we need candidate consent for background verification?
Background checks typically rely on information and documents the candidate provides and authorises for verification. Get clear written authorisation, preceded by a notice explaining what will be checked, by whom and why.
Can we run criminal record checks?
Only where the role justifies it. Limit checks to what is relevant, tell the candidate, and restrict access to results.
Can we collect Aadhaar for background verification?
Be careful. Prefer masked Aadhaar or offline verification methods, and do not store full Aadhaar numbers unless a law permits it.
Is our BGV vendor responsible under DPDP?
The employer remains responsible as Data Fiduciary (Section 8(1)). The vendor acts as a processor and must be bound by a valid contract with Rule 6 safeguards.
How long should we keep background check reports?
Keep the outcome and essential records for as long as employment and legal requirements need, and delete supporting documents and detailed reports once their purpose is served.
Related reading
Recruitment Under DPDP: Handling Candidate Data From Application to Talent Pool
Candidates are Data Principals too. CVs and assessments submitted for a role can be processed for that recruitment, but keeping them in a talent pool for future roles, sourcing profiles from portals and running AI screening each raise separate questions. Give candidates a clear notice, get consent for talent pools, check vendors and AI tools, and erase unsuccessful candidates' data on a fixed schedule.
ReadData Processing Agreement in India: 10 Clauses You Can't Skip
Under Section 8(2) of the DPDP Act, a Data Fiduciary may engage a processor only under a valid contract, and Rule 6 requires that contract to include security safeguards. Because the fiduciary stays liable for its processors, the contract is where you make vendors meet your obligations. A DPDP-ready data processing agreement covers instructions, security, breach notification, rights support, sub-processors, transfers, deletion, audit, regulatory cooperation and liability.
ReadDPDP for HR Leaders: What You Own and What to Do First
HR holds more personal data than almost any other function: candidates, employees, contractors, interns and former staff, much of it sensitive. Under the DPDP Act, most employment processing can rely on the Section 7(i) legitimate use rather than consent, but notices, security, vendors, retention limits and breach reporting all still apply. HR leaders should map their data, separate employment needs from extras, tighten vendor contracts and set retention schedules before 13 May 2027.
Read