What must your CRM vendor contract include under DPDPA?
November 17, 2026
A DPDPA-ready CRM vendor contract must appoint the vendor as your Data Processor under Section 8(2), limit it to processing only on your instructions, bind it to the Rule 6 security safeguards, require prompt breach alerts so you can meet the 72-hour Rule 7 report, control sub-processors and cross-border transfers, and force erasure when consent is withdrawn or the purpose ends.
Every Indian sales team that uses a SaaS CRM has, in law, handed its customers' personal data to a third party. Under the Digital Personal Data Protection Act, 2023 (DPDPA), that third party is a Data Processor, and the contract you signed with it is now a compliance document. The DPDP Rules were notified on 14 November 2025; Rule 4 on Consent Manager registration came into force on 13 November 2026; and the remaining obligations, including penalties, apply from 13 May 2027. That leaves six months to fix paperwork most sales and IT teams have never read.
In this guide we set out what the Act and the Rules require of a CRM vendor contract, the ten clauses we look for when we review one, and how to close the gaps before May 2027.
Section 8(1) is blunt: a Data Fiduciary is responsible for complying with the Act "irrespective of any agreement to the contrary", including for processing undertaken on its behalf by a Data Processor. If your CRM provider suffers a breach, uses your leads for its own analytics or keeps records after you have deleted them, the Data Protection Board will look to you, not to the vendor.
Section 8(2) then says you may engage a Data Processor "only under a valid contract". The Act does not list the clauses, but other provisions fill in what the contract must make possible: security safeguards under Rule 6, breach reporting under Rule 7, erasure under Section 8(7), cessation of processing on consent withdrawal under Section 6(6), and disclosure of the processors you share data with when a customer exercises the right to access under Section 11. A contract that cannot deliver these leaves you exposed to penalties of up to ₹250 crore for failing to take reasonable security safeguards.
It depends on who decides the purpose and means of processing. When your team decides which leads to capture, why and for how long, and the vendor merely hosts and runs the software, the vendor is your Data Processor. If the vendor also uses your contact data to train its own models, enrich other customers' databases or market its products, it is deciding purposes of its own, which makes it a Data Fiduciary for that processing, with its own consent and notice duties.
Most standard SaaS terms blur this line. The single most valuable clause in a renegotiation is often the one that says the vendor processes personal data only on your documented instructions and for no purpose of its own.
This is the checklist we use when we review CRM and sales-tool agreements for Indian clients. Each row maps to the provision that makes it necessary.
| Clause | What it should say | Why (DPDPA / DPDP Rules) |
|---|---|---|
| 1. Role and purpose | Vendor is a Data Processor, acting only on your documented instructions; no use for its own purposes | Section 8(1), Section 8(2) |
| 2. Security safeguards | Encryption, access control, logging, backups and continuity measures, with the right to review them | Section 8(5), Rule 6(1)(a)–(d), (f) |
| 3. Logs and retention of logs | Access and processing logs kept for at least one year and shared on request | Rule 6(1)(e) |
| 4. Breach notification | Vendor alerts you without delay (we recommend a fixed window such as 24 hours) with the facts you need | Section 8(6), Rule 7 (72-hour detailed report) |
| 5. Consent withdrawal | Vendor stops processing a contact's data when you pass on a withdrawal | Section 6(6) |
| 6. Erasure and return | Deletion on instruction, at purpose end and at contract exit, with written confirmation | Section 8(7), Rule 8 |
| 7. Sub-processors | List of sub-processors, prior notice of changes, same obligations flowed down | Section 8(1), Section 11(1)(b) |
| 8. Data location and transfers | Where data is stored and processed; compliance with any Government restriction on transfers | Section 16, Rule 15 |
| 9. Data Principal requests | Vendor helps you answer access, correction and erasure requests within your timelines | Sections 11–13, Rule 14 |
| 10. Audit, cooperation and liability | Audit rights, cooperation with the Board, and indemnity matched to the real exposure | Section 8(1), Section 33 and Schedule |
Rule 6(1) lists the minimum reasonable security safeguards: encryption, obfuscation, masking or virtual tokens; access control; visibility through logs, monitoring and review; continuity measures such as backups; one-year log retention; contractual provisions with processors; and organisational measures that make all of this effective. We covered the engineering side in our guide on what Rule 6 asks a CTO to build. For a CRM contract, three points matter most.
The Act requires you, as the Data Fiduciary, to inform the Board and each affected Data Principal of a personal data breach (Section 8(6)). Rule 7 asks for an intimation without delay and a detailed report to the Board within 72 hours of becoming aware of the breach, or a longer period if the Board allows. If your systems also fall under the CERT-In Directions of 28 April 2022, the six-hour CERT-In reporting window applies in parallel.
You cannot meet either clock if your vendor takes a week to tell you. The contract should define "breach" broadly, set a short notification window, and list the information the vendor must provide: what happened, which data and how many contacts, the likely impact, and what has been done to contain it.
Section 6(6) requires you, on withdrawal of consent, to cease processing within a reasonable time and to cause your processors to cease as well. Section 8(7) requires erasure once the purpose is no longer served, and again you must cause your processor to erase. In a CRM, that means the vendor must be able to delete a single contact across the main database, activity history, attachments, integrations and, within a defined period, backups. It also connects with retention: see our earlier pieces on how long a CRM may keep personal data and on fresh consent for existing CRM contacts.
Exit is the other half. Specify the export format, the time you have to retrieve your data, and a certified deletion date after termination. A vendor that cannot commit to these in writing is a red flag.
We built QQCRM, our AI CRM accelerator, so that consent status, purpose and retention travel with each contact record, and DAPro (Data Adhikaar) manages notices in 22 languages, consent and rights requests, with a tamper-evident Evidence Vault and 25+ connectors to the systems where your data already lives. If you would like a second pair of eyes on your CRM and sales-tool contracts, book a 30-minute call with our team.
Usually, yes. If your company decides why and how contact data is collected and used, and the vendor only hosts and runs the CRM on your instructions, the vendor is your Data Processor under Section 2(k). If the vendor uses your data for its own purposes, such as training its own models or marketing, it acts as a Data Fiduciary for that processing.
Yes. Section 8(2) allows a Data Fiduciary to engage a Data Processor only under a valid contract, and Rule 6(1)(f) expects reasonable security safeguards to be written into that contract. The Act does not prescribe a template, so the contract should cover role, security, breach alerts, erasure, sub-processors, transfers and audit rights.
Your company remains responsible. Section 8(1) makes the Data Fiduciary responsible for processing done on its behalf by a Data Processor, irrespective of any agreement to the contrary. Penalties for failing to take reasonable security safeguards can reach ₹250 crore, so the contract should give you breach alerts, cooperation and an indemnity that reflects that exposure.
The DPDP Rules require the Data Fiduciary to inform the Board without delay and file a detailed report within 72 hours of becoming aware of a breach. Your vendor contract should therefore set a much shorter window, such as 24 hours, and list the facts the vendor must share so you can meet that deadline.
The DPDP Rules were notified on 14 November 2025. Most substantive obligations, including Section 8 duties and Section 33 penalties, apply from 13 May 2027. Renegotiating CRM and sales-tool contracts takes time, so companies should begin the inventory and gap-check now rather than in the final quarter.
This article is for general information and is not legal advice. Confirm obligations against the official texts of the DPDP Act 2023 and the DPDP Rules 2025, and consult qualified counsel for your situation.
Monthly insights on AI, VR and DPDPA compliance — straight from our team to your inbox.
Free 30-minute consultation with our team — or see our products in action.