← All news and guides
Data protection

DPDP for SaaS Companies Acting as Data Processors: What Your Customers Will Ask

If your SaaS holds customer data, you are usually its Data Processor. What DPDP puts on your customers, what reaches you by contract, and the evidence.

Mono Team ·

A long shared desk in a Pune software office at dusk, two closed laptops and a printed contract with a pen on it, rain streaks on the window behind.

If your SaaS product stores or handles personal data for your customers, you are usually their Data Processor under the DPDP Act. The Act puts almost every duty on the customer, the Data Fiduciary. Those duties reach you through the contract: security safeguards, breach notice, deletion, one-year retention and control of your own vendors. From 13 May 2027 your customers have to be able to show those duties work, so they will ask you to prove it.

This post explains the two roles, what the Act and Rules actually say about processors, what customers put in contracts and questionnaires, and the engineering evidence that answers each ask. If you sell to banks, read the companion post on DPDP for SaaS selling to Indian banks, because RBI rules add a second layer.

Is my SaaS a Data Processor under DPDP?

The Act has two definitions that decide this:

  • Data Fiduciary: any person who, alone or with others, "determines the purpose and means of processing of personal data" (Section 2(i)).
  • Data Processor: any person "who processes personal data on behalf of a Data Fiduciary" (Section 2(k)).

The test is who decides why the data is processed. When your customer loads its own customers' or employees' records into your product, it decides why. You process the data on its behalf. For that data you are its Data Processor.

When a SaaS company is both

One company is often both a Fiduciary and a Processor, for different data. A typical B2B SaaS looks like this:

DataYour usual roleWhy
Records your customer uploads or creates in the product (its end users, patients, borrowers, staff)Your usual role: Data ProcessorWhy: You process it on the customer's behalf, for the customer's purposes
Admin and user accounts of the people who log in for your customerYour usual role: Often both; depends on the contractWhy: You need it to run the service for the customer, and may also use it for your own billing, security or product emails
Your marketing leads, newsletter list and website analyticsYour usual role: Data FiduciaryWhy: You decide why you collect it
Your own employees and job applicantsYour usual role: Data FiduciaryWhy: You decide why you collect it
Customer data you use for your own purposes, such as training a model or building benchmarksYour usual role: Possibly Data Fiduciary for that useWhy: You may be deciding a new purpose. Get legal advice before you do this

For the data where you are the Fiduciary, all the Fiduciary duties are yours: notices, consent, rights requests, security, breach reporting and retention. Our guide to the DPDP Act explained covers them. The last row of the table is where SaaS companies most often blur the line. Whether a particular use makes you a Fiduciary is a legal question, and the answer changes what your contract has to say.

What the Act puts on your customer, and how it reaches you

A printed contract lying open on a wooden table with a pen across it, a closed laptop beside it, in soft late-afternoon light.

Section 8 is headed "General obligations of Data Fiduciary". Each duty below is written for your customer. Each one covers the processing you do for it, so your customer needs you to carry it out.

  • It stays responsible for you. The Fiduciary is responsible for complying with the Act and Rules for any processing done on its behalf by a Data Processor, "irrespective of any agreement to the contrary" (Section 8(1)). It cannot contract that duty away to you.
  • It needs a valid contract with you. A Fiduciary may use a Data Processor for any activity related to offering goods or services to people "only under a valid contract" (Section 8(2)).
  • Its security safeguards must cover you. It must protect personal data, including processing done by a Data Processor, with reasonable security safeguards to prevent a breach (Section 8(5)). Rule 6 sets the minimum, and Rule 6(1)(f) requires security terms in the processor contract, where applicable.
  • It must report breaches. It must tell the Data Protection Board and each affected person about a personal data breach (Section 8(6)). Rule 7 sets the timing: without delay, and a detailed report to the Board within 72 hours of becoming aware of the breach.
  • It must make you stop and delete. When someone withdraws consent, it must cease, and cause its Data Processors to cease, processing their data (Section 6(6)). When consent is withdrawn or the purpose is over, it must cause its Data Processor to erase the data it gave you, unless a law requires it to be kept (Section 8(7)).
  • It must keep data and logs for a year first. Rule 8(3) requires personal data, traffic data and processing logs to be kept for at least one year, including for processing done by a Data Processor. The Rule's own example is a company that must ensure its cloud provider keeps the data and logs for a year before erasure.
  • It must be able to name you. A person can ask a Fiduciary for the identities of all Data Processors it has shared their data with (Section 11(1)(b)).

Penalties follow the same pattern. The Schedule's highest penalties, up to ₹250 crore for failing to take reasonable security safeguards and up to ₹200 crore for failing to report a breach, are for breaches of the Fiduciary's duties. That is why customers push the work down to you through contracts: they carry the penalty if your systems fail. Whether a processor faces any direct exposure under the Act is a question for your lawyers.

What the Act and Rules do not say

On our reading of the texts as notified, several things customers ask for are not in the law itself. They come from the contract:

  • No deadline for a processor to tell the customer about a breach. Rule 7 starts the customer's clock when it becomes aware. So customers set a notice period for you in the contract, and it is often short.
  • No rule on sub-processors. The Act does not mention a processor using its own processors. Customers still need to know about yours, because Section 8(1) holds them responsible for the whole chain, and Section 11(1)(b) may require them to name processors.
  • No list of contract clauses. Section 8(2) says "valid contract". Rule 6(1)(f) adds security terms. The rest is up to the parties.
  • No DPDP certificate. The Act and Rules do not set one up for companies or vendors. An ISO 27001 certificate or a SOC 2 report helps with security questions, but neither shows DPDP compliance.

What customers will put in the contract

Customers usually add a data processing agreement, or a DPDP addendum to an existing one. The clauses typically cover:

  • Instructions. You process the customer's personal data only for its purposes and on its documented instructions.
  • Security. Reasonable security safeguards, often listed against Rule 6: encryption or masking, access control, logging and monitoring, backups.
  • Breach notice. A fixed number of hours for you to tell the customer, what the notice must contain, and how you will help it report to the Board.
  • Sub-processors. A list of your vendors that touch its data, notice before you add one, and the same terms passed down to them.
  • Withdrawal and erasure. How you stop processing when told to, how you erase at the end of the purpose or contract, and how you confirm it.
  • Retention. At least one year for data and logs under Rule 8(3), then deletion, unless another law requires longer.
  • Rights requests. Help finding, correcting and erasing one person's data when the customer gets a request.
  • Location and transfers. Where the data is stored and processed. Section 16 lets the Government restrict transfers to particular countries by notification, and sector rules may be stricter.
  • Audit and evidence. The customer's right to ask for records, questionnaires or an audit.

Contract wording is legal work. Our partner law firm reviews it. What engineering decides is whether you can actually do what each clause promises.

SaaS DPDP compliance checklist: the asks and the evidence

Overhead view of a desk with neat stacks of printed pages held by binder clips, a notebook and a cup of chai, under warm lamp light.

A questionnaire turns each clause into a question. The table below matches the common asks to what the law rests on and the engineering evidence that answers them. Customers check evidence, so build the records, not just the answers.

What the customer asksWhat it rests onEngineering evidence to have ready
What personal data of ours do you hold, where, and why?What it rests on: Sections 8(1), 8(2)Engineering evidence to have ready: A data map per customer: tables, buckets, logs, warehouse copies, search indexes and support tickets that hold its data
Who are your sub-processors, and what does each get?What it rests on: Sections 8(1), 11(1)(b)Engineering evidence to have ready: A sub-processor register: vendor, data sent, country, purpose, contract date
Is our data encrypted and kept apart from other tenants?What it rests on: Section 8(5); Rule 6(1)(a)Engineering evidence to have ready: Encryption settings per data store, key management, and how tenant isolation is enforced and tested
Who on your team can access our data?What it rests on: Section 8(5); Rule 6(1)(b)Engineering evidence to have ready: A role and access matrix, SSO and MFA settings, dated access reviews, support-access approvals
Can you detect and investigate unauthorised access?What it rests on: Rule 6(1)(c)Engineering evidence to have ready: Log sources with sample entries, a log store the logged systems cannot edit, alert rules, one investigated alert
Do you keep logs and data for one year?What it rests on: Rule 6(1)(e); Rule 8(3)Engineering evidence to have ready: Retention settings for each log store and data store, matching your retention schedule
Can you keep running after an incident?What it rests on: Rule 6(1)(d)Engineering evidence to have ready: Backup schedule, dated restore tests, a recovery plan with owners
How fast will you tell us about a breach, and what will you send?What it rests on: Section 8(6); Rule 7Engineering evidence to have ready: A breach runbook with the customer-notice step, a notice template that covers Rule 7's contents, a dated drill
If a user withdraws consent, how do you stop processing?What it rests on: Section 6(6)Engineering evidence to have ready: An API or admin action that stops processing for one person, with a log of each request
How do you delete our data at the end of the purpose or contract?What it rests on: Section 8(7); Rule 8(3)Engineering evidence to have ready: Deletion jobs per system, deletion logs, and a written note on backups and when deleted data leaves them
Can you help with a rights request about one person?What it rests on: Sections 11 to 13Engineering evidence to have ready: A tested way to find, export, correct and erase one person's records across systems
Where is our data stored and processed?What it rests on: Section 16; contractEngineering evidence to have ready: Cloud regions per system, and a list of any processing or support access from outside India
What happens to our data in your AI features?What it rests on: Sections 8(2), 8(5)Engineering evidence to have ready: Which AI vendors receive customer data, under which terms, whether it is used for training, and what is masked first

Our Rule 6 checklist breaks the security rows into checks and evidence. The vendor evidence pack page shows how to put the records into one pack you can reuse for the next customer.

Where SaaS teams tend to fall short

The gap is often not the answer but the record behind it. Common gaps:

  • Deletion that stops at the primary database. The customer's data is erased in the app but stays in the warehouse, search index, logs, support tool and backups.
  • Short log retention. Application and access logs kept for 30 or 90 days, against the one-year minimum in Rule 6(1)(e) and Rule 8(3).
  • No per-customer data map. The team knows the architecture but cannot say which stores hold one customer's personal data.
  • A sub-processor list that leaves out tools. Email, error tracking, analytics, support and AI vendors that receive customer data in payloads, stack traces or tickets.
  • A breach runbook with no customer step. It covers CERT-In's 6-hour report but not the customer notice the contract requires.
  • Withdrawal handled by email. No way to stop processing for one person except a manual database change.
  • Production data in staging. Unmasked copies of customer data in test environments.

A DPDP gap assessment finds these system by system. Our post on what a DPDP technical audit delivers shows the format of the findings.

Don't forget your own Fiduciary duties

Customer questionnaires focus on the data you process for them. The Act also covers the data you hold for yourself. For your marketing list, website analytics, product emails to users, employees and applicants, you need notices, consent records or a legitimate use under Section 7, a way to handle rights requests, your own breach reporting and your own retention schedule. Much of the engineering is shared: the same logs, deletion jobs and runbook serve both roles.

The order of work before 13 May 2027

  • 1. Split your data by role. List the data you process for customers and the data you hold for yourself. Flag any use of customer data for your own purposes for legal review.
  • 2. Build the data map and sub-processor register. Most questionnaire answers depend on them.
  • 3. Start the records that need time. One-year log retention only proves itself after a year, so set it now.
  • 4. Fix deletion across every copy, and write down how backups work.
  • 5. Add the customer step to your breach runbook, with a notice template and a drill.
  • 6. Get the contract reviewed. Check that each clause in your standard DPA is something your systems can do. Our partner law firm does the legal review.
  • 7. Pack the evidence. Put it into one vendor evidence pack and keep it current.

We build these fixes as DPDP implementation work, in your stack. If your buyers also send AI or security questionnaires, see our work on security questionnaires. See everything we do for DPDP compliance.

This article is general information, not legal advice. Whether you are a Data Processor or a Data Fiduciary for a given use, and what your contracts must say, are questions for your lawyers.

Sources: Digital Personal Data Protection Act, 2023, Sections 2(i), 2(k), 6(6), 7, 8, 11, 12, 13, 16 and the Schedule. Digital Personal Data Protection Rules, 2025, Rules 6, 7 and 8 (G.S.R. 846(E), Gazette of India, 13 November 2025). CERT-In Directions, 28 April 2022. Last reviewed 18 November 2026.

FAQ

Is my SaaS a Data Processor under the DPDP Act?

Usually, for the personal data your customers put into your product. The Act defines a Data Processor as a person who processes personal data on behalf of a Data Fiduciary (Section 2(k)). For your own marketing, users' accounts used for your own purposes, and employees, you are a Data Fiduciary. If you use customer data for your own purposes, get legal advice on your role.

What are a Data Processor's obligations under the DPDP Act?

The Act writes the duties for the Data Fiduciary, which stays responsible for processing done on its behalf (Section 8(1)). They reach the processor through the valid contract that Section 8(2) requires. In practice that means security safeguards under Rule 6, prompt breach notice, stopping processing and erasing data when told, and keeping data and logs for at least one year under Rule 8(3).

Does Rule 6 apply to data processors?

Rule 6 puts the duty on the Data Fiduciary, but it covers processing a Data Processor does on its behalf. Rule 6(1)(f) requires the contract between them to provide for reasonable security safeguards, where applicable. So your customers will ask you for encryption, access control, logging, backups and one-year log retention.

Does the DPDP Act say how fast a processor must report a breach?

No. Rule 7 requires the Data Fiduciary to tell affected people and the Board without delay, and send the Board a detailed report within 72 hours of becoming aware. The Act and Rules set no separate deadline for the processor, so customers set one in the contract. Your runbook needs to meet it.

Is there a DPDP certificate a SaaS company can show customers?

No. The Act and Rules do not set up a DPDP compliance certificate. ISO 27001 or SOC 2 help with security questions but do not show DPDP compliance. What customers can check is evidence: a data map, a sub-processor register, security and deletion records, a breach runbook and the contract terms.

Find the gaps before your customers do.