When do the DPDP Act's duties start for recruiters?
The DPDP Act's duties for recruiters, including notice, consent, security, retention, candidates' rights and penalties, start on or about 13 May 2027. That is 18 months after the commencement notification and the DPDP Rules were both published in the Gazette on 13 Nov 2025. The notice you design now is what candidates will read then.
Consent Managers have been live since 13 Nov 2026. The recruiter's duties start on or about 13 May 2027.
- The DPDP Act is enactedAct No. 22 of 2023. Published, with no date set for its duties.
- The Rules are notifiedDefinitions and the Data Protection Board start.
- Consent ManagersRegistered Consent Managers can operate; in effect since this date.
- The recruiter's duties startNotice, consent, security, retention, candidates' rights and penalties.
- The DPDP Act is enactedAct No. 22 of 2023. Published, with no date set for its duties.
- The Rules are notifiedDefinitions and the Data Protection Board start.
- Consent ManagersRegistered Consent Managers can operate; in effect since this date.
- The recruiter's duties startNotice, consent, security, retention, candidates' rights and penalties.
Show the data
| Date | What starts | Detail |
|---|---|---|
| 11 Aug 2023 | The DPDP Act is enacted | Act No. 22 of 2023. Published, with no date set for its duties. |
| 13 Nov 2025 | The Rules are notified | Definitions and the Data Protection Board start. |
| 13 Nov 2026 | Consent Managers | Registered Consent Managers can operate; in effect since this date. |
| About 13 May 2027 | The recruiter's duties start | Notice, consent, security, retention, candidates' rights and penalties. |
The dates come from two gazette notices of 13 Nov 2025. The commencement notification, G.S.R. 843(E), sets them for the Act. Rule 1 of the DPDP Rules 2025, G.S.R. 846(E), sets them for the Rules. The gazette is dated 13 Nov 2025 but was digitally signed on 14 Nov, so the exact day can be argued either way. This guide says "on or about".
The parts of the DPDP Act 2023 in force since 13 Nov 2025 that matter to an agency are the definitions (s.2) and the Data Protection Board (s.18 to s.26). Consent Managers, registered platforms through which a person can give and withdraw consent (s.6(9), r.4), have been live since 13 Nov 2026. The Act's duties (s.3 to s.17) commence on or about 13 May 2027 (G.S.R. 843(E)); until then the DPDP Act sets an agency no notice duty, no consent standard and no penalty. Other law binds an agency today. The IT Act's section 72A makes it an offence to disclose personal information obtained under a lawful contract without consent, and section 43A and the SPDI Rules 2011 apply where the data is sensitive personal data.
Candidates already in your database matter on the day the duties start. For anyone who gave consent before then, the fiduciary must send a notice of what it holds and why "as soon as it is reasonably practicable", and may keep processing until the candidate withdraws (s.5(2)). The checklist below carries this as an action.
The Takshashila Institution reported on 26 Jan 2026 that MeitY had consulted large technology firms on shortening the timelines for some rules, pending approval. We found no notification changing the dates as of 11 Nov 2026.
Who is the Data Fiduciary when an agency screens for a client?
Under the DPDP Act, a recruitment agency is most likely the Data Fiduciary for candidates' data, and its screening tool most likely a Data Processor. The Act defines both roles by what a party does (s.2(i), s.2(k)) and never mentions agencies. Confirm your roles, and your clients', with counsel.
| Party | Most likely role | Why | What follows |
|---|---|---|---|
| Your agency | Data Fiduciary | Decides whom to source, screen and interview, and what each client sees (s.2(i)) | Carries the duties, and stays responsible for its processors' work (s.8(1)) |
| Your screening tool or ATS | Data Processor | Processes candidates' data on your behalf (s.2(k)) | Needs a valid contract with security terms (s.8(2), r.6(1)(f)); stops and erases when you tell it to (s.6(6), s.8(7)(b)) |
| Your hiring client | A Data Fiduciary for what you send it | Decides what to do with the shortlist it receives | Whether you are joint fiduciaries depends on the facts and the contract (s.2(i), "in conjunction with"); ask counsel |
| The candidate | Data Principal (s.2(j)) | The person the data is about | Has the rights in s.11 to s.14 from on or about 13 May 2027 |
Source: DPDP Act 2023, s.2, s.6, s.8; DPDP Rules 2025, r.6 · this guide's reading, not a ruling · not legal advice
The agency is the likely fiduciary because it decides why and how the data is used: whom to source, whom to interview and whom to put forward. That fits a placement consultancy that keeps its own candidate database.
An RPO team working inside a client's own process may look more like the client's processor. The facts decide. A contract can't move the duties the Act puts on the fiduciary, which stays responsible "irrespective of any agreement to the contrary" (s.8(1)).
A candidate can ask the fiduciary for "the identities of all other Data Fiduciaries and Data Processors" their data was shared with (s.11(1)(b)). That list includes each client and each tool, so keep a record of what every client received.
The shortlist you send at the end of the candidate screening process for recruitment agencies is a disclosure to another fiduciary. Data disclosed that way must be complete, accurate and consistent (s.8(3)).
What to put in a processor contract
The Act lets a fiduciary use a processor only under a valid contract (s.8(2)), and the Rules ask that contract to cover reasonable security safeguards (r.6(1)(f)). Three more duties reach the tool through the agency, so they belong in the same contract:
- it stops processing a candidate's data when that candidate withdraws consent (s.6(6));
- it erases what you gave it when you erase (s.8(7)(b));
- it keeps the data and logs of its processing for at least a year, as you must. The Rules' own example is a company and its cloud host (r.8(3)).
The contract doesn't move the duty. If the tool fails, the agency is still the one responsible (s.8(1)).
What notice and consent do you need for CVs, AI interviews and recordings?
From on or about 13 May 2027, the DPDP Act requires a standalone, itemised notice to candidates: the data, each purpose, and how to withdraw or complain. The notice comes before or with any request for consent (s.5(1)), in the form Rule 3 sets. You choose the ground for each purpose: consent or a legitimate use.
Consent or a legitimate use
The Act allows processing on one of two grounds: the person's consent, or one of the "certain legitimate uses" listed in s.7 (s.4(1)).
A candidate who sends a CV for a role may fall under s.7(a): data a person gives voluntarily for a specified purpose, without saying they object. The Act's own example is a woman who messages a real estate broker to find a flat to rent. The broker may use her details for that, and must stop once she says she no longer needs help.
Recordings and AI evaluation go beyond what a candidate sent a CV for. This guide's reading is that explicit consent is the safer ground for them.
The employment legitimate use (s.7(i)) is written for employers and their employees. Whether it covers a candidate an agency screens for a client is not settled, so this guide doesn't rely on it.
Voice and video have no special category under the Act. They are personal data like any other.
What the notice must say
| Requirement | Where it comes from |
|---|---|
| Stands on its own, not buried in other terms | r.3(a) |
| An itemised list of the data you collect, in clear and plain language | r.3(b) |
| Each purpose, including AI evaluation and recordings | s.5(1)(i), r.3(b) |
| How to withdraw consent, as easily as it was given | s.5(1)(ii), s.6(4), r.3(c) |
| How to use their rights and raise a grievance | s.5(1)(ii), r.3(c) |
| How to complain to the Data Protection Board | s.5(1)(iii), r.3(c) |
| A link to your website or app | r.3(c) |
| A contact person who can answer questions (a Data Protection Officer only where one is required) | s.6(3), s.8(9), r.9 |
| Available in English or any Eighth Schedule language | s.5(3), s.6(3) |
Source: DPDP Act 2023 s.5, s.6, s.8(9); DPDP Rules 2025 r.3, r.9 · duties start on or about 13 May 2027 · not legal advice
What valid consent looks like
Consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action", and limited to the data the purpose needs (s.6(1)). In this guide's reading, a pre-ticked box or a line inside general terms doesn't meet that standard.
Because consent must be specific, name each purpose: an itemised list or a separate box for each makes plain what the candidate agreed to. Storing a recording, having AI evaluate it and sending a report to a client are different purposes.
If a candidate later disputes it, the fiduciary has to prove that notice was given and consent was given (s.6(10)). Record what each candidate saw, which version, and when.
When a candidate withdraws
A candidate can withdraw consent at any time, and withdrawing must be as easy as agreeing was (s.6(4)). Within a reasonable time, the agency stops processing and has its tools stop too (s.6(6)).
Withdrawal doesn't undo what came before. Processing done while consent stood stays lawful, and the candidate bears the consequences of withdrawing (s.6(5)). In this guide's reading, that can mean leaving a hiring process that is still under way.
A consent term that breaks the Act is invalid to that extent (s.6(2)). The Act's own example is a waiver of the right to complain to the Board: the rest of the consent stands, and the waiver doesn't.
Proctoring consent
From on or about 13 May 2027, an agency asking for consent to proctor must list what each check collects and why, in a notice before or with that request (s.5(1), r.3(b)). Consent covers only the data that purpose needs (s.6(1)), so the list should match the checks the interview actually runs. Which checks a role needs is your decision.
What to name before each proctoring check, in this guide's reading:
| Check | What the notice names | Purpose to state |
|---|---|---|
| Activity record | Leaving the interview page or switching tabs, and what is copied or pasted | Reviewing whether answers came from outside the interview |
| Screen recording | A recording of the whole screen while the candidate answers | Reviewing what else was on screen |
| Camera photos or recording | Photos of the candidate's face at intervals, or video and audio from the camera and microphone | Reviewing whether the same person answered throughout, alone |
| ID photo and selfie | A photo of an identity document and a live selfie, with the two faces compared | Comparing the face on the ID with the person taking the interview |
Source: DPDP Act 2023 s.5(1), s.6(1); DPDP Rules 2025 r.3(b) · this guide's reading · duties start on or about 13 May 2027 · not legal advice
Name only what you run. In this guide's reading, a list that names checks the interview doesn't use isn't specific, and a check missing from the list wasn't consented to. Turn on only the checks each role needs, and keep the list in step with them.
Ask before the check starts. Consent is a ground for processing only once the candidate has given it (s.4(1)). In this guide's reading, for proctoring that means before the camera, the screen share or the ID photo starts, not partway through the interview.
From on or about 13 May 2027, tracking or behavioural monitoring of anyone under 18 is barred (s.2(f), s.9(3)). In this guide's reading, the activity record and the camera checks are that kind of tracking. Confirm a candidate's age yourself when you invite or shortlist them, before the interview link goes out.
If a candidate withdraws partway through, the duties under "When a candidate withdraws" above apply: the agency must stop processing within a reasonable time, and have its tools stop too (s.6(4), s.6(6)). The record of consent (s.6(10)) should keep the version of the list each candidate saw.
Recagn is our product. Its DPDP position statement, quoted in full under How Recagn does this below and on the page about what candidates see and agree to, tells candidates two things before a proctored interview. Under what's collected:
- Only if the interview's consent screen lists them:
- a record of when you leave the interview page or switch tabs, and of what you copy or paste;
- a recording of your whole screen;
- photos from your camera, or a recording of your camera and microphone;
- a photo of your ID and a selfie, so the faces can be compared.
And under what they agree to:
- Before an interview: one screen lists everything this interview records, then two boxes: one to agree and start, and one to confirm you are 18 or older. If you are under 18, nothing is recorded and you are asked to contact the recruiter.
What each check records, and what it costs in credits, is on Recagn's AI proctoring page.
Recagn's rules read the activity record, the camera photos and the face match, never the screen or camera recordings, and a person decides what any finding means. The rules are set out in how interview integrity works.
Candidates you didn't collect yourself
CVs uploaded from email, job boards or your own sourcing never passed through your notice. For candidates who gave consent before the duties start, s.5(2) asks for a notice as soon as it is reasonably practicable.
The Act doesn't apply to data the person "made or caused to be made publicly available" (s.3(c)(ii)). Whether a job-board CV or a public profile counts is a question for counsel.
How long can recruiters keep resumes and interview recordings?
From on or about 13 May 2027, keep a CV or recording only while its purpose is served; the DPDP Act sets no fixed period. The test is s.8(7); the three-year periods in the Rules' Third Schedule cover only large e-commerce, gaming and social media platforms. You set the period for each purpose and write it in your notice.
Retention
Under s.8(7), the fiduciary erases a candidate's data when they withdraw consent, or as soon as it is reasonable to assume the purpose is no longer served, whichever comes first. It must also have its processors erase what it gave them (s.8(7)(b)). A law that requires keeping the data overrides this.
| Class of Data Fiduciary | Registered users in India | Period |
|---|---|---|
| E-commerce entity | at least 2 crore | 3 years |
| Online gaming intermediary | at least 50 lakh | 3 years |
| Social media intermediary | at least 2 crore | 3 years |
Source: DPDP Rules 2025, Third Schedule (r.8(1)) · recruiters and recruitment tools are not listed · not legal advice
Only these three classes get the 48-hour warning before erasure (r.8(2)). Recruiters and recruitment tools are not on the list.
The Act also lets a purpose be treated as ended after a period of silence: when the person neither comes back for the purpose nor uses their rights for a prescribed time (s.8(8)). Silence means the person started no contact, whether in person, electronically or on paper (s.8(11)).
The Rules prescribe that period only for the three classes above. So, in this guide's reading, no inactivity clock runs for a recruiter, and the s.8(7) test, whether it is reasonable to assume the purpose is over, is the one that applies.
Every fiduciary has a floor, though. Rule 8(3) says it keeps the personal data, traffic data and logs of each processing for at least one year from the processing, including processing a processor did for it, and then erases them.
The Rules don't say how this sits with a candidate's erasure request. One plain reading is to keep a minimal record of the processing for a year and stop using the data. That is a question for counsel.
Setting a retention period per purpose
A purpose such as "considered for this role" ends when the role closes and the client has decided. Write down a period for each purpose, and apply it to recordings and transcripts as well as CVs.
This guide recommends no number. The Act gives none for recruiters, and a figure borrowed from the Third Schedule would be a guess.
One law firm, King Stubb & Kasiva, reads the Act as requiring rejected candidates' CVs to be erased unless they gave explicit consent to be considered later (read 11 Nov 2026).
What does the DPDP Act say about AI interviews?
The DPDP Act does not ban AI interviews, and it has no provision on AI, profiling or automated decisions. From on or about 13 May 2027, an AI interview follows the same rules as other processing: notice, a valid ground, accuracy (s.8(3)) and security (s.8(5)). Whether a person makes every decision is yours to decide.
Legal
No Indian law bans AI interviews or webcam proctoring, and none regulates them specifically. Today the IT Act's section 72A makes it an offence to disclose personal information obtained under a lawful contract without consent, and section 43A and the SPDI Rules 2011 apply where data is sensitive personal data. On or about 13 May 2027 the DPDP Act's duties commence, section 43A is omitted and section 72A stays (G.S.R. 843(E); s.44(2)). The DPDP Act has no provision on AI or automated decisions; an AI interview meets its ordinary duties, among them notice, consent, accuracy (s.8(3)) and security (s.8(5)). What applies today, what changes, and where a face match sits under the SPDI Rules are in the guide to whether an AI interview is legal in India.
Who decides
"A person makes every decision" and "no AI rejection" are choices a tool or an agency makes. They are not DPDP rules. The reasons to make them are practical: the s.8(3) accuracy duty, and what your client expects when it reads a shortlist.
The score is a recommendation. Whoever moves a candidate on, or doesn't, is the one deciding. How an AI interview is scored, and where the recruiter's decision comes in, is set out in the guide to AI interviews.
What should a DPDP compliance checklist for recruitment agencies cover?
A DPDP compliance checklist for a recruitment agency covers six areas: roles, notice and consent, retention and erasure, accuracy and AI, security and breach, and candidates' rights. Each item names the section or rule it comes from, to check against the gazette or with counsel. It works with any screening tool, and the download is an editable Word document.
Roles
- Write down who the Data Fiduciary is for each client's roles: usually your agency (s.2(i)).
- List every tool that holds candidate data, and sign a contract with each that covers security (s.8(2), r.6(1)(f)).
- Record what each client received, and when (s.11(1)(b)).
Notice and consent
- Give a standalone notice, before or with the request for consent (s.5(1), r.3(a)).
- Itemise the data and each purpose, naming AI evaluation and recordings (s.5(1)(i), r.3(b)).
- Say how to withdraw, use rights and complain to the Board (s.5(1), r.3(c)).
- Publish a contact person (s.8(9), r.9), and offer the notice in English or an Eighth Schedule language (s.5(3)).
- Record each consent with the wording the candidate saw (s.6(10)).
- Send a notice to candidates already in your database (s.5(2)).
- Get a parent's verifiable consent for anyone under 18 (s.9(1), r.10).
Retention and erasure
- Set a retention period for each purpose (s.8(7)).
- Erase when consent is withdrawn or the purpose ends, and have your tools erase too (s.6(6), s.8(7)(b)).
- Keep processing logs for at least one year (r.8(3)).
- Ask counsel how the one-year logs sit with erasure requests.
Accuracy and AI
- Check data before it informs a decision or goes to a client (s.8(3)).
- Write down who decides. The Act doesn't require a person to; that choice is yours.
Security and breach
- Put in place the minimum safeguards in r.6(1): encryption or masking, access control, access logs, backups, one-year log retention, security terms in processor contracts, and technical and organisational measures.
- On a breach, tell each affected candidate and the Board without delay, then send the Board a detailed report within 72 hours of becoming aware (r.7).
- Make sure your tools' contracts require them to tell you about a breach in time for that.
Candidates' rights
- Handle requests for access, correction and erasure (s.11, s.12).
- Correct, complete or update a candidate's data when asked (s.12(2)).
- Run a grievance process, and answer within the period you publish, at most 90 days (s.13, r.14(3)). Candidates must use it before they go to the Board (s.13(3)), so it has to exist and work (s.8(10)).
- Publish how a candidate makes a request (r.14(1)), and put your contact person's details in every reply to one (r.9).
- Let candidates nominate someone to act for them (s.14).
Questions to ask your screening tool
These work with any vendor.
- Will you sign processor terms covering security, stopping and erasing on our instruction, and one-year log retention (s.8(2), r.6(1)(f), r.8(3))?
- Can we export what you hold on one candidate, for an access request (s.11)?
- Can we erase a candidate completely, including one already in a pipeline?
- Is the consent wording versioned, with what each candidate saw recorded (s.6(10))?
- Can the notice name our agency as the one collecting the data?
- How fast will you tell us about a breach, so we can tell the Board within 72 hours (r.7(2))?
- Can candidates read the notice in a language other than English (s.5(3))?
Penalties
The Board sets a penalty only after an inquiry and a hearing (s.33(1)). It weighs the nature, seriousness and length of the breach, the type of data affected, whether the breach repeated, and any gain made or loss avoided. It also weighs what was done to limit the harm and how quickly, whether the penalty is proportionate, and its likely impact on the one who pays it (s.33(2)).
| Breach | Up to |
|---|---|
| Failing to take reasonable security safeguards (s.8(5)) | 250 crore rupees |
| Failing to notify a breach (s.8(6)) | 200 crore rupees |
| The additional duties for children's data (s.9) | 200 crore rupees |
| Any other provision of the Act or Rules | 50 crore rupees |
Source: DPDP Act 2023, Schedule · maximums, not typical amounts · in force from on or about 13 May 2027
Candidates have duties too, with a maximum penalty of 10,000 rupees (s.15): not to impersonate someone else, and not to file a false or frivolous complaint. The duty not to suppress material information covers only documents and identity proofs issued by the State (s.15(c)). In this guide's reading, it doesn't reach a CV that overstates experience.
What does the DPDP Act leave unsettled for recruiters?
The DPDP Act's text leaves four recruiter questions unsettled: joint responsibility with clients, the employment ground, public profiles, and erasure against the one-year log rule. This guide is a non-lawyer's reading of the official text, checked on 11 Nov 2026, and it is not legal advice. Take these four to counsel before you rely on an answer.
- Whether an agency and its client are joint fiduciaries, since a fiduciary can act "in conjunction with other persons" (s.2(i)).
- Whether the employment legitimate use (s.7(i)) covers a candidate an agency screens.
- Whether a job-board CV or a public profile is data "made publicly available" by the person (s.3(c)(ii)).
- How the one-year minimum in r.8(3) sits with an erasure request (s.12(3)) and with s.8(7).
This guide covers only the DPDP Act and Rules, not other laws that may bear on hiring. The law was last checked on 11 Nov 2026, and amendments after that date are not reflected. The section on Recagn was last checked on 15 Nov 2026.
How Recagn does this
Recagn is our product. It is a screening tool an agency uses inside its own workspace, so under this guide's reading it is the agency's processor. This section goes through the checklist. It says what Recagn does today and what it doesn't do yet, checked against Recagn's DPDP position statement on 15 Nov 2026.
What your candidates are told
The statement below is what your candidates read on Recagn's page about what candidates see and agree to. It speaks to the candidate as "you", and it is quoted here word for word.
1. What's collected.
- When you apply: your résumé and the details you enter.
- When you interview:
- your answers, as text, voice or video;
- transcripts of voice and video;
- any documents you upload;
- the AI's evaluation of your answers and its authenticity checks.
- Only if the interview's consent screen lists them:
- a record of when you leave the interview page or switch tabs, and of what you copy or paste;
- a recording of your whole screen;
- photos from your camera, or a recording of your camera and microphone;
- a photo of your ID and a selfie, so the faces can be compared.
2. Who sees it.
- The recruiters at the agency that invited you see it, inside that agency's own workspace.
- Each agency's data is kept separate from every other agency's.
- A hiring client sees only the report the agency chooses to share. That report's link expires after 30 days by default, and the agency can revoke it at any time.
- Screen and camera recordings, camera photos, your ID photo and selfie, the activity record and what Recagn's rules found in them are never in that report. The hiring client doesn't see them.
3. Who's responsible.
- The agency decides why your data is used, and it is responsible for it. Under India's DPDP Act it is most likely the Data Fiduciary.
- Recagn is the tool that processes your data for the agency.
- Recagn uses Amazon Web Services (AWS), in its Mumbai region, to read your ID photo and to find and compare faces in your selfie and camera photos.
4. What you agree to.
- Before an interview: one screen lists everything this interview records, then two boxes: one to agree and start, and one to confirm you are 18 or older. If you are under 18, nothing is recorded and you are asked to contact the recruiter.
- Interviews set up before 15 Nov 2026 ask instead for three separate boxes, one each for:
- storing your answers and documents;
- AI evaluation;
- a person making every decision.
- When you apply: one box covering storage, AI matching and a person deciding.
- Every agreement is versioned and recorded, along with the exact wording you saw.
5. A person decides.
- The AI scores and flags your answers. A recruiter makes every decision.
- Nothing is rejected automatically, including by the authenticity checks, the ID check or the activity record.
- Recagn's rules list what happened while you answered, such as time away from the page or a second face in a photo. The recruiter decides what it means. These findings never change your score or your place in the ranking.
- The ID check compares the face on your ID with your selfie. It does not check whether the ID itself is genuine.
- What the AI is given:
- The AI that scores your answers is given the role, the rubric and your answers.
- The AI that matches you to the role is given only your skills, experience, education, projects, location and work preferences.
- Neither is given your name, email or phone.
- Your résumé's full text is read by an AI only to pull out those details.
- This is Recagn's choice. The DPDP Act doesn't require it.
6. How long it's kept, and your requests.
- ID photo and selfie: deleted 90 days after you take them. Only an Aadhaar card is masked: its first 8 digits are hidden before the photo is saved. Any other ID is saved with nothing hidden. Your ID photo is used to compare faces, and the recruiter can see it and your selfie until they are deleted.
- Screen and camera recordings and camera photos: deleted 180 days after the interview is completed or closes. Recordings from an attempt you started over go at the same time.
- Everything else: your application, answers, evaluations, the activity record and the ID check's result (including the last 4 digits of an Aadhaar number) stay until the agency deletes them.
- Deletion: an agency can delete a candidate who hasn't been added to any of its hiring pipelines. Once you're in a pipeline, your record can't be deleted yet.
- Your requests: to ask what's held about you, or to correct or delete it, contact the agency that invited you. You can also write to us at the contact email, and we'll pass your request on.
7. The small print.
- This is not legal advice.
- The DPDP Act's duties for agencies begin on or about 13 May 2027.
- This statement was last checked on 2026-11-16.
Running the first-round interview comes off your plate. The questions and the hard gates stay yours.
The checklist, against Recagn
| Checklist area | What Recagn does today | Not built yet |
|---|---|---|
| Roles | The Apply form names the agency as the one storing the data, using Recagn. A client sees only the report the agency shares; its link expires after 30 days by default and can be revoked | Processor terms for agencies |
| Notice and consent | An interview screen that lists everything the interview records, with a box to agree and a box confirming the candidate is 18 or older (interviews set up before 15 Nov 2026 keep three separate boxes); one Apply box; each versioned and recorded with the wording the candidate saw | A full Rule 3 notice; a contact person per workspace; languages other than English; a notice for uploaded or sourced candidates; an age check beyond the candidate's own word |
| Retention and erasure | ID photos and selfies are deleted after 90 days, and screen and camera recordings 180 days after the interview ends. Other records stay until the agency deletes them. An agency can delete a candidate who isn't in any pipeline | A retention period for applications, answers and evaluations; erasure for candidates already in a pipeline; withdrawal of consent |
| Accuracy and AI | The AI scores and flags; a recruiter makes every decision, and nothing is rejected automatically. The scoring and matching AI is not given name, email or phone. The résumé's full text is read by an AI only to pull out the candidate's details | Nothing on the gap list |
| Security and breach | Each agency's candidate data is kept separate from every other agency's | A breach runbook |
| Candidates' rights | Requests go to the agency; candidates can also write to Recagn, which passes them on | Access, correction, erasure and grievance handling inside the product |
Source: Recagn's DPDP position statement, checked 15 Nov 2026, with its consent, retention, deletion, report-link and AI-input code re-read that day · this table is the guide's summary, not the statement · not legal advice
The gaps carry no dates here, and this page makes no promise about when they close.
Who decides in Recagn
Recagn recommends. Only you can reject a candidate.
Scoring answers and flagging likely cheating come off your plate; whether a flag matters stays yours. Recagn drafts the report for the client; who goes on the shortlist and what the client sees stay yours.
Recagn does not call itself DPDP compliant: the duties haven't started, and the gaps above are open.
Questions people ask
Is Recagn DPDP compliant?
Recagn does not call itself DPDP compliant. The DPDP Act's duties for agencies begin on or about 13 May 2027, and the agency is most likely the Data Fiduciary; Recagn is the tool that processes the data for the agency. Several pieces an agency will need, such as withdrawal of consent and erasure for candidates already in a pipeline, are not built yet. This is not legal advice.
Hyring's guide says AI hiring needs fairness audits. Does the DPDP Act require a bias audit?
No, not of a recruitment agency. The DPDP Act's audit duties fall only on a Significant Data Fiduciary that the Government notifies (s.10): from on or about 13 May 2027, an annual impact assessment and audit (r.13(1)), and checks that its algorithmic software is not likely to put people's rights at risk (r.13(3)). When we checked on 11 Nov 2026, we found no published list of Significant Data Fiduciaries, and so none naming a recruitment agency or screening tool. Hyring's guide to AI hiring compliance, published 3 Feb 2026 and read 11 Nov 2026, recommends fairness audits and suggests running them every year. An agency may choose to run them; the DPDP Act doesn't require it.
Does recording candidate consent cost extra on Recagn?
No. The consent screen comes with every interview on every plan. The interview itself uses credits: one for text or voice, three if any answer is video, and more if you turn on webcam proctoring. On Starter, monthly, that is at most ₹50 per text or voice interview (₹49.98; ₹58.98 with 18% GST) and at most ₹150 per video interview (₹149.95; ₹176.94 with GST). The checklist on this page is a free download.
Does the DPDP Act apply to CVs that arrive on paper or by email?
Yes, from on or about 13 May 2027, once they are in digital form. The Act covers personal data collected digitally, and data collected on paper and digitised later (s.3(a)). A CV that arrives by email is already digital.
Does a recruitment agency need a Data Protection Officer?
No, not unless the Government notifies it as a Significant Data Fiduciary (s.10(2)(a)). From on or about 13 May 2027, every fiduciary must still publish the contact details of a person who can answer candidates' questions about their data (s.8(9), r.9).
Can we keep rejected candidates' CVs for future roles?
Only for a purpose the candidate was told about. From on or about 13 May 2027, a CV collected for one role should be erased once that purpose is served (s.8(7)). To keep it for later roles, name that purpose in the notice and ask for consent to it (s.6(1)). This is this guide's reading, not legal advice.
Can a candidate ask an agency to delete their CV and interview?
Yes, from on or about 13 May 2027. A candidate can ask for erasure (s.12(3)), and the agency must erase unless it still needs the data for the purpose or to comply with a law, and must have its tools erase too (s.8(7)(b)). The one-year minimum for processing logs (r.8(3)) may mean keeping a record of the processing; ask counsel.
Does the DPDP Act cover candidates under 18, such as interns?
Yes. Anyone under 18 is a child under the Act (s.2(f)). From on or about 13 May 2027, a child's data needs a parent's verifiable consent before it is processed (s.9(1), r.10), and tracking or behavioural monitoring of children is barred (s.9(3)).