Merge branch 'master' into feature/AG-43463

Author: workingBanana

docs/adguard-for-android/features/low-level-settings.md

@@ -138,6 +138,12 @@ If this setting is enabled, AdGuard will filter requests sent over HTTP/3 in add
 
 **About HTTP/3**: This is the latest version of the HTTP protocol, based on QUIC.
 
+**Limitations**:
+
+- Chrome-based browsers do not accept user certificates, so HTTP/3 filtering is not supported in them.
+- Firefox-based browsers behave similarly by default, but you can set the `network.http.http3.disable_when_third_party_roots_found` option in `about:config` to `false` to allow user certificates for HTTP/3.
+- Safari supports HTTP/3 filtering without additional configuration.
+
 ### Outbound proxy
 
 #### Show the Filter DNS requests setting

docs/adguard-for-android/features/protection/tracking-protection.md

@@ -9,21 +9,21 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro
 
 :::
 
-The Tracking protection module can be accessed by tapping the *Protection* tab (second-left icon at the bottom of the screen) and then selecting *Tracking protection*.
+To access the Tracking protection module, tap the *Protection* tab (the second icon from the bottom of the screen) and then select *Tracking protection*.
 
-*Tracking protection* (formerly known as *Stealth Mode*) prevents websites from collecting information about you, such as your IP addresses, information about your browser and operating system, screen resolution, and the page you came or were redirected from. It can also block cookies that websites use to mark your browser, save your personal settings and user preferences, or recognize you on your next visit.
+*Tracking protection* (formerly *Stealth Mode*) prevents websites from collecting information about you, such as your IP address, information about your browser and operating system, screen resolution, and the page you came or were redirected from. It can also block cookies that websites use to mark your browser, save your personal settings and user preferences, or recognize you on your next visit.
 
-![Tracking protection *mobile_border](https://cdn.adtidy.org/blog/new/y5fuztracking_protection.png)
+![Tracking protection *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/features/tracking_protection.png)
 
-*Tracking protection* has three pre-configured levels of privacy protection (*Standard*, *High*, and *Extreme*) and one user-defined level (*Custom*).
+*Tracking protection* has three pre-configured privacy protection levels (*Standard*, *High*, and *Extreme*) and one user-defined level (*Custom*).
 
 Here are the active features of the pre-configured levels:
 
 1. **Standard**
 
     a. *Block trackers*. This feature uses *AdGuard Tracking Protection filter* to protect you from online counters and web analytics tools
 
-    b. *Ask websites not to track you*. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity
+    b. *Ask websites not to track me*. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity
 
     c. *Remove X-Client-Data header*. This feature prevents Google Chrome from sending information about its version and modifications to Google domains (including DoubleClick and Google Analytics)
 
@@ -33,11 +33,11 @@ Here are the active features of the pre-configured levels:
 
     b. *Remove tracking parameters from URLs*. This feature uses *AdGuard URL Tracking filter* to remove tracking parameters, such as `utm_*` and `fb_ref`, from page URLs
 
-    c. *Hide your search queries*. This feature hides queries for websites visited from a search engine
+    c. *Hide search queries*. This feature hides your searches from websites visited through search engine results
 
-    d. *Ask websites not to track you*. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity
+    d. *Ask websites not to track me*. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity
 
-    e. *Self-destruction of third-party cookies*. This feature limits the lifetime of third-party cookies to 180 minutes
+    e. *Delete third-party cookies*. This feature limits the lifetime of third-party cookies to 180 minutes and prevents advertisers from tracking your behavior across multiple pages
 
     :::caution
 
@@ -53,28 +53,28 @@ Here are the active features of the pre-configured levels:
 
     b. *Remove tracking parameters from URLs*. This feature uses *AdGuard URL Tracking filter* to remove tracking parameters, such as `utm_*` and `fb_ref`, from page URLs
 
-    c. *Hide your search queries*. This feature hides queries for websites visited from a search engine
+    c. *Hide search queries*. This feature hides your searches from websites visited through search engine results
 
-    d. *Ask websites not to track you*. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity
+    d. *Ask websites not to track me*. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity
 
-    e. *Self-destruction of third-party cookies*. This feature limits the lifetime of third-party cookies to 180 minutes
+    e. *Delete third-party cookies*. This feature limits the lifetime of third-party cookies to 180 minutes and prevents advertisers from tracking your behavior across multiple pages
 
     :::caution
 
     This feature deletes all third-party cookies after their forced expiration. This includes your logins through social networks or other third-party services. You may need to re-log in to some websites periodically or experience other cookie-related issues. To block only tracking cookies, use the *Standard* protection level.
 
     :::
 
-    f. *Block WebRTC*. This feature blocks WebRTC, a known vulnerability that can leak your real IP address even if you use a proxy or VPN
+    f. *Block WebRTC*. This feature blocks WebRTC that can leak your real IP address even if you use a proxy or VPN. Some messengers, streaming platforms, or games may stop working properly
 
-    g. *Block Push API*. This feature prevents your browsers from receiving push messages from servers
+    g. *Block Push API*. This feature blocks push notifications from websites
 
     h. *Block Location API*. This feature prevents browsers from accessing your GPS data and determining your location
 
     i. *Hide Referer from third parties*. This feature prevents third parties from knowing which websites you visit. It hides the HTTP header that contains the URL of the initial page and replaces it with a default or custom one that you can set
 
-    j. *Hide your User-Agent*. This feature removes identifying information from the User-Agent header, which typically includes the name and version of the browser, the operating system, and language settings
+    j. *Hide User-Agent*. This feature removes identifying information from the User-Agent header, which typically includes the name and version of the browser, the operating system, and language settings
 
     k. *Remove X-Client-Data header*. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics)
 
-You can tweak individual settings in *Tracking protection* and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various *Tracking protection* settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions.
+You can tweak individual settings in *Tracking protection* to create a custom configuration. Each setting has a description to help you understand its purpose. [Read more about various *Tracking protection* settings](/general/stealth-mode) and use them cautiously, as some may interfere with the functionality of websites and browser extensions.

docs/adguard-for-android/features/settings.md

@@ -145,13 +145,13 @@ Please note that DNS filtering will still be active in *Automatic proxy* routing
 In this section, you can find information about your license and manage it:
 
 - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full)
-- Log in to your AdGuard account or enter the license key to activate your license
-- Sign up to activate your 7-day trial period if you haven't used it yet
+- Log in to your AdGuard account or enter the activation code to activate your license
+- Sign up to activate your 14-day trial period. The activation code can be used on different devices and platforms
 - Refresh the license status from the three-dots menu (⋮)
 - Open the AdGuard account to manage your license there
 - Reset your license — for example, if you've reached device limit for this license and want to apply another one
 
-![License screen *mobile_border](https://cdn.adtidy.org/blog/new/3wyh5hlicense.png)
+![License screen *mobile_border](https://cdn.adtidy.org/content/Kb/ad_blocker/android/settings/licensetab.png)
 
 ## Support
 

docs/adguard-for-android/solving-problems/background-work.md

@@ -592,3 +592,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
     - Find **AdGuard** and enable the **Always-on VPN** option
 
     ![Always-on VPN *border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/realme678.png)
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+   - Go to **Settings → Apps** and find **AdGuard**
+   - Open **App battery usage**
+   - Enable **Allow background battery usage**
+   - Tap the option with the toggle
+   - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+   - Go to **Settings**
+   - Scroll down and tap **Apps & notifications**
+   - Find **AdGuard** and open **Advanced → Battery**
+   - Tap **Background restriction** or **Background limits**
+   - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+   - Go to **Settings**, then type **Managing background apps** in the search bar
+   - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+   - Go to **Settings → Battery**
+   - Turn off the **Adaptive Battery** option

docs/adguard-for-linux/cli-exclusions-and-filters.md

@@ -0,0 +1,75 @@
+---
+title: How to set app exclusions and custom filters
+sidebar_position: 5
+---
+
+In AdGuard CLI, it’s not possible to import app exclusions from other versions of the program. You can, however, manually create the required exclusions and filters by editing several configuration files in the app’s working directory.
+
+## How to add exclusions
+
+AdGuard CLI working directory:
+
+- Linux: `~/.local/share/adguard-cli/`
+- macOS: `~/Library/Application Support/adguard-cli/`
+
+Several key files are located in this folder:
+
+1. `browsers.yaml` — a list of browsers (Safari, Chrome, Firefox, etc.). Here you can enable or disable HTTPS filtering for individual browsers, or completely exclude them from filtering.
+
+**Example browsers.yaml (for Linux)**:
+
+```sh
+- name: firefox
+  action: default
+- name: chrome
+  action: default
+- name: chromium
+  action: default
+- name: brave
+  action: default
+```
+
+**Example `browsers.yaml` (for macOS)**:
+
+```sh
+- name: com.apple.Safari
+  action: default
+- name: com.google.Chrome
+  action: default
+- name: org.mozilla.firefox
+  action: default
+- name: com.brave.Browser
+  action: default
+```
+
+To disable HTTPS filtering, replace `default` with `bypass_https`. To completely exclude the app from filtering, replace `default` with `bypass`.
+
+1. `proxy.yaml` — the main configuration file. It has an apps section where exclusions for any other apps are set.
+
+**Example `proxy.yaml`**:
+
+```sh
+  - include-list: browsers.yaml
+  - name: '*vpn*'
+    action: 'bypass'          
+    skip_outbound_proxy: true
+  - name: '*'
+    action: 'bypass_https'   
+```
+
+:::note
+
+On **Linux**, specify the executable name (`chrome`, `firefox`, etc.). On **macOS**, specify the bundle ID, e.g., `com.google.Chrome`, `org.mozilla.firefox`.
+
+:::
+
+## How to add custom filters
+
+The working directory contains the `user.txt` file, where you can add your own blocking or allowing rules for websites. If you have your own list of rules in `.txt` format, connect it via `proxy.yaml`:
+
+```sh
+filters:
+  - 'flm://'
+  - 'user.txt'
+  - 'my_filter.txt' # connecting your own file
+```

docs/adguard-for-linux/installation.md

@@ -49,15 +49,15 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
 
 1. Then select the desired option:
 
-    ![adguard-cli activate *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation1.png)
+    ![adguard-cli activate *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/1activate.png)
 
 1. Once you have a license, follow the provided link to proceed with the activation:
 
-    ![Activate license *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation2.png)
+    ![Activate license *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/2activate_link.png)
 
 1. After activation, you can continue to work with the program:
 
-    ![Successful activation *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation3.png)
+    ![Successful activation *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/3activate_success.png)
 
 1. You can also reset your license by entering:
 
@@ -77,7 +77,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
     adguard-cli configure
     ```
 
-    ![Setup *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation4.png)
+    ![Setup *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/4configure.png)
 
     The wizard will ask basic questions required for the initial setup.
 
@@ -87,7 +87,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
     adguard-cli start
     ```
 
-    ![Start protecton *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation5.png)
+    ![Start protecton *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/5start.png)
 
 1. You can check the protection status using:
 
@@ -101,15 +101,15 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
     adguard-cli stop
     ```
 
-    ![Stop protecton *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation6.png)
+    ![Stop protecton *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/6status-stop.png)
 
 1. To check the current configuration, enter:
 
     ```sh
     adguard-cli config show
     ```
 
-    ![Current setup *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/activation7.png)
+    ![Current setup *border](https://cdn.adtidy.org/content/Kb/ad_blocker/linux/7config_show.png)
 
     The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
 

docs/adguard-for-linux/settings.md

@@ -115,3 +115,79 @@ If the listen address is set to anything other than `127.0.0.1`, then proxy clie
 
 - When running `adguard-cli config set listen_address <address>` where `<address>` is not `127.0.0.1`, AdGuard CLI will prompt for a username and password if proxy authentication is not already configured.
 - When editing the config file directly, look for the `listen_auth`key. Set the `enabled` sub-key to `true`, and `username` and `password` to non-empty values.
+
+## Configure outbound proxy
+
+You can configure `outbound_proxy` if you want AdGuard CLI to work through another proxy server.
+
+There are two ways to configure it:
+
+### 1. Configure via URL (recommended)
+
+Instead of setting each option step by step, you can set all parameters in a single line using a URL:
+
+```sh
+adguard-cli config set outbound_proxy https://user:pass@host:port
+```
+
+:::info
+
+Supported modes are HTTP, HTTPS, SOCKS4, and SOCKS5.
+
+:::
+
+You can also quickly enable or disable `outbound_proxy`:
+
+```sh
+adguard-cli config set outbound_proxy false
+```
+
+Or quickly clear the settings:
+
+```sh
+adguard-cli config set outbound_proxy ""
+```
+
+### 2. Configure individual parameters
+
+The ability to adjust specific parameters is also available:
+
+```sh
+adguard-cli config set outbound_proxy.enabled true
+adguard-cli config set outbound_proxy.host localhost
+adguard-cli config set outbound_proxy.port 3128
+adguard-cli config set outbound_proxy.username user
+adguard-cli config set outbound_proxy.password pass
+```
+
+Disable certificate verification for HTTPS proxies:
+
+```sh
+adguard-cli config set outbound_proxy.trust_any_certificate true
+```
+
+Enable SOCKS5 proxy for UDP traffic:
+
+```sh
+adguard-cli config set outbound_proxy.udp_through_socks5_enabled true
+```
+
+:::note
+
+If your SOCKS5 proxy does not support UDP, connections may fail.
+
+:::
+
+### Checking the current configuration
+
+To view the current `outbound_proxy` configuration, enter:
+
+```sh
+adguard-cli config show outbound_proxy
+```
+
+:::info Compatibility
+
+Configuring `outbound_proxy` via URL is available starting from AdGuard for Linux v1.1.26 nightly and v1.1 stable release.
+
+:::

docs/adguard-for-mac/features/stealth.md

@@ -9,8 +9,8 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect
 
 :::
 
-## Advanced privacy protection
+## Tracking protection
 
-![Stealth Mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/stealth.png)
+![Stealth Mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/tracking_protection.png)
 
-*Advanced privacy protection* protects your privacy by deleting cookies, UTM tags, online counters, and analytics systems. It doesn’t let websites collect your IP address, device and browser parameters, search queries, and personal information. [Learn more about Stealth Mode settings](/general/stealth-mode)
+*Tracking protection* (formerly Stealth Mode) safeguards your privacy by deleting cookies, UTM tags, online counters, and analytics systems. It prevents websites from collecting your IP address, device and browser parameters, search queries, and personal information. [Learn more about Tracking protection settings](/general/stealth-mode)

docs/adguard-for-mac/solving-problems/advanced-settings.md

@@ -81,6 +81,12 @@ Verifies the authenticity of all certificates for the domain based on Chrome Cer
 
 By setting `true`, you allow AdGuard to filter traffic sent over HTTP/3, the latest version of the HTTP protocol based on QUIC.
 
+**Limitations**:
+
+- Chrome-based browsers do not accept user certificates, so HTTP/3 filtering is not supported in them.
+- Firefox-based browsers behave similarly by default, but you can set the `network.http.http3.disable_when_third_party_roots_found` option in `about:config` to `false` to allow user certificates for HTTP/3.
+- Safari supports HTTP/3 filtering without additional configuration.
+
 #### `network.filtering.localnetwork`
 
 By setting `true`, you enable local network filtering.