Intent on paper
Policies establish principles, roles, and expectations. They do not by themselves show the current location or treatment of sensitive data in a working estate.
PRIVACY CONTROL OUTCOMES
Prove the privacy control.
Not the promise.
Policies and assessments describe intent. Operational confidence comes from showing where sensitive data exists, how it was classified, what control was applied, what evidence was produced, who reviewed it, and what approved remediation occurred. PDI turns that chain into a reviewable operating record across structured systems and source materials.
FIND · CLASSIFY · PROVE · REMEDIATE · EVIDENCE-LED PRIVACY OPERATIONS
Technical outcomes support customer and counsel review. Legal applicability and remediation approval remain with the customer and counsel.
The privacy control gap
A stated control is not yet an observable control.
A policy can define intent. A stated control can describe a planned process. Privacy control maturity requires a reviewable record of the data, the finding, the decision, and the bounded action taken—if an action is approved.
A process described
Assessments and control statements can describe a process. Reviewers still need the source, classification, decision, and approval context behind the result.
A result that can be reviewed
Evidence records, traceability, and review history make the technical outcome visible without turning it into a claim of legal sufficiency or universal compliance.
Four privacy control outcomes
One control story from discovery to approved action.
The service framework is deliberately connected: a finding informs classification; classification carries context into evidence; evidence supports review; and only an approved decision can lead to bounded remediation.
Inventory PII
Inventory PII across structured systems, attachments, PDFs, scans, images, and shared drives so the estate can be discussed from observed sources rather than assumptions.
Identify categories
Identify PII and sensitive categories with location and context, including the record or source material in which the finding appears.
Produce evidence
Provide evidence records, traceability, and review chains that connect the technical finding to the decision made about it.
Apply approved action
Mask, Vault, or Strip only approved supported structured data after the customer’s remediation decision and any applicable review.
Know what you actually hold
Follow sensitive data wherever the record travels.
Privacy exposure is rarely limited to a database table. The service starts by establishing an inspection boundary that includes operational records and the source materials that travel with them.
Records with operational context
Find, classify, and evidence PII in supported structured systems, with the location and context reviewers need to understand the control outcome.
Documents, scans, images, and attachments
Discover and classify PII in ERP and CRM attachments, PDFs, scans, images, and shared drives. These materials may be evidenced, but they are not represented as altered.
Inspection boundary
Aadhaar OCR remains detection, inventory, and review support only. It does not represent source-document alteration or a legal determination.
Turn findings into evidence
Evidence that keeps the decision traceable.
PDI connects the finding to its source and location, then carries the classification, review, decision, and approved action into one technical evidence chain. That supports customer and counsel review; it does not claim every statutory obligation has been addressed.
Capture the finding
Record the PII category, source location, relevant context, and technical result produced by the discovery and classification workflow.
Keep the control decision visible
Keep the relationship between source finding, classification, review decision, and approved supported-structured-data remediation available for inspection.
Preserve approval context
Carry review and approval history with the evidence so the customer and counsel can decide legal applicability, holds, exceptions, and remediation scope.
From evidence to approved action
Keep discovery, evidence, and action distinct.
The service separates what is observed from what is decided. That distinction keeps the operational record useful while leaving legal applicability, holds, exceptions, and remediation approval with the customer and counsel.
DiscoveryWHAT THE SUPPORTED INSPECTION SCOPE OBSERVESFind
ClassificationWHAT PII CATEGORY, LOCATION, AND CONTEXT THE FINDING CARRIESExplain
EvidenceWHAT REVIEW HISTORY AND TECHNICAL TRACEABILITY THE RECORD RETAINSProve
Approved remediationWHAT BOUNDED ACTION IS AUTHORIZED FOR SUPPORTED STRUCTURED DATAAct
Privacy control evidence in practice
Use privacy context to sharpen the control conversation.
PDI’s source-grounded evidence library helps put observable control outcomes in regulatory and enforcement context. These summaries are supporting reference points, not a substitute for legal analysis or a required step in understanding this service.
GDPR + UK GDPR
A cross-jurisdiction evidence view for accountability, security, breach, data-subject, and governance conversations.10distinct control outcomes in the supplied ten-use-case key
24attached-library cases in the source-grounded reference set
Review GDPR evidence →India DPDP
A readiness view that keeps phased implementation, evidence purpose, and the Aadhaar overlay in their proper context.7mapped provisions and outcomes in the library
Reviewtechnical evidence supports review; it does not determine legal applicability
Review India DPDP evidence →California
A scoped view of California-heading records whose legal basis explicitly includes CCPA.11CCPA-related case records in the library
$23,382,678nominal original-currency amount for those scoped records
Review California context →U.S. state privacy
A state-by-state reference layer for comparing active privacy-law context and supporting evidence.50state entries in the current reference index
8multistate case records, separately scoped in the library
Review state evidence →Evidence reference boundary
Library case records are scoped evidence references, not all-time government enforcement totals. Pending matters are excluded where the library says so, monetary figures remain in original currency, and shared multistate totals appear once nationally rather than being attributed in full to every state. A zero direct attribution does not mean zero enforcement. No reference establishes legal sufficiency or a compliance guarantee.
Jurisdiction control mappings
Make the regulatory question reviewable.
The service story does not require a buyer to read every case record. These concise mappings show how the evidence chain relates to the important control questions, while legal interpretation, applicability, and reporting decisions remain with the customer and counsel.
GDPR / UK GDPR: six obligation lenses
Data minimization
Articles 5(1)(c), 25. Inventory candidate PII and produce scoped evidence to support review of what is adequate, relevant, and limited.
Retention
Article 5(1)(e). Identify retained data and produce evidence for policy-led retention decisions; PDI does not set lawful retention periods.
Erasure
Article 17. Locate candidate records and support approved structured-data actions, subject to legal holds and applicable exceptions.
Records and accountability
Articles 5(2), 24, 30. Audit rows and evidence packs can support internal accountability work; they are not statutory records by themselves.
Security
Article 32. Discovery and inventory can inform risk review. Security compliance requires wider technical and organizational measures.
72-hour notification
Article 33. Evidence may support breach investigation; PDI does not decide reportability or whether notification is required.
These are service-level evidence mappings, not a complete legal checklist. The Evidence Library retains the selected enforcement examples, official-source links, and full jurisdiction notes.
India DPDP: seven readiness points
The Act and Rules use staged commencement. The supplied research keeps the Gazette-date ambiguity and future Tranche 3 timing explicit; within the supplied library, completed monetary DPDP enforcement is 0 cases / ₹0.
-
1 · Rule 6(1)(a) / working-paper item (i)
Timing: Future Tranche 3 — 13/14 May 2027; plan to 12 May 2027 due to Gazette-date ambiguity.
Requirement: Encryption, obfuscation, masking or virtual tokens as reasonable security safeguards.
Control outcome: Mask / Vault / Strip for supported structured data, subject to policy and legal hold.
Boundary: Structured-data remediation only; it does not establish that the full safeguard duty is legally sufficient.
-
2 · Rule 6(1)(c) / working-paper item (iii)
Timing: Future Tranche 3 — 13/14 May 2027; plan to 12 May 2027.
Requirement: Logs, monitoring and review enabling detection, investigation and remediation.
Control outcome: Kestryl audit row product capability supports review evidence.
Boundary: Audit rows support the control; they do not by themselves satisfy all monitoring, detection, investigation or remediation duties.
-
3 · Section 8(7) and Rule 8
Timing: Future Tranche 3 — 13/14 May 2027; plan to 12 May 2027. The three-year dormancy and 48-hour notice mechanics are future.
Requirement: Erase on withdrawal or when the specified purpose is no longer served, whichever is earlier, unless legal retention is necessary. Rule 8/Third Schedule adds a three-year inactivity trigger only for specified classes and thresholds: e-commerce entities with at least 2 crore registered users, online gaming intermediaries with at least 50 lakh users, and social-media intermediaries with at least 2 crore users, subject to stated exclusions; give at least 48 hours’ pre-erasure notice.
Control outcome: Strip for supported structured data plus erasure evidence.
Boundary: Subject to policy, legal hold, applicable retention law, class/threshold scoping and downstream processor duties. Documents and attachments are inventoried, not altered.
-
4 · Rule 7 (implementing Section 8(6))
Timing: Future Tranche 3 — 13/14 May 2027; plan to 12 May 2027.
Requirement: Inventory the nature, extent, timing and location of the breach; notify affected Data Principals without delay; notify the Board without delay and provide the detailed report within 72 hours of awareness, unless the Board allows longer on written request.
Control outcome: Discovery and inventory can support breach scoping and evidence preparation.
Boundary: Documents and attachments are scanned and inventoried, not altered. PDI does not send notices or determine legal reportability.
-
5 · Section 6(10)
Timing: Future Tranche 3 — 13/14 May 2027; plan to 12 May 2027.
Requirement: The burden is on the Data Fiduciary to prove notice and consent only where consent is relied upon.
Control outcome: Evidence packs support review of notice/consent artefacts and related data locations.
Boundary: Evidence packs do not prove legal sufficiency, validity of consent, or that consent is the correct lawful basis.
-
6 · Section 33(2)(e)
Timing: Future Tranche 3 — 13/14 May 2027; plan to 12 May 2027.
Requirement: The Board must consider whether mitigation occurred and the timeliness and effectiveness of that action when determining a monetary penalty.
Control outcome: The discovery-to-review-to-remediation chain supports evidence of mitigation activity and timing.
Boundary: Technical evidence supports review; it does not determine the Board’s penalty or prove effectiveness.
-
7 · Aadhaar (Sharing of Information) Regulations, 2016
Timing: Live now in the board paper; amended 25 January 2024 and 21 August 2025.
Requirement: Core biometric information may not be shared; core biometrics captured for authentication by a requesting entity may not be stored or shared; identity information is purpose- and consent-constrained.
Control outcome: OCR identifies Aadhaar text in scans, images and shared drives for inventory and review.
Boundary: PDI does not mask, redact or otherwise alter source documents or attachments.
The full DPDP mapping retains the official source links, commencement ledger, and educational-not-legal-advice qualification in the Evidence Library.
Evidence / control mapping
Map the question to an observable control outcome.
The evidence library groups its reference material through a ten-use-case key. It is a methodology for organizing a privacy-control discussion—not a legal checklist, representation that every obligation is covered, or a claim that a technical finding proves compliance.
- personal data inventory/data map
- sensitive-data discovery
- downstream copy tracking
- DSR response scoping
- deletion/erasure propagation
- opt-out propagation validation
- marketing/vendor provenance
- breach blast-radius analysis
- retention/minimization
- regulator audit evidence
Methodology and source recordsThe detailed library retains official-source links, jurisdiction-specific conditions, exclusions, and its own date definitions for evidence snapshot, research verification, and metadata modification.
Review the evidence library
The library retains its August 23, 2026 evidence snapshot, August 25, 2026 research verification/cutoff, and August 26, 2026 metadata modification markers as distinct dates with distinct meanings.
Delivery approach
Move from observed data to a reviewable result.
- 01 / DISCOVEREstablish the supported inspection scope. PDI identifies the relevant systems, source materials, categories, locations, and operational context before an outcome is discussed.
- 02 / REVIEWMake the finding usable. Findings are organized into records and traceability that can be examined with the customer’s privacy, governance, security, and legal stakeholders.
- 03 / VALIDATEConfirm the technical record. Classification, location, context, and evidence are checked against the agreed inspection scope without making a legal determination.
- 04 / APPROVEKeep the decision with the right owners. The customer and counsel determine legal applicability, holds, exceptions, and whether remediation is approved.
- 05 / REMEDIATE WHERE SUPPORTEDApply only the approved bounded action. Mask, Vault, or Strip may be applied to approved supported structured data—not documents, scans, images, or attachments.
- 06 / EVIDENCE / REPORTRetain the control story. The resulting record connects the finding, review, decision, and technical outcome for subsequent inspection and discussion.
Important control boundaries
Control the action without overstating the result.
Protect the visible value
Replace identified PII with a protected representation when the approved structured-data workflow requires the record to remain usable without exposing the original value.
Keep recovery controlled
Place an original value in a controlled, tokenized, key-recoverable vault only when that action is approved for supported structured data.
Remove the approved value
Remove identified PII from supported structured-data output when the approved remediation decision is permanent removal.
Non-negotiable boundary
Documents, PDFs, scans, images, and attachments may be discovered, classified, and evidenced, but must not be represented as source-document remediation. Aadhaar OCR remains detection, inventory, and review support only. Kestryl is enabling PDI product technology, not this service’s identity.
Why PDI / service outcome
Privacy control maturity is a showable result.
Privacy Control Outcomes brings the technical estate, review context, evidence chain, and approved action into one PDI service posture. The objective is an observable privacy-control result—not a product feature pitch or a blanket compliance promise.
Service identityDELIVERED BY PDI · KESTRYL MAY ENABLE THE TECHNICAL WORKFLOWPDI
Evidence purposeTECHNICAL OUTCOMES FOR CUSTOMER AND COUNSEL REVIEWReview
Remediation scopeAPPROVED MASK, VAULT, OR STRIP ON SUPPORTED STRUCTURED DATA ONLYBounded
Decision ownershipCUSTOMER AND COUNSEL DECIDE APPLICABILITY, HOLDS, EXCEPTIONS, AND APPROVALCustomer
Next step
Turn the privacy control into a reviewable outcome.
Tell us which systems and source materials need to be understood. We will define the evidence path, supported scope, and customer approval points in writing.
PACIFIC DATA INTEGRATORS · SERVICES · PRIVACY CONTROL OUTCOMES