Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Sprint:Fall 8 : 25 Nov to 6 Dec, Fall 9 : 9 Dec to 20 Dec, Spring 1 : 25 Dec to 17 Jan, Spring 2 : 20 Jan to 31 Jan, Spring 3 : 3 Feb to 14 Feb, Spring 3 : 17 Feb to 28 Feb, Spring 4 : 2 Mar to 13 Mar
Description
Situation: Europe requires any site that uses cookies to inform the user, and give them a chance to accept/deny.
Task: Implement a cookie notification that requires the user to accept or back out of the site.
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
While researching the standard way to implement cookie warnings in websites, I came across contradicting explanations on the EU Cookie law and the changes in the legislation made recently (2019). According to https://www.privacypolicies.com/blog/eu-cookie-law/, a simple warning to indicate our usage of cookies would suffice to comply with the law. They underscore this with a good example, the UK Information Commissioner office website (https://ico.org.uk/). This is the website for ICO, the independent authority in UK that enforces the cookie law in the country. However, the interpretation of the law by this website, https://www.cookiebot.com/en/cookie-banner/, says that we should provide options to the user "to opt-in or opt-out of various types of cookies". Cookiebot is a tool that we could register to that fixes compliance problem. However, I am not sure if that's necessary for our purposes.
Merged https://bitbucket.org/nfreese/django-cyversedev/pull-requests/132/igbf-2118-implemented-cookie-warning/diff
Basic cookie alert is working.
Closing issue.
Note, we may decide in the future to expand the cookie warning.