Turn a moving regulatory target into a versioned, auditable library.
Indian data law is mid-rollout: the DPDP Rules were notified in November 2025 with full compliance due by May 2027, and CERT-In directions already bind ICT operators. Praman stores every obligation as versioned data with its citation, so legal teams can amend the rule set as the law settles — and prove exactly which version applied on any given date.
The problems we hear from legal, risk & compliance teams
- ▹Rules change faster than internal policies can be re-issued
- ▹No way to show which obligation version was in force at a point in time
- ▹Audit responses assembled by hand under deadline pressure
- ▹Citations and evidence live apart from the controls they justify
What Praman does for you
Versioned obligation library
Each obligation carries a framework, severity, citation, effective-from date and version number. Amend without a redeploy.
Evidence-linked everything
Every status links to an immutable audit event — no claim without a traceable reason.
Audit Pack export
One click produces a regulator/auditor-ready bundle: posture, checks with citations, breach timeline, retention proofs and an integrity certificate.
Counsel-friendly disclaimers
Praman is tooling, not legal advice — and says so throughout. The library is yours to amend with counsel.
Obligations you’ll see covered
Each maps to an automated check with its statutory citation and tamper-evident evidence.
Frequently asked
Is the obligation library legal advice?
No. It is a configurable starting library with citations, intended to be reviewed and amended by your counsel. Praman provides compliance tooling, not legal advice.
Can we prove which rule applied last quarter?
Yes. Obligations are versioned with effective-from dates, and evaluations are recorded as immutable, time-stamped audit events.