Walk into a bank branch late in the afternoon and you'll often see the same thing. A stack of account opening forms sits beside a scanner. By evening each form is a PDF in a central folder, and the original sits in a carton bound for the record room.

Ask whether the DPDP Act covers that carton and many teams say no, because the Act is about digital data. It's one of the claims about DPDP that are only half right. The carton may sit outside the Act. The PDF does not.

Section 3(a) brings paper-sourced personal data into scope the moment it is digitised. The Act's operative duties take effect on 13 May 2027, so the countdown is already short. Archives scanned this year will be in scope on that date, along with every PDF the branch made this evening.

What Section 3 actually says

Section 3(a) applies the Act to digital personal data processed in India where the data was collected in one of two ways. Either it was collected in digital form, or "in non-digital form and digitised subsequently". The text of the Act on India Code is short and clear on this point.

Two definitions make the boundary sharper. Section 2(n) defines digital personal data simply as personal data in digital form. Section 2(x) defines processing as a "wholly or partly automated operation or set of operations performed on digital personal data".

Read together, they place the paper form itself outside the Act. Filling it in, filing it and reading it at a desk involve no automated operation. Scanning it, indexing it or emailing it all do.

So the trigger is a single act of conversion. Once a form is scanned, typed into a system or photographed, the result is digital personal data. From then on, the duties in Chapters II and III attach to that record.

What stays outside under Section 3(c)

Section 3(c) sets out two exclusions, and both are narrower than they sound. Section 3(c)(i) excludes data processed by an individual for a personal or domestic purpose. That covers a family address book. It does not cover a relationship manager's phone full of customer photos, because those photos serve the employer.

Section 3(c)(ii) excludes data made publicly available by the Data Principal, or by anyone a law obliges to publish it. The Act's own illustration is a person blogging her views on social media. A scanned KYC file, a salary slip or a hospital admission form fits neither exclusion.

Archive teams sometimes reach for a third route. Section 17(2)(b) disapplies the Act for research, archiving or statistical purposes. The data must not be used for any decision about a specific person. Rule 16 also ties the exemption to the standards in the Second Schedule. A bank scanning old forms to settle customer disputes will struggle to claim it.

Where paper becomes digital

Conversion rarely happens in one place. It happens wherever someone has a scanner, a keyboard or a phone camera. In a typical enterprise, these six are the usual ones.

Conversion pointWhat gets digitisedWhere it usually lands
Branch scanningAccount forms, mandates, chequesCentral repository, branch drive
KYC uploadsAadhaar, PAN, passport copiesOnboarding system, vendor portal
HR onboardingID proofs, bank details, offer lettersHR system, recruiter mailboxes
Hospital admissionAdmission and consent forms, IDsHospital system, ward PCs, billing
Data-entry teamsClaim forms, applications, surveysCore systems, spreadsheets
Staff phonesPhotos of forms and IDsChat apps, galleries, personal cloud

Banks will recognise most of these from their KYC flows, which we covered in DPDP for banks and NBFCs. Hospitals and large employers show the same pattern with different forms.

Two rows need a closer look. Data entry is often outsourced, and Section 8(1) keeps the Data Fiduciary responsible for processing done on its behalf. Section 8(2) requires a valid contract with the processor. Rule 6(1)(f) requires that contract to provide for security safeguards.

The staff phone is the other. A field officer photographs a customer's ID to save a trip, then forwards it to a colleague on a messaging app. That photo now sits on two personal devices and possibly a cloud backup. It is outside every control the organisation runs.

Where scanned paper ends up

A scanned form is rarely stored once. The scanner drops it in a network folder. Someone emails it to the credit team, and an analyst saves a copy to her laptop to work offline.

Each copy is digital personal data. Each needs the Rule 6 safeguards, and each has to be found when the person asks for access or erasure. You can't erase what you can't locate. That is why data discovery and classification across drives, mailboxes and endpoints has to come before any erasure policy.

This has happened before. In 2020, Digit reported that a BHIM-related website had left identity scans exposed on an AWS server. The files included Aadhaar cards, PAN cards and caste certificates. Business Insider India reported that CERT-In was alerted on 5 May and the exposure was fixed on 22 May. Most of those files began life as paper cards and certificates.

The duties that start at the point of scanning

From 13 May 2027, a scanned record carries the same duties as data collected online. These are the ones that bite first.

Lawful ground. Section 4 permits processing only with consent or for a certain legitimate use under Section 7. Employment purposes, for instance, are a legitimate use under Section 7(i). Record which ground covers each scanning stream.

Notice. Where consent is the ground, Section 5 requires a notice covering the data, the purpose and how to complain to the Board. A consent line printed on a form years ago will rarely meet that standard.

Security safeguards. Section 8(5) and Rule 6 require minimum measures such as encryption or masking, access control, logging and backups. Rule 6(1)(e) adds one-year retention of logs, unless another law requires otherwise. A scanned PDF in an open shared folder fails most of these.

Access. Section 11 lets a person who gave consent ask for a summary of their data and the processing done on it. They can also ask who else it was shared with. Answering that needs a rights request process that reaches scanned files as well as databases.

Erasure. Section 8(7) requires erasure once the purpose is served or consent is withdrawn, unless a law requires retention. The Act's own illustration is a bank keeping identity records for ten years after an account closes, because banking law requires it.

Breach reporting. Section 8(6) requires intimation to the Board and to each affected person. Under Rule 7, affected people must be told without delay. The detailed report to the Board is due within seventy-two hours of becoming aware of the breach.

The Schedule to the Act sets penalties of up to ₹250 crore for failing to take reasonable security safeguards. Failing to give breach intimation can cost up to ₹200 crore.

Old archives being digitised now

Many organisations are scanning decades of files to free up record rooms. Each project creates digital personal data in bulk. Every file it produces carries the duties above from 13 May 2027.

Section 5(2) deals with consent given before commencement. The fiduciary must give a fresh notice as soon as reasonably practicable. It may keep processing until the person withdraws consent. For a scanned archive, that means knowing whose data sits in it and how to reach them.

Archive scanning is also the cheapest moment to apply retention. Records past their legal retention period may not need scanning at all. Make that call before the vendor starts work.

Where things stand today

As of 30 October 2026, Sections 3 to 17 of the Act are not yet in force. Notification G.S.R. 843(E) brings them into force on 13 May 2027. Rules 3 and 5 to 16 start on the same date under Rule 1.

Section 44(2) also starts then, and it omits Section 43A of the Information Technology Act, 2000. Until that date, Section 43A continues to apply. Scanning streams set up now can be built to the Rule 6 standard from the start. That is far easier than fixing them later.

A checklist built on one question

Ask every function one question: where do paper forms go after they are filled in, and who scans or types them? The answers become your checklist.

QuestionOwnerEvidence to keep
1. Which forms collect personal data on paper?Function headsForm register
2. Who scans, types or photographs them?Operations, procurementProcess notes, vendor list
3. Where does each digital copy land?IT, CISOData map
4. Which lawful ground and notice cover each stream?DPO, legalNotice text, recorded ground
5. Are scan folders encrypted, restricted and logged?CISORule 6 control evidence
6. Do vendor contracts cover security and erasure?Legal, procurementSigned clauses
7. When does each record expire, paper and scan together?Records, complianceRetention schedule
8. Can you find every copy when a request arrives?DPO, ITTest request results

Question three usually takes the longest, because copies spread quietly. Building that data map of scan destinations is the foundation for questions five to eight. If several answers come back blank, a structured DPDP gap assessment will show where to begin.

The scanner is the boundary

The DPDP Act doesn't reach your record room. It reaches the scanner beside it, and every folder, inbox and phone the scan touches. Map those points before May 2027. The rest of your programme depends on that map.

Sources

  1. Ministry of Law and Justice, India Code, "The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023), as on 19 November 2025", 2025. Link
  2. DPDP Wiki (MYND Integrated Solutions), "The Digital Personal Data Protection Rules, 2025", updated 9 September 2026. Link
  3. DPDP Wiki (MYND Integrated Solutions), "Rule 6: Reasonable security safeguards", updated 9 September 2026. Link
  4. DPDP Wiki (MYND Integrated Solutions), "Rule 7: Intimation of personal data breach", updated 9 September 2026. Link
  5. DPDP Wiki (MYND Integrated Solutions), "Breach and security FAQ", updated 9 September 2026. Link
  6. DPDP Wiki (MYND Integrated Solutions), "Rule 16: Exemption from Act for research, archiving or statistical purposes", updated 9 September 2026. Link
  7. DPDP Wiki (MYND Integrated Solutions), "Key dates and commencement", updated 9 September 2026. Link
  8. Digit, "Financial, personal data of more than 7 million users left exposed in CSC BHIM website breach", 2020 incident. Link
  9. Business Insider India, "CSC BHIM site left Aadhaar cards, PAN numbers, and biometric information exposed", 1 June 2020. Link