Consent Engine
Purpose-bound, language-native consent for every collection point.
Capabilities
What Consent Engine does in your environment.
All 22 Indian scheduled languages
Notices served in every Eighth Schedule language. Comprehension is the standard, not just delivery. All translations maintained and versioned.
Per-purpose consent
Separate, granular consent for each stated processing purpose, stored with timestamp, version, and channel. Unbundled as DPDPA requires.
Notice version management
Every notice version is archived and linked to the consent record it generated. If a notice changes, affected consents are flagged for reconsent.
Multi-channel delivery
Web widgets, mobile SDK, SMS, email, and in-person kiosk modes. The same consent record regardless of which channel captured it.
Real-time consent status API
Query consent status per individual, purpose, and data type in real time. Integrates with your processing pipelines so unconsented processing is blocked upstream.
DPDPA Coverage
Which sections this maps to.
Notice must be given before or at the time of collecting personal data. The Consent Engine delivers it.
Consent must be free, specific, informed, unconditional, and unambiguous. Each attribute is enforced by the notice and consent flow design.
Deemed consent scenarios (employment, emergency, law) are handled as separate consent categories with their own audit trail.
See Consent Engine in action
A 30-minute walkthrough mapped to your data environment and DPDPA obligations.