DPDP compliance for digital lending apps means meeting two sets of rules at once: the DPDP Act and Rules, which apply to every business, and the RBI's digital lending rules, which apply to banks, NBFCs and the lending service providers they work with. Where they overlap, you build for both. In practice that means need-based data collection with consent you can prove, no access to phone contacts or media, borrower data stored in India, KYC records kept for as long as the law requires and nothing longer, and a clear record of which partner receives what. The DPDP duties start on 13 May 2027. The RBI rules already apply.
This guide is for the teams behind loan apps: lenders' own apps, lending service providers (LSPs) and co-lending platforms.
How DPDP and the RBI rules stack
The DPDP Act applies in addition to other laws (Section 38(1)), and prevails where the two conflict (Section 38(2)). Mostly there is no conflict. The RBI rules are more specific, and you can meet both.
The RBI's digital lending rules were first collected in the Reserve Bank of India (Digital Lending) Directions, 2025, issued on 8 May 2025. On 28 November 2025 the RBI consolidated its instructions into Master Directions for each type of lender. For NBFCs, the digital lending rules now sit in Chapter III of the Credit Facilities Directions, 2025. Other types of lender have matching provisions in their own Master Directions. The paragraph numbers below are from the NBFC version.
| Topic | DPDP Act and Rules | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III) |
|---|---|---|
| Who it binds | DPDP Act and Rules: Every Data Fiduciary, and its processors through contracts | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): The lender (the regulated entity), which must ensure its LSPs and their apps comply |
| Collecting data | DPDP Act and Rules: Only the data needed for the stated purpose (Section 6(1)) | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): Need-based collection, with prior and explicit consent and an audit trail (para 13(1)) |
| Phone access | DPDP Act and Rules: No specific rule | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): No access to files and media, contact list, call logs or telephony functions. One-time camera, microphone or location access for onboarding or KYC, with explicit consent (para 13(1)) |
| Sharing with third parties | DPDP Act and Rules: Consent or a legitimate use; processors only under a valid contract (Sections 4, 7 and 8(2)) | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): Explicit consent before sharing personal information with any third party, unless a statute or regulation requires it (para 13(4)) |
| Withdrawal and deletion | DPDP Act and Rules: Withdraw as easily as you consent; erase unless a law requires retention (Sections 6(4), 8(7) and 12(3)) | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): Borrower can deny, restrict or revoke consent, and ask for data to be deleted (para 13(2)) |
| Where data is stored | DPDP Act and Rules: Transfers abroad allowed unless the Government restricts a country (Section 16) | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): All data stored only on servers in India. Data processed abroad is deleted there and brought back within 24 hours (para 14(4)) |
| Security and breach | DPDP Act and Rules: Rule 6 safeguards; breach notice to the Board and each affected person (Rule 7) | RBI digital lending rules (NBFC Credit Facilities Directions, Chapter III): Compliance with RBI and other cybersecurity standards (para 16); a public policy on breach handling (para 14(2)) |
Localisation shows how the two fit. The DPDP Act allows most transfers abroad, but the RBI rules still require borrower data to be stored in India. You meet both by storing in India. Our DPDP Act explainer covers each DPDP duty.
Consent at onboarding

Onboarding is where most of the data enters, and where both rule sets bite hardest. The RBI rules say what the app may not touch:
- Files and media on the phone. No access.
- The contact list and call logs. No access.
- Telephony functions. No access.
- Camera, microphone and location. One-time access only, for onboarding or KYC, and only with the borrower's explicit consent.
- Biometric data. Not to be collected or stored by the lender or the LSP, unless existing statutory guidelines allow it (para 14(3)).
Check this in the build, not only in the policy. Read the permissions your Android and iOS builds request, including those added by third-party SDKs for analytics or fraud checks. An SDK that reads the contact list counts as your app reading it.
What a DPDP-ready consent screen looks like
- A notice before the request. What data, for what purpose, how to withdraw, how to use your rights, and how to complain to the Data Protection Board (Section 5, Rule 3).
- One consent per purpose. Loan processing, a bureau pull, sharing with a co-lender and marketing are separate purposes. Marketing must not be bundled with the loan.
- Disclosure at each stage. The RBI rules ask you to give the purpose of each consent at each stage (para 13(3)).
- A record you can produce. The consent, the notice version shown and the time. The RBI asks for an audit trail, and under the Act the burden of proving consent is on you.
- A way to say no and to withdraw. Deny a specific use, restrict sharing, revoke consent and ask for deletion, without calling support.
Our consent management page covers the consent log and how withdrawals reach every system that received the data.
KYC retention and DPDP erasure
A borrower closes their loan and asks you to delete everything. You cannot, and the DPDP Act does not ask you to. The duty to erase applies "unless retention is necessary for compliance with any law for the time being in force" (Section 8(7)). The right to erasure has the same exception (Section 12(3)).
For NBFCs, the RBI's Know Your Customer Directions, 2025 set two retention periods (para 47):
- Transaction records: at least five years from the date of each transaction.
- Identification and address records: at least five years after the business relationship has ended.
Other laws may set further periods. List each one with its source; our partner law firm confirms which apply.
How to build retention so it holds up
- A retention entry per record type, not per database. KYC documents, loan agreements, repayment history, app analytics and marketing leads each have their own period and legal basis.
- Narrow what you keep. When the purpose ends, move the fields the law requires to a restricted store and delete the rest. Retained data is not for cross-sell.
- Mark the reason on the record. A legal-hold flag naming the rule, so deletion jobs skip it and analysts cannot query it.
- Respect the one-year floor. Rule 8(3) has every Data Fiduciary keep personal data, traffic data and processing logs for at least one year, for purposes listed in the Rules. Your deletion jobs need a minimum as well as a maximum.
- Tell the borrower why. Say which records you keep, under which law, and until when.
The RBI rules also ask you to publish how long data is kept and how it is destroyed (para 14(2)). One retention schedule can serve that policy and your deletion jobs.
Co-lending and LSP data flows: who is responsible for what

Under the DPDP Act, a Data Fiduciary is whoever decides, alone or with others, why and how personal data is processed. A Data Processor processes it on a fiduciary's behalf. The label follows what each party actually does with the data, not what the contract calls them.
- The lender decides the purpose and means of lending. It is the Data Fiduciary for borrower data, and the RBI rules make it responsible for its LSPs' apps.
- An LSP that sources and services loans only for the lender usually acts as a processor. If it also uses borrower data for its own purposes, such as its own marketing or its own credit model, it may be a fiduciary in its own right for that use. The RBI rules also limit what an LSP may store to basic minimal data, such as name, address and contact details (para 14(1)).
- Co-lenders each decide to lend and each hold a share of the loan, so each is likely a fiduciary. The Act's definition covers fiduciaries acting "in conjunction with other persons". Your contracts should say who handles notices, rights requests and breach reports, so the borrower has one route.
For NBFCs, co-lending now sits in Part B of the RBI's Transfer and Distribution of Credit Risk Directions, 2025, in force for new arrangements from 1 January 2026. It has no data protection chapter, but its rules shape the data flow. Each lender keeps at least 10% of each loan (para 102). The loan agreement names a single point of interface with the customer (para 105). Money moves through an escrow account (para 117). Each lender meets the KYC rules, and may rely on the originating lender only for the customer identification process (para 120). Where co-lending is digital, the digital lending rules apply as well (para 98).
A data-flow table for a typical lending app
This is the map we start from. The role column is a working assumption for your lawyers to confirm.
| Flow | Data that moves | Likely DPDP role of the receiver | RBI rule that applies | Control to build |
|---|---|---|---|---|
| Borrower to the app (LSP or lender) | Data that moves: Identity, contact, income, bank statements, device data | Likely DPDP role of the receiver: LSP as processor for the lender | RBI rule that applies: Need-based collection, explicit consent, no phone resources | Control to build: Permission audit, consent log, data minimisation per field |
| App to KYC and video KYC vendors | Data that moves: Identity documents, photo, video, OTP results | Likely DPDP role of the receiver: Processor | RBI rule that applies: Storage in India; biometric limits | Control to build: Contract with security terms (Rule 6(1)(f)); vendor storage region |
| Lender to credit bureau | Data that moves: Identity and credit history | Likely DPDP role of the receiver: Recipient under its own legal duties | RBI rule that applies: Reporting duties under credit information law | Control to build: Purpose shown in the notice; access logs |
| Originating lender to co-lender | Data that moves: KYC, underwriting data, loan details, repayments | Likely DPDP role of the receiver: Co-lender as a separate fiduciary | RBI rule that applies: Co-lending Part B: KYC, escrow, asset classification sharing | Control to build: Agreed field list, consent record for sharing, one route for rights requests |
| Lender to LSP after disbursal | Data that moves: Repayment status for servicing | Likely DPDP role of the receiver: Processor | RBI rule that applies: LSP stores only basic minimal data | Control to build: Scoped API access, expiry on stored data |
| Lender to recovery agency | Data that moves: Name, contact, amount due, repayment history | Likely DPDP role of the receiver: Processor | RBI rule that applies: Agent particulars sent to the borrower before contact | Control to build: Minimum fields, access logs, contract terms, deletion when the case closes |
| App to analytics and crash tools | Data that moves: Device IDs, events, sometimes personal data in payloads | Likely DPDP role of the receiver: Processor | RBI rule that applies: Storage in India; consent at each stage | Control to build: Masking in SDK payloads; vendor data region |
Every row is a place where data leaves your control. A data map that lists each one is where the evidence starts.
Recovery agents and collections
Collections is the stage where borrower data travels furthest from the lender. The RBI rules ask the lender to send the borrower the particulars of the recovery agent by email or SMS before the agent makes contact, when a loan is first assigned and when the agent changes (para 9(6)). A lender that uses an LSP as a recovery agent must give it guidance and remains responsible for it.
Under the DPDP Act, a recovery agency working on your instructions is usually a processor. You stay responsible for it (Section 8(1)), and the contract must provide for security safeguards (Rule 6(1)(f)). In practice:
- Send only what the case needs. Name, phone number, amount due and repayment history. Not the KYC file or bank statements.
- No reference contacts from the phone. The app cannot read the contact list, so do not let a workaround feed it to collections.
- Give agents a scoped portal, not spreadsheets. Named logins, access logs, no bulk export, and access removed when the case closes.
Storage in India, security and breaches
The RBI rule covers "all data", so include backups, logs and vendor copies. If a tool processes data abroad, the data must be deleted there and brought back within 24 hours. Ask each vendor for its storage regions in writing.
Rule 6 of the DPDP Rules sets the minimum safeguards, including access logs kept for one year and security terms in processor contracts. Our Rule 6 checklist lists each clause with the evidence to keep, and our guide to one-year log retention covers the cloud settings.
After a personal data breach, tell each affected borrower and the Data Protection Board without delay, then send the Board a detailed report within 72 hours (Rule 7). CERT-In requires cyber incidents to be reported within 6 hours, and you may also have to report to the RBI. One runbook should cover all three. The highest DPDP penalty, up to ₹250 crore, is for failing to take reasonable security safeguards to prevent a breach.
Engineering checklist for lending apps
Run these checks against each app, each partner and each system that holds borrower data.
- 1. Permissions. No access to files, media, contacts, call logs or telephony, SDKs included. Camera, microphone and location are one-time and tied to KYC.
- 2. Consent records. One consent per purpose, with the notice version and time. Withdrawal works inside the app.
- 3. Third-party sharing. Every share has a consent or a recorded legal basis, and appears in the privacy policy.
- 4. LSP storage. Each LSP holds only basic minimal data, checked in its systems, not only its contract.
- 5. Localisation. Every store, backup, log pipeline and vendor is in India, confirmed in writing.
- 6. Retention. One entry per record type, with the period, the law behind it and the deletion job.
- 7. Erasure. Requests reach every system and partner. Retained records are flagged and restricted.
- 8. Co-lending. Each partner's field list is enforced in the API, with one route for rights requests.
- 9. Collections. Agents use a scoped, logged portal.
- 10. Logs and breach. Access logs kept for one year, and a drilled breach runbook.
A DPDP gap assessment maps every flow above and lists the gaps by risk, and DPDP implementation builds the consent log, retention jobs and partner controls. Our BFSI page covers banks and NBFCs more broadly, and everything else is on our DPDP compliance page.
This article is general information, not legal advice. Sector rules change, and our partner law firm confirms which RBI and other requirements apply to you, and reviews your partner contracts.
Sources: Digital Personal Data Protection Act, 2023, Sections 2, 5 to 8, 12, 16 and 38. Digital Personal Data Protection Rules, 2025, Rules 3, 6, 7 and 8 (G.S.R. 846(E), 13 November 2025). Reserve Bank of India (Digital Lending) Directions, 2025, RBI/2025-26/36, 8 May 2025. Reserve Bank of India (Non-Banking Financial Companies: Credit Facilities) Directions, 2025, RBI/DOR/2025-26/347, 28 November 2025, Chapter III. Reserve Bank of India (Non-Banking Financial Companies: Transfer and Distribution of Credit Risk) Directions, 2025, RBI/DOR/2025-26/352, 28 November 2025, Part B. Reserve Bank of India (Non-Banking Financial Companies: Know Your Customer) Directions, 2025, RBI/DOR/2025-26/361, 28 November 2025, para 47. Last reviewed 18 November 2026.
FAQ
Do loan apps need DPDP compliance if they already follow RBI rules?
Yes. The DPDP Act applies in addition to the RBI's digital lending rules. Many RBI rules, such as need-based collection and explicit consent, overlap with DPDP duties, but the Act adds its own notice contents, rights requests, breach reporting to the Data Protection Board and retention rules. Most DPDP duties start on 13 May 2027.
Can a digital lending app access a borrower's contacts or photos?
No. The RBI's digital lending rules say a lending app must not access files and media, the contact list, call logs or telephony functions. It may take one-time access to the camera, microphone or location for onboarding or KYC, with the borrower's explicit consent.
Can a borrower ask an NBFC to erase their KYC data under DPDP?
They can ask, but the NBFC may keep what a law requires. The DPDP Act's erasure duty and right both have an exception for retention needed to comply with a law. The RBI's KYC Directions for NBFCs require identification records to be kept for at least five years after the business relationship ends, and transaction records for five years from each transaction.
In co-lending, who is the data fiduciary under DPDP?
Usually each lender, because each decides to lend and holds a share of the loan. The DPDP Act's definition of a Data Fiduciary covers parties that decide the purpose and means of processing together with others. The contracts should say who handles notices, rights requests and breach reports. Our partner law firm confirms the roles for a given arrangement.
Is a lending service provider a data processor under DPDP?
Often, when it sources and services loans only for the lender. If it also uses borrower data for its own purposes, it may be a Data Fiduciary for that use. Separately, the RBI's rules limit what an LSP may store to basic minimal data, such as name, address and contact details.
