-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to configure how Never-Consent clicks through GDPR popups #2165
Comments
Looks like the underlying library https://github.com/duckduckgo/autoconsent already supports opt-in option, so it should be relatively easy to implement allowing all trackers: add checkbox "Always Consent" in the UI, and when it is checked pass Adding further configurability, i.e. ability to only allow specific trackers or specific types of cookies, is likely much harder because the underlying JSON configs for specific CMPs only have rules for optIn and optOut. |
Hi @rryk , Thanks for your feedback regarding our extension. Unless you disable the extension or its features completely, the extension blocks trackers regardless of the user response towards the consent. Still, we don't block the consent configuration popup to allow users to opt-in to specific feature if required. May we know if you had any confusion or difficulties while using our extension because of auto opt-out feature of Never Consent? For me, it's not straightforward to understand some people will want to allow specific trackers and I believe there should be some reasons for that. If you saw a broken page, or have page that doesn't function as expected, you can report it from: https://github.com/ghostery/broken-page-reports/issues/new/choose. For allow specific trackers, you can allow them in our panel (which can be opened by clicking our icon) or settings page. It's true that it will not disable autoconsent rules, but it'll effectively disable tracker filtering rules from our side. Disabling them will not disable detection functionality. We're also aware of some feature requests that ask us to allow disabling specific CMPs for any reasons. I believe hearing about the detailed use-case would help us a lot given that we want to make an easy tool for users. We hope you to have a wonderful year end, and appreciate to your feedback again. |
I use neither Ad-Blocking nor Anti-Tracking because I do believe that free content requires both so that companies can make more revenue by showing me targeted ads. That said I do not believe that GDPR popups is an effective way to give people choice. Given that popups show on each website and usually on each visit if one opts out, users tend to just opt-in to get rid of them. It is also often easier to find the opt-in button and it requires fewer clicks. Instead, I and probably many others would prefer to be able to decide once for all sites whether they want targeted ads or not. This extension provides a way to automatically opt-out, but does not provide a way to automatically opt-in. It is also feasible that later one learns, e.g. from the news, than one of the companies that track them collects too much data, i.e. more than necessary for targeted ads, and would like to block that specific company. GDPR popups allow to configure choice per company, but that is harder to automate due to lack of configuration in underlying CMP JSON configs: https://github.com/duckduckgo/autoconsent/tree/main/rules/autoconsent. This is a bit theoretical for me at the moment, so I would consider it a separate lower-priority feature request. |
Currently. Never-Consent automatically rejects all cookies and tracking, which is great for privacy. However, some people might not like GDPR popus, but don't mind specific trackers, specific types of cookies or maybe just want to allow all tracking. This is a feature request to add configuration options that allow to customize how GDPR popups are automatically clicked through.
The text was updated successfully, but these errors were encountered: