Salesforce rescue

India

DPDP Rules for Salesforce orgs: duties start 13 May 2027; logs keep 30 days, not a year

By Shivanath DevinarayananPublished 8 min read
Written forThe Salesforce owner with an org that isn't working“Our Salesforce org is stuck.”

The short answer

Our Salesforce org holds personal data of people in India. Which DPDP Rules apply when, and do Shield, Event Monitoring, Field Audit Trail, Privacy Center and backups make us compliant?

Data Fiduciary duties start on 13 May 2027; November 2026 only opened Consent Manager registration. Salesforce covers part of Rule 6 security and Rule 8 logs, but event logs keep 30 days by default against a one-year rule. Breach notices, request routes and contracts are your process. At Mindcat, we read your org against the rules.

Kochi desk at night: a printed log cut short beside a calendar on 30, with the words 30 days, not 365

Takeaways

  1. 01Rule 4 (Consent Manager registration) started on 13 November 2026. The duties of a Data Fiduciary start on 13 May 2027.
  2. 02Rules 6(1)(e) and 8(3) ask for one year of logs. Event Monitoring keeps 30 days by default; an admin can extend it to 365.
  3. 03Salesforce says event log files are not a system of record. Export them to a store you control.
  4. 04Deleting a record does not erase the person from Field Audit Trail history or from backups. Your erasure process has to reach both.
  5. 05No licence sends breach notices, publishes a route for rights requests or writes security terms into processor contracts.

If your Salesforce org holds personal data of people in India and someone has sent you a DPDP checklist that maps each rule to a Salesforce product, this is for you. It is not for an org with no personal data of people in India, or a small org with no named Salesforce admin to own the changes.

When do the DPDP Rules reach your Salesforce org?

On 13 May 2027, for the duties that touch your org. The checklists going round say the "consent manager framework" activates in November 2026, and that part is true. But Rule 4, which came into force on 13 November 2026, only lets Consent Managers register with the Data Protection Board. It puts no new duty on the company that runs the CRM.

Rule 1 of the DPDP Rules, 2025 sets three start dates. The government's press release of 14 November 2026 repeats the last one: the rights of Data Principals, the obligations of Data Fiduciaries and the Board's penalty process "are scheduled to come into effect on 13 May 2027."

When each part of the DPDP Rules starts

  1. 13 Nov 2025

    Rules 1, 2 and 17 to 21: definitions and the Data Protection Board

  2. 13 Nov 2026

    Rule 4: Consent Managers can register. No new duty on your org

  3. 13 May 2027

    Rules 3, 5 to 16, 22 and 23: notice, security, breach, retention, rights. Your org's duties

From Rule 1 of the DPDP Rules, 2025. Check the MeitY page for any amendment before you plan.

Two caveats. In January 2026, MeitY proposed cutting the 18-month window to 12 months. We found no amendment notified as of 18 November 2026, and the 14 November release still names 13 May 2027. And the Board itself had no chairperson or members as of 16 November 2026. Neither is a reason to wait. Six months is about right for the work below, and most of it is not buying a licence.

Which rule asks for what, and what covers it?

Four rules decide most of the work in a Salesforce org: Rule 6 (security), Rule 7 (breach notice), Rule 8 (erasure and logs) and Rule 14 (rights requests). The checklist you were sent maps them to products. Here is the same map with the part no product covers.

RuleWhat it asksSalesforce control that helpsWhat stays yours
6(1)(a)Encryption, obfuscation, masking or virtual tokensShield Platform Encryption; data masking in sandboxes
6(1)(b), (c)Control who can access; logs, monitoring and review of accessProfiles, permission sets, sharing; Event Monitoring; Transaction Security policies
6(1)(d)Keep processing going after a breach, including backupsSalesforce Backup & Recover, or your own backup
6(1)(e), 8(3)Keep logs (and the personal data processed) for one yearEvent Monitoring retention extended to 365 days; Field Audit Trail
6(1)(f)Security terms in contracts with Data ProcessorsNone
7Tell each affected person and the Board; detailed report within 72 hoursNone (logs help you find the facts)
8(1), (2)Erase data no longer needed (Third Schedule for large platforms), with 48 hours' warningPrivacy Center retention and deletion policies
14Publish how to make a rights request; answer grievances within 90 daysPrivacy Center data subject requests; Service Cloud cases

Read the last column first. Every row has one, and two rows have no product at all.

If your org has grown controls nobody reviews, our Salesforce optimisation review starts from what is actually switched on in Setup, not from the licence list.

Why are 30 days of logs a problem?

Because Rule 6(1)(e) asks you to keep logs and personal data for one year, and Rule 8(3) asks you to keep "such personal data, associated traffic data and other logs" for at least one year from the processing. Salesforce Event Monitoring does not keep that long unless someone changes it.

Without Shield or the Event Monitoring add-on, Salesforce gives you a few event types for one day (Event Monitoring FAQ). With Shield or the add-on, Salesforce Help says event log files are kept for 30 days by default, and an admin can extend retention up to one year, in Setup or through the eventLogRetentionDuration field of the EventSettings metadata.

Bars: DPDP Rules 6 and 8 ask for 365 days of logs; the Event Monitoring default keeps 30 days
The rule asks for a year. The default keeps a month.

Extending the setting is not the end of it. The Salesforce REST API guide says event log files "aren't a system of record" and that data loss can occur. If you need a year of logs to answer the Board, export them daily to storage you control and check that the export ran.

Field history is the other log people count on. Standard Field History Tracking keeps 18 to 24 months for up to 20 fields an object. Field Audit Trail, part of Shield or sold alone, tracks up to 200 fields an object and keeps history until you delete it (Field Audit Trail). That length helps with Rule 8(3). It causes the problem in the next section.

One default changed this year without anyone buying anything. Salesforce now asks for step-up authentication when someone exports more than 10,000 records from a report in the browser, enforced in production from 13 July 2026. It does not cover API or Data Loader exports. Those still need a Transaction Security policy of your own, on API events, that blocks or asks for MFA above a row count you choose.

Does deleting a record erase the person?

No. When you delete a Contact, the record goes to the Recycle Bin and then away. The person's old values can stay in three other places.

A deleted record still leaves data in the field history archive, backups, and exports and integrations
An erasure request has to reach all three places.
  • Field history. Field Audit Trail copies history to an archive object and keeps it until deleted. Deleting the record does not delete its archived history.
  • Backups. Salesforce Backup & Recover, formerly Own Recover, keeps 99 years of backups by default, with policies you can shorten. Any other backup tool keeps its own copies.
  • Exports and integrations. The data warehouse, the marketing tool and last quarter's spreadsheet export.

Rule 8 asks you to erase data once its purpose is served, and Rule 14 lets a person ask for erasure. Your erasure process has to name all three places.

The one-year log rule pulls the other way. Section 8(7) of the Act lets you keep data where a law requires it, and Rule 8(3) is such a requirement for logs. So keep the logs a year even after an erasure request, restrict who can read them, and delete them on schedule. Have counsel confirm that reading for your org. Privacy Center, a paid add-on, can run retention policies and right-to-be-forgotten requests and can remove field history and Field Audit Trail records. Backup & Recover has its own right-to-be-forgotten step for backups. Without them, an admin does it by hand, and writes down that it was done.

What does no Salesforce licence do for you?

Four things, and the penalties reach them. The Act's Schedule allows up to ₹200 crore for failing to notify a breach, and up to ₹250 crore for failing to take reasonable security safeguards, which Rule 6 says include the contract terms below (DPDP Act Schedule).

  • Breach notice (Rule 7). Tell each affected person without delay, in plain language, and tell the Board without delay. Within 72 hours, send the Board a detailed report. That needs a runbook, a named owner and a drafted notice, ready before the first incident.
  • Rights requests (Rule 14). Publish on your website or app how a person makes a request and what details you need to identify them. Answer grievances within a period not over 90 days. A Service Cloud queue can hold the case; it cannot write the policy.
  • Processor contracts (Rule 6(1)(f)). Your Salesforce partner, AppExchange vendors and integrators process your data. Your contracts with them need security terms.
  • Notice and consent records (Rule 3, Act sections 5 and 6). A notice in clear language for each purpose, and a record of who agreed to what. Salesforce has consent objects; what goes in them is yours. Our EMI reminder calls checklist shows what those records look like for a calling agent.

What should you do before 13 May 2027?

  1. 01List every object and field that holds personal data of people in India, and the purpose for each.
  2. 02Check Setup: is Event Monitoring on, and what is the event log retention? Extend it to 365 days and start a daily export.
  3. 03Decide retention per purpose, and write down where history, backups and exports keep copies.
  4. 04Encrypt only fields where the risk is real. Encrypted fields lose some filtering, sorting and formula use, so test reports, search and AppExchange packages in a sandbox first.
  5. 05Write the Rule 7 breach runbook and the Rule 14 request page, with named owners.
  6. 06Add security terms to every processor contract that touches the org.
  7. 07Run one rehearsal: a fake breach and a fake erasure request, end to end.

Do steps 1 and 2 this week; they cost nothing and tell you how far apart the checklist and your org are. Buy licences after step 3, when you know which gaps a product closes. We are not lawyers: have your counsel read the notice, the runbook and the contracts.

This list is not for you if your org holds no personal data of people in India, or if nobody owns Salesforce day to day; name that owner first.

At Mindcat, we read your org against these rules and give you a written list: settings to change, licences you need and do not need, and the process work with an owner for each. It runs like our rescue week: we price the fixes after the read, not before. The work is run from our India company in Kochi.

Filed under

Salesforce rescuedpdp rules 2025dpdp rules timelinesalesforce shield dpdpdpdp act compliance checklist
Useful to someone on your team?

FAQ

Questions teams ask next

When do the DPDP Rules 2025 come into force?
In three steps, under Rule 1. Rules 1, 2 and 17 to 21 (the Data Protection Board) came into force on 13 November 2025. Rule 4 (registration of Consent Managers) came into force on 13 November 2026. Rules 3, 5 to 16, 22 and 23, which hold the duties of a Data Fiduciary, come into force on 13 May 2027. MeitY proposed a shorter timeline in January 2026; we found no amendment notified as of 18 November 2026.
Does Salesforce Shield make an org DPDP compliant?
No product makes an org compliant. Shield Platform Encryption, Event Monitoring and Field Audit Trail help with parts of Rule 6 (encryption, access logs, monitoring) and Rule 8(3) (one year of logs). Rule 7 breach notices, Rule 14 request routes, Rule 6(1)(f) contract terms and your notice and consent records are process work your team owns.
How long does Salesforce keep Event Monitoring logs?
Without Shield or the Event Monitoring add-on, a few event types for one day. With Shield or the add-on, Salesforce Help says event log files are kept 30 days by default, and an admin can extend retention up to one year in Setup or through the EventSettings metadata. Salesforce also says the files are not a system of record, so export them to your own store.
Who do I have to tell after a personal data breach under the DPDP Rules?
Under Rule 7, each affected Data Principal, without delay, in plain language, and the Data Protection Board, without delay. Within 72 hours of becoming aware, or a longer period the Board allows, you send the Board a detailed report with the facts, the measures taken and the findings about the person who caused the breach.
What is the penalty for weak security under the DPDP Act?
Up to ₹250 crore for failing to take reasonable security safeguards to prevent a personal data breach (section 8(5) of the Act, item 1 of the Schedule), and up to ₹200 crore for failing to notify the Board or affected people of a breach (item 2).

Sources

  1. 01MeitY: Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025)Accessed 18 Nov 2026
  2. 02PIB: Data Protection Board portal launched; remaining provisions from 13 May 2027 (14 November 2026)Accessed 18 Nov 2026
  3. 03India Code: Digital Personal Data Protection Act, 2023, Schedule of penaltiesAccessed 18 Nov 2026
  4. 04Business Standard: MeitY may cut compliance timeline for key DPDP rules to 12 months (22 January 2026)Accessed 18 Nov 2026
  5. 05Hindustan Times: Data Protection Board still without chairperson or members (16 November 2026)Accessed 18 Nov 2026
  6. 06Salesforce Help: Retain Event Monitoring event log files for up to one year (21 August 2026)Accessed 18 Nov 2026
  7. 07Salesforce Help: Event Monitoring frequently asked questionsAccessed 18 Nov 2026
  8. 08Salesforce REST API Developer Guide: Using Event MonitoringAccessed 18 Nov 2026
  9. 09Salesforce Help: Prepare for Transaction Security Policy enhancements (9 October 2026)Accessed 18 Nov 2026
  10. 10Salesforce Help: Field Audit TrailAccessed 18 Nov 2026
  11. 11Salesforce: Privacy CenterAccessed 18 Nov 2026
  12. 12Salesforce: Backup & RecoverAccessed 18 Nov 2026
Shivanath Devinarayanan, founder of Mindcat

Written by

Shivanath Devinarayanan

Founder, Mindcat Consulting · Salesforce MVP Hall of Fame

Builds and runs AI agents in production. Reads every brief that comes in and signs the work that goes out.

About Shivanath

Rescue and Optimize · the written assessment

We work in real estate and right now, our Salesforce org is stuck.

Industry
Problem

Brief: Real estate. Leads from portals and WhatsApp. Follow-up has no owner. The org is stuck. Stabilise first, then decide what is worth finishing. From: /blog/dpdp-rules-salesforce-controls.