Kestryl · Native DPDP operating surface
Kestryl Cockpit for DPDP brings the personal data held across Salesforce and nine other enterprise systems into one governed corpus on the Informatica Secure Agent you already run — then computes what India’s Digital Personal Data Protection law asks of you, proves what was done, and hands your board the evidence. Adding another system is a row on a screen, not a programme.
The moment
India notified the DPDP Rules on 14 November 2025 with an eighteen-month phased path to full compliance. Every access, correction or erasure request must be answered within ninety days. A personal-data breach must be reported to the Board and to affected individuals. Failing to maintain reasonable security safeguards carries a penalty of up to ₹250 crore; failing to notify a breach, up to ₹200 crore.
Most enterprises will meet this the expensive way: one project per obligation, one project per system, a spreadsheet to reconcile them, and a scramble before every audit. Kestryl Cockpit for DPDP is the alternative — one corpus, one journey, one evidence pack — built on infrastructure you already own.
Facts as published by the Press Information Bureau, Government of India and summarised in KPMG’s guidance to the DPDP Rules. Confirm applicability with counsel.
What you get
Salesforce, SAP, Oracle, Microsoft, ServiceNow, Workday and SharePoint read through Informatica’s own connectors into a read-only copy on a server you control, in the region you choose. Tables and their attachments, decided once, inherited by everything after.
Corpus → Scan → Review → Attest → Retention → Requests → Erasure → Evidence → DPDP. The ninety-day clock and the 48-hour erasure notice are on the screen, not in someone’s memory.
Six questions a regulator asks, six artefacts that answer them — signed with the rule fingerprint and the run ID, assembled per run and per request, containing counts and decisions but never a personal value.
The engine underneath
Every value is checked against its published validation, a confidence floor is set by you, masking needs deliberate approval, and the chained log is designed so edits are detectable. The cockpit makes that discipline operable by a Data Protection Officer rather than an engineer.
Coverage
Each connects through an Informatica IDMC Cloud Data Integration connector that already exists and is already documented. Each exposes a catalog the cockpit can read, and each has a vendor-documented route to its attachments.
Connectors per Informatica’s IDMC Cloud Data Integration documentation. Attachment retrieval is delivered by a separate extractor module against each vendor’s documented interface and is scoped per engagement; SAP Ariba’s document interface is confirmed per module.
The DPDP board
Seven obligations are proven at record level directly from the corpus. The remaining seven are carried by Salesforce Privacy Center’s consent tools, contributed to by the cockpit, or belong to your programme — and the board says so, in colour, so nobody mistakes a dashboard for a legal opinion.
| # | Obligation | Status | Where it lives |
|---|---|---|---|
| 1 | Notice to individuals | Cockpit contributes | Preference Manager forms |
| 2 | Consent and withdrawal | Carried by Salesforce Privacy Center | Preference Manager · Consent API |
| 3 | Purpose limitation, minimisation | Proven from the corpus | Inventory → policy scope |
| 4 | Accuracy | Cockpit contributes | Correction request |
| 5 | Erasure, retention, 48-hour notice | Proven from the corpus | Erasure screen · residual scan |
| 6 | Security safeguards and logs | Proven from the corpus | Masking · chained log · telemetry |
| 7 | Breach notice | Cockpit contributes | Inventory scopes fields and counts |
| 8 | Access requests, 90 days | Proven from the corpus | Requests screen |
| 9 | Correction and erasure requests, 90 days | Proven from the corpus | Requests screen · residual |
| 10 | Grievance and nomination | Cockpit contributes | Request as a ticket |
| 11 | Children’s data | Your programme, informed by the corpus | Date-of-birth and guardian fields located |
| 12 | Significant Data Fiduciary: DPO, audit, DPIA | Proven from the corpus | Evidence pack |
| 13 | Cross-border transfer | Your programme, informed by the corpus | Records in scope confirmed |
| 14 | Processors | Cockpit contributes | Evidence pack |
Status is PDI’s assessment against Salesforce Help and Object Reference, the Informatica CDGC data sheet, and PDI’s published Kestryl pages. DPDP references per the MeitY text and PIB explainer. Confirm sections with counsel before external use.
Control
CORPUS PINNED · RULE FINGERPRINT IN THE RUN HEADER · MODE DECLARED BEFORE THE FIRST ROW IS READ
Stated plainly
The Kestryl engine, the IDMC Secure Agent and the ten CDI connectors are shipping products. The cockpit screens on these pages are the design standard now being built; the click-through shown to leadership uses synthetic data. The attachment extractor is built as a separate module against each vendor’s documented interface. Handing a confirmed field to a Privacy Center policy is a guided step today — Salesforce publishes no API to create a policy definition. Per-individual scans and the full India identifier pack (PAN, mobile, IFSC; Aadhaar is already in the rule library) are on the enhancement path.
We would rather you hear this from us than discover it in a pilot. DPDP board statuses are PDI assessments, not legal determinations.
FAQ
An extension. Kestryl Cockpit for DPDP is the operating surface on top of the Kestryl engine, running on the Informatica IDMC Secure Agent Server you host. The engine finds and remediates personal data; the cockpit turns that into the DPDP journey and the fourteen-obligation board.
Ten systems through Informatica’s own IDMC CDI connectors: Salesforce, SAP S/4HANA and ECC, SAP SuccessFactors, SAP Ariba, Oracle E-Business Suite, Oracle NetSuite, Microsoft Dynamics 365, ServiceNow, Workday and SharePoint Online. Others connect through JDBC or ODBC. Attachments are reached through each vendor’s documented interface by a separate extractor module, scoped per engagement.
No. The corpus is a read-only copy on a Secure Agent Server you control, in the region you choose; the design shows a Mumbai host with no egress during a scan. Enforcement of erasure and retention happens in Salesforce Privacy Center or your other systems’ native tools; the cockpit proves the result.
No product does. Seven of the fourteen obligations are proven at record level from the corpus; the other seven are carried by Privacy Center, contributed to by the cockpit, or remain your programme — and the board says which. Legal applicability, consent design, notices and grievance handling remain decisions for you and your counsel.
Why Pacific Data Integrators
PDI has spent 15+ years and 100+ implementations inside Informatica, Salesforce, Snowflake and Databricks for banks, insurers, healthcare, government and retail. Kestryl Cockpit for DPDP is what that experience looks like pointed at one law: not another scanner, but the operating surface that lets a privacy officer run the whole obligation from one screen and prove it.