Generate a signature-ready DPA for any vendor in 3 minutes. Covers every Rule 6(f) mandatory item — data categories, purpose, security mandate, breach SLA under 48 hours, erasure-on-instruction, sub-processor approval and audit rights.
Why this matters
DPA absence is the cheapest violation to find — and the most expensive to fix in court
Direct Section 8(2) exposure
Sharing personal data with a processor without a DPA is processing without lawful basis — immediate ₹50 cr cap exposure under Schedule 1, and joint liability when the processor breaches.
DPAs flow down to sub-processors
Rule 6(f) requires equivalent obligations on every sub-processor your vendor uses. The DPA template below includes the sub-processor approval clause that makes this enforceable.
Common questions
FAQ
What is a DPA?
A Data Processing Agreement is a contract between a Data Fiduciary (you) and a Data Processor (your vendor). Section 8(2) of the DPDP Act and Rule 6(f) require one before processing personal data through any vendor.
Is this DPA enforceable?
Yes — the output is a standard contractual template covering all Rule 6(f) mandatory items. Both parties must sign it. Have your counsel review before signing if the vendor relationship is high-value or high-risk.
Which vendors need a DPA?
Every vendor that processes personal data on your behalf — cloud (AWS / GCP / Azure), email (SES, SendGrid), CRM (HubSpot, Zoho), analytics (GA4, Mixpanel), payment (Razorpay, Stripe), KYC providers, courier and SMS vendors. If they touch any data about your users, they need a DPA.
What if a vendor refuses to sign?
Most major vendors publish their own DPA — sign theirs (verify it covers Rule 6(f)). For vendors that refuse and have no published DPA, you have an immediate Section 8 exposure — move to a vendor that will sign one.