| 133 | | ''[tbd]'' |
| | 133 | |
| | 134 | Every consent record contains an encrypted hash of itself and the consent option it refers to. If the text of the consent option is changed after users have given their consent, or the consent record is manipulated, then this hash becomes invalid. |
| | 135 | |
| | 136 | To verify the hash of a consent record, you can use the {{{auth_Consent.verify}}} method with the consent record ID: |
| | 137 | {{{#!python |
| | 138 | is_valid = s3db.auth_Consent.verify(consent_record_id) |
| | 139 | }}} |
| | 140 | |
| | 141 | This check is not required for regular use of the framework - but in case of a dispute, it can be used to prove the integrity of consent records. Note that this does not disprove willful manipulation of consent records, but it precludes crude/accidental modifications outside of the framework (e.g. DB modifications through the Web GUI). |
