Skip to content
ONE3.ai

How it works · Flow F14

Access and erasure requests that reach every store — including AI

Requests are verified, data is located across records, files, vectors, memory, caches and analytics, an access report or erasure plan is approved, executed, propagated and evidenced.

What the DPDP data-principal requests flow does

India's Digital Personal Data Protection (DPDP) Act gives people rights over their personal data. One3 plans to make those rights reach everywhere data lives, including AI systems.

A request arrives through the portal or by email. The person's identity is verified. One3 locates their data across Objects, files, vector indexes, agent memory, caches, analytics and the backup policy. It produces an access report or an erasure plan, which is approved. Erasure or anonymisation runs and propagates to indexes and training lineage. Confirmation is sent within the statutory timeline, and evidence is stored.

DPDP basics (consent, notices, data-principal requests) are planned for W1; Privacy Ops as a full module is W3. Statutory timelines and obligations are items to verify with privacy counsel — this page is not legal advice.

Every step on this page is an Action: a typed verb with a risk tier (R0 read-only to R4 irreversible or financial), a permission check and a reversibility class. Agents and humans call the same Actions, so the same approval rules apply whether a person clicks a button or a Digital Employee acts.

DPDP data-principal requests, step by step

Eight steps from request to stored evidence.

  1. 1

    1. Request received

    **Platform · Trust & Audit · portal or email.** A data-principal request is logged as a DataRequest.

  2. 2

    2. Identity verification

    **Platform · Identity & Access.** The requester's identity is verified.

  3. 3

    3. Locate data everywhere

    **Platform · Trust & Audit.** Objects, files, vectors, memory, caches, analytics and backup policy.

  4. 4

    4. Access report or erasure plan

    **Legal, Risk & Compliance · Privacy Ops.** A clear report or a plan listing every store.

  5. 5

    5. Approval

    **Human gate · DPO or owner.** Privacy-impact Actions need human approval.

  6. 6

    6. Execute and propagate

    **Platform.** Erasure or anonymisation, propagated to search and vector indexes, memory and training lineage.

  7. 7

    7. Confirmation

    **Platform · Notifications.** Within the statutory timeline (verify).

  8. 8

    8. Evidence stored

    **Trust & Audit.** Evidence kept for audit.

Regulatory note

DPDP Act and Rules obligations, including timelines, are verify items in the Fact Register. Confirm with privacy counsel before relying on them.

Questions about this flow

Does erasure reach AI memory and indexes?

Yes, that is the design. Erasure propagates into vector indexes, caches, memory stores, training-dataset lineage and per-tenant adapters.

Who approves an erasure?

A human — typically the DPO or data owner. Privacy-impact Actions always need human approval.

Can a person see what One3 remembers about them?

Yes. Memory items are user-visible and erasable.

Is this legal advice?

No. Regulatory points are pointers. Verify obligations with counsel.

When is this planned?

DPDP basics in W1; the full Privacy Ops module in W3.

Talk to us about privacy

Privacy and compliance leads can help us test data-principal requests end to end.

Become a design partner