Skip to main content

The 3rd and main DPDP commencement date is computed as 13 May 2027, which is interpretation until officially confirmed.

Sources last verified on 28 October 2026. Methodology

DPDP DPA clauses: requirements versus good drafting

Vendors

By · Primary sources verified by dpdprules.orgPublished · Last reviewed 9 min read

Jump to sources

What clauses need to be included in a Data Processing Agreement (DPA) under the DPDP Act?

The short answer

Not yet. When the relevant provisions commence, section 8(2) will permit a Data Fiduciary to involve a Data Processor only under a valid contract when the processing is on its behalf for an activity related to offering goods or services to Data Principals. Rule 6(1)(f) is the only express content requirement found for that fiduciary to processor contract: wherever applicable, it must contain an appropriate provision for taking reasonable security safeguards. Sections 6(6), 8(1) and 8(7) place duties on the fiduciary; contract terms can operationalise them, but those sections do not prescribe clauses. Instructions, confidentiality, subprocessor approval, processor audit rights, return, indemnity and a processor notice window are recommendations, not express DPA terms. Neither instrument fixes a processor to fiduciary breach deadline. Rule 7 instead places the without delay and 72 hour Board duties on the fiduciary. Section 17 can disapply some Act duties, while sections 8(1) and 8(5) survive a section 17(1) route. The operative contract conditions and fiduciary duties discussed are in 18 month groups. This site computes 13 May 2027 and treats 15 May 2027 as the outer date because official publication records and counting can each move the date by a day. Both dates are interpretation until officially confirmed.

More answered questions →

Diagram: DPDP processor contract: 2 express points, then recommendations. The same diagram appears further down this article, where it is described in full.

Status as at 27 October 2026: the provisions shown are not in force; they sit in 18 month groups, computed 13 May 2027, may fall as late as 15 May 2027, and the dates are interpretation until officially confirmed.

As at 27 October 2026, no DPDP processor contract rule discussed here binds yet. When the relevant provisions commence, the framework will have one scoped valid contract condition and one express clause content rule. The familiar longer lists mix those propositions with operational recommendations. This article separates the layers. For the prior question of whether a contract is required, see do you need a contract with your Data Processor.

Start with what a Data Processor is

Section 2(k) defines a Data Processor as "any person who processes personal data on behalf of a Data Fiduciary". Section 8(1) then addresses the fiduciary's responsibility for processing undertaken by it or on its behalf by a processor:

DPDP Act 2023, s. 8, (1) · General obligations of Data Fiduciary · verbatim

"A Data Fiduciary shall, irrespective of any agreement to the contrary or failure of a Data Principal to carry out the duties provided under this Act, be responsible for complying with the provisions of this Act and the rules made thereunder in respect of any processing undertaken by it or on its behalf by a Data Processor."

A contract cannot displace that section 8(1) responsibility where the provision applies. Contract terms, instructions and system design are practical mechanisms for obtaining the processor's help; they are not substitutes for the fiduciary's duty. Whether section 4(1), which uses the wider word "person", directly binds a processor acting only on instructions remains an interpretation question. The Data Processor obligations guide owns that processor side analysis.

Decision map headed "DPDP processor contract: 2 express points, then recommendations". A status band says that as at 27 October 2026 the provisions shown are not in force. The first panel states that section 8(2) permits a processor only under a valid contract when the processing is on the fiduciary's behalf for an activity related to offering goods or services to Data Principals. It also states that Rule 6(1)(f), wherever applicable, requires an appropriate safeguards provision. The second panel labels section 8 as a group and specifically lists sections 6(6), 8(1), 8(3), 8(5), 8(6), 8(7), sections 11 to 13, Rule 7 and Rule 8 as fiduciary duties rather than prescribed clauses. It says section 17 can change which Act duties apply, while sections 8(1) and 8(5) survive a section 17(1) route. The third panel labels instructions, confidentiality, subprocessor approval, processor audit rights, return, indemnity, processor notice windows and cross border cooperation as recommendations. The footer says the 18 month groups compute to 13 May 2027 and may fall as late as 15 May 2027, interpretation until officially confirmed.

Open the processor contract map at full size.

The 2 express contract points

Two propositions about the fiduciary to processor contract are express.

  1. A valid contract is a condition in the scope section 8(2) names. A Data Fiduciary may involve a processor to process personal data on its behalf for an activity related to offering goods or services to Data Principals "only under a valid contract". The Act does not define valid contract or prescribe a clause list.

  2. The contract carries a safeguards provision wherever applicable. Rule 6(1)(f) includes "appropriate provision in the contract entered into between such Data Fiduciary and such a Data Processor, wherever applicable, for taking reasonable security safeguards". A whole text comparison found this to be the only express content requirement for that section 8(2) contract.

Section 17 can change whether section 8(2) applies. That qualification is considered below. It does not change the wording of the 2 contract points.

Fiduciary duties that may motivate clauses

The following provisions place duties on the fiduciary. A negotiated clause may help operate them, but the provision does not itself prescribe that clause.

Cessation after consent withdrawal. Section 6(6) requires the fiduciary, within a reasonable time, to cease and cause its processors to cease after withdrawal, unless processing without consent is required or authorised by the Act, the Rules or another law in force. A processor instruction term is a recommendation tied to that result.

Erasure after the section 8(7) trigger. Subject to retention necessary for compliance with law, section 8(7)(a) triggers erasure on consent withdrawal or when it is reasonable to assume the specified purpose is no longer served, whichever is earlier. Section 8(7)(b) then requires the fiduciary to cause its processor to erase the personal data made available for processing. An erasure instruction and evidence term is a recommendation.

Breach support. Section 8(6) and Rule 7 place the intimation duties on the fiduciary. Rule 7 requires affected Data Principal and initial Board intimations without delay, then the 6 listed detailed items for the Board within 72 hours unless it allows longer on written request. A processor detection, notice and evidence term creates a practical route for the fiduciary to meet those clocks where they apply. Neither instrument fixes the processor's notice deadline.

Security in practice. Section 8(5) requires safeguards for processing undertaken by the fiduciary or on its behalf by a processor. Rule 6 lists minimum measures and, through Rule 6(1)(f), adds the express contract provision wherever applicable. The provision is one measure inside the wider safeguards duty, not proof that every appropriate safeguard has been taken.

The Rule 8(3) retention and erasure sequence. Without prejudice to Rule 8(1) and (2), Rule 8(3) requires the fiduciary to retain the specified personal data, associated traffic data and other processing logs for at least 1 year from processing for the Seventh Schedule purposes. It then requires erasure unless further retention is required by another law or notified by the Government. The cloud provider illustration applies that sequence to processing on behalf of the fiduciary. Contract support for that bounded sequence is a recommendation, not a general 1 year DPA clause.

Accuracy support. Section 8(3) applies where personal data is likely to be used to make a decision affecting the Data Principal or disclosed to another Data Fiduciary. It makes the fiduciary ensure completeness, accuracy and consistency. Processor correction support is a recommended way to operate that duty.

Rights and grievance support. Sections 11 and 12 carry previous consent scope and their own exceptions. Section 13 addresses grievance redressal by a Data Fiduciary or Consent Manager. A processor assistance term can support access, correction and erasure outcomes, but none of those sections prescribes a processor clause. The grievance redressal guide owns the separate Rule 14(3) interpretation.

Section 17 can change the duty map

Before turning any duty into a clause, test section 17. When a section 17(1) condition applies, Chapter II except sections 8(1) and 8(5), Chapter III and section 16 do not apply. That can remove section 6(6), section 8(2), section 8(7) and the rights duties from a processing flow while preserving the fiduciary's section 8(1) responsibility and section 8(5) safeguards duty.

Clause 17(1)(d), the overseas client route, requires both personal data of Data Principals outside India and processing under a contract with a person outside India by a person based in India. An overseas customer alone is not enough. Other section 17 sub sections have different scopes, so the exemptions guide should be applied provision by provision.

Section 17 names provisions of the Act. It does not state how an Act exemption affects related Rules. Any conclusion that a Rule automatically switches off is therefore interpretation, not the printed text.

Prudent drafting the statute never asks for

The following are recommendations for the fiduciary to processor DPA. The processor contract checklist template includes them as controls, but the Act and Rules do not prescribe them as those contract terms.

  • Documented instructions and confidentiality. No provision prescribes either as a Data Processor DPA term. Both can define and control the service.
  • Subprocessor approval and flow down. No Data Processor subprocessor approval term is prescribed. The First Schedule separately bars a Consent Manager from sub contracting or assigning its obligations; that is a different role and rule.
  • Processor audit and inspection rights. No provision grants a fiduciary an audit or inspection right against its processor or requires that DPA term. The framework does require audits in other contexts, including Significant Data Fiduciaries and Consent Managers, so the negative is deliberately narrow.
  • A processor notice deadline. Neither instrument fixes a processor to fiduciary breach deadline. Rule 7(2)(b)'s 72 hour deadline is the fiduciary's deadline to the Board. A shorter processor window is negotiated protection.
  • Return of data on exit. Section 8(7)(b) speaks of erasure, not return. Return in a usable format is a negotiated term.
  • Indemnity and liability allocation. An agreement cannot displace section 8(1) where it applies. Indemnity can allocate contractual financial risk without transferring the statutory duty.
  • Cross border cooperation. Rule 15 puts on the fiduciary any Government requirements about making personal data available to a foreign State, or to a person or entity under the control of or an agency of such a State. Processor cooperation is a recommendation prompted by that rule, subject to the section 17 analysis.

The clause list, mapped

QuestionBasis in the official textClaim type
Is a valid contract required?Section 8(2), only in its stated processor activity scope and subject to section 17Official condition
What contract content is express?Rule 6(1)(f), an appropriate safeguards provision wherever applicableOfficial requirement
Do sections 6(6), 8(1), 8(3), 8(5), 8(6) and 8(7) prescribe clauses?They place scoped duties on the fiduciaryOfficial duties; contract implementation is recommendation
Does Rule 8(3) prescribe a general retention clause?It creates the bounded Seventh Schedule retention and erasure sequenceOfficial fiduciary duty; contract support is recommendation
Do sections 11 to 13 prescribe processor support?They create scoped rights and fiduciary or Consent Manager dutiesOfficial duties; processor support is recommendation
Is a processor notice window fixed?No; section 8(6) and Rule 7 place their clocks on the fiduciaryExplanation from a whole text comparison
Are instructions, confidentiality, subprocessor approval, processor audit rights, return and indemnity prescribed DPA terms?No Data Processor DPA provision prescribes themRecommendation, scoped to this contract
Is cross border cooperation prescribed as a DPA term?Rule 15 can require fiduciary compliance with a Government order, subject to section 17Recommendation prompted by Rule 15

Timing and next steps

The operative contract conditions and fiduciary duties discussed here sit in 18 month groups; section 2(k)'s definition is already in force. Counting from the printed 13 November 2025 date gives 13 May 2027. The official eGazette file code and recorded listing use 14 November 2025, and the instruments do not state how the period is counted, so the date may fall as late as 15 May 2027. These dates are interpretation until officially confirmed.

Use the time to identify each processor relationship, test whether section 8(2) covers the activity and whether section 17 changes the result, then draft the controls the relationship needs. Run each vendor through the vendor and processor checklist, fold the results into a tracked plan with the company compliance plan tool, and read the official text at section 8. For the shorter contract decision, see what must be in processor contracts.

Processor contract checklist template →Section 8, official text →DPDP processor contracts: what must be in them →DPDP for legal and privacy counsel →

ContractsData ProcessorVendorsDPA

Share this: