On a Tuesday evening, a salaried professional fills in a ₹5 lakh personal loan application on a mid-sized NBFC's website. By Friday the lender holds her payslips, six months of bank statements and a verified PAN. It also holds a watermarked live photograph and a credit report from CIBIL. Copies of several of this sit in a sales agent's WhatsApp and on a relationship manager's laptop.

Most DPDP programmes file all of this under "customer data" and move on. That label hides the real work. Every step in the loan journey collects new data, creates new copies and sends data to new recipients. Every step also starts a new purpose and a new retention clock.

The deadline is close. Most operative sections of the DPDP Act, and Rules 3 and 5 to 16 of the DPDP Rules, come into force on 13 May 2027. That is about six and a half months away, and a plan that works back from 13 May 2027 leaves a lender little slack.

This piece follows one application from lead to former customer. At each stage it shows what is collected, where it lands, who receives it and what the law expects. The method for discovery, classification and mapping is covered in our previous article, so this one stays with the case.

Lead, applicant, customer: different relationships, different purposes

Our borrower first appeared as a lead. She clicked a campaign, gave her mobile number and agreed to receive calls about loan offers. That consent covers marketing. It does not cover processing a loan application.

Section 6(1) of the DPDP Act requires consent that is specific and limited to the data needed for the specified purpose. Section 2(za) defines the specified purpose as the one stated in the notice. The purpose is therefore only as wide as the notice that described it.

So the application needs its own notice. Rule 3 of the DPDP Rules requires a notice that can be understood on its own. It must give an itemised description of the personal data and the specified purpose. The illustration to Section 5 even uses a bank's video-based KYC as its example of where a notice is due.

Her status will change twice more. She becomes a customer at sanction and a former customer at closure. Each status brings new purposes, and some of them rest on legal obligations rather than consent.

That is why each record needs a stage tag and a purpose tag. Section 6(6) requires processing to stop when she withdraws consent, unless law requires or authorises it. The tags tell you which processing stops and which continues. A consent management record kept per purpose makes that split workable.

The wider sector picture sits in our guide to DPDP for banks and NBFCs. Here we stay with one borrower.

Application: the first wave of documents

The application form captures her name, conta ct details, date of birth, address, employer, income and existing EMIs. She then uploads salary slips, bank statements and address proof. A larger loan might add a co-applicant or a guarantor.

The structured fields go into the loan origination system. The PDFs go into the document management system. In practice, the documents rarely travel only through the portal.

A direct selling agent may have collected the bank statement over WhatsApp before the upload. A relationship manager may have saved it to a laptop to check salary credits. A credit analyst may have emailed it to a colleague for a second view. Each copy is processing that the notice must cover and the retention policy must reach.

Section 8(1) keeps the lender responsible for processing done on its behalf. The NBFC Responsible Business Conduct Directions require lenders to train agents on privacy of customer information. Training helps. The lender still needs to know which agent holds which file.

Guarantors and co-applicants are Data Principals in their own right. Their PAN, income proofs and bank statements need a notice addressed to them. Their data also travels further. The NBFC Credit Information Reporting Directions list changes in guarantor details among the account updates that lenders report to the bureaus.

KYC: collected under one law, kept under another

KYC runs under the RBI KYC Directions for NBFCs, as updated on 29 December 2025. Each step leaves an artefact that discovery must find and classification must label.

  • Officially valid documents. The list covers the passport, driving licence, proof of possession of Aadhaar, voter ID. Each upload is an identity image.[Ss1.1]
  • PAN or Form 60. The lender must obtain one and verify the PAN with the issuing authority. The verification response is a new record.
  • Aadhaar. Aadhaar is not mandatory for KYC. Where authentication isn't required, the lender must ensure the customer redacts or blacks out the number.
  • Digital KYC. The live photograph carries a watermark with the application form number, GPS coordinates, the official's name and employee code, and a date and time stamp. The image records where and when she was, as well as who she is.
  • Video KYC. V-CIP recordings and data must be stored in systems located in India. Any cloud or technology provider assisting the session must retain no data afterwards.
  • CKYCR download. With her explicit consent, the lender can retrieve her records from the Central KYC Records Registry using her KYC Identifier.

Some lenders authenticate Aadhaar themselves. For them, UIDAI Circular No. 14 of 2025, dated 4 November 2025, applies. Aadhaar numbers and connected data must sit only in an Aadhaar Data Vault. Business systems must use a reference key, and a hash of the number does not qualify as one.

The bureau check: data the applicant never gave you

With KYC complete, the credit team requests her Credit Information Report. RBI lists four registered credit information companies: CRIF, Equifax, Experian and TransUnion CIBIL. The lender sends her identifying details and receives her history with every other reporting lender.

That report is new data. She never gave it to this lender. It shows her other loans, her repayment record and past enquiries. It is among the most sensitive files in the loan folder.

Read the consent position precisely. Paragraph 11 of the NBFC Credit Information Reporting Directions says CICRA gives statutory backing to sharing credit information with CICs. It adds that a consent clause for that reporting has become redundant. The DPDP notice should still tell her that the lender will obtain her report and use it for the credit decision.

She will also know you looked. Under RBI's circular of 26 October 2023, CICs must send an SMS or email alert when a specified user accesses a customer's report. The alert goes out when the enquiry reflects in her report.

Then comes the unstructured problem. The report often arrives as a PDF that is saved to the loan file and attached to a credit memo. It is emailed to the sanctioning authority and sometimes printed for a credit committee. Each of those copies needs an owner, a location on record and an end date.

Rule 6 sets the floor for who can open it. It requires access controls on computer resources, plus logs that let you detect unauthorised access. Rule 6(1)(e) requires those logs to be kept for one year, unless another law requires otherwise.

The rejected applicant: data without a relationship

Suppose the credit committee declines her. The KYC Directions require the officer to record the reasons when an onboarding application is rejected. That record must be kept, and it must be findable.

Now ask what happens to everything else. No account was opened, and no account-based relationship began. Yet her payslips, bank statements and bureau report sit in the origination system, the document store, an analyst's inbox and the agent's phone.

The five-year KYC clocks are framed around a business relationship and its transactions. Counsel should decide which of her records, if any, another law requires the lender to keep. Everything else falls under Section 8(7). Erase it once the purpose is no longer served, and have your processors do the same.

There is a wrinkle here. Rule 8(3) requires a lender to keep personal data, traffic data and processing logs for at least one year from processing. Take a documented view on how this hold sits alongside an erasure request under Section 12(3).

Her bureau enquiry also sits with the CIC, outside the lender's systems. Erasure at the lender's end will not reach it.

Sanction and onboarding: a customer is created

Approval produces a new set of documents. The Responsible Business Conduct Directions require a sanction letter stating the amount, terms and annualised interest rate. The borrower must receive a copy of the loan agreement with every enclosure. Retail loans also need a Key Facts Statement with a unique proposal number.

Then come the e-sign record, the NACH mandate with her bank account details and the disbursal entry. The signed sanction letter often lives as a PDF on the relationship manager's laptop and in an email thread. The KYC Directions also require a Unique Customer Identification Code for every new individual customer.

Two recipients appear at this stage. The lender must upload her KYC records to CKYCR within 10 days of starting the relationship. It must then share the KYC Identifier with her. From 1 July 2026, the lender must also report her CKYC number to the CICs whenever it has one.

Bureau reporting now runs four times a month. Lenders submit data as on the 9th, 16th, 23rd and last day of each month. The month-end full file is due by the 5th of the next month.

Life as a customer: servicing, collections and cross-selling

Servicing creates a steady stream of records. EMI reminders, statements, customer service calls and their recordings all carry her data. If she falls behind, collection agencies receive her contact details and dues.

The conduct rules are specific. Outside microfinance, the Responsible Business Conduct Directions bar recovery calls before 8:00 a.m. and after 7:00 p.m. Lenders must also alert customers when they report a default or days past due to the CICs.

Section 17(1)(f) of the Act exempts some processing from most of Chapters II and III. It covers processing to ascertain a defaulter's financial information, assets and liabilities. The exemption is narrow and depends on other disclosure laws. Treat it as a tool for defaulted accounts only.

KYC does not end at onboarding. Periodic updation is due at least every two years for high-risk customers, every eight for medium risk and every ten for low risk. Before each due date, the lender must send at least three advance intimations, including one by letter.

The KYC Directions also bar the lender from divulging account-opening information for cross-selling without her express permission. Treat the KYC file as off limits for campaigns unless she has said yes.

Calls follow TRAI's Telecom Commercial Communications Customer Preference Regulations, as amended in February 2025. Consent given to complete an ongoing transaction is valid for only seven days. Implicit consent for service and transactional messages lasts only for the duration of the contract. After closure, service calls need her explicit consent. If she opts out of promotions, the sender cannot seek her consent again for 90 days. NBFCs must also use only registered telemarketers.

Retention: one customer, several clocks

Paragraph 47 of the KYC Directions sets two floors. Transaction records must be kept for at least five years from each transaction. Identification and address records must be kept for at least five years after the relationship ends. Identification records include account files and business correspondence.

Section 8(7) sets the default for everything else. Erase personal data once the purpose is served, unless the law requires retention. The Act's own illustration describes a bank keeping identity records for ten years after closure. NBFCs should check their actual obligation rather than copy that figure.

So one borrower carries several clocks at once. Her KYC file runs until five years after closure. Each EMI record runs five years from its own date. Processing logs carry the one-year floor under Rule 8(3). Her marketing consent runs until she withdraws it or the purpose ends.

The practical consequence sits in email. Correspondence with her about the loan forms part of the identification record and must stay. A two-year-old export of applicant mobile numbers on a shared drive must go.

One person, many records

By closure, the same woman exists under at least five identifiers. She has a CRM lead ID, an application number, a UCIC, a KYC Identifier and a loan account number. Each bureau holds her under its own references.

Rule 14(5) anticipates this. It defines an identifier to include a customer identification file number, an application reference number, an email address and a mobile number. A rights request can arrive under any of them.

An access request under Section 11 needs a summary of her data and the processing done on it. It also needs the identities of every other Data Fiduciary and Data Processor that received her data. For a borrower, that list includes CKYCR, the CICs, KYC vendors and collection agencies.

Bureau corrections carry their own clock. The lender has 21 days to send corrected data to the CIC. Delays beyond 30 days from the complaint attract compensation of ₹100 a day.

None of this works without identity resolution across systems. A Data Principal rights portal can only return what the links behind it can find.

The journey at a glance

The flowchart shows the main obligation at each stage. The table shows where the data goes.

StageData createdWhere copies landWho receives itRetention
LeadMobile, campaign source, consentCRM, diallerTelemarketerUntil withdrawal or purpose ends
ApplicationForm, payslips, bank statementsLOS, DMS, WhatsApp, emailDSA, credit teamSection 8(7)
KYCOVD images, PAN check, photo, videoKYC app, V-CIP serverKYC vendor, CKYCR5 years after relationship ends
Bureau checkCredit Information ReportLoan file, memo PDF, emailCredit committeeSet per policy
SanctionLetter, KFS, agreement, NACHDMS, RM laptope-sign provider, sponsor bankPer record type
CustomerRepayments, calls, KYC updatesLMS, call recorderCICs, collection agency5 years per transaction
ClosureClosure letter, final statementDMS, emailCICsKYC 5 years after closure

What breaks without discovery, classification and mapping

Consent withdrawal that goes too far, or not far enough. She withdraws marketing consent. A system that tags data only by customer stops her EMI reminders too. The reverse failure is quieter. A team cites "servicing" to keep a lead list alive long after those leads stopped being applicants.

An erasure request that misses the bureau PDF. The rejected applicant asks for erasure, and the origination record goes. The report PDF attached to a credit memo in someone's inbox stays. So does the copy on the agent's phone. Without data discovery and classification across unstructured stores, the lender cannot honestly confirm erasure.

A breach of a shared folder. A misconfigured share exposes a folder of bank statements and KYC images. Rule 7 requires notice to each affected Data Principal without delay. The Data Protection Board must receive a detailed report within 72 hours. CERT-In's FAQs say data breaches and leaks must be reported to CERT-In within six hours of noticing them.

You cannot notify people you cannot identify from a folder of PDFs. Only data mapping that links each file to a person and a recipient makes those deadlines achievable.

Seven tasks for the next quarter

Most lenders start with a gap assessment against the Act and Rules, scoped to one product. Personal loans make a good first choice because the journey is short and well documented.

TaskWhat good looks like
Map each stageOne journey map from lead to closure, with systems and recipients per stage
Tag every recordA stage tag and a purpose tag on structured and unstructured records
Search unstructured storesBureau PDFs, KYC images, V-CIP files and statements found in email, drives, laptops and chat exports
Map outbound flowsKYC vendors, CKYCR, the four CICs, e-sign, NACH and collection agencies on record
Set retention per record typeSeparate rules for KYC, transactions, bureau reports, rejected files and logs
Link identifiersLead ID, application number, UCIC, KYC Identifier and loan account resolve to one person
Rewrite notices by stageSeparate Rule 3 notices for the lead, the application and the KYC process

How DataSurity handles this

DataSurity tags each record with its lifecycle stage and purpose, so a withdrawal or an erasure reaches the right records. It discovers KYC images and bureau report PDFs in unstructured stores. It maps data flows to CKYCR, the CICs and vendors. Its rights portal finds every record linked to one person across identifiers.

Follow the borrower through the file

Customer data in lending is a sequence of relationships. Each one has its own notice, its own recipients and its own clock. A programme that maps the sequence can answer a borrower's request in one search. A programme that maps only systems will keep finding her bank statement in places nobody listed.

Sources

  1. Ministry of Law and Justice, India Code, "The Digital Personal Data Protection Act, 2023 (as on 19 November 2025)", 11 August 2023. Link
  2. Ministry of Electronics and Information Technology, "Digital Personal Data Protection Rules, 2025, G.S.R. 846(E)", 13 November 2025. Link
  3. Reserve Bank of India, "Reserve Bank of India (Non-Banking Financial Companies, Know Your Customer) Directions, 2025 (Updated as on December 29, 2025)", 28 November 2025. Link
  4. Reserve Bank of India, "Reserve Bank of India (Non-Banking Financial Companies, Credit Information Reporting) Directions, 2025 (Updated as on July 01, 2026)", 28 November 2025. Link
  5. Reserve Bank of India, "Reserve Bank of India (Non-Banking Financial Companies, Responsible Business Conduct) Directions, 2025 (Updated as on July 1, 2026)", 28 November 2025. Link
  6. Reserve Bank of India, "Strengthening of customer service rendered by Credit Information Companies and Credit Institutions, RBI/2023-24/73", 26 October 2023. Link
  7. Unique Identification Authority of India, "Circular No. 14 of 2025: Revised guidelines for hosting HSM, Aadhaar Data Vault and authentication application", 4 November 2025. Link
  8. Telecom Regulatory Authority of India, "Press Release No. 11/2025: TRAI Strengthens Consumer Protection with Amendments to TCCCPR, 2018", 12 February 2025. Link
  9. CERT-In, "FAQs on Cyber Security Directions of 28.04.2022", May 2022. Link