Automatic consent test for changes

  • Resolved neoset

    (@neoset)


    4 years, 9 months ago

    This is what the “Proof of consent” section says:
    When you make significant changes to your cookie policy, cookie banner, or revocation functionality, we will add a time-stamped document under “Proof of Consent” with the latest changes. Daily, the document will be generated if the plugin has detected significant changes.
    So is it necessary to generate 1 proof of consent or is the application already generating it?
    Every time changes are made to the cookie policy, cookie banner or revocation functionality, does the application automatically generate a new document or update the existing one?
    Do I need to manually generate a new document every so often, for example every day or is the first document generated the one that is continually updated?
    Thanks for the patience and greetings.

Viewing 1 replies (of 1 total)
  • Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @neoset,

    The proof of consent will be generated after 24 hours when a significant change was made in the wizard. For example, when you have added a new service to your list, the cookie policy will be updated and all prior consent revoked. This means users will need to consent to your new cookie policy again, after significant changes.

    Because changes are infrequent and sometimes multiple times a day during a development sprint, for example, it takes 24 hours after the last significant change, for the new proof of consent to be generated.

    A full explanation can be found here: https://complianz.io/user-consent-registration/
    What your users will read if you send them the proof of consent: https://complianz.io/consent/

    Let me know if you have any questions,

    regards Aert

Viewing 1 replies (of 1 total)
  • The topic ‘Automatic consent test for changes’ is closed to new replies.