diff --git a/docs/general/ad-filtering/filter-policy.md b/docs/general/ad-filtering/filter-policy.md index 9a34d3b8348..c90b5b72169 100644 --- a/docs/general/ad-filtering/filter-policy.md +++ b/docs/general/ad-filtering/filter-policy.md @@ -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**. **Limitations and exceptions** diff --git a/docs/miscellaneous/contribute/filters.md b/docs/miscellaneous/contribute/filters.md index cf402e668fb..6da93c5423f 100644 --- a/docs/miscellaneous/contribute/filters.md +++ b/docs/miscellaneous/contribute/filters.md @@ -9,9 +9,17 @@ As you probably know, AdGuard uses filtering rules to block ads, and these rules Websites constantly change the way they embed ads, and we add new rules to our filters to keep them effective. Filter engineers are working on creating new rules, but we always welcome the help and support of volunteers. +:::note + +All volunteers must follow the **AdGuard filter policy** when creating rules. By participating, you agree to comply with the Policy and ensure your rules adhere to its requirements. Volunteers must not create rules intended to deliberately block websites or services that do not meet the criteria for blocking or that fall under exceptions described in the Policy. + +::: + ### How to start {#how-to-start} -However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. +However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. Before you start contributing, we recommend reviewing the [guidelines](https://github.com/AdguardTeam/AdguardFilters/blob/master/CONTRIBUTING.md). + +In the repository, you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters).