The full consent lifecycle across web, app and API touchpoints, specified clause by clause against the Act and the Rules before a line of code was written. This module also runs standalone, and its onboarding data carries into every module you add later.
Granular, purpose-specific, affirmative consent across web, app and API touchpoints. Default-deny: nothing is pre-ticked and no purpose is bundled into another. Notice is served in English plus Eighth Schedule languages, and the version and language actually shown are written onto the artefact.
A pre-processing gate. Before any processing act, the Data Fiduciary queries the API: does consent exist, is it active, has it not expired, and does the requested use fall inside the consented purpose? All four must pass. It fails closed: an error or a timeout is a refusal, not an approval.
A Data Principal can modify individual purposes without disturbing the others. Each change writes a new artefact version; the prior version is retained and remains retrievable, because the question you will be asked is what the consent was on a given date.
Scheduler-driven reminders ahead of expiry, with re-affirmation as simple as the original grant. A renewal that is harder than the first consent produces attrition that looks like withdrawal and is not.
As easy as giving. Processing halts in real time, every downstream processor is instructed to cease, and each must acknowledge that it did. The acknowledgements are part of the record, because instructing a processor is not the same as proving it stopped.
Consent lapses automatically at the end of its validity period and processing halts. No silent extension, no grace period that nobody agreed to.
Stored immutably and versioned. Prior versions are never overwritten, because the question is rarely what the consent is now. It is what the consent was on the day the processing happened.
Every write, and every read of a validation decision, appends to a tamper-evident audit log with cryptographic hashing.
Access, correction, erasure and nomination through a self-serve portal. Every request is logged, assigned to an owner, tracked against the statutory response window, and closed with an exportable record of what was done and when.
Grievances route to a named Grievance Redressal Officer with acknowledgement and response timers running from receipt. A Data Principal must exhaust this before approaching the Board, which makes it the mechanism that decides whether you ever meet the Board at all.
Pushes the correct privacy policy, consent notice and retention policy to each touchpoint and each purpose, and forces re-consent where a change requires it. One place to change a notice, every surface updated, with a version history behind it.
