DPDP for Background Verification Firms
BGV firms process identity documents and criminal records. Learn how to manage employee vetting data under India's DPDP Act.
Discuss this page with an LLM
DPDP Action Sheet
Use this before your next workflow goes live. It keeps the useful parts visible and turns DPDP into checks your team can actually answer.
For DPDP for Background Verification Firms, the DPDP question is how personal data enters the workflow, where it is stored, which tools touch it, what purpose was explained, and how deletion or withdrawal will work.
1. Lead Forms
Check:
- What data are you collecting?
- Is the purpose clear at the point of collection?
- Is marketing consent separate from service communication?
- Can the user withdraw consent later?
Common mistake: one checkbox that silently covers newsletters, sales calls, partner sharing and remarketing.
2. Email and WhatsApp
Check:
- Who is on the list?
- Where did consent come from?
- Is the list imported from a vendor, event, webinar, scrape or old CRM?
- Can you prove the source of consent?
Common mistake: treating every lead as permanently marketable.
3. Ads and Retargeting
Check:
- Are pixels or ad platforms receiving identifiable user behavior?
- Are audiences built from customer lists?
- Are lookalike or remarketing audiences using personal data?
Common mistake: assuming "the ad platform handles it" means your company has no DPDP responsibility.
4. Website Analytics
Check:
- Which tools run on the site?
- Are IP address, device identifiers, session IDs or form fields being captured?
- Is analytics used only for measurement, or also for profiling and targeting?
Common mistake: installing tools first and asking privacy questions later.
5. Vendor List
Make a quick list:
- CRM
- Email platform
- WhatsApp provider
- Analytics
- Ad pixels
- Form tool
- Landing page builder
- Webinar tool
For each vendor, answer: what data goes there, why, who can access it and how deletion works.
6. This Week's Action
Map one campaign from first click to final follow-up. Mark every place personal data is collected, enriched, shared, uploaded or used for targeting.
If your team cannot answer where the data came from and where it goes next, start with a data flow map before rewriting policy copy.
Book a DPDP clarity callWant all of this handled, end to end? Sanctum is the all-in-one DPDP compliance programme behind this site: legal position, data map, gap analysis, implementation, tooling, training, readiness opinion, and breach cover under one accountable owner. How all-in-one DPDP compliance works or see the Sanctum programme.
Processing Identity and Criminal Data
Background verification firms handle identity documents, employment history, and criminal records. This data comes from candidates and third-party sources like universities and courts. You must verify that every piece of data collected is necessary for the specific job role. Collecting a marriage certificate for a technical role might exceed the purpose of the check. Under DPDP, you must provide a notice that lists every specific document you intend to verify before you start the process.
The Challenge of Data Retention
Most firms keep candidate folders for years to handle future disputes or to reuse data if the candidate applies for a different job. DPDP requires you to delete data once the purpose is fulfilled. Once the final report is sent to the employer and the dispute window closes, you must scrub the identity documents and salary slips from your servers. You cannot keep master databases of candidate documents without a new legal basis.
Managing Verification Workflows
| Verification Area | Personal Data Involved | DPDP Risk Level |
|---|---|---|
| Identity Check | Aadhaar, PAN, Passport scans | Very High |
| Criminal Check | Court records, police station logs | High |
| Financial Check | Salary slips, bank statements | High |
| Education Check | Marks sheets, degree certificates | Medium |
| Reference Check | Peer feedback, manager comments | Medium |
This week
Audit your candidate authorization letter. Replace generic phrases like “sharing with third parties” with a clear list of categories, such as “educational institutions,” “previous employers,” and “criminal database vendors.” Ensure this notice is presented to the candidate before they upload any documents.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Can we keep candidate data for future verification?
No. Under DPDP, you must delete personal data once the specific purpose—the background report—is completed. You cannot store data indefinitely to save costs on future checks.
Is an employer's consent form enough for us to start?
No. The BGV firm must ensure the candidate received a notice explaining exactly what data is collected and who it is shared with. You cannot rely on a generic 'all-purpose' signature.
What happens if a candidate asks to see their report?
Candidates have the right to access a summary of the personal data you have processed about them. You must provide this information if they make a formal request.