4 min read

DPDP Vendor Onboarding Checklist For Enterprise Compliance Teams

A step-by-step checklist for enterprise compliance heads to evaluate B2B SaaS vendors and secure DPDP Act 2023 compliance before signing.

Written byVipul Abhishek· Former Advocate, Supreme Court of India

Last updated:

When To Use This Checklist

Enterprise compliance teams face maximum exposure through their vendor supply chain. Section 8(1) of the Digital Personal Data Protection Act, 2023 makes the Data Fiduciary liable for any processing undertaken by a Data Processor on its behalf. You cannot outsource regulatory liability.

Use this checklist when onboarding a new B2B SaaS vendor or renewing an existing procurement contract. Exactly 219 days remain until the DPDP hard compliance deadline of 13 May 2027. You need a structured approach to evaluate vendor readiness before giving procurement the green light.

Prerequisites For Vendor Assessment

You need a baseline record of processing activities before evaluating a third party. Document the specific categories of personal data the vendor will handle. Identify the control owner within your procurement or compliance team. Ensure you have a standardized vendor risk assessment template ready for deployment.

Step By Step Vendor Checklist

1. Map the data flow. Owner: IT Security. Action: Document how personal data moves from your systems to the vendor environment. Evidence: Approved data flow diagram.

2. Execute a valid contract. Owner: Legal. Action: Draft an agreement enforcing Section 8(2) requirements for processing personal data. Evidence: Signed DPDP vendor addendum.

3. Verify sub-processor dependencies. Owner: Procurement. Action: Require the vendor to list all third parties processing your data. Evidence: Maintained sub-processor registry.

4. Test breach intimation workflows. Owner: Incident Response. Action: Set strict timelines for the vendor to report security incidents to your team. Evidence: Contractual SLA ensuring immediate notification.

5. Map data principal rights. Owner: IT. Action: Verify the vendor can locate and delete specific user records when a Data Principal withdraws consent. Evidence: Documented erasure procedure.

6. Review retention limits. Owner: Compliance. Action: Confirm the vendor automatically purges data when the business purpose concludes. Evidence: Data retention schedule and deletion certificates.

7. Secure audit rights. Owner: Legal. Action: Ensure the contract permits your enterprise to audit the vendor for DPDP compliance. Evidence: Executed audit clause.

8. Assess cross-border transfers. Owner: Compliance. Action: Check if the vendor routes data outside India and verify the destination is not restricted by the Central Government. Evidence: Server location registry.

DPBI Breach Intimation Requirements

A vendor security failure becomes your regulatory problem immediately. The DPDP Rules, 2025 require the Data Fiduciary to intimate the Data Protection Board and affected Data Principals without delay. You must submit a detailed report to the Board within 72 hours.

Your vendor contracts must force processors to report incidents to you well before this 72-hour window expires. A 48-hour vendor SLA leaves your internal team only 24 hours to draft and file the regulatory notice.

Effort And Budget Reality

Manual vendor risk assessments take 10 to 15 hours per contract. Your legal team must review redlines, track consent sync mechanisms, and chase security questionnaires. This creates a massive bottleneck for enterprise procurement.

Tooling changes this equation. Automated platforms issue standard DPDP questionnaires and flag non-compliant contract clauses instantly. Budget for a centralized vendor compliance platform if your enterprise manages more than 20 external processors.

Documentation Pack Required For Audit

Auditors will request specific artefacts to prove supply chain compliance. You must produce the updated vendor addendum template. Retain the completed vendor risk assessments for every processor. Maintain a live dashboard mapping which vendor holds what data and the corresponding legal basis for processing.

Red Flags Before Signing

Reject vendors who refuse to sign an India-specific DPDP addendum. A generic global privacy policy fails to meet the specific requirements of the Act. Walk away if the vendor cannot guarantee data deletion upon contract termination.

Treat any refusal to accept strict breach notification SLAs as a critical risk. If a vendor insists on a 72-hour reporting window to you, they guarantee your enterprise will miss the statutory deadline to notify the Board.

Next Steps

Stop guessing your vendor exposure. Run a free scan at https://www.complydp.com/audit-preview to baseline your vendor contracts and identify critical supply chain gaps today.

Sources

Frequently asked questions

Is the enterprise liable if a vendor breaches the DPDP Act?

Yes. Section 8(1) of the DPDP Act makes the Data Fiduciary responsible for compliance regarding any processing undertaken by a Data Processor on its behalf.

What must be included in a vendor contract under DPDP 2023?

Section 8(2) requires a valid contract between the Fiduciary and Processor. This should include data retention limits, audit rights, breach notification SLAs, and procedures for executing Data Principal rights.

How fast must a vendor report a data breach?

The Rules, 2025 require Data Fiduciaries to submit a detailed report to the DPBI within 72 hours. Vendors must report breaches to the Fiduciary much faster than 72 hours to allow time for this regulatory filing.

Can vendors transfer Indian personal data outside India?

Yes, cross-border transfers are generally permitted. The Central Government may restrict transfers to specific notified countries or territories, so vendor server locations must be documented.

How much time does a manual vendor DPDP assessment take?

A manual review of data flows, sub-processors, and contract redlines typically takes 10 to 15 hours per vendor. Enterprises scaling their procurement process should budget for compliance automation.