Enforce and prove consent across every system.
One consent decision, carried across every named system, with an audit-ready ledger you keep. Not a banner. Not a Consent Manager.
Made in India · Data stays in India
Blocked · Consent Withdrawn
- MarketingALLOWED
- AnalyticsBLOCKED
- PersonalizationBLOCKED
The problem
Consent is decided once. Then ignored.
A notice captures a decision. Analytics keeps processing. A processor keeps sharing. Personalization keeps tuning. The warehouse never hears about a withdrawal. Nobody has to be negligent for the decision to stop mattering.
“the decision had nowhere to go.”Sunil Mishra, Founder
Without a decision layer
A withdrawal reaches one system. The rest keep going. The decision stops mattering the moment it leaves the notice.
With a decision layer
One decision is checked on every read, across every named system. The next section shows what that check does.
Enforcement
They withdraw once. Everything stops.
On the next check, marketing, analytics, partners, and the warehouse all get a no. Same principal, purpose, and system contract. You keep the record.
Trigger
Consent withdrawn
DEC-34984 · 14:18:00Z
Analytics
✕ BLOCKED
Processors
✕ BLOCKED
Personalization
✕ BLOCKED
Warehouse
✕ BLOCKED
CDP
✕ BLOCKED
The ledger
The ledger is the product.
A regulator-grade record of every consent decision. Status, purpose, system, timestamp, decision id: the artifact you keep when banners are not enough.
Sample data. Your ledger looks like this.
| Purpose | System | Status | Timestamp | Decision ID |
|---|---|---|---|---|
| Marketing email | CDP | Granted | 14 Jul 2026, 09:12 UTC 2026-07-14T09:12:04Z | DEC-88421 |
| Product analytics | Analytics | Granted | 14 Jul 2026, 09:12 UTC 2026-07-14T09:12:04Z | DEC-88421 |
| Processor sharing | Payments vendor | Pending | 14 Jul 2026, 09:12 UTC 2026-07-14T09:12:11Z | DEC-88421 |
| Marketing email | CDP | Revoked | 15 Jul 2026, 14:18 UTC 2026-07-15T14:18:00Z | DEC-34984 |
| Personalization | Warehouse | Revoked | 15 Jul 2026, 14:18 UTC 2026-07-15T14:18:01Z | DEC-34984 |
Marketing email
Granted- System
- CDP
- Timestamp
14 Jul 2026, 09:12 UTC
2026-07-14T09:12:04Z
- Decision id
- DEC-88421
Product analytics
Granted- System
- Analytics
- Timestamp
14 Jul 2026, 09:12 UTC
2026-07-14T09:12:04Z
- Decision id
- DEC-88421
Processor sharing
Pending- System
- Payments vendor
- Timestamp
14 Jul 2026, 09:12 UTC
2026-07-14T09:12:11Z
- Decision id
- DEC-88421
Marketing email
Revoked- System
- CDP
- Timestamp
15 Jul 2026, 14:18 UTC
2026-07-15T14:18:00Z
- Decision id
- DEC-34984
Personalization
Revoked- System
- Warehouse
- Timestamp
15 Jul 2026, 14:18 UTC
2026-07-15T14:18:01Z
- Decision id
- DEC-34984
Sunil Mishra
Founder
Why we built it
“I spent years watching consent get decided properly and then quietly ignored. The CDP heard a week late, the warehouse never did.
Nobody was negligent; the decision had nowhere to go. Consentry is the layer that carries the decision to every system and keeps the record of why. That's the whole product.”
Pricing
How we price
From ₹24 / principal / year
Check consent on every read. It costs nothing extra. We don't bill per decision. We bill per year on active principals.
Metering decisions would tax the exact behaviour this product exists to encourage. Per-principal keeps checks free and costs forecastable.
Billed on
Active data principals
Unlimited
Decisions · Systems · Checks
| Tier | Active principals | ₹ / principal / yr |
|---|---|---|
| Starter | Up to 50k | ₹24 / principal |
| Growth | 50k–500k | ₹18 / principal |
| Scale | 500k+ | Talk to us |
Annual fee = active principals × the rate for your tier.
Trust, statute, and the clock.
One decision ledger for compliance, security, and engineering before core DPDP obligations land on 13 May 2027.
Until core obligations
292 days remaining until core DPDPA obligations on 13 May 2027.
13 May 2027 · 23:52 IST
Get proof-ready before the clock.
Get early access to the decision ledger
For compliance and platform teams building under the DPDP Rules. We reply within 1–2 business days.