AGM-2854 Legal changes to the Filters policy#834
AGM-2854 Legal changes to the Filters policy#834anastasiia-fedotova wants to merge 2 commits intomasterfrom
Conversation
| This filter is designed to block both cookie notices and requests from cookie management platforms (CMPs). Depending on how a website implements its consent mechanism, different methods may be applied. | ||
|
|
||
| - Scriptlets are used to bypass the consent request (practically not applicable on sites with restrictions on loading third-party content until a decision is made) | ||
| - Setting a cookie or key in the site’s local storage in such a way that the script considers the user to have made a choice | ||
| - Simulating user action using a rule that clicks a specified button and interrupts its execution 10 seconds after loading. Two options are possible: | ||
| - Reject (except for functional cookies — depending on the CMP system) — the preferred option, as there is less risk of loading additional analytics tools | ||
| - Accept — this option is used as the last resort if other methods fail. In this case, the site is additionally checked for the use of analytics tools, which are then blocked by the **AdGuard Tracking Protection filter** | ||
| In most cases, simply hiding or blocking the corresponding scripts is sufficient. However, when the site’s functionality and display of third-party content require cookie consent, the filter applies alternative handling methods to resolve the request automatically. | ||
|
|
||
| Whenever possible, non-essential cookies are declined by default. If declining is not technically feasible and consent must be granted for the site to function correctly, the website is additionally reviewed for analytics and tracking technologies, which are then blocked by the **AdGuard Tracking Protection filter**. |
There was a problem hiding this comment.
The revised cookie notices section removes specific technical details about how consent is handled (scriptlets, cookie setting, simulating user actions). Consider preserving some of these technical details to maintain transparency about the methods used, especially for technical users who may want to understand how the filter works.
There was a problem hiding this comment.
The task was to remove these details
|
|
||
| - The site’s own advertising should not be deliberately blocked. However, it should not be unblocked if the blocking is caused by general filtering rules | ||
| - Content access measures like paywalls are not blocked | ||
| - Content access measures like paywalls are not blocked by Ad blocking filters. However, they may be blocked by Tracking protection filters if their operation results in a violation of user privacy |
There was a problem hiding this comment.
Consider rephrasing for clarity: "Content access measures like paywalls are not blocked by Ad blocking filters. However, they may be blocked by Tracking protection filters if they implement tracking mechanisms that compromise user privacy."
|
Preview was deployed to: https://pull-request-834.kb-adg.pages.dev/ |
1 similar comment
|
Preview was deployed to: https://pull-request-834.kb-adg.pages.dev/ |
No description provided.