HI All, This would be of interest, (thanks for the share Tim) Some Consent Receipts v1.1 this one is a concept (from 2018): in which the consent receipt was not finished, but moved to ISO by some advanced digital identity management companies, First is https://www.ubisecure.com/data-protection/what-is-consent-receipt/. It does, indeed, show the data subject receiving the receipt. Here is another article on consent receipts that recognizes the value to data controllers:https://clym.io/blog/what-is-a-consent-receipt-and-why-it-matters Although neither of these enable operational consent, which the consent receipt v2 spec with the Consent by Design model, would / will address In this model, a) a Notice receipt is generated from the PII Controller credential- listed at our controller registry, via our notary API (this can be for any legal justification including consent) b) the notice receipt can then be used by the individual as a consent receipt token, with the individual (the user) sending it back to the controller to direct or manage consent. Hopefully we can get some ANCR resources to move this work forward this summer, Mark