SovereignShield
Checking local DPDP storage…The workspace must be able to write to this browser before you enter data.

Storage is browser-managed. Private browsing may provide session-only storage even when this capability check succeeds; export important records before closing that session.

Something wrong? Email us

← DPDP workspacePhase 2 · local only

Notice & consent generator

Draft one notice per purpose from a static local dictionary. Each purpose has its own modeled choice; there is no bundled accept action.

Local dictionary only: translations are bundled in this application. No translation API or notice content network request is made.

Translation provenance will appear when a language is selected.

Step 1

Set notice context

These values stay in this browser and are inserted into each local draft.

A “draft” language is available for local review but is not presented as linguistically or legally verified.

Step 2

Choose purposes separately

Save, export, and model a choice per purpose. A single bundled consent action is intentionally not provided.

Step 3

Export package

The combined package contains separate notices and separate modeled choices.

Modeled consent limitation: any choice recorded here is self-reported configuration data. It is not proof that a production consent event occurred and does not write to a customer database.

Drafts and modeled choices use the dedicated local DPDP IndexedDB database. DPDP records are not included in peer-sync in v1.