Use ASP.NET Core cookie consent
@Flarescape said:
Since 01.01.2020 the following things are required:
-No cookies, except the absolutely necessary ones, are allowed before the user makes a decision
-All used cookies must be listed and described with technical name and what exactly they are for
-The user must have three options with the cookie banner (3 buttons): deny all, accept all, decide individually(button to save the individual decision)
-The individual decision should be made on cookie "categories" and not every single cookie e.g. use/don't use marketing cookies, use/don't use statistik cookies
-A direct link to the data protection information and the imprint
-It must be possible for the user to change the settings at any time
-The decision of the user should be saved for a maximum of 12 months and then be asked again.
The point "All used cookies must be listed and described with technical name and what exactly they are for" can also be solved by adding a link to a site where all cookies are listed and described, so the cookie banner is not that overfilled.
the user settings can be saved in a cookie even if the user clicks on "deny all" because this is categorized as "necessary cookie for basic functionality" like session cookies or a "cart cookie" for a webshop.
It has been implemented in OCC, if there's a plan to support it in OC I can send a PR for it
@hishamco That's great, I'll have a look. Thank you. 馃槃
Most helpful comment
@Flarescape said:
Since 01.01.2020 the following things are required:
-No cookies, except the absolutely necessary ones, are allowed before the user makes a decision
-All used cookies must be listed and described with technical name and what exactly they are for
-The user must have three options with the cookie banner (3 buttons): deny all, accept all, decide individually(button to save the individual decision)
-The individual decision should be made on cookie "categories" and not every single cookie e.g. use/don't use marketing cookies, use/don't use statistik cookies
-A direct link to the data protection information and the imprint
-It must be possible for the user to change the settings at any time
-The decision of the user should be saved for a maximum of 12 months and then be asked again.
The point "All used cookies must be listed and described with technical name and what exactly they are for" can also be solved by adding a link to a site where all cookies are listed and described, so the cookie banner is not that overfilled.
the user settings can be saved in a cookie even if the user clicks on "deny all" because this is categorized as "necessary cookie for basic functionality" like session cookies or a "cart cookie" for a webshop.