-
Notifications
You must be signed in to change notification settings - Fork 372
AGM-2854 Legal changes to the Filters policy #834
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -81,11 +81,12 @@ The goal of ad-blocking filters is to block all types of advertising on websites | |
| ### Limitations and exceptions | ||
|
|
||
| - 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 | ||
| - Anti-adblock walls will be blocked in the following cases: | ||
| - They aggressively insist on disabling or removing the ad blocker or effectively prevent using the website | ||
| - They feature incorrect and misleading descriptions of possible consequences of ad blockers’ use | ||
| - They put visitors at risk of malvertising — when unblocked advertisements come from dubious sources | ||
| - They violate or negatively impact user privacy | ||
| - We do not block ad blocker detection messages that satisfy at least one of the following criteria: | ||
| - They allow the usage of the website and do not overlay the significant amount of content | ||
| - They provide an alternative to disabling an ad blocker given that this alternative does not put the users’ privacy or security at risk | ||
|
|
@@ -165,13 +166,11 @@ For better customization, annoyance filters are divided by their purpose: | |
|
|
||
| #### AdGuard Cookie Notices filter | ||
|
|
||
| This filter is designed to block both cookie notices and requests from cookie management platforms (CMPs). Various methods may be applied to cookie notices and CMPs. 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 following methods are applied: | ||
| 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**. | ||
|
Comment on lines
+169
to
+173
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The task was to remove these details |
||
|
|
||
| **Limitations and exceptions** | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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."