The problem with ordinary consent logs
Most consent "proof" is just a row in the Fiduciary's own database. If a dispute arises, it's the organisation's word that the record wasn't changed after the fact. A regulator or court has to trust the keeper of the log — exactly the party with an incentive to edit it.
How a verifiable receipt is different
When a Data Principal consents, DPDP Bridge creates a receipt capturing who consented, to what purpose, under which notice version, and when — then signs it with a private cryptographic key. The matching public key is published. Anyone can run the receipt and the public key through a standard check and confirm two things: the receipt is genuinely ours, and not a single character has been altered since it was issued.
Why it matters under the DPDP Act
The Act puts the burden on you to show valid consent. An independently verifiable receipt is the strongest form of that evidence: it stands up without relying on your internal systems, and it's the same evidence your customer can keep for themselves — building trust, not just ticking a box.