Fintech Data Sharing: Loan Apps, Consent and Grievance Records
A fintech data-sharing control covering loan apps, need-based collection, mobile permissions, fund flows, LSP contracts and grievance evidence.
A loan app should not collect a customer’s contact list, files and call logs merely because the phone permits it.
The DPDP framework is phased. The 14 November 2025 commencement notification brought specified institutional and enabling provisions into force immediately; section 6(9), section 27(1)(d) and rule 4 follow after one year; most operating duties and rules follow eighteen months after Gazette publication. As of 22 June 2026, readiness should distinguish current law from future-state DPDP controls.
RBI’s digital-lending framework places responsibilities on regulated entities for their lending service providers and apps.
Data collection should be need-based, consented and auditable, with restrictions and expectations around mobile-resource access.
Disbursal and repayment should generally flow directly between borrower and regulated entity accounts, subject to specified exceptions.
What the organisation should understand
- The DPDP framework is phased. The 14 November 2025 commencement notification brought specified institutional and enabling provisions into force immediately; section 6(9), section 27(1)(d) and rule 4 follow after one year; most operating duties and rules follow eighteen months after Gazette publication. As of 22 June 2026, readiness should distinguish current law from future-state DPDP controls.
- RBI’s digital-lending framework places responsibilities on regulated entities for their lending service providers and apps.
- Data collection should be need-based, consented and auditable, with restrictions and expectations around mobile-resource access.
- Disbursal and repayment should generally flow directly between borrower and regulated entity accounts, subject to specified exceptions.
- DPDP readiness should integrate with RBI disclosure, consent, grievance, retention and vendor requirements.
The five-point review
| Check | What to examine |
|---|---|
| Entity | Bank/NBFC, LSP, DLA and vendor. |
| Data | Identity, financial, device and permission. |
| Purpose | Underwriting, servicing, fraud or collection. |
| Flow | Who receives data and money. |
| Grievance | Lender, nodal officer and evidence. |
Practical example
A lending app requests contacts and media and sends data to an unreviewed analytics SDK. The lender must challenge necessity, permission design and downstream sharing.
How to apply the framework
Maintain a lender-approved data field, permission and SDK catalogue.
Keep borrower-level consent and sharing evidence so the regulated entity can answer complaints without relying entirely on the LSP.
Operating workflow
Define the processing or incident precisely
Identify the people, data, system, purpose, owner, vendor and transaction or event. Review entity, data and purpose together. Do not start from a policy template or software feature; start from what the business and system actually do.
Separate current duties from future-state DPDP readiness
Apply the 14 November 2025 commencement notification provision by provision. Continue complying with currently operative IT, CERT-In, telecom, banking, insurance, employment, consumer, contract and criminal-law requirements. Build the future DPDP process now, but do not describe a scheduled rule as already legally operative.
Preserve proof and improve the system
Keep the approved decision, notice or workflow version, access or event logs, vendor evidence, user communications and remediation record. Update product design, role access, retention, support scripts or incident playbooks so the same weakness does not recur.
Action checklist
- Map roles.
- Approve fields and permissions.
- Control SDKs.
- Maintain consent evidence.
- Keep direct fund flows.
- Operate lender-visible grievances.
Evidence to keep
- LSP agreement
- Permission inventory
- Consent logs
- Sharing records
- Grievance file
Warning signs
- Contact-list access by default
- Lender cannot name sub-vendors
- Pass-through repayment
- Vendor-only grievance
- Collection messages to contacts
Finin2min takeaway
Privacy governance is an operating system, not a policy PDF. The data map, purpose, access, vendor, retention, user workflow, incident response and evidence file must all tell the same story.