THE QUICK READ

The story in brief

DEPA is an architectural and institutional idea for consent-based data sharing. Its discussion-paper origins should be kept distinct from the current rules applying to a specific product.

Source starting point: NITI Aayog: DEPA draft for discussion, August 2020 ↗. Full sources and context appear below.

NITI Aayog’s 2020 discussion paper introduced Data Empowerment and Protection Architecture as a framework for consent-based data sharing. It is useful to read DEPA as an architectural and institutional idea in its historical context. The paper is a discussion document, not a substitute for the laws and sector rules that apply to a particular product today.

A permission screen is only one part

Consent has to connect to an actual data flow. The person granting it should be able to understand the intended purpose, while the system needs ways to carry that decision through the process. A well-written button cannot compensate for an unclear relationship between the request and what happens afterward.

Design the whole information journey

Our editorial question is where a user’s understanding can become separated from the system’s behaviour. Consider the request, the recipient, the duration and how someone learns what happened. That perspective can help a startup ask better product questions even before a particular integration is chosen. The practical implementation still needs to follow the current requirements of its domain.

Use the architecture to ask better product questions

A framework can help a team see where permission, information movement and responsibility belong in a service. It does not supply every answer for a particular implementation. Begin with the proposed use of data, then map the organisations and decisions involved. Ask what the person sharing information needs to understand and how that understanding is reflected in the product. Keep historical concepts separate from current legal and sector requirements. This makes an architecture discussion useful without turning it into a copied compliance checklist. The founder benefit is a more explicit design conversation about data use, rather than treating consent as a label added to a finished form.

Turn a principle into a visible product behaviour

Consent-based data sharing becomes meaningful in the choices a person can see and exercise. A founder studying DEPA can use the historical paper to frame questions about purpose, control and accountability, then consult the current legal and sector-specific framework for implementation. Write down what the product actually does when a person agrees, declines or changes a permission. Those behaviours are easier to review than a broad statement that the product respects data. The architecture and a compliant implementation are related but distinct subjects.

YOUR WORKING NOTES

A practical next-step checklist

Use these questions to investigate the idea in your own context.

  1. Map each requested data item to a specific purpose and recipient.
  2. Document the behaviour of consent, refusal and any available withdrawal controls.
  3. Check the present applicable requirements with qualified support rather than treating a discussion paper as law.

A closer look

Can the DEPA discussion paper replace current data-protection guidance?

No. It explains an architectural direction in a particular historical context. A live product needs to be assessed against the current rules and obligations that apply to it. This article is an ecosystem explanation, not a compliance determination.

Sources & editorial note

This guide draws on the sources below. Our practical questions and analysis are editorial interpretation. Historical documents describe their own period; use current official programme information for availability, terms and applications.

See our editorial standards or request a correction. For a useful comparison, read Nandan Nilekani: the EkStep founder story. Explore the founder topic guides for connected reading paths.