Keep the person in view.
Behind every record is someone who may ask what happened to their information.
DPDPHQ / PEOPLE. DATA. PROGRESS.
They trust you
with their data.
A phone number at billing. An email in your CRM. If it can identify a person, it is personal data. India’s Digital Personal Data Protection (DPDP) law sets rules for how businesses collect, use and protect it.
SWARN is in development. Register interest for early-access updates.
THE WORK BEHIND THE DATA
Permission has
a purpose.
A phone number given for a delivery is not blanket permission for marketing. When you rely on consent under DPDP, explain the purpose, ask for a clear choice and make withdrawal straightforward.
Know the path it took.
See which tools hold the details, what each team uses them for, and where they went next.
Close the loop.
Put the unresolved step in front of the team that can act, with a record of what follows.
MEET OUR FIRST PRODUCT
SWARN A DPDPHQ PRODUCT
A customer says
Delete my data.
The answer may sit in your billing software, CRM, spreadsheets and messages. We’re building SWARN to help you find those records, follow the request across tools and keep evidence of what was done.
Step inside SWARN
THE FRAMEWORK IN PRACTICE
Consent is more
than a checkbox.
A clear choice needs a clear purpose. It also needs a way to remember what was agreed, respect a changed mind and show the work done after a request.
01Collect consentMake the purpose clear before data moves.
THE PUBLISHED FRAMEWORK
When consent is the applicable basis, section 6 requires a clear affirmative choice that is free, specific and informed for the stated purpose.
Read Act sections 5–6 ↗WHERE SWARN FITS
SWARN is being built to show where consent was collected, the stated purpose and the systems where a team needs to review the record.
A contact import is not proof of consent. The illustrative workspace does not collect customer records.
Explore notice and purpose →02Manage choicesKeep choices visible as data crosses tools.
THE PUBLISHED FRAMEWORK
Section 6 says a person should be able to withdraw consent with comparable ease. Section 8 keeps the organisation responsible for personal data it processes, including through processors.
Read Act sections 6 and 8 ↗WHERE SWARN FITS
SWARN’s planned systems, inventory and data-flow views are intended to map hand-offs across CRM, POS, sheets and messages.
No named business-tool connection is operating through this website, and no universal integration is promised.
Explore the integration roadmap →03Prove permissionKeep the notice, choice and later events together.
THE PUBLISHED FRAMEWORK
Section 6(10) places the burden of proving that notice was given and consent was obtained on the organisation relying on consent. A useful record keeps the notice, purpose, choice and later events distinct.
Read Act section 6(10) ↗WHERE SWARN FITS
SWARN’s audit and reports modules show the intended place to examine a trail and identify what still needs evidence.
A dashboard view is not a certification or a legal conclusion.
Explore evidence engineering →04Honour requestsRoute access, correction and erasure work to the people who can act.
THE PUBLISHED FRAMEWORK
Sections 11 and 12 describe access, correction, completion, updating and erasure rights, subject to the Act. Section 6(6) requires processing to stop within a reasonable time after withdrawal. Sections 8(7) and 12(3) keep purpose and legal-retention exceptions in view for erasure.
Read Act sections 6, 8, 11–12 ↗WHERE SWARN FITS
SWARN’s planned requests view is intended to organise the owner, action and downstream follow-up a responsible team must verify and complete.
A recorded request does not prove deletion in every downstream system or provide a legal certificate.
Explore rights operations →Educational summary. Commencement varies by provision. Most business-facing provisions discussed here are scheduled for 13 May 2027. Check the legal-status ledger ↗
- Final Rules published
- 13 Nov 2025
- Cited provisions scheduled
- 13 May 2027
- Wording checked
- 29 Sep 2026
SOURCES AND ENGINEERING
Trust the source.
Show the work.
Read the official documents behind the guidance. Then examine the engineering records, controls and patterns that turn a principle into decisions a team can inspect.
Search 78 engineering records01 / FOR THE BUILDERSFrom principle to practice.
Eight implementation layers, linked controls, and patterns.
↗02 / CHECK THE FOUNDATIONThe source, before the summary.Official documents, publication dates, and commencement.
↗03 / FOLLOW YOUR QUESTIONA network of different perspectives.Find a specialist learning path across the DPDP network.
↗Clarity begins with purpose.