Vendors and processors
A processor may handle personal data only under a valid contract, and the data fiduciary stays responsible for what its processors do.
Reviewed 16 September 2026Educational self-assessment content, not legal advice
- Requirements
- 3
- Must-do
- 1
- Penalty ceiling
- Up to ₹50 crore
Breach of any other provision. This is a statutory maximum the Data Protection Board applies case by case, never a predicted fine. 1 of these requirements are in the quick check.
What we assess in this area
- MustIn the quick checkVEN-01
A valid contract with every processor
You may use a processor to handle personal data for you only under a valid contract. You stay responsible for what the processor does with that data. The contract should set out what they may and may not do.
What good looks like
Every processor that touches personal data has a signed contract. It covers purpose limits, security, breach reporting, erasure, sub-processors and audit rights. Contracts are tracked and renewed on time.
How to get there
List every vendor that handles personal data for you. Check that each has a signed contract. Add a standard data protection clause set. Track renewal dates and fix gaps with the riskiest vendors first.
- ShouldVEN-02
Processors are checked before onboarding and reviewed periodically
The law places overall responsibility on you, even when a processor does the work. That means you should check a processor can protect the data before you share it. You should also keep checking over time.
What good looks like
Every new processor passes a privacy and security check before it receives data. Existing processors are reviewed on a set cycle based on risk. Findings are tracked and closed.
How to get there
Create a short due diligence questionnaire. Use it before signing any new processor. Rate existing processors by risk. Review high risk processors every year and record the results.
- ShouldVEN-03
Sub-processors are visible and approved
Processors often pass data to their own vendors. You remain responsible for that data wherever it goes. You need to know who these sub-processors are and control whether they can be used.
What good looks like
You hold a current list of sub-processors for each processor. Contracts require your approval, or at least advance notice, before a new one is added. The same duties flow down to every sub-processor.
How to get there
Ask each processor for its sub-processor list. Record it against the processor. Add approval or notice terms to contracts. Check that security and erasure duties pass down to each sub-processor.
Other areas we assess
Related guides
- DPDP Act 2023 requirements for businesses, in plain EnglishDPDP Act 2023 requirements explained for Indian businesses: scope, data fiduciary duties, consent, notice, rights and penalties, and what is in force in 2026.Read the guide
- The DPDP Rules 2025 and what they addDPDP Rules 2025 explained: notice wording, consent managers, security safeguards, breach reporting, erasure, children and transfers, with commencement dates.Read the guide
- DPDP compliance checklistFree DPDP compliance checklist for 2026: 73 requirements across 13 areas, mapped to the Act and Rules, with priority and evidence columns you can score.Read the guide
Check this area against your own business
The free assessment scores this area with the rest and shows you where it ranks against your other gaps.
The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer
A free self-assessment tool for educational use. Not legal advice.