Skip to content
DPDP
Ahmedabad·built for Indian law

We Build the Boring Part of Privacy

Policies are easy to write and hard to keep true. We build the machinery that keeps the promise your privacy notice makes.

Data residency
IndiaData residency
Languages
22Languages
Training on your data
0Training on your data

Why we exist

The DPDP Act arrived with real penalties and very little tooling built for Indian reality — 22 languages, Indian data residency, RBI and clinical retention rules that pull against erasure rights. Teams were left stitching a global suite to a spreadsheet. We thought the country deserved software written for its own statute.

How we think about compliance

Compliance is not a document, it is a state your systems are in. That means the useful question is never “do we have a policy” but “can we prove, today, what we told this person and what we did with their data”. Everything we build answers that second question.

What we will not do

We will not ship dark patterns, even when a customer asks. We will not train models on customer data. We will not claim a module exists before it ships — a compliance vendor that misrepresents its own capability has already failed the only test that matters.

Where we are

Ahmedabad, Gujarat, with infrastructure in Indian regions. Support runs on IST, because a compliance question at 3pm in Mumbai should not wait for a timezone to wake up.

Company details on this page — legal entity name, registration and leadership — need to be confirmed before publication.