Compliance
DPDP Significant Data Fiduciary: Obligations and Implications
What makes a company a Significant Data Fiduciary under DPDP 2023, what extra obligations apply, and how to prepare before the government designates your organisation.
What Is a Significant Data Fiduciary?
Under DPDP Section 10, the Central Government can designate any Data Fiduciary as a 'Significant Data Fiduciary' (SDF) based on: volume and sensitivity of personal data processed, risk to rights of data principals, potential impact on sovereignty and integrity of India, risk to electoral democracy, security of the state, or public order.
No revenue or user count thresholds are specified — the designation is at government discretion. However, the criteria suggest that large consumer platforms (social media, e-commerce, payments), healthcare AI systems, and companies processing sensitive data at scale are most at risk of designation.
Additional SDF Obligations
Significant Data Fiduciaries must: (1) Appoint a Data Protection Officer (DPO) based in India who is responsible to the Board of Directors, (2) Appoint an independent Data Auditor to conduct periodic audits, (3) Conduct Data Protection Impact Assessments (DPIA) for new processing activities, (4) Ensure that algorithms that may affect data principals' rights are auditable.
These obligations are significantly more onerous than those for ordinary Data Fiduciaries. The DPO must be a senior, experienced professional — not just a designated compliance email address. The Data Auditor requirement will create a new service industry in India for certified compliance auditors.
Preparing Before Designation
Even if you're not designated yet, building SDF-ready infrastructure is wise if you're growing fast or processing sensitive data at scale. The gap between basic DPDP compliance and SDF compliance is significant — a DPO, Data Auditor, and DPIA process can't be set up overnight.
Start with: (1) Identify a potential internal DPO candidate and begin their DPDP training, (2) Document all current processing activities in a Record of Processing Activities (RoPA), (3) Conduct an initial DPIA for your highest-risk AI systems, (4) Ensure your audit log infrastructure (see Kafka architecture) is ready to support a Data Auditor's queries.
Compliance operational checklist
DPDP Significant Data Fiduciary: Obligations and Implications should be reviewed as an operating control, not only as a reference article. The minimum checklist is a data inventory, a stated processing purpose, owner approval, PII detection at the AI boundary, redaction or tokenisation where possible, retention limits, vendor transfer records, and a tested user-rights workflow. This checklist gives engineering and compliance teams a shared language for deciding what must be blocked, what can be allowed in shadow mode, and what needs human review before production release.
For AI systems, the review should include prompts, retrieved context, tool call arguments, model responses, logs, traces, analytics events, exports, and support attachments. Many incidents happen because teams scan only the visible form field while sensitive data moves through background context or observability tooling. CrewCheck's recommended pattern is to place the scanner at the request boundary, record the policy version, and keep audit evidence that shows which identifiers were detected and what action was taken.
A practical rollout starts with representative samples from production-like traffic. Run a DPDP scan, sort findings by identifier sensitivity and blast radius, fix Aadhaar, PAN, financial, health, children's, and precise-location exposure first, then move to consent wording, retention, deletion, and vendor review. Use shadow mode when false positives could disrupt users, and promote to enforcement only after the exceptions have owners and expiry dates.
This page is educational and should be paired with legal review for final policy interpretation. The operational proof should still come from repeatable evidence: scanner results, audit exports, pull-request checks, policy configuration, and a documented owner for the workflow. That combination is what makes the content useful during buyer diligence, board review, regulatory questions, or an incident investigation.
Related pages
Check your own workflow
Run a free DPDP scan before this risk reaches production.
Scan prompts, logs, documents, and API payloads for Indian PII exposure, missing redaction, and audit gaps. Backlinks: learn hub, developer docs, pricing, and the DPDP scanner.