You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Thanks very much for adding the privacy pack option ( #507). GDPR is a big deal for everyone.
The cookie consent banner has a “Learn more” link to https://cookiesandyou.com/, which has some explanatory text including “a simple way we could tell our mums”. The explanatory content of "About cookies" is quite reasonable, but the "our mums" bit is down the bottom in the bit about the company that made the website. I think it's patronising and not necessary for the purpose of the page. I would really prefer not have my website linking to it. Would it be possible to have the "Learn more" link point to somewhere else with an explanation of cookies?
Thanks
The text was updated successfully, but these errors were encountered:
gcushen
changed the title
Cookie consent "learn more" links to a page with some patronising content
Enable cookie consent "learn more" link to be customised
May 12, 2018
The cookie consent "learn more" is now linked to your privacy policy, if it exists. To enable, update the theme, create privacy.md in content/ and add the content of your privacy policy just like a normal post. An example privacy.md can be found in bf01c80.
Thanks very much for adding the privacy pack option ( #507). GDPR is a big deal for everyone.
The cookie consent banner has a “Learn more” link to https://cookiesandyou.com/, which has some explanatory text including “a simple way we could tell our mums”. The explanatory content of "About cookies" is quite reasonable, but the "our mums" bit is down the bottom in the bit about the company that made the website. I think it's patronising and not necessary for the purpose of the page. I would really prefer not have my website linking to it. Would it be possible to have the "Learn more" link point to somewhere else with an explanation of cookies?
Thanks
The text was updated successfully, but these errors were encountered: