GDPR cookie compliance - Githubissues

hemebond / quaddicted

Quaddicted upgrade written with Django

MIT License

7 stars 1 forks source link

Closed hemebond closed 3 years ago

hemebond commented 4 years ago

[ ] If no consent cookie then no other cookies should be set
[ ] If consent cookie is missing or declined, then no forms, which require a CSRF cookie, should be presented to the user
[ ] If no consent cookie then all pages with forms (and hence CSRF tokens) should include a modal asking for consent, and reload the page on selection

hemebond commented 4 years ago

No cookies should be set until the user has granted or declined consent to set cookies. Re-opened with new tasks.

SpiritQuaddicted commented 4 years ago

Brrrr, so complicated and overkill for sites like this. Maybe there is some Django add-on that does it?

hemebond commented 3 years ago

I'm going to remove it completely. The site does not use any non-essential or third-party cookies so a banner or warning is not required.

SpiritQuaddicted commented 3 years ago

Are you 100% sure about that? To my knowledge being restricted to first-party cookies does not remove the need for consent (or information at least).

hemebond commented 3 years ago

Yip. Quaddicted only uses functional cookies (sessions). Github just removed their cookie banner for the same reason.