Legal, Risk & Compliance · Module
Privacy Ops
Data inventory, data-principal requests, DPIAs and breaches as clocked workflows
Privacy Ops runs the privacy programme on live data: what personal data exists where, why it is processed and by whom. Data-principal requests, DPIAs and breaches run as clocked, evidenced workflows.
What it does
Privacy Ops is designed to operate the privacy programme on live data. It knows what personal data exists and where, including files, vector collections, agent memory and caches; why it is processed; and who processes it. It extends the platform's Trust & Audit data request capability with full workflows.
Inventory and records
The data inventory is auto-seeded from field classifications in the shared data model, Pack schemas, files, vector collections and agent memory stores, with owners per app. Processing activity records describe purpose, categories of data and principals, systems, recipients, processors, retention, transfers and safeguards. At GA, the processor and sub-processor register is built from Contracts DPAs and Procurement vendors, and a cross-border transfer register records destinations and safeguards.
Data-principal requests
Requests arrive by portal, email, WhatsApp, Service Desk ticket or API, with request types per DPDP (to be verified). Identity is verified by OTP, documents through KYC where subscribed, or representative and nominee evidence. Discovery resolves the person and all their role records, files, activities, messages, vectors, agent memory and analytics copies. Access reports redact third-party data and need reviewer approval. Erasure plans list delete, pseudonymise or retain-with-reason per location, check blockers such as statutory retention, legal hold and open disputes, and are approved as R4 Actions before running as a durable workflow with an erasure ledger. Correction requests route to the owning module. SLA clocks track statutory and configured deadlines with recorded pauses.
Breaches and DPIAs
The breach register takes intake from Security Center or manual reports and records severity, affected principals and data, containment, the decision to notify, clocks and evidence. DPIAs start with a screening questionnaire, are drafted from the processing record, reviewed by the DPO and periodically re-reviewed. A Significant Data Fiduciary pack and grievance redressal are planned.
Planned for W3 (Year 2), with external system discovery and global packs in W4. All regulatory timelines are pointers to verify with counsel.
Features
What Privacy Ops includes
Auto-seeded data inventory
Personal-data fields from classifications, Pack schemas, files, vectors and agent memory, with owners per app.
Processing activity records
Purpose, data and principal categories, systems, recipients, processors, retention, transfers and safeguards.
Request intake
Portal, email, WhatsApp, ticket and API intake for access, correction, completion, update, erasure, grievance and nomination.
Identity verification
OTP, document verification through KYC, and authorised representative or nominee evidence.
Data discovery for a request
Resolves the person across records, files, activities, messages, vectors, agent memory and analytics copies.
Access reports with redaction
Human-readable packages with third-party data redacted and reviewer approval.
Erasure plan and execution
Per-location delete, pseudonymise or retain-with-reason, blocker checks, R4 approval and an erasure ledger.
SLA clocks
Deadlines per request type and jurisdiction with recorded pause rules.
Breach register and workflow
Severity, affected data, containment, notification decisions, clocks and evidence.
DPIA templates and workflow
Screening, AI-drafted DPIA from the processing record, DPO review, approval and periodic review.
Processor and transfer registers
Processors from DPAs and vendors; cross-border transfers by destination, basis and safeguards.
Grievance redressal and dashboards
Grievance officer contact and timelines; requests, SLA, breaches, DPIA coverage and inventory completeness.
Workflow
Erasure request
- 1
The request is triaged and identity verified
- 2
Discovery locates the person's data across One3
- 3
An erasure plan is computed with blockers such as retention and holds
- 4
A person approves the plan as an R4 Action
- 5
Execution runs as a durable workflow and writes the erasure ledger
- 6
The principal is informed
Workflow
Breach response
- 1
A suspected breach arrives from Security Center or a manual report
- 2
Severity, affected principals and data are recorded
- 3
Containment actions are logged
- 4
A decision to notify the authority and principals is recorded against the clock
- 5
Notification drafts are approved and sent
- 6
Evidence is retained
AI
AI skills and Digital Employees
Request triage
Request type, duplicates and missing identity information.
Data location narrative
Plain-language report from deterministic discovery results.
Third-party data redaction
Detects third-party personal data in access reports and proposes redactions.
Breach and DPIA drafts
Impact summaries, notification drafts and DPIA drafts citing processing record fields.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Does discovery include AI agent memory?
Yes. Discovery is designed to cover records, files, messages, vector collections and agent memory.
Can AI erase data?
No. Erasure is an R4 Action approved by a person. AI drafts plans and communications only.
What are the DPDP deadlines?
Timelines are configured from Fact Register entries that must be verified with counsel. This page is not legal advice.
See Privacy Ops in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.