Panel 01. Self-hosted in your environment
This document specifies a self-hosted compliance solution that helps companies comply with the Digital Personal Data Protection (DPDP) Act 2023 and the rules published thereunder in 2025. The product is delivered as software that each client deploys inside its own environment: a Java / Spring Boot / Maven backend and a React frontend, installed and operated by the client's own IT / Platform Administrator, with no requirement to send compliance data outside the client's infrastructure.
The intended audience is the client organization's compliance and platform staff:
A binding precondition on all work described here: the applicable 2025 rules published regarding the DPDP Act must be researched and incorporated as the authoritative basis for the compliance workflows before implementation of those workflows begins.
The system is a compliance system of record. It maintains durable, client-owned records of consent, data-principal requests, and compliance evidence, and it presents the organization's compliance status against the obligations of the DPDP Act 2023 and the 2025 rules.
Current delivery is a first-party web application, self-hosted by the client:
Actors:
Accepted behavior covers: anonymous explanation of the product and its self-hosted model; identity establishment and returning verification for the client's compliance and platform staff; a protected compliance overview; management of durable consent records; tracking and completion of data-principal request lifecycles; production and revisiting of compliance evidence; and management of compliance-team access by the client-side platform administrator.
Narrow exclusions: this document does not add adjacent account-management capabilities beyond first-use invitation acceptance, returning login, and the platform administrator's provisioning of compliance-team access; it does not add capabilities from the broader legal-tech or privacy-platform category that the source did not accept; and it does not place any compliance capability with an external or provider-owned surface.
The product exists so that a company can demonstrate DPDP Act 2023 compliance without moving its compliance data out of its own environment. Everything the compliance team does — reviewing status, managing consent, handling data-principal requests, producing evidence — happens inside the instance the client deployed.
Access ownership is first-party and application-owned. The Landing page is anonymously reachable and explains the product, its intended company users, and the self-hosted deployment model. Identity is established through first-use invitation acceptance, and returning users verify through Login. Protected destinations require an established identity; the interaction that establishes access is never owned by the destination it protects.
The 2025 rules are in scope now, not later: they are the authoritative basis for the compliance workflows, and the work of researching and incorporating them precedes implementation of those workflows. The rulebook references surfaced in the interface are the visible expression of that incorporation.
The reference directive for "2025 rules published regarding the DPDP Act 2023" is declared with uses: ["domain_context", "content_source"] and authority: authoritative. The verified factual content available from that directive, as carried into this document, is:
No further verified factual entities, collection items, field values, dates, contacts, links, or media references were supplied by that directive; nothing beyond the above is asserted as verified content.
FR-1 — Research the 2025 rules before implementation (explicit) As a Compliance Officer, I should have the compliance workflows built on the 2025 rules published regarding the DPDP Act 2023, so that the organization's compliance posture reflects the current regulatory basis.
FR-2 — Understand the product and its self-hosted model before committing (explicit) As a Compliance Officer, I should be able to understand, without an account, what the solution does, who it is for, and that it is deployed in my own environment, so that I can decide whether to pursue it.
FR-3 — Establish identity on first use and verify it on return (required_inference) As an invited compliance-team member, I should be able to accept my first-use invitation and, on later visits, verify my identity, so that my compliance work remains bound to me and resumable.
FR-4 — Provision compliance-team access (required_inference) As an IT / Platform Administrator (client-side deployer), I should be able to provision compliance-team access in the deployed instance, so that invited users can use the protected workflows.
FR-5 — Review compliance status and continue into the work that needs attention (required_inference) As a Compliance Officer, I should be able to see the organization's compliance status and the 2025-rule context for the current screen, so that I can continue into the workstream that needs attention.
FR-6 — Manage durable consent records (required_inference) As a Data Protection / Privacy Administrator, I should be able to browse and manage durable consent records and their related DPDP obligations, so that consent lifecycles are handled accurately and traceably.
FR-7 — Track and complete data-principal request lifecycles (required_inference) As a Data Protection / Privacy Administrator, I should be able to track and complete data-principal request lifecycles and their related records, so that requests are handled accurately and traceably.
FR-8 — Produce and revisit compliance evidence (required_inference) As a Compliance Officer, I should be able to produce and revisit compliance evidence for audits or regulators, so that the organization can demonstrate DPDP compliance.
FR-9 — Deploy and run the solution in the client's own environment (explicit) As an IT / Platform Administrator (client-side deployer), I should be able to deploy and run the Java / Spring Boot / Maven backend and the React frontend inside the client's own environment, so that the compliance team can use the solution without external hosting.
The creative direction is authoritative for this section. Muse: Erik Spiekermann. Headline idea: typographic infrastructure for data protection — compliance as public wayfinding. The product is a compliance system of record: every screen is a form, a register, a deadline, or an evidence artefact.
Colour tokens — light mode
| Role | Hex | Use |
|---|---|---|
| Background | #F4F1EA | Warm paper ground; never #FFFFFF |
| Surface | #FFFFFF | Register surfaces |
| Text | #16181A | Near-black ink type |
| Primary | #1B3A6B | Deep transit blue — structure only: rules, headers, navigation, links, focus rings |
| Accent | #E4572E | Signal orange — reserved strictly for urgency: overdue DPDP deadlines, breach-clock countdowns, unverified consent, and the single CTA on each screen |
| Muted | #8A8578 | Secondary text and inactive structure |
| Status — verified/closed | #2E7D5B | Coded status alphabet |
| Status — pending review | #C9A227 | Coded status alphabet |
| Status — draft/archived | #6B7280 | Coded status alphabet |
Proportion: ~70% paper, 20% ink/blue structure, 7% coded status chips, 3% orange. Never place orange on blue. Never use blue for status meaning — blue is structure only. Every colour on screen must map to a status, a route, or a section boundary.
Typography
Shape language
#16181A at 12% opacity divide everything; 2px solid rules in #1B3A6B mark section boundaries.0 1px 2px rgba(22,24,26,0.06) on modals.Layout
Imagery
The DPDP route map as the public entry. The Landing page is a full-viewport wayfinding poster, not a centred SaaS hero. The left two-thirds carry a schematic transit map of DPDP compliance drawn in #1B3A6B lines on the #F4F1EA ground, with stations labelled in 13px uppercase Fira Sans Condensed: Notice, Consent, Purpose Limitation, Data Principal Request, Erasure, Breach Notification, Consent Manager. One route is drawn in #E4572E and labelled "2025 Rules: breach notification in 72 hours", so the accent carries the single most urgent regulatory fact. The right one-third is a vertical stack of three numbered fact panels separated by 2px rules: "01 Self-hosted in your environment", "02 DPDP Act 2023 + 2025 Rules", "03 Evidence for the Data Protection Board". Above the map, a 48px Fira Sans Condensed headline spans the full grid width, flush-left, ragged-right: "Compliance you can point to." The primary CTA is a rectangular #E4572E block cut into the bottom-left of the map, with white uppercase 13px tracked label "Request deployment brief". No gradient, no blob, no centred stack, no blue button.
The concept recomposes only accepted content and controls: the obligation stations, the 2025 breach-notification rule, the self-hosted deployment fact, the DPDP Act 2023 plus 2025 Rules basis, the Data Protection Board as evidence recipient, and the entry into Login.
Interaction Model: Static Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
#F4F1EA ground, with the single #E4572E route labelled "2025 Rules: breach notification in 72 hours".#E4572E. Rationale: the accepted work is deadline-driven and audit-facing; misreading a deadline is a material failure of the accepted outcome.#F4F1EA, and the blue is deep transit #1B3A6B used for structure only.
DPDP Act 2023 + 2025 Rules
Deployment basis
Panel 01. Self-hosted in your environment
Panel 02. DPDP Act 2023 + 2025 Rules
Panel 03. Evidence for the Data Protection Board
Rule 3(2) · Rule 6(1)(a) · Rule 8
Deployment
Legend — DPDP obligations
Pictograms are drawn on the same 24px grid as the route map stations above. Breach notification — 72 hours under the 2025 Rules.

DPDP Act 2023 + 2025 Rules
Deployment basis
Panel 01. Self-hosted in your environment
Panel 02. DPDP Act 2023 + 2025 Rules
Panel 03. Evidence for the Data Protection Board
Rule 3(2) · Rule 6(1)(a) · Rule 8
Deployment
Legend — DPDP obligations
Pictograms are drawn on the same 24px grid as the route map stations above. Breach notification — 72 hours under the 2025 Rules.
No comments yet. Be the first!