├── .github └── workflows │ ├── crowdin.yml │ └── markdown-lint.yml ├── .gitignore ├── .markdownlint.json ├── .markdownlintignore ├── .npmrc ├── README.md ├── adguard-dns.io ├── README.md ├── eula.html.md └── privacy.html.md ├── adguard-mail.com ├── README.md ├── eula.html.md └── privacy │ └── app.html.md ├── adguard-vpn.com ├── README.md ├── eula.html.md ├── privacy.html.md └── privacy │ ├── android.html.md │ ├── extension.html.md │ ├── ios.html.md │ ├── mac.html.md │ └── windows.html.md ├── adguard.com ├── README.md ├── data-processing-agreement.html.md ├── eula.html.md ├── extension-eula.html.md ├── privacy.html.md ├── privacy │ ├── android.html.md │ ├── browser-assistant.html.md │ ├── content-blocker.html.md │ ├── extension.html.md │ ├── home.html.md │ ├── ios.html.md │ ├── mac.html.md │ ├── safari.html.md │ └── windows.html.md ├── terms-and-conditions.html.md └── website-privacy.html.md ├── adguardpartner.com └── terms-and-conditions.html.md ├── build-resx.js ├── crowdin.yml ├── package-lock.json └── package.json /.github/workflows/crowdin.yml: -------------------------------------------------------------------------------- 1 | name: Upload to Crowdin 2 | 3 | on: 4 | push: 5 | branches: 6 | - "*" 7 | 8 | jobs: 9 | crowdin: 10 | if: github.event.pull_request.head.repo.fork == false 11 | runs-on: ubuntu-latest 12 | steps: 13 | - uses: actions/checkout@v4 14 | - name: Setup Node.js 15 | uses: actions/setup-node@v4 16 | with: 17 | node-version: 22 18 | 19 | - name: Install dependencies 20 | run: npm install 21 | 22 | - name: Build resx files 23 | run: npm run build:resx 24 | 25 | - name: Run Crowdin upload 26 | env: 27 | CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }} 28 | run: | 29 | if [ "${{ github.ref_name }}" = "master" ]; then 30 | npm run crowdin:upload 31 | else 32 | npm run crowdin:upload:dryrun 33 | fi 34 | -------------------------------------------------------------------------------- /.github/workflows/markdown-lint.yml: -------------------------------------------------------------------------------- 1 | name: Lint Markdown 2 | 3 | on: push 4 | 5 | jobs: 6 | build: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - uses: actions/checkout@v3 10 | - name: Use Node.js 11 | uses: actions/setup-node@v3 12 | with: 13 | node-version: 18.x 14 | 15 | - name: npm install 16 | run: npm install 17 | 18 | - name: npm run lint 19 | run: npm run lint 20 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | *.iml 3 | .idea/ 4 | crowdin 5 | -------------------------------------------------------------------------------- /.markdownlint.json: -------------------------------------------------------------------------------- 1 | { 2 | "ul-indent": { 3 | "indent": 4 4 | }, 5 | "ul-style": { 6 | "style": "dash" 7 | }, 8 | "emphasis-style": { 9 | "style": "asterisk" 10 | }, 11 | "no-duplicate-header": { 12 | "siblings_only": true 13 | }, 14 | "no-inline-html": { 15 | "allowed_elements": [] 16 | }, 17 | "no-trailing-spaces": { 18 | "br_spaces": 0 19 | }, 20 | "line-length": false, 21 | "no-bare-urls": false, 22 | "no-emphasis-as-heading": false, 23 | "link-fragments": false 24 | } -------------------------------------------------------------------------------- /.markdownlintignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | -------------------------------------------------------------------------------- /.npmrc: -------------------------------------------------------------------------------- 1 | save-exact=true 2 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Legal Documents 2 | 3 | This repository contains AdGuard’s legal documents, they are later synced to the 4 | website. The purpose is to be transparent about the history of their changes. 5 | 6 | The file names and directories structure explain where the files should be 7 | located on the server. For instance, `./adguard.com/eula.html.md` corresponds 8 | to `https://adguard.com/eula.html`. 9 | 10 | Translations need to be done internally and are not stored in this repo. 11 | On the website we must indicate that the document was translated and point to 12 | the original version in English language. 13 | 14 | See the README file for each website to see how the links to the legal documents should be listed on these websites. 15 | 16 | Links to legal documents in the footer are arranged in order of importance. The same applies to the list of other documents at the end of each legal document. 17 | -------------------------------------------------------------------------------- /adguard-dns.io/README.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard DNS Documents 3 | 4 | - [eula.html.md](eula.html.md) - AdGuard DNS End-User License Agreement. 5 | - [privacy.html.md](privacy.html.md) - AdGuard DNS Privacy Policy. 6 | 7 | ## List of documents in the footer 8 | 9 | - [EULA](eula.html.md) 10 | - [Privacy policy](privacy.html.md) 11 | - [Privacy policy of AdGuard websites](adguard.com/website-privacy.html.md) 12 | - [Terms and conditions of AdGuard Websites](https://adguard.com/en/terms-and-conditions.html) 13 | - [Terms of sale](https://adguard.com/en/terms-of-sale.html) 14 | - [Refund policy](https://adguard.com/en/terms-of-sale.html) 15 | - [Data processing agreement](https://adguard.com/en/data-processing-agreement.html) 16 | 17 | Links to legal documents in the footer are arranged in order of importance. The same applies to the list of other documents at the end of each legal document. 18 | 19 | For example, this is what it should look like when you open the Privacy policy: 20 | 21 | - [EULA](eula.html.md) 22 | - [Privacy policy of AdGuard websites](adguard.com/website-privacy.html.md) 23 | - [Terms and conditions of AdGuard Websites](https://adguard.com/en/terms-and-conditions.html) 24 | - [Terms of sale](https://adguard.com/en/terms-of-sale.html) 25 | - [Refund policy](https://adguard.com/en/terms-of-sale.html) 26 | - [Data processing agreement](https://adguard.com/en/data-processing-agreement.html) 27 | -------------------------------------------------------------------------------- /adguard-dns.io/eula.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard DNS End-User License Agreement 3 | 4 | *April 10, 2024* 5 | 6 | IMPORTANT: THIS END-USER LICENSE AGREEMENT (“EULA” OR “AGREEMENT”) IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR, IF PURCHASED OR OTHERWISE ACQUIRED BY OR FOR AN ENTITY, AN ENTITY) AND ADGUARD SOFTWARE LIMITED (OWNER OF ALL RIGHTS, WHETHER EXCLUSIVE OR OTHERWISE TO THE SOFTWARE, HEREAFTER “RIGHTHOLDER”). READ IT CAREFULLY BEFORE USING THE ADGUARD DNS PRODUCTS AND SERVICES. 7 | BY CONNECTING TO ADGUARD DNS, OR BY USING IT, OR BY PRESSING A BUTTON INDICATING YOUR ACCEPTANCE IN THE WINDOW CONTAINING THIS EULA, OR BY TYPING THE APPROPRIATE SYMBOL(S), YOU ARE CONFIRMING YOUR ACCEPTANCE OF ADGUARD DNS AND AGREEING TO BECOME BOUND BY TERMS OF THIS EULA. 8 | 9 | IF YOU DO NOT AGREE TO BE BOUND BY THIS EULA, DO NOT CONNECT TO ADGUARD DNS AND DO NOT USE ADGUARD DNS. 10 | 11 | NOTE THAT THIS EULA REQUIRE THAT YOU AND ADGUARD SOFTWARE LIMITED SUBMIT ANY DISPUTE ARISING OUT OF THE INTERPRETATION OR APPLICATION OF THIS EULA OR ANY BREACH THEREOF TO ARBITRATION. 12 | 13 | AdGuard Software Limited (“Rightholder”, “we”, “us”, “our”) may modify this EULA from time to time without prior notification. The amendment of EULA may be broadcasted to You by sending an email and/or by publishing the updated EULA on the [AdGuard DNS website](https://adguard-dns.io) (“Website”). 14 | 15 | **A certain component of AdGuard DNS, public DNS server, is subject to dual licensing, making it accessible through both a commercial license and an open-source license, namely, the GNU Affero General Public License, Version 3 (AGPLv3).** 16 | 17 | **If Your project aligns with the AGPLv3 license criteria, You are permitted to utilize this component of AdGuard DNS under the provisions of the open-source license. For projects that do not meet these requirements, such as closed-source projects, adherence to the licensing terms outlined in the AdGuard DNS End-User License Agreement below is mandatory.** 18 | 19 | **The text of the AGPLv3 license is accessible in the project’s source code repository and also on the Free Software Foundation website at [www.gnu.org/licenses/agpl-3.0.html](https://www.gnu.org/licenses/agpl-3.0.html).** 20 | 21 | ## 1. General 22 | 23 | 1.1. AdGuard Software Limited provides AdGuard DNS, a cloud-based DNS service, at your own risk and responsibility. You are solely and exclusively responsible for the use of AdGuard DNS. AdGuard DNS shall not be liable for any loss, monetary or non-monetary harm, and this shall not include attorney fees or court costs irrespective of any laws or statutes that prescribe otherwise. 24 | 25 | 1.2. AdGuard Software Limited grants You a limited license to connect to and use AdGuard DNS within the scope of its functionality described on the AdGuard DNS website, provided that You comply with all requirements, restrictions and terms specified in this EULA. The AdGuard DNS products and services are owned and copyrighted by AdGuard Software Limited, and are protected worldwide. AdGuard Software Limited retain all right, title and interest in and to the AdGuard DNS products and services and any portion thereof, including, without limitation, all copyrights, trademarks, service marks, trade secrets and other intellectual property rights. All rights are reserved unless otherwise noted. Modifying, distributing to unauthorized parties, reverse engineering, or otherwise using AdGuard DNS in any way not expressly authorized by AdGuard Software Limited with a written consent is strictly prohibited. 26 | 27 | 1.3. You are entitled, in accordance with the license granted in clause 1.2 herein, to connect to and use AdGuard DNS on a certain number of devices, with certain number of monthly requests, certain number of available DNS servers, certain number of rules You can set, and certain level of support, which are indicated when you purchased Your subscription. 28 | 29 | 1.4. In order to use private AdGuard DNS, You shall register Your AdGuard account using Your email address and create a private DNS server. A valid email address must be provided at registration for creation of the AdGuard DNS account. You may also log in with an email and password You have already registered at adguard.com before. You can connect to and use public AdGuard DNS without registering Your AdGuard account. 30 | 31 | 1.5. We may also modify or discontinue our free services and benefits without notice at any time at our sole discretion. Non-gratuitous services may be discontinued at the end of the term of the respective contract. 32 | 33 | ## 2. Terms of Sale, Term 34 | 35 | The provisions of this section apply to plans for private AdGuard DNS requiring paid subscription and do not apply to public AdGuard DNS and free Starter plan for private AdGuard DNS. 36 | 37 | 2.1. A customer pays for a subscription that allows them to activate AdGuard DNS, a service that is available at [adguard-dns.io](https://adguard-dns.io). 38 | To test private AdGuard DNS, you can try the Starter plan. For more monthly requests, devices and servers, You need to purchase a subscription: Personal, Team, or Enterprise plans with monthly or yearly payments. Once You purchase a subscription, it is automatically and immediately activated and linked to Your AdGuard account, so You can enjoy using Your private AdGuard DNS right after purchasing Your subscription until it is expired or canceled. 39 | 40 | 2.2. You may be entitled to a refund. Please refer to the refund terms and conditions in section 3. 41 | 42 | 2.3. You can cancel the purchased subscription at any time. The canceled subscription will be valid until its expiry date. 43 | 44 | 2.4. You can upgrade the purchased license at any time to increase the number of monthly requests, number of devices to protect, number of available DNS servers, number of rules You can set, and level of support. 45 | 46 | 2.5. The order process is handled by the online reseller Paddle.com. Paddle handles all customer service inquiries and refunds. 47 | 48 | 2.6. If You have not turned off the auto-renewal feature, the funds will be automatically withdrawn from Your account and the AdGuard DNS subscription will be renewed or extended. If You disable auto-renewal before Your AdGuard DNS subscription expires, You will receive a notification at the email address You provided during the initial purchase with complete information about the renewal terms. You will also be notified in advance if the price of the AdGuard DNS subscription increases. 49 | 50 | 2.7. After the subscription that was purchased using promo codes or discounts expires, the payment for the subscription renewal will be charged at full price. All changes to prices will be sent to you in the email you’ve registered when purchasing the license. 51 | 52 | 2.8. You can cancel automatic renewal at any time in Your AdGuard account to which the AdGuard DNS subscription is bound at no additional cost. Your paid subscription will still be valid, but you will need to manually renew it when it expires. 53 | 54 | 2.9 When You purchase Your subscription, Your AdGuard account is automatically created for the email address that You used at the purchase. Your AdGuard account can also be created via the AdGuard website, if You decide to sign up at the website. By registering Your AdGuard account, you affirm that You are 18 years or older. Note that when Your AdGuard account is created, You are subscribed to messages about modifications, new versions, and features of AdGuard DNS. 55 | 56 | ## 3. Refund policy 57 | 58 | We grant our customers a possibility to return 100% of funds they spent on AdGuard DNS Yearly subscriptions purchased from [adguard-dns.io](https://adguard-dns.io) (for subscriptions purchased elsewhere, look for the refund policy of that particular reseller). 59 | 60 | --- 61 | 62 | **Important**: monthly subscriptions are not refunded. For Yearly subscriptions we have a 30-day money-back-guarantee. All refund requests made within 30 days since the Yearly subscription purchase are satisfied no matter what the reason is. 63 | 64 | --- 65 | 66 | The subscription in question becomes blocked the moment the refund is issued. After 30 days, all requests are considered individually and the decision whether to issue a refund is left up to AdGuard Software Ltd. We do not grant partial refunds for subscription upgrades and renewals. Each case of partial refund request is discussed separately between You and our Customer Support Service, and satisfied only upon mutual agreement. To get a refund for a subscription purchased [on the official website](https://adguard-dns.io), You need to contact our Customer Support Service at [support@adguard.com](mailto:support@adguard.com). Processing time will depend on the payment method You have chosen and usually takes up to 10 business days. 67 | 68 | ## 4. Restrictions 69 | 70 | You have no right to: 71 | 72 | - rent, lease, loan, export or sell access to AdGuard DNS services to third parties; 73 | 74 | - utilize framing techniques to enclose AdGuard DNS logos, trademarks, author attribution and copyright notices; 75 | 76 | - use automated agents or inject scripts into AdGuard DNS products and services to create multiple accounts, generate automated searches, requests, scrape, strip, or mine data from AdGuard DNS products and services; 77 | 78 | - run or disclose the results of any benchmark tests or analyses of AdGuard DNS products and services without AdGuard DNS’s written consent; 79 | 80 | - hide, conceal or obscure any part of the AdGuard DNS website via HTML/CSS, scripting, or any other means; 81 | 82 | - use AdGuard DNS for any unauthorized or illegal purpose or activity under applicable international, national, and local laws in countries where it is used; 83 | 84 | - use another person’s email address or misrepresent yourself as another person when signing up to create Your account or when logging in to use AdGuard DNS; 85 | 86 | - perform illegal monitoring of and a list of websites accessed by other individuals when users who use private DNS to filter Internet access for others must not violate the privacy of those individuals; 87 | 88 | - disclose to third parties and otherwise misuse a list of websites from the query log visited by other individuals, if private AdGuard DNS is used to filter Internet access for such individuals with the logging function enabled; 89 | 90 | - connect to and use AdGuard DNS or purchase the subscription to AdGuard DNS if the country in which You reside belongs to E.U. or U.S. embargoed countries, or if You are a person to which shipment of software is prohibited by the export control laws, rules, regulations, restrictions and national security controls of the European Union, the United States, and other applicable foreign agencies. 91 | 92 | ## 5. Use of blocking and filtering functionality 93 | 94 | 5.1. By using AdGuard DNS, You acknowledge and agree to use blocklists, rules, filters that may be produced by AdGuard Software Limited or by You or by third parties and utilized by blocking and filtering functionality of AdGuard DNS solely at Your own will and risk. 95 | 96 | 5.2. You are solely responsible for using blocking and filtering functionality of AdGuard DNS, connecting Your devices to, enabling, disabling, configuring, customizing of such functionality, editing rules used in such functionality. 97 | 98 | 5.3. You and users of devices connected by You to AdGuard DNS are solely responsible for their compliance with terms of use of visited websites. AdGuard Software Limited shall not be responsible and shall not be liable for compliance with terms of use of any visited website. 99 | 100 | ## 6. User data and Privacy Policy 101 | 102 | 6.1. AdGuard DNS collects and processes very limited user data and has a strong Privacy Policy available at [adguard-dns.io/privacy.html](https://adguard-dns.io/privacy.html) that explains in detail how AdGuard Software Limited handles your personal data in relation to Your use of AdGuard DNS and Your browsing of the [adguard-dns.io](https://adguard-dns.io) website. 103 | 104 | 6.2. By connecting to and by using AdGuard DNS, You agree to have read, understand and accept terms and conditions of data processing set out in our Privacy Policy available at the link mentioned above, which explains what type of information we collect, how it is shared and used. 105 | 106 | 6.3. AdGuard Software Limited shall receive and process certain data to perform our obligations set forth in this EULA and to provide You with the functionality of AdGuard DNS. The data we process may be treated as personal data in accordance with the laws of certain territories and countries. You can read more about data processing in our Privacy Policy. 107 | 108 | 6.4. To provide You with logging functionality after You activate it in Private AdGuard DNS, AdGuard Software Limited needs to process IP addresses of connected devices from which incoming DNS requests are received. AdGuard Software Limited does not automatically collect such data until You enable the appropriate functionality. 109 | You represent and warrant that 110 | 111 | - You have the necessary authorizations and consents from persons who use devices connected to Your account to enable logging of IP addresses of such devices when DNS queries are received from them, 112 | 113 | - You are using appropriate legal bases to process such IP addresses and other logging information, 114 | 115 | - You have duly informed such persons of this functionality and that such IP addresses and other logging information will be provided to the Company for processing. 116 | 117 | 6.5. AdGuard Software Limited will use Your email address that You used when binding AdGuard DNS to Your account or creating a new account to send You notifications about modifications, new versions, and features of AdGuard DNS. In addition, You can provide Your consent to receive promotional information about AdGuard DNS, or similar products or services offered by AdGuard Software Limited. If You wish to stop receiving the marketing emails, You can withdraw Your consent any time in Your AdGuard account or unsubscribe right in the received email. 118 | 119 | 6.6. If You subscribe to AdGuard blog or AdGuard affiliate program, AdGuard Software Limited will use Your email address that You specified when subscribing to send You related notifications. By subscribing, You affirm that You are 18 years or older. If You wish to unsubscribe, You may contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 120 | 121 | ## 7. Warranty disclaimer 122 | 123 | 7.1 YOU EXPRESSLY AGREE THAT YOUR USE OF THE SERVICE IS AT YOUR SOLE RISK. THE SERVICE IS PROVIDED ON AN “AS IS” AND AN “AS AVAILABLE” BASIS. RIGHTHOLDER AND ITS SUPPLIERS AND PARTNERS DISCLAIM ALL WARRANTIES AND REPRESENTATIONS WITH REGARD TO THE PRODUCTS AND SERVICES PROVIDED UNDER THIS EULA, WHETHER EXPRESS, IMPLIED, OR OTHERWISE, INCLUDING THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, TITLE, AND QUIET ENJOYMENT. RIGHTHOLDER DOES NOT WARRANT THAT THE SERVICE IS ERROR-FREE OR WILL OPERATE WITHOUT INTERRUPTION. NO RIGHTS OR REMEDIES REFERRED TO IN ARTICLE 2 or ARTICLE 2A OF THE UNIFORM COMMERCIAL CODE (UCC), AS IMPLEMENTED IN ANY JURISDICTION, WILL BE CONFERRED ON YOU UNLESS EXPRESSLY GRANTED HEREIN. THE SERVICE IS NOT DESIGNED, INTENDED OR LICENSED FOR USE IN HAZARDOUS OR HIGH-RISK ENVIRONMENTS OR USE CASES REQUIRING FAIL-SAFE CONTROLS, INCLUDING WITHOUT LIMITATION, THE DESIGN, CONSTRUCTION, MAINTENANCE OR OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, AND LIFE SUPPORT OR WEAPONS SYSTEMS. RIGHTHOLDER SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH PURPOSES. 124 | 125 | 7.2. IF APPLICABLE LAW REQUIRES ANY WARRANTIES WITH RESPECT TO THE PRODUCTS AND SERVICES PROVIDED UNDER THIS EULA, ALL SUCH WARRANTIES ARE LIMITED IN DURATION TO SIXTY (60) DAYS FROM THE DATE OF DELIVERY OF SUCH SERVICES. 126 | 127 | 7.3. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY RIGHTHOLDER OR ITS PARTNERS, OR ITS OR THEIR AGENTS OR EMPLOYEES, SHALL CREATE A REPRESENTATION OR WARRANTY, NOR IN ANY WAY INCREASE THE SCOPE OF ANY EXPRESS REPRESENTATION OR WARRANTY PROVIDED HEREIN. 128 | 129 | 7.4. RIGHTHOLDER SHALL HAVE NO LIABILITY, AND YOU RELEASE RIGHTHOLDER OF ANY AND ALL LIABILITY, IF THE SERVICE HAS BEEN ALTERED IN ANY WAY, OR FOR ANY FAILURE THAT ARISES OUT OF USE OF THE SERVICE WITH OTHER THAN A RECOMMENDED HARDWARE CONFIGURATION, PLATFORM OR OPERATING SYSTEM. 130 | 131 | 7.5. RIGHTHOLDER IS NOT RESPONSIBLE FOR ANY THIRD-PARTY SERVICE INSTALLED BY YOU, INTENTIONALLY OR INADVERTENTLY, BY PURCHASING LICENSES OR DOWNLOADING THE SERVICE FROM AN UNAUTHORIZED PARTY THAT IS NOT A RIGHTHOLDER’S PARTNER. 132 | 133 | 7.6. YOU ARE RESPONSIBLE FOR ENSURING THAT YOUR PARTICULAR USE OF THE SERVICE DOES NOT VIOLATE APPLICABLE LAW, THIRD-PARTY RIGHTS, OR YOUR CONTRACTUAL OBLIGATIONS TO THIRD PARTIES. 134 | 135 | ## 8. Limitation of liability 136 | 137 | 8.1. TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER RIGHTHOLDER NOR ITS SUPPLIERS OR PARTNERS SHALL BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, COVER OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR THE INABILITY TO USE EQUIPMENT OR ACCESS DATA, LOSS OF DATA, LOSS OF BUSINESS, LOSS OF PROFITS, BUSINESS INTERRUPTION OR THE LIKE), ARISING OUT OF THE USE OF, OR INABILITY TO USE, THE PRODUCTS OR SERVICES PROVIDED UNDER THIS EULA WHETHER BASED ON ANY THEORY OF LIABILITY, INCLUDING BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF RIGHTHOLDER OR ITS SUPPLIERS OR PARTNERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. 138 | 139 | 8.2. TO THE MAXIMUM EXTENT PERMITTED BY LAW, RIGHTHOLDER’S TOTAL LIABILITY TO YOU FOR ACTUAL DAMAGES FOR ANY CAUSE WHATSOEVER WILL BE LIMITED TO THE AMOUNT YOU ACTUALLY PAID TO RIGHTHOLDER FOR ANY PRODUCTS OR SERVICES PROVIDED UNDER THIS EULA. 140 | 141 | 8.3. THE FOREGOING LIMITATIONS ON LIABILITY ARE INTENDED TO APPLY TO ALL ASPECTS OF THIS EULA. 142 | 143 | ## 9. Licenses to third party software 144 | 145 | You are granted a license (or sublicense) under the terms of the GNU General Public License (GPL) or other similar license to certain Third Party Software. Such licenses allow You to copy, modify, and redistribute the Third Party Software or part of it covered by such licenses, and to obtain its source code. If such licenses demand the provision of the source code of any Third Party Software, the Rightholder will provide You with the source code upon receipt of Your request at the Rightholder’s email address [support@adguard.com](mailto:support@adguard.com). If such licenses demand the provision of rights to use, copy or modify any Third Party Software that are greater than the rights granted herein, such rights will prevail over the rights and restrictions set forth herein. 146 | 147 | ## 10. Miscellaneous 148 | 149 | 10.1. Applicable Law, Arbitration, and Choice of Venue. This EULA will be governed by and construed in accordance with the laws of the Republic of Cyprus without reference to conflicts of law rules and principles. This EULA shall not be governed by the United Nations Convention on Contracts for the International Sale of Goods, the application of which is expressly excluded. Any dispute arising out of the interpretation or application of the terms of this EULA or any breach thereof shall, unless it is settled by direct negotiation, be adjudicated by arbitration in the Republic of Cyprus. Any award rendered by the arbitrator shall be final and binding on the parties and any judgment on such arbitration award may be enforced in any court of competent jurisdiction. Nothing in this Section 10 shall prevent a Party from seeking or obtaining equitable relief from a court of competent jurisdiction, whether before, during or after arbitration proceedings. 150 | 151 | 10.2. Entire Agreement and Non-waiver. This EULA contains the complete agreement between the parties with respect to the subject matter hereof and supersedes all prior or contemporaneous agreements or understandings, whether oral or written. You agree that any varying or additional terms contained in any purchase order or other written notification or document issued by You in relation to the Software licensed hereunder shall be of no effect. The failure or delay of Rightholder to exercise any of its rights under this EULA or upon any breach of this EULA shall not be deemed a waiver of those rights or of the breach. 152 | 153 | 10.3. Restriction on Amendments. No Rightholder Partner, or agent or employee of a Rightholder Partner, is authorized to make any amendment to this EULA. Any conflict or ambiguity between this EULA and any separate terms or conditions provided by a Rightholder Partner regarding the Services shall be resolved in favor of this EULA. 154 | 155 | 10.4. Severability. If any provision of this EULA shall be held by a court of competent jurisdiction to be contrary to law, that provision will be enforced to the maximum extent permissible, and the remaining provisions of this EULA will remain in full force and effect. 156 | 157 | 10.5. No Use Where Prohibited. Use of the Services is unauthorized in any jurisdiction that does not give effect to all provisions of this EULA. 158 | 159 | 10.6. Assignment. You may not assign, by operation of law or otherwise, any rights or delegate any duties under the EULA to any third party without prior written consent by Rightholder. Any purported assignment lacking such consent will be void at its inception. Rightholder may assign all or part of its rights and/or delegate all or part of its duties under the EULA to any party, at any time, and in its sole discretion, upon notice of assignment by publishing such notice on its website. 160 | 161 | ## 11. Period for bringing actions 162 | 163 | No action, regardless of form, arising out of the transactions under this EULA, may be brought by either party hereto more than one (1) year after the cause of action has accrued, except that an action for infringement of intellectual property rights may be brought within the maximum applicable statutory period. 164 | 165 | ## 12. Contact Information 166 | 167 | Should You have any questions concerning this EULA, or if You desire to contact the Rightholder for any reason, please contact our Customer Support Service: 168 | 169 | Email: [support@adguard.com](mailto:support@adguard.com) 170 | 171 | Website: [adguard-dns.io](https://adguard-dns.io) 172 | 173 | © ADGUARD SOFTWARE LIMITED. All Rights Reserved. The Services and any accompanying documentation are copyrighted and protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. 174 | -------------------------------------------------------------------------------- /adguard-dns.io/privacy.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard DNS Privacy Policy 3 | 4 | *August 6, 2024* 5 | 6 | ## Summary 7 | 8 | We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | 1. The information we process includes no more than is crucial to provide the full functionality of AdGuard DNS, both public and private versions. 11 | 12 | 1. AdGuard DNS periodically connects to our servers to check updates and your subscription status. 13 | 14 | 1. When you sign up for our services or buy an AdGuard DNS subscription, you provide us with your email address. We’ll use it to notify you of changes to your AdGuard account. If you agree, we’ll also keep you informed about AdGuard DNS sales and news. 15 | 16 | 1. You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account at adguardaccount.com or by sending us a request at [privacy@adguard.com](mailto:privacy@adguard.com). 17 | 18 | Below, we list all the information we may process via AdGuard DNS and explain why we do it and how we use this information. We do not collect anything for tracking purposes and take all necessary measures to protect the information you share with us. 19 | 20 | ## Who we are 21 | 22 | ADGUARD SOFTWARE LIMITED (“We”, “Our” or “Us”) collects and processes your data in accordance with this Privacy Policy and in compliance with the applicable data protection laws. This Policy informs you of your rights and our obligations and explains how, why, and when we process your personal data. Our general principle is to collect only the information necessary to provide you with full functionality of our products and services. We strictly follow the principle of “minimization” when processing your data. 23 | 24 | ADGUARD SOFTWARE LIMITED is a company registered in Limassol, Cyprus, registered office is at Anexartisias and Athinon 79, Nora Court Flat/Office 203-205, 3040 Limassol, Cyprus. ADGUARD SOFTWARE LIMITED acts as the data controller when processing your data. 25 | 26 | If you have any questions about this Privacy Policy or if you want to exercise any of your rights, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 27 | 28 | Please read this Privacy Policy thoroughly. 29 | 30 | If you do not agree with our policies and practices described in this Privacy Policy, please do not use our software and services, do not visit our website, and do not provide your information to us. 31 | 32 | ## What we do 33 | 34 | AdGuard DNS operates as a DNS resolver that can block access to certain domains depending on the chosen configuration (server): 35 | 36 | - **AdGuard DNS Default** blocks access to domains that we consider ad, tracking, or malware. [This list](https://adguardteam.github.io/AdGuardSDNSFilter/Filters/filter.txt) is constantly updated based on the community feedback. 37 | 38 | - **AdGuard DNS Family** blocks access to the same domains as Default, and also to domains that may contain adult content. It also enforces safe search and other safe modes wherever possible, which can result in modified search results, missing comment sections, and other differences in the appearance of web pages compared to their original state. 39 | 40 | - **Non-filtering AdGuard DNS** doesn’t block or redirect anything. It only returns the IP address of the requested domain. 41 | 42 | - **Private AdGuard DNS** blocks DNS queries or modifies DNS responses in accordance with the user’s preferences. In addition to that, it displays the queries and statistics to the user via the AdGuard DNS dashboard. Registering an AdGuard account is required to use this type of DNS resolver. 43 | 44 | If you disagree with our classification of a certain domain as advertising, tracking, malicious, or adult one, or if you believe a certain domain should be blocked by one of AdGuard DNS servers, contact us at [support@adguard.com](mailto:support@adguard.com). 45 | 46 | ## What data we process and when 47 | 48 | We process different data depending on the situation. You can learn details about what data we process in this section. 49 | 50 | Some data that we receive and process may be treated as personal data (“Personal Data”) in accordance with the laws of certain territories and countries. When we use terms “personal data” or “personal information”, we mean any information relating to an identified or identifiable natural person, excluding any anonymized and depersonalized data where your identity is absent or has been removed and cannot be recovered. 51 | 52 | We do not collect anything about the user specifically, except where necessary to provide you with the functionality of AdGuard DNS. 53 | 54 | - We store aggregated performance metrics of our DNS servers, namely the number of complete requests to a particular server, the number of blocked requests, and the speed of processing requests. 55 | 56 | - We keep and store an anonymous database of domains requested in the last 24 hours. There is no information whatsoever that could link any of these domain names to the original user who sent the request. We need this information to identify and block new trackers and threats. 57 | 58 | - We also log how many times this or that tracker has been blocked. We need this information to remove outdated rules from our filters. 59 | 60 | All this data that we process is not shared with any third parties. It is used solely for internal purposes such as performance analytics. The only information we may share is derivative information, i.e., lists of domains that our servers recognize as advertising, tracking, or malicious. 61 | 62 | ## When you are using our website 63 | 64 | **Account registration.** We process your email address and a hash of the password you use for authorization. That ensures that you can retrieve your password if needed. 65 | 66 | **Sending messages.** We can communicate with you using your email address when we have any announcements to make, to inform you about our software or service updates and new features, to advise or errors to report. 67 | 68 | You can also provide us with your consent to process your email for sending marketing messages about our other software or services. You can withdraw your consent any time by unsubscribing from our newsletter via AdGuard Account or by clicking the “Unsubscribe” button or link in the email itself. 69 | 70 | **Cookies.** We use our cookies for personalizing the content of the AdGuard DNS website, such as setting the default language. None of the information we may acquire through the use of cookies is considered Personal Data as it does not allow us to identify you. You can always disable or clear cookies in your browser, but please note that some of our services may not function properly without the aid of cookies. Please refer to the [Privacy Policy of AdGuard Websites](https://adguard.com/website-privacy.html) for details. 71 | 72 | **Buying a subscription.** If you purchase a subscription to Private AdGuard DNS, we’ll use the email address you provide to send you information about your purchase. We’ll also use your email address to create an account for you. This account will allow you to manage your purchased subscription. 73 | 74 | We conduct all transactions via the Paddle payment provider [Paddle.com Market Ltd](https://www.paddle.com) to enable payments if you purchase a subscription to use our software and services. The data processed depends on the payment provider and may include the following: 75 | 76 | - Email address 77 | 78 | - Country of residence 79 | 80 | - Zip or postal code 81 | 82 | - (If you use a bank card to make a purchase) Number, name, expiration date, and the security code associated with the bank card 83 | 84 | For the exact data that the payment provider collects about you, please see the corresponding privacy policy: [Paddle’s Privacy Policy](https://www.paddle.com/legal/privacy). 85 | 86 | ## When you are using public AdGuard DNS 87 | 88 | We do not process any of your Personal Data when you connect to and use public AdGuard DNS. 89 | 90 | However, we obtain and process general statistics on the use of public AdGuard DNS as we described above. This data is not linked to you in any way; it is accumulated when public AdGuard DNS is used by all users in general. 91 | 92 | ## When you are using private AdGuard DNS 93 | 94 | AdGuard DNS users may opt to use the “private AdGuard DNS” server. This functionality allows them to control their DNS queries, observe statistics and query logs. 95 | 96 | In this case, AdGuard DNS will block DNS queries or modify them according to the user’s preferences. 97 | 98 | We process the following data to enable you to use private AdGuard DNS: 99 | 100 | - The email address you used to create your account. 101 | 102 | - We store logs of DNS queries from connected devices in order to display it to you on the AdGuard DNS dashboard. Logs contain status and content of requests, names of companies who own the requested resources, names of connected devices, date of requests. Additionally, we will log anonymized IP addresses (limited to subnet) of connected devices from which incoming DNS requests are received, when this option is enabled by you. Users may opt to disable logging via the account settings. The log is only stored for a limited period of time which can also be configured via the account settings. 103 | 104 | ## What legal bases we use to process your Personal Data 105 | 106 | We use different legal bases to process Personal Data depending on the type of data, the purposes, and circumstances of processing. 107 | 108 | **Consent.** We process your personal data if you have provided us with your consent to use your Personal Data for certain purposes. For example, to send you marketing messages or to help you troubleshoot problems with using our software. You can withdraw your consent any time without any detriment to your use of our software. 109 | 110 | **Performance of a contract.** We process your Personal Data when it is necessary to fulfill our contractual obligations to you, including providing the functionality of our software and services or at your request prior to entering into a contract with you. 111 | 112 | **Legal obligations.** We process your Personal Data where it is necessary for compliance with our legal obligations, such as to exercise or defend our legal rights, or for taxation purposes. 113 | 114 | **Legitimate interest.** We process your Personal Data when we pursue our legitimate interests, except where such interests are overridden by the interests or fundamental rights and freedoms of data subjects. 115 | 116 | ## Where we process your Personal Data 117 | 118 | We store your Personal Data in our own data center located in Frankfurt. Your Personal Data may be processed by our employees, who can only access your data through their job duties on a need-to-know basis. If you have questions or want to know from which countries access may be possible, you can write to us at [privacy@adguard.com](mailto:privacy@adguard.com). 119 | 120 | For data transfers to other countries, we always implement appropriate safeguards to ensure that your Personal Data always remains safe and that your rights are respected: 121 | 122 | - The country or the third party is recognized as providing adequate protection. 123 | 124 | - A valid transfer mechanism is applied such as the Standard Contractual Clauses and the supplementary measures are implemented, where necessary. 125 | 126 | - The transfer has your explicit consent. 127 | 128 | - The transfer is necessary for the performance of a contract with you or to take steps requested by you prior to entering into that contract. 129 | 130 | If you would like a copy of the Standard Contractual Clauses used, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 131 | 132 | To determine if a non-EU country has an adequate level of data protection, please [the European Commission website](https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en). 133 | 134 | ## How we use your Personal Data 135 | 136 | ### Retaining your data 137 | 138 | We retain Personal Data for as long as necessary to continue providing you with our products and services, or until you revoke your consent to share this information. 139 | 140 | ### Your rights 141 | 142 | In some countries and regions, you may have certain rights in relation to your Personal Data under applicable data protection laws. 143 | 144 | If you wish to exercise your rights with respect to your Personal Data, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). We will consider and act upon any request in accordance with applicable data protection laws. We may ask you to further confirm your identity and will respond to you within the time period specified by applicable data protection law. Please note that in certain cases stipulated by applicable data protection law, we may charge you a reasonable fee for processing your request or refuse your request. 145 | 146 | You are entitled to exercise the following rights in relation to your Personal Data: 147 | 148 | **Right of access:** the right to obtain all your Personal Data we store. In some cases, the right of access may be limited for technical reasons, including if the data has been anonymized and cannot be linked to any data subject. 149 | 150 | **Right to erasure** or **right to be forgotten:** the right to completely delete your Personal Data. You can do this at will via AdGuard account, or by sending a request to [privacy@adguard.com](privacy@adguard.com). 151 | 152 | **Right to rectification:** the right to correct any incomplete or inaccurate Personal Data about you. We will do so as quickly as possible, unless there is a valid reason not to, in which case you will be notified. 153 | 154 | **Right to restriction:** the right to impose restrictions on processing of your Personal Data. 155 | 156 | **Right to object:** the right to object to processing of your Personal Data. 157 | 158 | **Right to data portability:** the right to receive provided Personal Data in a structured, commonly used and machine-readable format and to transmit that data to another controller. You can export all Personal Data that we hold about you to a local file from the AdGuard account on [adguardaccount.com](https://adguardaccount.com). 159 | 160 | **Right not to be subject to a decision based solely on automated processing**, including profiling. 161 | 162 | **Right to withdraw a consent** where the data processing is based on the consent. 163 | 164 | **Right to lodge a complaint** with a data protection authority. You can find contact details of our data protection authorities [here](https://www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument). 165 | 166 | When we receive your Personal Data from a third party, we will use reasonable efforts to inform you about it. 167 | 168 | ### Safeguarding measures 169 | 170 | We make every possible effort to protect your Personal Data from unauthorized access, alteration, disclosure or destruction. We implement and maintain the following technical and security measures: 171 | 172 | - **System access controls:** We take reasonable measures to prevent unauthorized use of Personal Data. These controls vary depending on the nature of the processing undertaken and may include, among other controls, authentication via passwords and/or two-factor authentication, documented authorization processes, documented change management processes, and/or logging of access on several levels. 173 | 174 | - **Data access controls:** We take reasonable measures to ensure that Personal Data is accessed and managed only by properly authorized staff. Direct database query access is restricted and application access rights are established and enforced to ensure that individuals authorized to use a data processing system have access only to the Personal Data to which they have access privileges, and that Personal Data cannot be read, copied, modified, or removed during processing without authorization. 175 | 176 | - **Storing data in a data center:** Personal information is stored in our own data center located in Frankfurt, Germany. This is secure — the data center does not demand that we collect any data about your traffic or your use of our products and services. If they request us to start doing so, we will stop using them and find an alternative. 177 | 178 | - **Transmission controls:** We take reasonable measures to ensure that we are able to verify and determine the entities to which Personal Data is to be transmitted via data transmission facilities so that personal data cannot be read, copied, modified, or deleted without authorization during electronic transmission or in transit. 179 | 180 | - **Input controls:** We take reasonable measures to ensure that it is possible to verify and establish whether and by whom personal data has been entered into, modified in, or removed from data processing systems. 181 | 182 | - **Data backup:** Databases are backed up regularly, secured, and encrypted to ensure that Personal Data is protected from accidental destruction or loss when while in our possession. 183 | 184 | - **Logical separation:** Personal Data is logically segregated on our systems to ensure that Personal Data collected for different purposes is processed separately. 185 | 186 | ### Consequences of not providing your Personal Data 187 | 188 | You are not obligated to provide your Personal Data to us. However, because this information is necessary for us to provide you with our services or respond to your enquiries, we will not be able to provide some or all of our services without it. 189 | 190 | ### Age limitations 191 | 192 | To the extent not prohibited by applicable law, we do not permit the use of our Services, Products and Website by anyone under the age of 18. If you learn that someone under the age of 18 has unlawfully provided us with Personal Data, please contact us and we will take steps to delete such information. 193 | 194 | ## Changes to this Privacy Policy 195 | 196 | We may change this Privacy Policy from time to time and inform you of the important changes. Laws, regulations and industry standards evolve, which may require such changes, or we may make changes to our business. We will post the changes on this page and encourage you to review our Privacy Policy to stay informed. 197 | -------------------------------------------------------------------------------- /adguard-mail.com/README.md: -------------------------------------------------------------------------------- 1 | # AdGuard Mail Documents 2 | 3 | - [eula.html.md](eula.html.md) - AdGuard Mail End-User License Agreement. 4 | - [privacy.html.md](privacy/app.html.md) - AdGuard Mail Privacy Notice. 5 | 6 | ## List of documents in the footer 7 | 8 | - [EULA](eula.html.md) 9 | - [Privacy notice](privacy/app.html.md) 10 | 11 | Links to legal documents in the footer are arranged in order of importance. The same applies to the list of other documents at the end of each legal document. 12 | 13 | For example, this is what it should look like when you open the Privacy policy: 14 | 15 | [EULA](eula.html.md) 16 | -------------------------------------------------------------------------------- /adguard-mail.com/privacy/app.html.md: -------------------------------------------------------------------------------- 1 | # AdGuard Mail Privacy Policy 2 | 3 | *March 18, 2025* 4 | 5 | --- 6 | 7 | **Keynote:** This Privacy Policy lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 8 | 9 | --- 10 | 11 | ## What data AdGuard Mail apps can collect and when 12 | 13 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 14 | 15 | --- 16 | 17 | AdGuard Mail applications are available on multiple platforms: iOS, Android, macOS, Windows, and Web. They share identical functionality and a common code base. The following information represents the full range of data that may be collected, although the specific details gathered can vary depending on the platform, with some platforms collecting less. 18 | 19 | --- 20 | 21 | ### Starting the application 22 | 23 | When you launch AdGuard Mail for the first time, we collect the following data: 24 | 25 | - **App version** 26 | - **App identifier** 27 | - **App language** 28 | - **Device OS** 29 | - **OS language** 30 | - **OS theme** 31 | - **User-Agent** 32 | - **App installation channel** 33 | 34 | **Why we need this information:** 35 | 36 | - To count the number of apps of a certain type and version 37 | - To communicate with you in your language 38 | - To know if the user was referred by an AdGuard affiliate, and if so, which affiliate 39 | - To learn the source of AdGuard Mail installation 40 | - To make the AdGuard Mail theme match the system theme 41 | 42 | The collection of this information is a **default process** and is critical to maintaining and improving app performance. 43 | 44 | ### Using the app 45 | 46 | AdGuard Mail periodically connects to our server to check the account status. The following information is sent: 47 | 48 | - **Authorization token** 49 | - **User in-app purchase data** 50 | - **App identifier** 51 | - **App version** 52 | - **Device OS** 53 | - **OS language** 54 | - **Limits of the free version**: number of aliases and recipients used, emails forwarded to aliases, and emails sent to Temp Mail address 55 | 56 | We need this information to check the account status and authorization on the server. 57 | 58 | ### User registration and authorization 59 | 60 | Registration and authorization for AdGuard Mail are managed through the AdGuard web-based authentication service at [auth.adguardaccount.com](https://auth.adguardaccount.com). The privacy policy governing the AdGuard website and related sites is outlined in the document available at [adguard.com/website-privacy.html](https://adguard.com/website-privacy.html). 61 | 62 | When you register or log in to AdGuard Mail or other AdGuard services, you will be directed to [auth.adguardaccount.com](https://auth.adguardaccount.com), where you may be required to provide your login credentials (email and password). Upon successful authorization, an OAuth access token is issued to the app. 63 | 64 | ### Mailbox management in Temp Mail 65 | 66 | When you manage your mailboxes, including actions such as creating, retrieving, or deleting a mailbox, the following information may be transmitted: 67 | 68 | - **Mailbox ID**: A unique identifier for the mailbox associated with your account that is used to perform the requested action. 69 | - **Temporary email address**: The temporary email address linked to the mailbox. 70 | - **Language preference (optional)**: The language used to create the mailbox, which is automatically determined based on the language settings of the AdGuard Mail application. These settings are derived from your operating system or browser language preferences. 71 | 72 | The information transmitted allows us to manage your mailboxes efficiently. While mailbox IDs are used internally, the temporary email address is inherently transient and non-identifiable, reducing privacy risks. 73 | 74 | ### Message handling in Temp Mail 75 | 76 | When interacting with messages in your in Temp Mail mailboxes, such as retrieving, updating (marking as read), or deleting messages, the following information is transmitted: 77 | 78 | - **Mailbox ID and message ID**: Unique identifiers used to retrieve, update, or delete specific messages. 79 | - **Message content**: When requesting an email message, the full contents of the messages and the status of read messages are transmitted. 80 | 81 | Storing the content of incoming emails is a fundamental function of the temporary email service within AdGuard Mail. AdGuard Mail stores all information related to incoming messages, including the sender, subject, full email text, time of receipt, and more. This information is retained until you explicitly delete it or delete the account to which it belongs. 82 | 83 | Meanwhile, the alias service of AdGuard Mail does not store incoming messages and only performs the function of forwarding messages to the target mailboxes specified by you. 84 | 85 | ### Alias and recipient management 86 | 87 | When managing aliases and recipients, including actions like creating, retrieving, updating, or deleting, the following information is transmitted: 88 | 89 | - **Alias ID**: The unique identifier, name, description, and status of the alias. Fields that may contain user-defined information about the recipient. 90 | - **Recipient ID**: The unique identifier, name, description, and status of the recipient. Fields that may contain user-defined information about the recipient. 91 | - **Email address**: The email address associated with the recipient or alias. 92 | 93 | Alias and recipient management involves data that directly identifies email addresses and associated users. While email addresses are considered Personally Identifiable Information (PII), they are essential for the functionality of the service. 94 | 95 | ### Session and account access management 96 | 97 | When managing your account access or sessions, including actions like logging out, the following information may be transmitted: 98 | 99 | - **User ID**: The unique identifier and status of your account. 100 | - **Email address**: The email address associated with your account. 101 | - **Session information**: Details about the active sessions associated with your account. 102 | - **Authorization token**: A token used to authenticate and maintain your session. 103 | 104 | This information is crucial for maintaining secure access to your account and managing sessions across multiple devices. 105 | 106 | ### Statistics and blocked senders 107 | 108 | When viewing or managing statistics and blocked senders, the following information is transmitted: 109 | 110 | - **Alias IDs**: Identifiers used to retrieve statistics related to specific aliases. 111 | - **Sender email address**: The email address of the blocked sender. 112 | 113 | This information allows you to monitor activity and manage unwanted communications effectively. The data transmitted is used primarily for user interface purposes and generally does not contain sensitive personal information. 114 | 115 | ### Sending a message to support 116 | 117 | You can send messages to support directly from the app. If the *Send app and system info* option is enabled, the following information will be sent along with the message and the email address provided: 118 | 119 | - **App version** 120 | - **App identifier** 121 | - **App language** 122 | - **Device OS** 123 | - **Browser or OS version** 124 | - **App configuration** 125 | - **Account info**: Email address, user status, limits, default recipient 126 | - **System theme** 127 | - **Device language** 128 | - **Info about active temp mail address, aliases, and blocked senders** 129 | 130 | This detailed information is used by the support team to better assist with resolving your issue. 131 | 132 | ### Automatic crash reports 133 | 134 | The first time the app is launched, you will be asked if you want to allow AdGuard to send automatic crash reports. If you agree (and only if you agree), the following information will be sent to our servers if the app crashes: 135 | 136 | - **App identifier and version** 137 | - **Build identifier** 138 | - **Crash information**: Error message, stack trace, and timezone of the user 139 | - **Device name and model** 140 | - **OS version, architecture, root status, and kernel build** 141 | - **Hardware device info**: Screen orientation, resolution, and density, total and free RAM and ROM, etc. 142 | - **Device meta info** 143 | - **Unidentifiable device ID** 144 | 145 | **Why we need this information:** To troubleshoot critical issues. It helps us stay informed about new problems that are not reported by users. 146 | 147 | Crash report data is stored only on our servers. We do not use any third-party services with external hosting to collect or store crash reports. All crash reports are stored on our servers. 148 | 149 | ### Technical and interaction data 150 | 151 | The first time the app is launched, you will be asked if you want to allow AdGuard Mail to send technical and interaction data. If you agree, the following information will be sent: 152 | 153 | - **App identifier and version** 154 | - **Build identifier** 155 | - **Crash information**: Error message, stack trace, and timezone of the user 156 | - **Device name and model** 157 | - **OS version, architecture, root status, and kernel build** 158 | - **Hardware device info**: Screen orientation, resolution, and density, total and free RAM and ROM, etc. 159 | - **Device meta info** 160 | - **Unidentifiable device ID** 161 | - **Accessibility tool status** 162 | - **The last time the app was launched** 163 | - **Permissions granted by the user to the app** 164 | 165 | When the data is sent to AdGuard, your IP address may be temporarily collected as part of our server logs. 166 | 167 | This data is used only internally and is not shared with third parties. 168 | 169 | **Why we need this information:** 170 | 171 | - To find out which features are used the most 172 | - To identify issues users may face while using the app 173 | - To fix mistakes in the UI/UX 174 | - To learn what people like or don’t like about our app 175 | 176 | ### Buying a subscription 177 | 178 | We process your email address for billing and payment purposes. If you purchase a subscription to AdGuard Mail, we’ll need to know your contact details to send you information about the purchase. 179 | 180 | We’ll also use your email address to create an account for you. This account will allow you to manage your purchased subscription. 181 | 182 | We conduct all transactions via [Paddle.com Market Ltd](https://www.paddle.com) and [PayPro Global, Inc.](https://payproglobal.com) to enable payments if you purchase a subscription to use our software and services. 183 | The data processed depends on the payment provider and may include the following: 184 | 185 | - Email address 186 | - Country of residence 187 | - Zip or postal code 188 | - (If you use a bank card to make a purchase) Number, name, expiration date, and the security code associated with the bank card 189 | 190 | For the exact data that the payment provider collects about you, please see the corresponding privacy policy: [Paddle’s Privacy Policy](https://www.paddle.com/legal/privacy), [PayPro Global’s Privacy Policy](https://docs.payproglobal.com/documents/legal/privacyPolicy.pdf) 191 | 192 | ## Server data storage and logging practices 193 | 194 | **AdGuard Mail** consists of two main components: the temporary email service and the alias service. Each component handles data storage and logging differently to ensure user privacy while maintaining essential functionality. 195 | 196 | ### Alias service 197 | 198 | - **No logging of individual email forwarding**: The alias service does not log or store any records of individual emails being forwarded. This ensures that details of your email activity remain private. 199 | - **Aggregated statistics**: The alias service only stores aggregated statistics related to the number of emails forwarded through each alias. These statistics do not include any details about the emails themselves, such as content or specific sender/recipient information. 200 | 201 | ### Temporary email service 202 | 203 | - **Storage of received emails**: The temporary email service stores all emails received at the temporary email addresses you create. This allows you to access these emails as needed. 204 | - **Email deletion**: Emails stored by the temporary email service are deleted in two scenarios: 205 | - When you delete the temporary mailbox associated with the email. 206 | - When you manually delete individual emails. 207 | 208 | This approach ensures that the temporary email service retains emails only as long as they are needed. 209 | 210 | ## Third-party service: Amazon SES 211 | 212 | AdGuard Mail utilizes Amazon Simple Email Service (Amazon SES) to forward emails. When emails are forwarded using AdGuard Mail, the content of these emails and associated metadata (such as sender and recipient email addresses) are temporarily stored and processed by Amazon SES to ensure successful delivery. 213 | 214 | Amazon SES may retain certain data, such as logs, for a limited period of time for operational purposes, including tracking email deliverability and investigating service issues. However, the content of the emails is typically deleted shortly after processing is complete. 215 | 216 | Amazon SES is a trusted service provider that complies with strict privacy and security standards. By using AdGuard Mail, you acknowledge and agree that your email data will be handled by Amazon SES in accordance with their privacy practices. For more details, please refer to [Amazon’s Privacy Notice](https://aws.amazon.com/privacy) and [AWS SES Data Handling Policies](https://docs.aws.amazon.com/ses/latest/dg/deleting-personal-data.html). 217 | -------------------------------------------------------------------------------- /adguard-vpn.com/README.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard VPN Documents 3 | 4 | - [eula.html.md](eula.html.md) - AdGuard VPN End-User License Agreement. 5 | - [privacy.html.md](privacy.html.md) - AdGuard VPN Privacy Policy. 6 | - [extension.html.md](privacy/extension.html.md) - AdGuard VPN Browser Extension Privacy Notice. 7 | - [android.html.md](privacy/android.html.md) - AdGuard VPN for Android Privacy Notice. 8 | - [ios.html.md](privacy/ios.html.md) - AdGuard VPN for iOS Privacy Notice. 9 | - [mac.html.md](privacy/mac.html.md) - AdGuard VPN for Mac Privacy Notice. 10 | - [windows.html.md](privacy/windows.html.md) - AdGuard VPN for Windows Privacy Notice. 11 | 12 | ## List of documents in the footer 13 | 14 | - [EULA](eula.html.md) 15 | - [Privacy policy](privacy.html.md) 16 | - [Privacy policy of AdGuard websites](adguard.com/website-privacy.html.md) 17 | - [Terms and conditions of AdGuard websites](https://adguard.com/en/terms-and-conditions.html) 18 | - [Terms of sale](https://adguard.com/en/terms-of-sale.html) 19 | - [Data processing agreement](https://adguard.com/en/data-processing-agreement.html) 20 | 21 | Links to legal documents in the footer are arranged in order of importance. The same applies to the list of other documents at the end of each legal document. 22 | 23 | For example, this is what it should look like when you open the Privacy policy: 24 | 25 | Other documents: 26 | 27 | - [EULA](eula.html.md) 28 | - [Privacy policy of AdGuard websites](adguard.com/website-privacy.html.md) 29 | 30 | - [Terms and conditions of AdGuard websites](https://adguard.com/en/terms-and-conditions.html) 31 | - [Terms of sale](https://adguard.com/en/terms-of-sale.html) 32 | - [Data processing agreement](https://adguard.com/en/data-processing-agreement.html) 33 | 34 | - Privacy notices: 35 | - [AdGuard VPN Browser Extension](privacy/extension.html.md) 36 | - [AdGuard VPN for Android](privacy/android.html.md) 37 | - [AdGuard VPN for iOS](privacy/ios.html.md) 38 | - [AdGuard VPN for Mac](privacy/mac.html.md) 39 | - [AdGuard for Windows](privacy/windows.html.md) 40 | -------------------------------------------------------------------------------- /adguard-vpn.com/privacy.html.md: -------------------------------------------------------------------------------- 1 | # AdGuard VPN Privacy Policy 2 | 3 | *December 23, 2024* 4 | 5 | ## Summary 6 | 7 | We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 8 | 9 | 1. We don’t collect logs on VPN servers and don’t know what websites you visit. 10 | 1. We collect only the information necessary for our products and services to function properly. 11 | 1. You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account at my.adguard-vpn.com or by sending us a request at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 12 | 13 | ## Who we are 14 | 15 | ADGUARD SOFTWARE LIMITED (“We”, “Our” or “Us”) collects and processes your data in accordance with this Privacy Policy and in compliance with the applicable data protection laws. This Policy provides you with the necessary information regarding your rights and our obligations and explains how, why and when we process your personal data. Our general principle is to collect only the information that is necessary to provide you with full functionality of our products and services. We strictly follow the principle of “minimization” when processing your data. 16 | 17 | ADGUARD SOFTWARE LIMITED is a company registered in Limassol, Cyprus, registered office is at Anexartisias and Athinon 79, Nora Court Flat/Office 203-205, 3040 Limassol, Cyprus. ADGUARD SOFTWARE LIMITED acts as the data controller when processing your data. 18 | 19 | If you have any questions about this Privacy Policy or if you want to exercise any of your rights, please contact us at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 20 | 21 | Please read this Privacy Policy thoroughly. 22 | 23 | If you do not agree with our policies and practices described in this Privacy Policy, please do not use our software and services, do not visit our website, and do not provide your information to us. 24 | 25 | ## What data we process 26 | 27 | We process different data depending on the situation. You can learn details about what data we process in this section. 28 | 29 | Some data that we receive and process may be treated as personal data (“Personal Data”) in accordance with the laws of certain territories and countries. When we use terms “personal data” or “personal information”, we mean any information relating to an identified or identifiable natural person, excluding any anonymized and depersonalized data where your identity is absent or has been removed and cannot be recovered. 30 | 31 | ### When you are using our website 32 | 33 | **When you visit our website [adguard-vpn.com](https://adguard-vpn.com) and its subdomains**. For more information about what data is collected, how it is collected, and how you can manage it, please see the [Privacy Policy of AdGuard Websites](https://adguard.com/website-privacy.html). 34 | 35 | **Account registration**. We process your email address and a hash of the password which you provide to us at the registration. That ensures that you can retrieve your password if needed. 36 | 37 | **Sending messages**. We can use your email address to make announcements, inform you of updates and new features in our software or services, provide you with advice, or to communicate with you when reporting errors. 38 | 39 | You can also provide us with your consent to process your email for sending marketing messages about our other software or services. You can withdraw your consent any time by unsubscribing from our newsletters via AdGuard Account or by clicking the “Unsubscribe” button or link in the newsletter itself. 40 | 41 | **Cookies**. We use our cookies to personalize the content of AdGuard VPN website, such as setting the default language. None of the information we may acquire through the use of cookies is considered Personal Data as it does not allow us to identify you. You can always disable cookies in your web browsing software or clear existing cookies, but please note that some of our services may not function properly without the use of cookies. Please refer to the [Privacy Policy of AdGuard Websites](https://adguard.com/website-privacy.html). 42 | 43 | **Buying a subscription**. We process your email address for billing and payment purposes. If you purchase a subscription to AdGuard VPN, we’ll need to know your contact details to send you information about the purchase. 44 | 45 | We’ll also use your email address to create an account for you. This account will allow you to manage your purchased subscription. 46 | 47 | We conduct all transactions via [Paddle.com Market Ltd](https://www.paddle.com) and [PayPro Global, Inc.](https://payproglobal.com) to enable payments if you purchase a subscription to use our software and services. 48 | The data processed depends on the payment provider and may include the following: 49 | 50 | - Email address 51 | - Country of residence 52 | - Zip or postal code 53 | - (If you use a bank card to make a purchase) Number, name, expiration date, and the security code associated with the bank card 54 | 55 | For the exact data that the payment provider collects about you, please see the corresponding privacy policy: [Paddle’s Privacy Policy](https://www.paddle.com/legal/privacy), [PayPro Global’s Privacy Policy](https://docs.payproglobal.com/documents/legal/privacyPolicy.pdf). 56 | 57 | ### When you are using our software 58 | 59 | **Sign-in / Account registration**. When signing in to connect the installed app to your account or registering a new account, you need to provide your email address and create a password to initially create a VPN connection. We process this essential data to provide you with the AdGuard VPN service. 60 | 61 | **Using our software**. When you choose to use our app, you will provide us your data, including Personal Data. This information, which we must process to ensure the full functionality of AdGuard VPN services, depends on the operating system for which the software is designed. For details, please refer to the corresponding privacy notices. 62 | 63 | - For AdGuard VPN for Windows: [adguard-vpn.com/privacy/windows.html](https://adguard-vpn.com/privacy/windows.html) 64 | - For AdGuard VPN for Android: [adguard-vpn.com/privacy/android.html](https://adguard-vpn.com/privacy/android.html) 65 | - For AdGuard VPN for Mac: [adguard-vpn.com/privacy/mac.html](https://adguard-vpn.com/privacy/mac.html) 66 | - For AdGuard VPN for iOS: [adguard-vpn.com/privacy/ios.html](https://adguard-vpn.com/privacy/ios.html) 67 | - For AdGuard VPN Browser Extension: [adguard-vpn.com/privacy/extension.html](https://adguard-vpn.com/privacy/extension.html) 68 | 69 | **Usage information**. When you use our VPN service, we need to make sure that you stay within the agreed-upon limits. Therefore, we collect data on your traffic usage. This is done for two reasons: to prevent misuse of our service and to know when a user’s subscription has expired. When the subscription expires or is canceled, the free limit is reactivated and without knowing your previous data usage we cannot properly enforce the rules that limit using the free version. 70 | 71 | We store only the number of bytes used by the account, it is not associated with locations. Traffic usage data is stored for 90 days. 72 | 73 | Additionally, we collect information on the number of instances of our software that have an active VPN connection for both the free and paid versions. We receive this information from our VPN servers through which you establish a VPN connection. This is also done for the same reason — to make sure the user stays within the agreed-upon limits. 74 | 75 | **Diagnostic / Device information**. However, if you experience problems using our software and you give us your consent, we will collect and process some diagnostic information for crash reports and some information about the device used to run our software in order to help you. The exact information we collect and process depends on the AdGuard VPN software you are using. For details, please refer to the corresponding privacy notices. 76 | 77 | **User experience metrics**. To analyze and improve the current functionality, we collect user experience metrics pertaining to interactions with various screens. The collected information includes the following: 78 | 79 | - Screen name: the name of the screens the user interacts with 80 | - Buttons clicked: actions taken by clicking specific buttons 81 | - Synthetic identifier: a unique identifier used to link multiple events within the same session. All collected data is anonymized and **cannot be associated with your AdGuard account** under any circumstances. 82 | 83 | **By default this data is not collected**. We only gather user experience metrics if you explicitly agree to send them. If you initially agree to share metrics but change your mind later, you may revoke your consent at any time by disabling data collection in the settings of AdGuard VPN apps and extensions. 84 | 85 | ## What legal bases we use to process your Personal Data 86 | 87 | We use different legal bases to process Personal Data depending on the type of data, the purposes, and circumstances of processing. 88 | 89 | **Consent**. We process your Personal Data if you have provided us with your consent to use your personal data for certain purposes. For example, to send you marketing messages or to help you troubleshoot problems with using our software. You can withdraw your consent any time without affecting your use of our software. 90 | 91 | **Performance of a contract**. We process your Personal Data when it is necessary to fulfill our contractual obligations to you, including providing the functionality of our software and services or at your request prior to entering into a contract with you. 92 | 93 | **Legal obligations**. We process your Personal Data where it is necessary for compliance with our legal obligations, such as to exercise or defend our legal rights, or for taxation purposes. 94 | 95 | **Legitimate interest**. We process your Personal Data when we pursue our legitimate interests, except where such interests are overridden by the interests or fundamental rights and freedoms of data subjects. 96 | 97 | ## Where we process your Personal Data 98 | 99 | We store your Personal Data in our own data center located in Frankfurt. Your Personal Data may be processed by our employees, who can only access your data through their job duties on a need-to-know basis. If you have questions or would like to know from which countries your Personal Data may be accessed, you can write to us at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 100 | 101 | For data transfers to other countries, we always implement appropriate safeguards to ensure that your Personal Data always remains safe and that your rights are respected: 102 | 103 | - The country or the third party is recognized as providing adequate protection. 104 | - A valid transfer mechanism is used, such as the Standard Contractual Clauses, and supplementary measures are implemented where necessary. 105 | - The transfer has your explicit consent. 106 | - The transfer is necessary for the performance of a contract with you or to take steps requested by you prior to entering into that contract. 107 | 108 | If you would like a copy of the Standard Contractual Clauses used, please contact us at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 109 | 110 | To determine if a non-EU country has an adequate level of data protection, please visit [the European Commission website](https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en). 111 | 112 | ## How we use your Personal Data 113 | 114 | ### Retaining your data 115 | 116 | We retain Personal Data for as long as necessary to provide you with our products and services, or until you withdraw your consent to share this information. 117 | 118 | ### Your rights 119 | 120 | In some countries and regions, you may have certain rights in relation to your Personal Data under applicable data protection laws. 121 | 122 | If you wish to exercise your rights with respect to your Personal Data, please contact us at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). We will consider and act upon any request in accordance with applicable data protection laws. We may ask you to further confirm your identity and will respond to you within the time period specified by applicable data protection law. Please note that in certain cases stipulated by applicable data protection law, we may charge you a reasonable fee for processing your request or refuse your request. 123 | 124 | You are entitled to exercise the following rights in relation to your Personal Data: 125 | 126 | **Right of access**: The right to obtain all your Personal Data we store. In some cases, the right of access may be limited for technical reasons, including if the data has been anonymized and cannot be linked to any data subject. 127 | 128 | **Right to erasure or right to be forgotten**: The right to completely delete your Personal Data. You can do this at will via AdGuard Account, or by sending a request to [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 129 | 130 | **Right to rectification**: The right to correct any incomplete or inaccurate Personal Data about you. We will do so as quickly as possible, unless there is a valid reason not to, in which case you will be notified. 131 | 132 | **Right to restriction**: The right to impose restrictions on processing of your Personal Data. 133 | 134 | **Right to object**: The right to object to processing of your Personal Data. 135 | 136 | **Right to data portability**: The right to receive provided Personal Data in a structured, commonly used and machine-readable format and to transmit that data to another controller. You can export all Personal Data that we hold about you to a local file from your AdGuard Account at [adguardaccount.com](https://adguardaccount.com). 137 | 138 | **Right not to be subject to a decision based solely on automated processing**, including profiling. 139 | 140 | **Right to withdraw a consent** where the data processing is based on the consent. 141 | 142 | **Right to lodge a complaint** with a data protection authority. You can find contact details of our data protection authorities at [www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument](https://www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument). 143 | 144 | When we receive your Personal Data from a third party, we will use reasonable efforts to inform you about it. 145 | 146 | ### Safeguarding measures 147 | 148 | We make every possible effort to protect you and your Personal Data from unauthorized access, alteration, disclosure or destruction. We implement and maintain the following technical and security measures: 149 | 150 | **System access controls**: We take reasonable measures to prevent Personal Data from being used without authorization. These controls shall vary based on the nature of the processing undertaken and may include, among other controls, authentication via passwords and/or two-factor authentication, documented authorization processes, documented change management processes and/or logging of access on several levels. 151 | 152 | **Data access controls**: We take reasonable measures to ensure that Personal Data is accessible and manageable only by properly authorized staff. Direct database query access is restricted and application access rights are established and enforced to ensure that persons entitled to use a data processing system only have access to the Personal Data to which they have privilege of access; and that personal data cannot be read, copied, modified or removed without authorization in the course of processing. 153 | 154 | **Storing data in a data center**: Personal information is stored in our own data center located in Frankfurt. This is secure: the data center does not demand that we collect any data about your traffic or your use of our products and services. If they request us to start doing so, we will stop working with this provider and find an alternative. 155 | 156 | **Transmission controls**: We take reasonable measures to ensure that it is possible to check and establish to which entities the transfer of Personal Data by means of data transmission facilities is envisaged so Personal Data cannot be read, copied, modified or removed without authorization during electronic transmission or transport. 157 | 158 | **Input controls**: We take reasonable measures to make it possible to check and establish whether and by whom personal data has been entered into data processing systems, modified or removed. 159 | 160 | **Data backup**: We regularly back up our databases to protect Personal Data from accidental destruction or loss when hosted by us. The data is also encrypted so that it cannot be used if lost. 161 | 162 | **Logical separation**: Personal Data is logically segregated on our systems to ensure that Personal Data collected for different purposes can be processed separately. 163 | 164 | ### Consequences of not providing your Personal Data 165 | 166 | You are not obligated to provide your Personal Data to us. However, as this information is required for us to provide you with our services or respond to your requests, we will not be able to offer our services without it. 167 | 168 | ### Age limitations 169 | 170 | To the extent not prohibited by applicable law, we do not allow the use of our Services, Products, and Website by persons under the age of 18. If you learn that someone under the age of 18 has unlawfully provided us with Personal Data, please contact us at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). We will take steps to delete such information. 171 | 172 | ## Changes to this Privacy Policy 173 | 174 | We may change this Privacy Policy from time to time and inform you of some important changes. Laws, regulations and industry standards evolve, which may require these changes, or we may make changes to our business. We will post the changes on this page and encourage you to review our Privacy Policy to stay informed. 175 | -------------------------------------------------------------------------------- /adguard-vpn.com/privacy/android.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard VPN for Android Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | This Privacy Notice lists all the information that we, Adguard Software Ltd. (“we”, “us”, or “our”), may collect when you use AdGuard VPN for Android and explains why we do it and how we use this information. 7 | 8 | This Privacy Notice supplements the AdGuard VPN Privacy Policy available at [adguard-vpn.com/privacy.html](https://adguard-vpn.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 9 | 10 | --- 11 | 12 | **Keynote**: 13 | 14 | - We do not collect logs on VPN servers and do not know what websites you visit. 15 | - We only collect the information necessary for AdGuard VPN for Android to function fully and properly. 16 | - We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 17 | - You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account or by sending us a request at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 18 | 19 | --- 20 | 21 | ## What data AdGuard VPN for Android can collect and when 22 | 23 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 24 | 25 | ### Signing up 26 | 27 | When you create an AdGuard account, the following information is sent to our servers: 28 | 29 | - Email address 30 | - OAuth provider name: Google/Facebook/Apple (only if it was used for registering the account) 31 | - OS language 32 | - App identifier 33 | - App version 34 | - Build identifier 35 | 36 | **Why we need this information:** 37 | 38 | - We need your email address to register an AdGuard account and log you in. 39 | - We use the app identifier to control the simultaneous use of multiple apps. 40 | - OS language is required to communicate with you in your language. 41 | 42 | ### Logging in 43 | 44 | When you login to the application, your email address and the app version are sent to our servers. We need to know this because your email address is the login of your AdGuard VPN account. 45 | 46 | ### Subscribing to the AdGuard VPN newsletter 47 | 48 | After you sign up, you will be prompted to subscribe to the emails about AdGuard VPN news and promotions. If you agree, the app will notify the server to add you to the mailing list. 49 | 50 | ### The first launch of the app 51 | 52 | When you launch AdGuard VPN for Android for the first time, the following information is sent to our servers: 53 | 54 | - App identifier 55 | - App version 56 | - Device OS 57 | - OS language 58 | 59 | **Why we need this information:** 60 | 61 | - To monitor the number of simultaneous connections 62 | - To count the number of applications of a certain type and version 63 | 64 | ### Using the app 65 | 66 | AdGuard VPN periodically connects to our server to check the account status. The following information is sent: 67 | 68 | - Authorization token 69 | - App ID 70 | - App version 71 | - App language 72 | - App type 73 | - OS language 74 | 75 | ## Connecting to the VPN server 76 | 77 | When you click *Connect*, the app will send your authorization token to AdGuard servers. We need this information to check the account status and authorization on the VPN server. 78 | 79 | ### Contacting support 80 | 81 | You can send messages to support by tapping *Report a bug* or *Request a feature*. 82 | 83 | When you submit a report, your email address is sent to our servers. The AdGuard VPN support team may use it for follow-up communication about the issue. 84 | 85 | The following information is also included in the report: 86 | 87 | - Report type (*Bug report* or *Feature request*) 88 | - Email address 89 | - Authorization token 90 | - App identifier 91 | - App version 92 | 93 | If you check the checkbox for *Send app logs and system info*, a 10 MB zip file with the following information will be sent to our servers: 94 | 95 | - App settings 96 | - Exclusion lists 97 | - License info 98 | - Currently used VPN server location 99 | - App logs 100 | - Device model 101 | - OS version 102 | 103 | This detailed information is used by the support team to help solve more complicated problems. 104 | 105 | ### Automatic crash reports 106 | 107 | If you enable *Send anonymous crash reports*, the following data will be collected and stored if the app crashes: 108 | 109 | - Device name and model 110 | - OS version and kernel build 111 | - ROOT status 112 | - Android ID 113 | - Amounts of total and free RAM 114 | - Screen orientation 115 | - Screen resolution and density 116 | - App name and version 117 | - Information related to the crash (error message and stack trace) 118 | - The last lines of the log file 119 | 120 | This data will be sent to our servers along with the crash report the next time the app is launched. 121 | 122 | We need this information to troubleshoot critical issues. It keeps us aware of new problems not reported by users. 123 | 124 | Crash reports are stored only on our servers. We do not use any third-party services to collect and store crash reports. All crash reports are stored for 30 days. 125 | -------------------------------------------------------------------------------- /adguard-vpn.com/privacy/extension.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard VPN Browser Extension Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | This Privacy Notice lists all the information that we, Adguard Software Ltd. (“we”, “us”, or “our”), may collect when you use AdGuard VPN Browser Extension and explains why we do it and how we use this information. 7 | 8 | This Privacy Notice supplements the AdGuard VPN Privacy Policy available at [adguard-vpn.com/privacy.html](https://adguard-vpn.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 9 | 10 | --- 11 | 12 | **Keynote:** 13 | 14 | - We do not collect logs of your activity on VPN servers and do not know what websites you visit 15 | - We only collect the information necessary for AdGuard VPN Browser Extension to function fully and properly 16 | - We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible 17 | - You can delete your information by deleting your AdGuard account or by sending us a request at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com) 18 | - The information we collect about you depends on how you interact with our extension. 19 | 20 | --- 21 | 22 | ## What data AdGuard VPN Browser Extension can collect and when 23 | 24 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the extension to work properly. 25 | 26 | ### Signing up 27 | 28 | When we create an account for the user, the following information is sent to our servers: 29 | 30 | - Email address 31 | - App identifier 32 | - OS language 33 | - Marketing consent flag indicating whether user has consented to receive marketing emails 34 | 35 | **Why we need this information:** 36 | 37 | - We need your email address to register an AdGuard account and log you in. 38 | - We use the app identifier to control the simultaneous use of multiple apps. 39 | - OS language is required to communicate with you in your language. 40 | 41 | ### Logging in 42 | 43 | When you login, your email address is sent to our servers. We need your email address to register an AdGuard account and log you in. 44 | 45 | ### First launch of the extension 46 | 47 | When AdGuard VPN Browser Extension is first launched, the following information is sent to our servers: 48 | 49 | - App identifier 50 | - Extension version 51 | - Extension language 52 | - OS language 53 | 54 | **Why we need this information:** 55 | 56 | - To monitor the number of simultaneous connections 57 | - To count the number of apps of a certain type and version 58 | 59 | ### User authorization 60 | 61 | To make sure that the user is authorized, the following information is sent to our servers: 62 | 63 | - Email address 64 | - Extension version 65 | 66 | ### Using the extension 67 | 68 | AdGuard VPN periodically connects to our server to check the account status. The following information is sent: 69 | 70 | - App identifier 71 | - Authorization token 72 | - Extension language 73 | 74 | **Why we need this information:** To ensure that users have access to available server locations and the VPN server, and give users the choice of available locations. 75 | 76 | ### Sending a message to support 77 | 78 | If a user does not attach debug logs, only their message is sent, along with the following information: 79 | 80 | - Email address 81 | - App identifier 82 | - Authorization token 83 | - Extension version 84 | 85 | **Why do we need this information:** This information is used by our support team to perform minimal diagnostics. 86 | When a user attaches debug logs, logs stored on the user’s device are also sent. This detailed information is used by the support team to help solve more complicated problems. 87 | -------------------------------------------------------------------------------- /adguard-vpn.com/privacy/ios.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard VPN for iOS Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | This Privacy Notice lists all the information that we, Adguard Software Ltd. (“we”, “us”, or “our”), may collect when you use AdGuard VPN for iOS and explains why we do it and how we use this information. 7 | 8 | This Privacy Notice supplements the AdGuard VPN Privacy Policy available at [adguard-vpn.com/privacy.html](https://adguard-vpn.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 9 | 10 | --- 11 | 12 | **Keynote**: 13 | 14 | - We do not collect logs on VPN servers and do not know what websites you visit. 15 | - We only collect the information necessary for AdGuard VPN for iOS to function fully and properly. 16 | - We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 17 | - You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account or by sending us a request at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 18 | 19 | --- 20 | 21 | ## What data AdGuard VPN for iOS can collect and when 22 | 23 | Here we describe when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the app to work properly. The information we collect about you depends on how you interact with our app. 24 | 25 | ### Signing up 26 | 27 | When we create an AdGuard account for you, the following information is sent to our servers: 28 | 29 | - Email address 30 | - OAuth provider name: Google/Facebook/Apple (only if it was used to register the account) 31 | - App identifier 32 | - App version 33 | 34 | **Why we need this information:** 35 | 36 | - We need your email address to register an AdGuard account and log you in. 37 | - We need your app identifier to control the simultaneous use of multiple apps. 38 | 39 | ### Logging in 40 | 41 | When you log in to the app, your email address and the app version are sent to our servers. We need your email address to register an AdGuard account and log you in. 42 | 43 | ### Subscribing to the AdGuard VPN newsletter 44 | 45 | After you log in or sign up, you will be prompted to subscribe to the AdGuard VPN newsletter. If you agree, the app will notify the server to add you to the mailing list. 46 | 47 | ### The first launch of the app 48 | 49 | When you launch AdGuard VPN for iOS for the first time, the following information is sent to our servers: 50 | 51 | - App identifier 52 | - App version 53 | - Device OS: iOS 54 | - OS language 55 | - Apple AdServices Token 56 | 57 | **Why we need this information:** 58 | 59 | - To monitor the number of simultaneous connections 60 | - To count the number of apps of a certain type and version 61 | - To communicate with you in your language 62 | - To integrate with Apple Search Ads 63 | 64 | ### Using the app 65 | 66 | AdGuard VPN periodically connects to our server to check the account status. The following information is sent: 67 | 68 | - Authorization token 69 | - App ID 70 | - App version 71 | - App language 72 | - App type 73 | - OS language 74 | 75 | ### Connecting to the VPN server 76 | 77 | When you click *Connect*, the app will send your authorization token to AdGuard servers. We need this information to check the account status and authorization on the VPN server. 78 | 79 | ### Contacting support 80 | 81 | You can send messages to support by tapping *Report a bug* or *Request a feature*. 82 | 83 | When you submit a report, your email address is sent to our servers. The AdGuard VPN support team may use it for follow-up communication about the issue. 84 | 85 | The following information is also included in the report: 86 | 87 | - Report type (*Bug report* or *Feature request*) 88 | - Email address 89 | - Authorization token 90 | - App identifier 91 | - App version 92 | 93 | If you check the checkbox for *Send app logs and system info*, a 10 MB zip file with the following information will be sent to our servers: 94 | 95 | - App settings 96 | - Exclusion lists 97 | - License info 98 | - Currently used VPN server location 99 | - App logs 100 | - Device model 101 | - OS version 102 | 103 | This detailed information is used by the support team to help solve more complicated problems. 104 | 105 | ### Automatic crash reports 106 | 107 | If you enable *Send anonymous crash reports*, the following data will be collected and stored if the app crashes: 108 | 109 | - App name, version, and build number 110 | - Versions of app libraries 111 | - Name of the crashed process 112 | - Type of environment where the crash occurred 113 | - Type of mechanism used to record the crash 114 | - OS and its version 115 | - Device name, model, and ID 116 | - User ID 117 | 118 | This data will be sent to our servers along with the crash report the next time the app is launched. 119 | 120 | We need this information to troubleshoot critical issues. It keeps us aware of new problems not reported by users. 121 | 122 | Crash reports are stored only on our servers. We do not use any third-party services to collect and store crash reports. All crash reports are stored for 30 days. 123 | -------------------------------------------------------------------------------- /adguard-vpn.com/privacy/mac.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard VPN for Mac Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | This Privacy Notice lists all the information that we, Adguard Software Ltd. (”we”, ”us”, or ”our”), may collect when you use AdGuard VPN for Mac and explains why we do it and how we use this information. 7 | 8 | This Privacy Notice supplements the AdGuard VPN Privacy Policy available at [adguard-vpn.com/privacy.html](https://adguard-vpn.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 9 | 10 | --- 11 | 12 | **Keynote**: 13 | 14 | - We do not collect logs on VPN servers and do not know what websites you visit. 15 | - We only collect the information necessary for AdGuard VPN for Mac to function fully and properly. 16 | - We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 17 | - You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account or by sending us a request at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 18 | 19 | --- 20 | 21 | ## What data AdGuard VPN for Mac can collect and when 22 | 23 | Here we describe when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the app to work properly. The information we collect about you depends on how you interact with our app. 24 | 25 | ### Signing up 26 | 27 | When we create an AdGuard account for you, the following information is sent to our servers: 28 | 29 | - Email address 30 | - OAuth provider name: Google/Facebook/Apple (only if it was used to register the account) 31 | - MAC address hash 32 | - OS language 33 | - App identifier 34 | - App version 35 | - Build identifier 36 | 37 | **Why we need this information:** 38 | 39 | - We need your email address to register an AdGuard account and log you in. 40 | - We need your app identifier to control the simultaneous use of multiple apps. 41 | - OS language is required to communicate with you in your language. 42 | 43 | ### Logging in 44 | 45 | When you log in to the app, your email address and the app version are sent to our servers. We need your email address to register an AdGuard account and log you in. 46 | 47 | ### Subscribing to the AdGuard VPN newsletter 48 | 49 | After you log in or sign up, you will be prompted to subscribe to the AdGuard VPN newsletter. If you agree, the app will notify the server to add you to the mailing list. 50 | 51 | ### The first launch of the app 52 | 53 | When you launch AdGuard VPN for Mac for the first time, the following information is sent to our servers: 54 | 55 | - App identifier 56 | - App version 57 | - Device OS: macOS 58 | - OS language 59 | 60 | **Why we need this information:** 61 | 62 | - To monitor the number of simultaneous connections 63 | - To count the number of apps of a certain type and version 64 | - To communicate with you in your language 65 | 66 | ### Using the app 67 | 68 | AdGuard VPN periodically connects to our server to check the account status. The following information is sent: 69 | 70 | - Authorization token 71 | - App identifier 72 | - App version 73 | - Device OS: macOS 74 | - OS language 75 | 76 | We need this information to check the account status and authorization on the VPN server. 77 | 78 | ### Program update checks 79 | 80 | AdGuard VPN for Mac periodically connects to its servers to check for app updates. When it happens, no personal information is sent to our servers. 81 | 82 | ### Contacting support 83 | 84 | Users can send messages to support from the *Support* tab in the app by clicking *Report a bug*. 85 | 86 | When the user submits a report, their email address is sent to our servers. The AdGuard VPN support team may use it for follow-up communication about the issue. 87 | 88 | The following information is also included in the report: 89 | 90 | - App identifier 91 | - App version 92 | - Authorization token 93 | 94 | If the user checks the checkbox for *Send detailed system info*, a file with the following information will be sent to our servers: 95 | 96 | - App settings 97 | - OS language 98 | - OS version 99 | - App logs 100 | 101 | This detailed information is used by the support team to help solve more complicated problems. 102 | 103 | ### Automatic and manual crash reports 104 | 105 | If the app crashes, it will collect and store the following data: 106 | 107 | - App identifier 108 | - App version 109 | - Device hardware hash 110 | - Device model, its memory size, and disk space 111 | - OS version 112 | - Stack trace 113 | - List of components used by the app and their versions 114 | - The timestamp of the last OS start 115 | - The timestamp of the last app start 116 | 117 | If you enable *Send crash reports* in Settings, this data will be automatically sent to our servers along with the crash report the next time the app is launched. 118 | 119 | If you don’t enable *Send crash reports*, the app will prompt you to send a report. If you agree, it will send the above-mentioned information to our servers. If you enter your email address, its hashed version will also be sent. 120 | 121 | We need this information to troubleshoot critical issues. It keeps us aware of new problems not reported by users. 122 | 123 | Crash reports are stored only on our servers. We do not use any third-party services to collect and store crash reports. All crash reports are stored for 30 days. 124 | -------------------------------------------------------------------------------- /adguard-vpn.com/privacy/windows.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard VPN for Windows Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | This Privacy Notice lists all the information that we, Adguard Software Ltd. (“we”, “us”, or “our”), may collect when you use AdGuard VPN for Windows and explains why we do it and how we use this information. 7 | 8 | This Privacy Notice supplements the AdGuard VPN Privacy Policy available at [adguard-vpn.com/privacy.html](https://adguard-vpn.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 9 | 10 | --- 11 | 12 | **Keynote:** 13 | 14 | - We do not collect logs on VPN servers and do not know what websites you visit. 15 | - We only collect the information necessary for AdGuard VPN for Windows to function fully and properly. 16 | - We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 17 | - You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account or by sending us a request at [privacy@adguard-vpn.com](mailto:privacy@adguard-vpn.com). 18 | 19 | --- 20 | 21 | ## What data AdGuard VPN for Windows can collect and when 22 | 23 | Here we describe when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the app to work properly. The information we collect about you depends on how you interact with our app. 24 | 25 | ### Signing up 26 | 27 | When you create an AdGuard account, the following information is sent to our servers: 28 | 29 | - Email address 30 | 31 | - OAuth provider name: Google/Facebook/Apple (only if it was used to register the account) 32 | 33 | - OS language 34 | 35 | - App identifier 36 | 37 | - App version 38 | 39 | - Build identifier 40 | 41 | **Why we need this information:** 42 | 43 | - We need your email address to register an AdGuard account and log you in. 44 | 45 | - We use the app identifier to control the simultaneous use of multiple apps. 46 | 47 | - OS language is required to communicate with you in your language. 48 | 49 | ### Logging in 50 | 51 | When you log in to the app, your email address and the app version are sent to our servers. We need your email address to register an AdGuard account and log you in. 52 | 53 | ### Subscribing to the AdGuard VPN newsletter 54 | 55 | After you sign up, you will be prompted to subscribe to the emails about AdGuard VPN news and promotions. If you agree, the app will notify the server to add you to the mailing list. 56 | 57 | ### The first launch of the app 58 | 59 | When you launch AdGuard VPN for Windows for the first time, the following information is sent to our servers: 60 | 61 | - App identifier 62 | 63 | - App version 64 | 65 | - Device OS 66 | 67 | - OS language 68 | 69 | **Why we need this information:** 70 | 71 | - To monitor the number of simultaneous connections 72 | 73 | - To count the number of apps of a certain type and version 74 | 75 | ### Using the app 76 | 77 | AdGuard VPN periodically connects to our server to check the account status. The following information is sent: 78 | 79 | - Authorization token 80 | 81 | - App identifier 82 | 83 | - App version 84 | 85 | - Device OS 86 | 87 | - OS language 88 | 89 | We need this information to check the account status and authorization on the VPN server. 90 | 91 | ### Checking for program updates 92 | 93 | AdGuard VPN for Windows periodically connects to its servers to check for app updates. When it happens, no personal information is sent to our servers. 94 | 95 | ### Contacting support 96 | 97 | You can send messages to support from the *Support* tab in the app by clicking *Report a bug* or *Leave feedback*. 98 | 99 | When you submit a report, your email address is sent to our servers. The AdGuard VPN support team may use it for follow-up communication about the issue. 100 | 101 | The following information is also included in the report: 102 | 103 | - App identifier 104 | 105 | - App version 106 | 107 | - Authorization token 108 | 109 | If you check the *Send detailed system info* checkbox, a file with the following information will be sent to our servers: 110 | 111 | - App settings 112 | 113 | - OS language 114 | 115 | - OS version 116 | 117 | - App logs 118 | 119 | This detailed information is used by the support team to help solve more complicated problems. 120 | 121 | ### Automatic and manual crash reports 122 | 123 | If AdGuard VPN crashes, it will create an automatic crash report. Upon the next launch, AdGuard VPN will ask you to send it to us. In this report, the following information is sent: 124 | 125 | - App identifier 126 | 127 | - App version 128 | 129 | - Device hardware hash 130 | 131 | - Device model, its memory size, and disk space 132 | 133 | - OS version 134 | 135 | - Stack trace 136 | 137 | - List of components used by the app and their versions 138 | 139 | - The timestamp of the last OS start 140 | 141 | - The timestamp of the last app start 142 | 143 | If you enable *Send crash reports*, this data will be automatically sent to our servers along with the crash report the next time the app is launched. 144 | 145 | We need this information to troubleshoot critical issues. It keeps us aware of new problems not reported by users. 146 | 147 | Crash report data is stored only on our servers. We do not use any third-party services to collect and store crash reports. All crash reports are stored for 30 days. 148 | -------------------------------------------------------------------------------- /adguard.com/README.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard Documents 3 | 4 | - [eula.html.md](eula.html.md) - AdGuard End-User License Agreement. 5 | - [privacy.html.md](privacy.html.md) - AdGuard Privacy Policy. 6 | - [website-privacy.html.md](website-privacy.html.md) - Privacy Policy of AdGuard Websites. 7 | - [terms-and-conditions.html.md](terms-and-conditions.html.md) - Terms and Conditions of AdGuard Account and AdGuard Websites. 8 | - [extension-eula.html.md](extension-eula.html.md) - AdGuard Browser Extension End User License Agreement. 9 | - [browser-assistant.html.md](browser-assistant.html.md) - AdGuard Browser Assistant Privacy Notice. 10 | - [extension.html.md](privacy/extension.html.md) - AdGuard Browser Extension Privacy Notice. 11 | - [content-blocker.html.md](privacy/content-blocker.html.md) - AdGuard Content Blocker Privacy Notice. 12 | - [android.html.md](privacy/android.html.md) - AdGuard for Android Privacy Notice. 13 | - [ios.html.md](privacy/ios.html.md) - AdGuard for iOS Privacy Notice. 14 | - [mac.html.md](privacy/mac.html.md) - AdGuard for Mac Privacy Notice. 15 | - [safari.html.md](privacy/safari.html.md) - AdGuard for Safari Privacy Notice. 16 | - [windows.html.md](privacy/windows.html.md) - AdGuard for Windows Privacy Notice. 17 | - [home.html.md](privacy/home.html.md) - AdGuard Home Privacy Notice. 18 | 19 | ## List of documents in the footer 20 | 21 | - [EULA](eula.html.md) 22 | - [EULA of AdGuard Temp Mail](https://adguard.com/adguard-temp-mail/eula.html) 23 | - [Privacy policy](privacy.html.md) 24 | - [Privacy policy of AdGuard websites](website-privacy.html.md) 25 | - [Terms and conditions of AdGuard websites](terms-and-conditions.html.md) 26 | - [Terms of sale](https://adguard.com/en/terms-of-sale.html) 27 | - [Data processing agreement](data-processing-agreement.html.md) 28 | 29 | Links to legal documents in the footer are arranged in order of importance. The same applies to the list of other documents at the end of each legal document. 30 | 31 | For example, this is what it should look like when you open the Privacy policy: 32 | 33 | Other documents: 34 | 35 | - [EULA](eula.html.md) 36 | - [EULA of AdGuard Temp Mail](https://adguard.com/adguard-temp-mail/eula.html) 37 | - [Privacy policy of AdGuard websites](website-privacy.html.md) 38 | - [Terms and conditions of AdGuard websites](terms-and-conditions.html.md) 39 | - [Terms of sale](https://adguard.com/en/terms-of-sale.html) 40 | - [Data processing agreement](data-processing-agreement.html.md) 41 | 42 | - Privacy notices: 43 | - [AdGuard Assistant](privacy/browser-assistant.html.md) 44 | - [AdGuard Browser Extension](privacy/extension.html.md) 45 | - [AdGuard Content Blocker](privacy/content-blocker.html.md) 46 | - [AdGuard for Android](privacy/android.html.md) 47 | - [AdGuard for iOS](privacy/ios.html.md) 48 | - [AdGuard for Mac](privacy/mac.html.md) 49 | - [AdGuard for Safari](privacy/safari.html.md) 50 | - [AdGuard for Windows](privacy/windows.html.md) 51 | - [AdGuard Home](privacy/home.html.md) 52 | - [AdGuard Temp Mail](https://adguard.com/privacy/temp-mail.html) 53 | -------------------------------------------------------------------------------- /adguard.com/data-processing-agreement.html.md: -------------------------------------------------------------------------------- 1 | # AdGuard Data Processing Agreement 2 | 3 | *October 31, 2024* 4 | 5 | This Data Processing Agreement (”Agreement”) governs the specific requirements of Data Protection Laws to the extent that Company’s use of AdGuard Services implies the processing of Personal Data subject to Data Protection Laws. 6 | 7 | This Agreement is complementary to our Privacy Policy, which serves as the primary reference for our data protection practices and measures. 8 | 9 | The term of this Agreement shall follow the term of the Service Agreement. Terms not defined herein shall have the meaning as set forth in the Service Agreement. 10 | 11 | **THE PERSONS WHO DO NOT AGREE WITH THE AGREEMENT IN FULL AND/OR IN PART, AND/OR WHO DO NOT UNDERSTAND ANY OF THE PROVISIONS OF AGREEMENT, SHOULD NOT TAKE ANY ACTIONS AIMED TO ACCESS AND USE THE SERVICES, OTHERWISE SUCH PERSONS ARE CONSIDERED UNCONDITIONALLY ACCEPTED AGREEMENT, WITHOUT ANY EXCEPTIONS.** 12 | 13 | ## DEFINITIONS AND INTERPRETATION 14 | 15 | Unless otherwise defined herein, capitalized terms and expressions used in this DPA shall have the following meaning: 16 | 17 | Terms and definitions 18 | 19 | - **”AdGuard”**: AdGuard Software Limited, a company duly incorporated under the laws of Cyprus, with a registration number 332952. 20 | - **”AdGuard Services” or ”Services”**: The Services are provided by AdGuard and specified on the Website. 21 | - **”Agreement”**: Means this Data Processing Agreement and all Schedules. 22 | - **”Company”**: A customer of the AdGuard Services under the Service Agreement. 23 | - **”Company Personal Data”**: Means any Personal Data related to the Company or the Company’s customers or employees processed in connection with the Service Agreement. 24 | - **”Contracted Processor”**: Means a Subprocessor. 25 | - **”Data Protection Laws”**: Means EU Data Protection Laws and, to the extent applicable, the data protection or privacy laws of any other country. 26 | - **”EEA”**: Means the European Economic Area. 27 | - **”EU Data Protection Laws”**: Means EU Directive 95/46/EC, as transposed into domestic legislation of each Member State and as amended, replaced, or superseded from time to time, including by the GDPR and laws implementing or supplementing the GDPR. 28 | - **”GDPR”**: Means the EU General Data Protection Regulation 2016/679. 29 | - **”Data Transfer”**: Means a transfer of a Company’s Personal Data from a Controller to a Processor or a Contracted Processor, or an onward transfer of Company Personal Data from a Processor to a Subprocessor, or between two establishments of a Subprocessor. 30 | - **”Service Agreement”**: Means an agreement between AdGuard and Customer which is regulated by separate written document under which AdGuard may grant to Company a non-exclusive, non-transferable right to access and use the AdGuard Services, in accordance with the terms and limitations set forth in that Service Agreement and the applicable Subscription Plan. Under that Service Agreement, the Company may have the right to distribute the AdGuard Services to the End Users. Therefore, in order to secure the personal data of End Users to whom the AdGuard Services may be distributed under the Service Agreement, the Company undertakes to follow the rules specified in the present Agreement (Data Processing Agreement). 31 | - **”Subprocessor”**: Means any person appointed by or on behalf of a Processor to process Personal Data on behalf of a Controller in connection with the Agreement. 32 | - **”Website”**: https://adguard.com, https://adguard-vpn.com, https://adguard-dns.io/, or any other website related to the provision of AdGuard Services on behalf of AdGuard. 33 | 34 | The terms, ”Commission”, ”Controller”, ”Data Subject”, ”Member State”, ”Personal Data”, ”Personal Data Breach”, ”Processing” and ”Supervisory Authority” shall have the same meaning as in the GDPR or other applicable Data Protection Law, and their cognate terms shall be construed accordingly. 35 | 36 | The following terminology applies to these Agreement: “Company”, ”You” and ”Your” refers to you as a Company and a Contractor under Service Agreement. ”We”, ”Ourselves”, ”Our” and ”Us”, refers to AdGuard. ”Party”, ”Parties” refers to both the Company and AdGuard. Any use of the above terminology or other words in the singular, plural, capitalization and/or he/she or they, are taken as interchangeable and therefore as referring to same. 37 | 38 | ### 1. GENERAL PROVISIONS 39 | 40 | In order to protect and secure personal data of End Users of the Services the Parties hereby agree about the following: 41 | 42 | - The Company act as a Data Controller (the ”Controller”). 43 | 44 | - The Company wishes to subcontract certain Services (as defined below), which imply the processing of Personal Data, to AdGuard, acting as a Data Processor (the ”Processor”). 45 | 46 | - The Parties seek to implement a data processing agreement that complies with the requirements of the current legal framework in relation to data processing and with the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of Personal Data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) and other applicable data protection laws. 47 | 48 | - The Parties wish to lay down their rights and obligations. 49 | 50 | ### 2. PROCESSING OF COMPANY PERSONAL DATA 51 | 52 | Processor shall: 53 | 54 | - comply with all applicable Data Protection Laws in the Processing of Company Personal Data; 55 | 56 | - and not process Company Personal Data other than on Controller’s documented instructions in section 2. 57 | 58 | Controller instructs Processor to process Company Personal Data to: 59 | 60 | - provide the Services and related technical support; 61 | 62 | - fulfill legal obligations or resolve disputes; 63 | 64 | - exercise any internal task aimed to optimize the security, privacy, confidentiality and functionalities of the Services; 65 | 66 | - exercise internal reporting, financial reporting and other similar internal tasks. 67 | 68 | ### 3. PROCESSOR PERSONNEL 69 | 70 | Processor shall take reasonable steps to ensure the reliability of any employee, agent or contractor of any Contracted Processor who may have access to Company Personal Data, ensuring in each case that access is strictly limited to those individuals who need to know / access the relevant Company Personal Data, as strictly necessary for the purposes of the Principal Agreement, and/or to comply with Data Protection Laws and other relevant legislation in the context of that individual’s duties to the Contracted Processor, ensuring that all such individuals are subject to confidentiality undertakings or professional or statutory obligations of confidentiality. 71 | 72 | ### 4. SECURITY 73 | 74 | In accordance with Article 32 (1) of the GDPR, the Processor shall implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of processing. These measures shall be designed to protect the rights and freedoms of natural persons, considering the risks of varying likelihood and severity, including the risk of a Personal Data Breach. 75 | 76 | The Processor shall also assess the risks associated with processing activities and apply measures that are consistent with the requirements set forth in Article 32 (1) GDPR, ensuring the security of Company Personal Data at all times. 77 | 78 | ### 5. SUBPROCESSING 79 | 80 | Subject to this Agreement, the Company grants general authorization to the Processor to engage Subprocessors and disclose or transfer Company Personal Data to them. The Company acknowledges and approves the list of Subprocessors outlined in the Processor’s Privacy Policy, understanding that this list may be updated by the Processor regularly, in which case the company shall be informed by the Processor according to the Privacy Policy notification process. Furthermore, the Company authorizes the Processor to disclose and transfer Personal Data to any company within its corporate group. 81 | 82 | Processor ensures that Subprocessors are subject to an agreement with Processor no less restrictive and protective than the present Agreement with respect to the protection of Company Personal Data to the extent applicable to the nature of the services provided by the Subprocessor. 83 | 84 | ### 6. DATA SUBJECT RIGHTS 85 | 86 | Taking into account the nature of the processing, Processor shall reasonably assist Company for the fulfillment of Company’s obligations to respond to requests to exercise Data Subject rights under the Data Protection Laws. 87 | 88 | Processor shall: 89 | 90 | - promptly notify Company if it receives a request from a Data Subject under any Data Protection Law in respect of Company Personal Data; and 91 | 92 | - ensure that it does not respond to that request except on the documented instructions of Controller or as required by Applicable Laws to which the Processor is subject, in which case Processor shall to the extent permitted by Applicable Laws inform Controller of that legal requirement before the Contracted Processor responds to the request. 93 | 94 | ### 7. PERSONAL DATA BREACH 95 | 96 | The Processor shall manage any Personal Data Breach in compliance with applicable Data Protection Laws and its internal Personal Data Breach procedures. In the event of a Personal Data Breach affecting company Personal Data, the Processor shall notify the Company without delay, providing sufficient information to enable the Company to fulfill its obligations under Data Protection Laws, including informing Data Subjects as necessary. In such cases, Processor shall provide Company with sufficient information to allow Company to meet any obligations to report or inform Data Subjects of the Personal Data Breach under the Data Protection Laws. 97 | 98 | Processor shall co-operate with Company and take reasonable commercial steps as are directed by Company to assist in the investigation, mitigation and remediation of each such Personal Data Breach. 99 | Each party shall bear the costs of the investigation, remediation, mitigation, and other related costs to the extent a Data Breach is caused by such party. 100 | 101 | Each party shall bear the costs of any fines, penalties, damages, or other related amounts imposed by an authorized regulatory body, governmental agency, or court of competent jurisdiction to the extent arising from such party’s breach of its obligations under this Agreement. 102 | 103 | ### 8. DATA PROTECTION IMPACT ASSESSMENT AND PRIOR CONSULTATION 104 | 105 | Processor shall provide reasonable assistance to Company with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Controller reasonably considers to be required by article 35 or 36 of the GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Company Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors. 106 | 107 | ### 9. DELETION OR RETURN OF COMPANY PERSONAL DATA 108 | 109 | In case of cessation of any Service involving the Processing of Company Personal Data, the Processor shall delete all Company Personal Data to the extent permitted by applicable laws and in accordance with Processor’s Terms and Conditions and Privacy Policy. Should the Company require a copy of their data, they must request it before the deletion of their account; requests made after the account has been deleted can no longer be considered. 110 | 111 | ### 10. AUDIT RIGHTS 112 | 113 | Subject to this section 10, Processor shall make available to Company on request all information necessary to demonstrate compliance with this Agreement. Company shall not exercise its rights more than once per calendar year except following a Personal Data Breach or an instruction by a regulatory authority. 114 | 115 | Company shall give Processor at least sixty (60) days prior written notice of its intention to audit Processor pursuant to this Agreement. Audit shall be conducted during Processor’s business hours, shall not disrupt Processor’s operations and shall ensure the protection of the Company’s, Processor’s and other Data Subjects’ Personal Data. Processor and Company shall mutually agree in advance on the date, scope, duration and security and confidentiality controls applicable to the audit. Company acknowledges that the signing of a non-disclosure agreement may be required by the Controller prior to the conduction of the audit. 116 | 117 | Information and audit rights of Company only arise under section 10 to the extent that the Agreement does not otherwise give them information and audit rights meeting the relevant requirements of Data Protection Law. 118 | 119 | ### 11. DATA TRANSFER 120 | 121 | To the extent possible, the Processor shall only transfer or authorize the transfer of Data to countries within Switzerland, the EU and/or countries subject to an adequacy decision, as provided for in art. 45 GDPR and art. 16 Swiss FADP. If Personal Data processed under this Agreement is transferred from Switzerland or any country within the EU or any country subject to an adequacy decision to a country outside of this scope, the Parties shall ensure that the Personal Data are adequately protected. To achieve this, the Parties shall, unless agreed otherwise, rely on Switzerland- and/or EU- and/or UK- approved and then-current standard contractual clauses for the transfer of Personal Data or other transfer mechanisms as provided for by Data Protection Laws. Processor shall be authorized to perform such transfers to Subprocessors provided that adequate safeguards are implemented with regards to the nature of the transfer. 122 | 123 | ### 12. REPRESENTATION AND WARRANTIES 124 | 125 | Through engagement, payment for services, transmission of any documents, data, or information, receipt of services, and/or any other form of interaction with the AdGuard, the Company represents and warrants that: 126 | 127 | - the Company accept the Privacy Policy concerning the processing and safeguarding of personal data, as outlined and made available on the official website of the AdGuard, encompassing, but not limited to, granting consent for the processing of their own personal data and/or his employee, and/or representors, and/or End Users, etc.; 128 | - he has obtained all requisite consents and approvals in advance from the individuals and End Users whose personal data will be transferred to the AdGuard in the course of executing Service agreement and hereof. Notwithstanding of any other provisions of the Agreement, the Company shall be liable to the AdGuard and compensate for all losses associated with improper and/or careless fulfillment of obligations under the Agreement, which entail: 129 | - harm to life and/or health and/or reputation of the Company and/or third parties; 130 | - the obligation to pay penalties related to bringing the AdGuard to administrative and/or other public responsibility; 131 | - the obligation to compensate to third parties the losses and/or damages of illegal personal data processing, data breach and/or improper data processing. 132 | 133 | ### 13. FINAL PROVISIONS 134 | 135 | **Compliance with Applicable Laws.** Processor will process Company Personal Data in accordance with this Agreement and Data Protection Laws applicable to its role under this Agreement. Processor is not responsible nor liable for complying with Data Protection Laws solely applicable to Company by virtue of its business or industry. 136 | 137 | **Confidentiality.** Each party must keep any information it receives about the other party and its business in connection with this Agreement (“Confidential Information”) confidential and must not use or disclose that Confidential Information without the prior written consent of the other party except to the extent that: 138 | 139 | - disclosure is required by law; 140 | 141 | - the relevant information is already in the public domain through no fault of the Parties. 142 | 143 | **Notices.** All notices and communications given under this Agreement must be in writing and will be sent by email. Controller shall be notified by email sent to the address related to its use of the Services under the Service Agreement. Processor shall be notified by email sent to the address: [privacy@adguard.com](mailto:privacy@adguard.com). 144 | 145 | **Governing Law and Jurisdiction.** This Agreement shall be governed by Cyprus law, without regard to the choice or conflicts of law provisions of any jurisdiction to the contrary, and disputed, actions, claims or causes of action arising out of or in connection with this Agreement, an order form, any document incorporated by reference, AdGuard technology, or the Services shall be subject to the exclusive jurisdiction of Republic of Cyprus. 146 | 147 | **Changes.** We may change this Data Processing Agreement from time to time. Laws, regulations, and industry standards evolve, which may require these changes, or we may make changes to our business. We will post the changes on this page and encourage you to review our Data Processing Agreement to stay informed. If we make changes that materially alter your privacy rights, we will provide additional notice via email. If you disagree with the changes to this Data Processing Agreement, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 148 | -------------------------------------------------------------------------------- /adguard.com/extension-eula.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard Browser Extension End-User License Agreement 3 | 4 | *April 10, 2024* 5 | 6 | IMPORTANT: THIS SOFTWARE END-USER LICENSE AGREEMENT (“EULA” OR “AGREEMENT”) IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR, IF PURCHASED OR OTHERWISE ACQUIRED BY OR FOR AN ENTITY, AN ENTITY) AND ADGUARD SOFTWARE LIMITED (OWNER OF ALL RIGHTS, WHETHER EXCLUSIVE OR OTHERWISE TO THE SOFTWARE). READ IT CAREFULLY BEFORE COMPLETING THE INSTALLATION PROCESS AND USING SOFTWARE. 7 | 8 | BY INSTALLING THE SOFTWARE, OR BY USING THE SOFTWARE, OR BY PRESSING A BUTTON INDICATING YOUR ACCEPTANCE IN THE WINDOW CONTAINING THIS EULA, OR BY TYPING THE APPROPRIATE SYMBOL(S), YOU ARE CONFIRMING YOUR ACCEPTANCE OF THE SOFTWARE AND AGREEING TO BECOME BOUND BY TERMS OF THIS EULA. 9 | 10 | IF YOU DO NOT AGREE TO BE BOUND BY THIS EULA, THEN DO NOT DOWNLOAD, DO NOT INSTALL AND DO NOT USE THE SOFTWARE, AND/OR YOU MUST DELETE THE INSTALLED SOFTWARE. 11 | NOTE THAT THIS EULA REQUIRES THAT YOU AND ADGUARD SOFTWARE LIMITED SUBMIT ANY DISPUTE ARISING OUT OF THE INTERPRETATION OR APPLICATION OF THE TERMS OF THIS EULA OR ANY BREACH THEREOF TO ARBITRATION. 12 | 13 | AdGuard Software Limited may modify this EULA from time to time without prior notification. The amendment of EULA may be broadcasted to you by sending an email and/or by publishing the updated EULA on the AdGuard website. 14 | 15 | **The AdGuard Browser Extension, AdGuard for Safari and AdGuard Content Blocker are subject to dual licensing, making them accessible through both a commercial license and an open-source license, namely the GNU General Public License v3.0 (or later).** 16 | 17 | **If your project aligns with the GNU General Public License v3.0 license criteria, you are permitted to utilize the AdGuard Browser Extension, AdGuard for Safari and AdGuard Content Blocker under the provisions of the open-source license.** 18 | 19 | **For projects that do not meet these requirements, such as closed-source projects, adherence to the licensing terms outlined in the END-USER LICENSE AGREEMENT OF ADGUARD below is mandatory.** 20 | 21 | **The text of the GNU GPL-3 license is accessible in the project’s source code repository and also on the GNU Project website at [www.gnu.org/licenses/gpl-3.0.html](https://www.gnu.org/licenses/gpl-3.0.html).** 22 | 23 | ## 1. Definitions 24 | 25 | 1.1. “End User” (“You”, “Your”, “Yourself”) is a person who accepts this EULA and installs and uses the Software. If the Software is to be used by a company for its business purposes, the End User is such company; whereas the person accepting this EULA represents and warrants that the person is empowered to do so on behalf of the company; whereas the company means an entity of any type of ownership. 26 | 27 | 1.2. “Partner(s)” are persons and companies that are authorized by Rightholder to distribute the Software. 28 | 29 | 1.3. “Rightholder” (“we”, “us”, “our”) is ADGUARD SOFTWARE LIMITED, an entity organized and existing under the laws of the Republic of Cyprus. The Rightholder is the owner of all rights, exclusive or otherwise, to the Software. 30 | 31 | 1.4. “Software” is the ADGUARD software program, such as AdGuard Browser Extension, AdGuard for Safari, AdGuard Content Blocker, and corresponding documentation, associated media, printed materials, and online or electronic documentation, and all updates or upgrades of the above that are provided to You. 32 | 33 | 1.5. “Software Beta Application” is a version of the Software, so identified, to be used only to test the Software for a limited time period. The beta version of the Software may have limited features and will cease operating after a predetermined amount of time due to an internal mechanism within the Software. 34 | 35 | 1.6. “Third-party Software” are software modules, libraries and applications owned and/or licensed by third parties that are distributed with the Software and that may be part of the Software. 36 | 37 | 1.7. “Update(s)” are all upgrades, revisions, patches, enhancements, fixes, modifications, copies, additions or maintenance packs, etc., applicable to the Software that the Rightholder provides from time to time at its discretion. Any Update that You may receive from the Rightholder’s online services, or the Website and install is a part of the Software and all requirements, restrictions and terms of this EULA apply to any such Update. 38 | 39 | 1.8. “Website” is the website operated by the Rightholder (for example, [adguard.com](https://adguard.com)). 40 | 41 | ## 2. License grant 42 | 43 | 2.1. The Rightholder hereby grants You a non-exclusive free license to download, install and use the Software within the scope of the Software’s functionality described on the Website, provided that You comply with all requirements, restrictions and terms specified in this EULA. 44 | 45 | 2.2. In case You intend to install and use a Software Beta Application, the Rightholder hereby grants You a non-exclusive free license to use the Software Beta Application to test its functionality during the granted term of testing, provided that You participate in the Beta testing program of the Rightholder and comply with all rules of the Beta testing program and with all requirements, restrictions and terms specified in this EULA. You are not allowed to use the Software Beta Application for purposes other than those specified in this clause or after the expiry of the granted term of testing. 46 | 47 | 2.3. You are entitled to receive technical support via the Website and by contacting the Rightholder’s support team at [support@adguard.com](mailto:support@adguard.com) and to get Updates. 48 | 49 | ## 3. License restrictions 50 | 51 | 3.1. You may not make or distribute copies of the Software, or electronically transfer the Software from one computer to another or over a network. 52 | 53 | 3.2. You may not alter, merge, modify, or adapt the Software, or decompile, reverse engineer, disassemble, or otherwise reduce the Software to a human-perceivable form, except to the extent permitted by applicable law notwithstanding this restriction or to the extent otherwise expressly permitted by the Rightholder. 54 | 55 | 3.3. You may not sell, resell, rent, lease, or sublicense the Software. Only authorized Partners of the Rightholder are permitted to resell or sublicense the Software. 56 | 3.4. You may not modify the Software or create derivative works based upon the Software. 57 | 58 | 3.5. In the event that You fail to comply with this EULA, the Rightholder may terminate all licenses to the Software and You must destroy all copies of the Software. 59 | 60 | 3.6. Unless otherwise provided herein, You shall not when using the Software Beta Application 61 | 62 | (A) use the Software Beta Application for a purpose other than the sole purpose of testing the Software, 63 | 64 | (B) use the Software Beta Application if You do not participate in the Beta testing program of the Rightholder or if You violate the rules of the Beta testing program, 65 | 66 | (C) distribute, share, send, or make the Software Beta Application otherwise available to third parties without prior written consent of the Rightholder, or 67 | 68 | (D) breach the confidentiality of the Software Beta Application, its functions, features, characteristics, design, user interface, documentation, or other related materials by publishing, sharing, sending, disclosing, or otherwise making available to third parties without prior written consent of the Rightholder. 69 | 70 | 3.7. You shall not disclose, share, send, or make otherwise available to third parties information about vulnerabilities in the Software of which you become aware or discover, or use information about such vulnerabilities to compromise the security or privacy of other End Users, or otherwise violate the terms, conditions and restrictions of the Responsible Disclosure Program of the Rightholder available on the Website. 71 | 72 | 3.8. You may not remove or modify any proprietary notice or labels from the Software or any output of the Software, including author attribution and copyright notices. 73 | 74 | 3.9. You may not use the Software for any unauthorized or illegal purpose or activity under applicable international, national, and local laws in countries where the Software is used. 75 | 76 | 3.10. You may not download, install, use the Software if the country in which You reside has restricted or prohibited the use of the Software, or the country belongs to E.U. or U.S. embargoed countries, or if You are a person to which shipment of the Software is prohibited by the export control laws, rules, regulations, restrictions and national security controls of the European Union, the United States, and other applicable foreign agencies. 77 | 78 | ## 4. Use of blocking and filtering components 79 | 80 | 4.1. By using the Software, You acknowledge and agree to use filters that may be produced by the Rightholder or by third parties and utilized by blocking and filtering components of the Software solely at Your own will and risk, in accordance with the Rightholder’s Filter Policy available on the Website. 81 | 82 | 4.2. You are solely responsible for using filters utilized by blocking and filtering components of the Software, enabling, disabling, configuring, customizing of such filters, editing rules used in such filters. 83 | 84 | 4.3. If the Software is intended to be installed and run in a web browser application, You understand and agree that 85 | 86 | (A) results of operation of blocking and filtering components of the Software will apply only to the web browser application in which You installed the Software, and 87 | 88 | (B) the functionality of the Software, including operation of its blocking and filtering components, may be limited due to the characteristics and settings of the web browser application in which You installed the Software. 89 | 90 | To use the Software in other web browser applications, You may install the Software in those applications, or You may install AdGuard Ad Blocker, which provides enhanced blocking and filtering functionality: [adguard.com](https://adguard.com). 91 | 92 | 4.4. You are solely responsible for compliance with terms of use of websites You visit. 93 | 94 | 4.5. The Rightholder shall not be responsible and shall not be liable for Your compliance with terms of use of websites You visit when using the Software. 95 | 96 | ## 5. Privacy Policy and data processing 97 | 98 | 5.1. The Rightholder handles Your data in accordance with its Privacy Policy, which is amended from time to time and is available at [adguard.com/privacy.html](https://adguard.com/privacy.html). The Privacy Policy in effect at the time Your data is processed shall apply to how the Rightholder obtains, uses, and shares Your data. 99 | 100 | 5.2. Before using the Software, You acknowledge that You have read and understand our Privacy Policy. 101 | 102 | By installing and using the Software, You acknowledge that You agree to this EULA and terms and conditions of data processing by the Rightholder set out in our Privacy Policy available at the link mentioned above. 103 | 104 | 5.3. The Rightholder shall receive and process certain data to perform our obligations set forth in this EULA and to provide You with the functionality of the Software. Such data may be treated as personal data in accordance with the laws of certain territories and countries. You can read more about data processing in our Privacy Policy and in the Privacy Notice applicable for the Software or for a version of the Software designed for the operating system or platform or web browser application You are using. 105 | 106 | ## 6. WARRANTY DISCLAIMER 107 | 108 | 6.1. YOU EXPRESSLY AGREE THAT YOUR USE OF THE SOFTWARE IS AT YOUR SOLE RISK. THE SOFTWARE IS PROVIDED ON AN “AS IS” AND AN “AS AVAILABLE” BASIS. THE RIGHTHOLDER AND ITS SUPPLIERS AND PARTNERS DISCLAIM ALL WARRANTIES AND REPRESENTATIONS WITH REGARD TO THE SOFTWARE OR ANY PRODUCTS OR SERVICES PROVIDED UNDER THIS EULA, WHETHER EXPRESS, IMPLIED, OR OTHERWISE, INCLUDING THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, TITLE, AND QUIET ENJOYMENT. THE RIGHTHOLDER DOES NOT WARRANT THAT THE SOFTWARE IS ERROR-FREE OR WILL OPERATE WITHOUT INTERRUPTION. NO RIGHTS OR REMEDIES REFERRED TO IN ARTICLE 2 or ARTICLE 2A OF THE UNIFORM COMMERCIAL CODE (UCC), AS IMPLEMENTED IN ANY JURISDICTION, WILL BE CONFERRED ON YOU UNLESS EXPRESSLY GRANTED HEREIN. THE SOFTWARE IS NOT DESIGNED, INTENDED OR LICENSED FOR USE IN HAZARDOUS OR HIGH-RISK ENVIRONMENTS OR USE CASES REQUIRING FAIL-SAFE CONTROLS, INCLUDING WITHOUT LIMITATION, THE DESIGN, CONSTRUCTION, MAINTENANCE OR OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, AND LIFE SUPPORT OR WEAPONS SYSTEMS. THE RIGHTHOLDER SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH PURPOSES. 109 | 110 | 6.2. IF APPLICABLE LAW REQUIRES ANY WARRANTIES WITH RESPECT TO THE SOFTWARE OR ANY PRODUCTS OR SERVICES PROVIDED UNDER THIS EULA, ALL SUCH WARRANTIES ARE LIMITED IN DURATION TO SIXTY (60) DAYS FROM THE DATE OF DELIVERY OF SUCH SOFTWARE, PRODUCTS, OR SERVICES. 111 | 112 | 6.3. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY THE RIGHTHOLDER OR ITS PARTNERS, OR ITS OR THEIR AGENTS OR EMPLOYEES, SHALL CREATE A REPRESENTATION OR WARRANTY, NOR IN ANY WAY INCREASE THE SCOPE OF ANY EXPRESS REPRESENTATION OR WARRANTY PROVIDED HEREIN. 113 | 114 | 6.4. THE RIGHTHOLDER SHALL HAVE NO LIABILITY, AND YOU RELEASE THE RIGHTHOLDER OF ANY AND ALL LIABILITY, IF THE SOFTWARE HAS BEEN ALTERED IN ANY WAY, OR FOR ANY FAILURE THAT ARISES OUT OF USE OF THE SOFTWARE WITH OTHER THAN A RECOMMENDED HARDWARE CONFIGURATION, PLATFORM OR OPERATING SYSTEM. 115 | 116 | 6.5. THE RIGHTHOLDER IS NOT RESPONSIBLE FOR ANY THIRD-PARTY SOFTWARE INSTALLED BY YOU, INTENTIONALLY OR INADVERTENTLY, BY DOWNLOADING THE SOFTWARE FROM AN UNAUTHORIZED PARTY THAT IS NOT A RIGHTHOLDER PARTNER. 117 | 118 | 6.6. YOU ARE RESPONSIBLE FOR ENSURING THAT YOUR PARTICULAR USE OF THE SOFTWARE DOES NOT VIOLATE APPLICABLE LAW, THIRD-PARTY RIGHTS, OR YOUR CONTRACTUAL OBLIGATIONS TO THIRD PARTIES. 119 | 120 | ## 7. LIMITATION OF LIABILITY 121 | 122 | 7.1. TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER THE RIGHTHOLDER NOR ITS SUPPLIERS OR PARTNERS SHALL BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, COVER OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR THE INABILITY TO USE EQUIPMENT OR ACCESS DATA, LOSS OF DATA, LOSS OF BUSINESS, LOSS OF PROFITS, BUSINESS INTERRUPTION OR THE LIKE), ARISING OUT OF THE USE OF, OR INABILITY TO USE, THE SOFTWARE OR ANY PRODUCTS OR SERVICES PROVIDED UNDER THIS EULA WHETHER BASED ON ANY THEORY OF LIABILITY, INCLUDING BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF THE RIGHTHOLDER OR ITS SUPPLIERS OR PARTNERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. 123 | 124 | 7.2. THE FOREGOING LIMITATIONS ON LIABILITY ARE INTENDED TO APPLY TO ALL ASPECTS OF THIS EULA. 125 | 126 | ## 8. Licenses to Third-party Software 127 | 128 | You are granted a license (or sublicense) under the terms of the GNU General Public License (GPL) or other similar license to certain Third-party Software. Such licenses allow You to copy, modify, and redistribute the Third-party Software or part of it covered by such licenses, and to obtain its source code. If such licenses demand the provision of the source code of any Third-party Software, the Rightholder will provide You with the source code upon receipt of Your request at the Rightholder’s email address [support@adguard.com](mailto:support@adguard.com). If such licenses demand the provision of rights to use, copy or modify any Third-party Software that are greater than the rights granted herein, such rights will prevail over the rights and restrictions set forth herein. 129 | 130 | ## 9. Ownership 131 | 132 | This EULA gives You a limited license to use the Software. The Rightholder and its suppliers and Partners retain all right, title and interest, including all copyright and other intellectual property rights, in and to the Software and all copies thereof. All rights not specifically granted in this EULA, including federal and international copyrights, are reserved by the Rightholder, its suppliers and its Partners. 133 | 134 | ## 10. Term 135 | 136 | 10.1. You are entitled to use the Software under the license provided in clause 2.1 perpetually unless the license is terminated sooner as provided hereinbelow. 137 | 138 | 10.2. The Rightholder has the right to terminate the license provided in clause 2.1 at any time without notice to You. 139 | 140 | ## 11. General 141 | 142 | 11.1. **Applicable law, arbitration, and choice of venue.** This EULA will be governed by and construed in accordance with the laws of the Republic of Cyprus without reference to conflicts of law rules and principles. This EULA shall not be governed by the United Nations Convention on Contracts for the International Sale of Goods, the application of which is expressly excluded. Any dispute arising out of the interpretation or application of the terms of this EULA or any breach thereof shall, unless it is settled by direct negotiation, be adjudicated by arbitration in the Republic of Cyprus. Any award rendered by the arbitrator shall be final and binding on the parties and any judgment on such arbitration award may be enforced in any court of competent jurisdiction. Nothing in this Section 11 shall prevent a Party from seeking or obtaining equitable relief from a court of competent jurisdiction, whether before, during or after arbitration proceedings. 143 | 144 | 11.2. **Entire agreement and non-waiver.** This EULA contains the complete agreement between the parties with respect to the subject matter hereof and supersedes all prior or contemporaneous agreements or understandings, whether oral or written. You agree that any varying or additional terms contained in any purchase order or other written notification or document issued by You in relation to the Software licensed hereunder shall be of no effect. The failure or delay of the Rightholder to exercise any of its rights under this EULA or upon any breach of this EULA shall not be deemed a waiver of those rights or of the breach. 145 | 146 | 11.3. **Restriction on amendments.** No Rightholder Partner, or agent or employee of a Rightholder Partner, is authorized to make any amendment to this EULA. Any conflict or ambiguity between this EULA and any separate terms or conditions provided by a Rightholder Partner regarding the Software shall be resolved in favor of this EULA. 147 | 148 | 11.4. **Severability.** If any provision of this EULA shall be held by a court of competent jurisdiction to be contrary to law, that provision will be enforced to the maximum extent permissible, and the remaining provisions of this EULA will remain in full force and effect. 149 | 150 | 11.5. **No use where prohibited.** Use of the Software is unauthorized in any jurisdiction that does not give effect to all provisions of this EULA. 151 | 152 | 11.6. **Assignment.** You may not assign, by operation of law or otherwise, any rights or delegate any duties under the EULA to any third party without prior written consent by the Rightholder. Any purported assignment lacking such consent will be void at its inception. The Rightholder may assign all or part of its rights and/or delegate all or part of its duties under the EULA to any party, at any time, and in its sole discretion, upon notice of assignment by publishing such notice on its website. 153 | 154 | ## 12. Period for bringing actions 155 | 156 | No action, regardless of form, arising out of the transactions under this EULA, may be brought by either party hereto more than one (1) year after the cause of action has accrued, except that an action for infringement of intellectual property rights may be brought within the maximum applicable statutory period. 157 | 158 | ## 13. Contact Information 159 | 160 | Should You have any questions concerning this EULA, or if You desire to contact the Rightholder for any reason, please contact us: 161 | 162 | Email: [support@adguard.com](mailto:support@adguard.com) 163 | Website: [adguard.com](https://adguard.com) 164 | 165 | © ADGUARD SOFTWARE LIMITED. All Rights Reserved. The Software and any accompanying documentation are copyrighted and protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. 166 | -------------------------------------------------------------------------------- /adguard.com/privacy.html.md: -------------------------------------------------------------------------------- 1 | # AdGuard Privacy Policy 2 | 3 | *August 7, 2024* 4 | 5 | ## Summary 6 | 7 | We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 8 | 9 | 1. We collect only the information necessary for our products and services to function properly. 10 | 1. AdGuard apps filter traffic locally on your device. We don’t know what websites you visit. 11 | 1. AdGuard apps periodically connect to our servers to download filter updates and check your license status. 12 | 1. You are not required to share your personal data with us. You can delete your information by deleting your AdGuard account at [adguardaccount.com](https://adguardaccount.com) or by sending us a request at [privacy@adguard.com](mailto:privacy@adguard.com). 13 | 14 | ## Who we are 15 | 16 | ADGUARD SOFTWARE LIMITED (“We”, “Our” or “Us”) collects and processes your data in accordance with this Privacy Policy and in compliance with the applicable data protection laws. This Policy provides you with the necessary information regarding your rights and our obligations, and explains how, why, and when we process your Personal Data. Our general principle is to collect only the information that is necessary to provide you with the full functionality of our products and services. We strictly follow the principle of “minimization” when processing your data. 17 | 18 | ADGUARD SOFTWARE LIMITED is a company registered in Limassol, Cyprus, at Anexartisias and Athinon 79, Nora Court Flat/Office 203–205, 3040. ADGUARD SOFTWARE LIMITED acts as the data controller when processing your data. 19 | 20 | If you have any questions about this Privacy Policy or if you want to exercise any of your rights, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 21 | 22 | Please read this Privacy Policy thoroughly. 23 | 24 | If you do not agree with our policies and practices described in this Privacy Policy, please do not use our software and services, do not visit our website, and do not provide your information to us. 25 | 26 | ## How we collect personal data 27 | 28 | There are several ways how we may get your Personal Data: 29 | 30 | - When you visit our website adguard.com and its subdomains (“Website”). For more information about what data is collected, how it is collected, and how you can manage it, please see the Privacy Policy of AdGuard Websites at [adguard.com/website-privacy.html](https://adguard.com/website-privacy.html). 31 | - When you use our products. You can find the full list of Personal Data collected on a privacy notice page dedicated to the product you use. 32 | 33 | ## What data we process 34 | 35 | We process different data depending on the situation. You can learn details about what data we process in this section. 36 | 37 | Some data that we receive and process may be treated as personal data (“Personal Data”) in accordance with the laws of certain territories and countries. When we use terms “personal data” or “personal information”, we mean any information relating to an identified or identifiable natural person, excluding any anonymized and depersonalized data where your identity is absent or has been removed and cannot be recovered. 38 | 39 | Data we process includes no more than is crucial to provide full functionality of AdGuard products, websites, and services. We do not process anything for tracking purposes and take all necessary technical, administrative, and physical measures to protect the information we get. 40 | 41 | ### When you are using our website 42 | 43 | **Account registration**. We process your email address and a hash of the password which you provide to us at the registration. That ensures that you can retrieve your password if needed. 44 | 45 | **Sending messages**. We can use your email address to make announcements, inform you of updates and new features in our software or services, provide you with advice, or to communicate with you when reporting errors. 46 | 47 | You can also provide us with your consent to process your email for sending marketing messages about our other software or services. You can withdraw your consent any time by unsubscribing from our newsletters via AdGuard Account or by clicking the “Unsubscribe” button or link in the newsletter itself. 48 | 49 | **Cookies**. We use our cookies to personalize the content of the Website, such as setting the default language. None of the information we may acquire through the use of cookies is considered Personal Data as it does not allow us to identify you. You can always disable cookies in your web browsing software or clear existing cookies, but please note that some of our services may not function properly without the use of cookies. Please refer to the [Privacy Policy of AdGuard Websites](https://adguard.com/website-privacy.html) for details. 50 | 51 | **Buying a license**. If you purchase a license for AdGuard software, we’ll use the email address you provide to send you information about your purchase. We’ll also use your email address to create an account for you. This account will allow you to manage your purchased license. 52 | 53 | We conduct all transactions via [Paddle.com Market Ltd.](https://www.paddle.com) and [PayPro Global, Inc.](https://payproglobal.com) to enable payments if you purchase a subscription to use our software and services. 54 | The data processed depends on the payment provider and may include the following: 55 | 56 | - Email address 57 | - Country of residence 58 | - Zip or postal code 59 | - (If you use a bank card to make a purchase) Number, name, expiration date, and the security code associated with the bank card 60 | 61 | For the exact data that the payment provider collects about you, please see the corresponding privacy policy: [Paddle’s Privacy Policy](https://www.paddle.com/legal/privacy), [PayPro Global’s Privacy Policy](https://docs.payproglobal.com/documents/legal/privacyPolicy.pdf). 62 | 63 | ### When you are using our software 64 | 65 | **Sign-in / Account registration**. When signing in to connect the installed app to your account or registering a new account, you need to provide your email address and create a password. We process this essential data to provide you with the functionality of our software. 66 | 67 | **Using our software**. When you choose to use our app, you provide us your data, including Personal Data. This information, which we must process to ensure the full functionality of the AdGuard software, depends on the operating system for which the software is designed and is listed as follows: 68 | 69 | - For AdGuard for Windows: [adguard.com/privacy/windows.html](https://adguard.com/privacy/windows.html) 70 | - For AdGuard for Android: [adguard.com/privacy/android.html](https://adguard.com/privacy/android.html) 71 | - For AdGuard for Mac: [adguard.com/privacy/mac.html](https://adguard.com/privacy/mac.html) 72 | - For AdGuard for iOS: [adguard.com/privacy/ios.html](https://adguard.com/privacy/ios.html) 73 | - For AdGuard Browser Extension: [adguard.com/privacy/browser-extension.html](https://adguard.com/privacy/browser-extension.html) 74 | - For AdGuard for Safari: [adguard.com/privacy/safari.html](https://adguard.com/privacy/safari.html) 75 | - For AdGuard Browser Assistant: [adguard.com/privacy/assistant.html](https://adguard.com/privacy/assistant.html) 76 | - For AdGuard Content Blocker: [adguard.com/privacy/content-blocker.html](https://adguard.com/privacy/content-blocker.html) 77 | - For AdGuard Home: [adguard.com/privacy/home.html](https://adguard.com/privacy/home.html) 78 | 79 | **Diagnostic / Device information**. By default, we do not collect any information about your device. However, if you experience problems using our software and you give us your consent, we will collect and process some diagnostic information for crash reports and some information about the device used to run our software in order to help you. The exact information we collect and process depends on the AdGuard software you are using. Please refer to the respective privacy notices for more information. 80 | 81 | Some files, such as trace logs and dump files, can only be created by you: please follow instructions on the Website or from our support team, and send the generated files to us by email. By sending us the files, you provide us with your consent to process the files and data for the purpose of providing technical support. 82 | 83 | ## What legal bases we use to process your Personal Data 84 | 85 | We use different legal bases to process Personal Data depending on the type of data, the purposes, and circumstances of processing. 86 | 87 | **Consent**. We process your Personal Data if you have provided us with your consent to use your Personal Data for certain purposes. For example, to send you marketing messages or to help you troubleshoot problems with using our software. You can withdraw your consent at any time without affecting your use of our software. 88 | 89 | **Performance of a contract**. We process your Personal Data when it is necessary to fulfill our contractual obligations to you, including providing the functionality of our software and services or at your request prior to entering into a contract with you. 90 | 91 | **Legal obligations**. We process your Personal Data where it is necessary for compliance with our legal obligations, such as to exercise or defend our legal rights, or for taxation purposes. 92 | 93 | **Legitimate interest**. We process your Personal Data when we pursue our legitimate interests, except where such interests are overridden by the interests or fundamental rights and freedoms of data subjects. 94 | 95 | ## Where we process your Personal Data 96 | 97 | We store your Personal Data in our own data center located in Frankfurt, Germany. Your Personal Data may be processed by our employees, who can only access your data through their job duties on a need-to-know basis. If you have questions or would like to know from which countries your Personal Data may be accessed, you can write to us at [privacy@adguard.com](mailto:privacy@adguard.com). 98 | 99 | For data transfers to other countries, we always implement appropriate safeguards to ensure that your Personal Data always remains safe and that your rights are respected: 100 | 101 | - The country or the third party is recognized as providing adequate protection. 102 | - A valid transfer mechanism is used, such as the Standard Contractual Clauses, and supplementary measures are implemented where necessary. 103 | - The transfer has your explicit consent. 104 | - The transfer is necessary for the performance of a contract with you or to take steps requested by you prior to entering into that contract. 105 | 106 | If you would like a copy of the Standard Contractual Clauses used, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 107 | To determine if a non-EU country has an adequate level of data protection, please visit [the European Commission website](https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en). 108 | 109 | ## How we use your Personal Data 110 | 111 | Your privacy is our highest priority. We take it very seriously and will never disclose, share, or sell your data unless we have your consent or are required to do so by law. The only purpose of collecting and storing your Personal Data is to provide you with our products and services at their full potential. 112 | 113 | ### Retaining your data 114 | 115 | We retain Personal Data for as long as necessary to provide you with these products and services, or until you withdraw your consent to share this information. 116 | 117 | ### Your rights 118 | 119 | In some countries and regions, you may have certain rights in relation to your Personal Data under applicable data protection laws. 120 | 121 | If you wish to exercise your rights with respect to your Personal Data, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). We will consider and act upon any request in accordance with applicable data protection laws. We may ask you to further confirm your identity and will respond to you within the time period specified by applicable data protection law. Please note that in certain cases stipulated by applicable data protection law, we may charge you a reasonable fee for processing your request or refuse your request. 122 | 123 | You are entitled to exercise the following rights in relation to your Personal Data: 124 | 125 | **Right of access**: The right to obtain all your Personal Data we store. In some cases, the right of access may be limited for technical reasons, including if the data has been anonymized and cannot be linked to any data subject. 126 | 127 | **Right to erasure or right to be forgotten**: The right to completely delete your Personal Data. You can do this at will in your AdGuard account or by sending a request to [privacy@adguard.com](mailto:privacy@adguard.com). 128 | 129 | **Right to rectification**: The right to correct any incomplete or inaccurate Personal Data about you. We will do so as quickly as possible, unless there is a valid reason not to, in which case you will be notified. 130 | 131 | **Right to restriction**: The right to impose restrictions on processing of your Personal Data. 132 | 133 | **Right to object**: The right to object to processing of your Personal Data. 134 | 135 | **Right to data portability**: The right to receive provided Personal Data in a structured, commonly used, and machine-readable format and to transmit that data to another controller. You can export all Personal Data that we hold about you to a local file from your AdGuard account at [adguardaccount.com](https://adguardaccount.com). 136 | 137 | **Right not to be subject to a decision based solely on automated processing**, including profiling. 138 | 139 | **Right to withdraw a consent** where the data processing is based on the consent. 140 | 141 | **Right to lodge a complaint** with a data protection authority. You can find contact details of our data protection authorities at [www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument](https://www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument). 142 | 143 | When we receive your Personal Data from a third party, we will use reasonable efforts to inform you about it. 144 | 145 | ### Safeguarding measures 146 | 147 | We make every possible effort to protect you and your Personal Data from unauthorized access, alteration, disclosure, or destruction. We implement and maintain the following technical and security measures: 148 | 149 | **System access controls**: We take reasonable measures to prevent Personal Data from being used without authorization. These controls shall vary based on the nature of the processing undertaken and may include, among other controls, authentication via passwords and/or two-factor authentication, documented authorization processes, documented change management processes and/or logging of access on several levels. 150 | 151 | **Data access controls**: We take reasonable measures to ensure that Personal Data is accessible and manageable only by properly authorized staff. Direct database query access is restricted and application access rights are established and enforced to ensure that persons entitled to use a data processing system only have access to the Personal Data to which they have privilege of access; and that Personal Data cannot be read, copied, modified or removed without authorization in the course of processing. 152 | 153 | **Storing data in a data center**: Personal information is stored in our own data center located in Frankfurt. This is secure: the data center does not demand that we collect any data about your traffic or your use of our products and services. If they request us to start doing so, we will stop working with this provider and find an alternative. 154 | 155 | **Transmission controls**: We take reasonable measures to ensure that it is possible to check and establish to which entities the transfer of Personal Data by means of data transmission facilities is envisaged so Personal Data cannot be read, copied, modified or removed without authorization during electronic transmission or transport. 156 | 157 | **Input controls**: We take reasonable measures to make it possible to check and establish whether and by whom Personal Data has been entered into data processing systems, modified or removed. 158 | 159 | **Data backup**: Back-ups of the databases are made on a regular basis, are secured, and encrypted to ensure that Personal Data is protected against accidental destruction or loss when hosted by us. 160 | 161 | **Logical separation**: Personal Data is logically segregated on our systems to ensure that Personal Data that is collected for different purposes can be processed separately. 162 | 163 | ### Consequences of not providing your Personal Data 164 | 165 | You are not obligated to provide your Personal Data to us. However, as this information is required for us to provide you with our services or respond to your requests, we will not be able to offer some or all our services without it. 166 | 167 | ### Age limitations 168 | 169 | To the extent not prohibited by applicable law, we do not allow the use of our services, products, and Website by persons under the age of 16. If you learn that someone under the age of 16 has unlawfully provided us with Personal Data, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). We will take steps to delete that information. 170 | 171 | ## How we use cookies 172 | 173 | The definition of cookies and how we use them is explained in detail in the dedicated section of our Privacy Policy. For details, please see the Privacy Policy of AdGuard Websites at [adguard.com/website-privacy.html](https://adguard.com/website-privacy.html). 174 | 175 | ## Changes to this Privacy Policy 176 | 177 | We may change this Privacy Policy from time to time. Laws, regulations, and industry standards evolve, which may require these changes, or we may make changes to our business. We will post the changes on this page and encourage you to review our Privacy Policy to stay informed. If we make changes that materially alter your privacy rights, we will provide additional notice via email. If you disagree with the changes to this Privacy Policy, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 178 | -------------------------------------------------------------------------------- /adguard.com/privacy/android.html.md: -------------------------------------------------------------------------------- 1 | # AdGuard for Android Privacy Notice 2 | 3 | *May 28, 2025* 4 | 5 | --- 6 | 7 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 8 | 9 | --- 10 | 11 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 12 | 13 | ## What data AdGuard for Android can collect and when 14 | 15 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 16 | 17 | ### Registration of a new user 18 | 19 | When we create an AdGuard account for the user, the following information is sent to our servers: 20 | 21 | - Email 22 | - Password 23 | - App identifier 24 | 25 | **Why we need this information:** We need your email address because this is the login of your AdGuard account. We use the app identifier to control the simultaneous use of multiple applications. 26 | 27 | ### User authorization 28 | 29 | Users have the option to activate the license by logging into their personal account in the app. The following information is sent to our servers: 30 | 31 | - Login (email address) 32 | - Password 33 | 34 | Upon authorization, the app receives an active license for that account from the server. 35 | 36 | ### License status check 37 | 38 | To validate the license status, AdGuard connects to its servers. When it happens, the following information is sent: 39 | 40 | - App identifier 41 | - App version 42 | - Device name (used in the AdGuard account so that the user can see the list of devices activated with their license keys) 43 | - License key 44 | - App language 45 | - Build identifier 46 | - User consent to send crash reports 47 | - User consent to send telemetry data 48 | 49 | **Why we need this information:** 50 | 51 | We use this data primarily to verify the license status and to bind the license to the device, ensuring that your license keys are properly associated with your activated devices. This information also allows us to display your license keys and device list in your AdGuard account. 52 | 53 | If you have consented to send crash reports and telemetry data, we collect this information to help us identify and fix issues within the app, improve its stability, and enhance overall performance and user experience. Collecting crash reports enables us to detect unexpected errors, while telemetry data provides insights into how the app is used, allowing us to optimize features and address potential problems proactively. 54 | 55 | If you activate the full version of the app using your AdGuard account credentials, the app sends your login and password to authenticate your identity securely. 56 | 57 | ### License reset 58 | 59 | The license is reset upon user request. When it happens, the app identifier is sent. 60 | 61 | **Why we need this information:** In order to know which app to do the license reset for. 62 | 63 | ### Trial period request 64 | 65 | When a user requests the trial period, the following information is sent to our server for activation: 66 | 67 | - App identifier 68 | - User’s email address 69 | - App language 70 | - Marketing consent flag indicating whether user has consented to receive marketing emails 71 | - Build identifier 72 | - App installation channel 73 | 74 | **Why we need this information:** 75 | 76 | - To know which device is requesting the trial features 77 | - To notify the user of their trial period. Activation instructions and other trial materials will be sent to the email address provided 78 | - To know if the user was referred by an AdGuard affiliate, and if so, which affiliate 79 | - To learn the source of AdGuard installation 80 | 81 | ### App updates check 82 | 83 | To check for app updates, AdGuard connects to its servers. When it happens, the following information is sent: 84 | 85 | - App identifier 86 | - App version 87 | - App language 88 | - SDK (OS version of the device) 89 | - Update channel 90 | 91 | Update checks are performed periodically or when prompted by the user. We do not store or use this data in the future, but we aggregate it in an anonymous form to count the total number of AdGuard products installed. 92 | 93 | ### Checking for filter updates 94 | 95 | To check for updates of blocking filters, AdGuard connects to its servers. When it happens, no information is sent. The application periodically downloads a file with all filter versions and their available updates. 96 | When updating custom filters, we access the resources specified by the user when adding the custom filter. 97 | 98 | ### Userscripts 99 | 100 | When updating userscripts, we first check for a new version and then download the update. Pre-installed userscripts are stored on our servers. We also access the resources specified by the user when adding the userscripts. 101 | 102 | ### Sending a web page complaint 103 | 104 | The user can submit a report of a website problem directly from the app. The app will automatically open [reports.adguard.com](reports.adguard.com/new_issue.html) and forward some information about its configuration. The user can then alter or delete it. 105 | 106 | Unless the user agrees to submit this information by clicking *Next*, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/AdguardTeam/AdguardFilters/issues). 107 | 108 | ### Sending a message to support 109 | 110 | Users can send messages to support directly from the app. In that case, the following information will be sent along with the message and the email address provided: 111 | 112 | - App identifier 113 | - App version 114 | - Device name (which includes both device manufacturer name and device model name) 115 | - Android version 116 | - Android kernel version 117 | - List of enabled filters 118 | - App configuration 119 | 120 | If *Send app logs and system info* is enabled, the program will also send additional information: 121 | 122 | - List of app threads and their stack traces 123 | - Log file contents 124 | - List of installed apps 125 | 126 | This detailed information is used by the support team to help solve more complicated problems. 127 | 128 | ### Automatic crash reports 129 | 130 | The first time the app is launched, users are asked if they want to allow AdGuard to send automatic crash reports. If they do (and only if they do), the following information will be sent to our servers when the app crashes: 131 | 132 | - Device name and model 133 | - OS version and kernel build 134 | - ROOT status 135 | - Unidentifiable Android ID 136 | - Amounts of total and free RAM 137 | - Screen orientation 138 | - Screen resolution and density 139 | - App name and version 140 | - Information related to the crash (error message and stack trace) 141 | - The last lines of the log file 142 | 143 | **Why we need this information:** To troubleshoot critical issues. It keeps us aware of new problems not reported by users. 144 | 145 | Crash report data is stored only on our servers. We do not use any third party services to collect and store crash reports. All crash reports are stored for 30 days. 146 | 147 | ### Technical and interaction data 148 | 149 | The first time the app is launched, users are asked if they want to allow AdGuard to send technical and interaction data. If they do, the following information is sent: 150 | 151 | - App version 152 | - App language 153 | - App theme 154 | - App configuration (enabled features and activation status) 155 | - Names of the screens, dialogs, and toasts viewed inside the app 156 | - User clicks on app elements 157 | - Time since the app was first used 158 | - Device information (type, screen size, language, platform, and OS version) 159 | - User agent (device brand and model, name, version, and system architecture) 160 | - Unique generated identifier 161 | - Authorization status 162 | - Kill Switch status 163 | - License status and expiration date 164 | 165 | When the data is sent to AdGuard, your IP address may be temporarily collected as part of our server logs. 166 | 167 | This data is used only internally and is not shared with third parties. 168 | 169 | **Why we need this information:** 170 | 171 | - To find out which features are used the most 172 | - To find issues that one may face while using the app 173 | - To fix mistakes in the UI/UX 174 | - To learn what people like or don’t like about our app 175 | 176 | ### Browsing Security website check 177 | 178 | If *Browsing Security* is enabled, AdGuard will check each website before the user visits it. We use the [Safe Browsing API](https://adguard.com/kb/general/browsing-security/) for this purpose, and the information about the visited website is sent in the form of hash prefixes. This doesn’t allow us to determine which website is being visited. In addition, we periodically pull database updates from our servers. 179 | 180 | The information described above, when collected by AdGuard for Android, is generally not correlated with any other personal information and is used anonymously aggregated with similar information from other users of the AdGuard software for analytical purposes. 181 | -------------------------------------------------------------------------------- /adguard.com/privacy/browser-assistant.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard Browser Assistant Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | --- 7 | 8 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | --- 11 | 12 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.htm](https://adguard.com/privacy.htm), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 13 | 14 | ## What data AdGuard Browser Assistant can collect and when 15 | 16 | AdGuard Browser Assistant is a companion add-on that extends the functionality of our standalone desktop apps. It does not collect any information by itself, but it communicates with the standalone apps. To find out what data AdGuard Ad Blocker collects, please refer to the respective Privacy Notices for [AdGuard for Mac](https://adguard.com/privacy/mac.html) and [AdGuard for Windows](https://adguard.com/privacy/windows.html). 17 | 18 | ### Launching for the first time 19 | 20 | When AdGuard Browser Assistant is first launched, the following information is sent to the standalone app: 21 | 22 | - User-Agent 23 | 24 | - Version 25 | 26 | ### Current page state 27 | 28 | Every time a user opens a new tab, the add-on communicates with the standalone app and requests information about the current page status. To do this, it sends the URL of the current page to the standalone app. 29 | 30 | ### Sending a web page complaint 31 | 32 | The user can submit a report of a website problem directly from AdGuard Browser Assistant. The app will automatically open the [reports.adguard.com](https://reports.adguard.com/new_issue.html) web page and forward some information about its configuration. The user can then alter or delete it. 33 | Unless the user agrees to submit this information by manually clicking the “Submit” button, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/adguardteam/adguardfilters/issues). 34 | -------------------------------------------------------------------------------- /adguard.com/privacy/content-blocker.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard Content Blocker Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | --- 7 | 8 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | --- 11 | 12 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 13 | 14 | ## What data AdGuard Content Blocker can collect and when 15 | 16 | ### Checking for filter updates 17 | 18 | To check for filter updates, AdGuard connects to its servers. When it happens, no information is sent. 19 | 20 | Filter updates are checked at user-defined intervals in accordance with the application’s settings. We do not store this data, but we do aggregate it in an anonymous form to count the total number of active users. 21 | -------------------------------------------------------------------------------- /adguard.com/privacy/extension.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard Browser Extension Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | This Privacy Notice lists all the information that we, Adguard Software Ltd. (“we”, “us”, or “our”), may collect when you use AdGuard Browser Extension and explains why we do it and how we use this information. 7 | 8 | --- 9 | 10 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 11 | 12 | --- 13 | 14 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 15 | 16 | ## What data AdGuard Browser Extension can collect and when 17 | 18 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 19 | 20 | ### Checking for filter updates 21 | 22 | To check for filter updates, AdGuard connects to its servers. When it happens, the following information is sent: 23 | 24 | - Browser language 25 | 26 | - App identifier 27 | 28 | - Extension version 29 | 30 | Filter updates are checked at user-defined intervals in accordance with the application’s settings. We do not store this data, but we do aggregate it in an anonymous form to count the total number of active users. 31 | 32 | ### ​​Help with the development of AdGuard filters 33 | 34 | The “Help with the development of AdGuard filters” option is **disabled by default**. Nothing will be sent unless the user manually enables it to help us improve our blocking filters. [This Knowledge base article](https://adguard.com/kb/general/ad-filtering/tracking-filter-statistics/) explains how enabling this option helps us. 35 | 36 | If the “Send statistics for ad filters usage” option is enabled, the following information is sent periodically: 37 | 38 | - Filter list ID 39 | 40 | - Rule text 41 | 42 | - How many times the rule was triggered 43 | 44 | **Why do we need this information:** We automatically optimize filters and remove rules that are rarely used. To do this, we collect information about which rules are triggered. 45 | 46 | ### Sending a web page complaint 47 | 48 | The user can submit a report of a website problem directly from the extension. The extension will automatically open the [reports.adguard.com](https://reports.adguard.com/new_issue.html) web page and forward some information about its configuration. The user can then alter or delete it. 49 | Unless the user agrees to submit this information by manually clicking the “Submit” button, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/adguardteam/adguardfilters/issues). 50 | 51 | ### Browsing Security website check 52 | 53 | If the “Phishing and malware protection” option is enabled, AdGuard checks every website before the user visits it. We use the [Safe Browsing API](https://adguard.com/kb/general/browsing-security/) for this purpose, and the information about visited websites is sent in the form of hash prefixes. This doesn’t allow us to determine which website is being visited. 54 | -------------------------------------------------------------------------------- /adguard.com/privacy/home.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard Home Privacy Notice 3 | 4 | *February 10, 2025* 5 | 6 | --- 7 | 8 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | --- 11 | 12 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 13 | 14 | ## What data AdGuard Home can collect and when 15 | 16 | AdGuard Home logs and DNS query logs that it processes are stored on the device where AdGuard Home is running. They and their retention are managed by the user. 17 | 18 | AdGuard Home itself does not send anything to us and all cases when it connects to any servers are related to its functionality. These cases are described below. 19 | 20 | ### Processing DNS queries 21 | 22 | AdGuard Home connects to the DNS servers configured as “Upstreams” and sends DNS queries to them. 23 | 24 | ### Checking for updates 25 | 26 | AdGuard Home periodically downloads a .json file to check if there’s a newer version. No information is sent when this happens. 27 | 28 | ### Checking for filter updates 29 | 30 | To check for updates for enabled filters, AdGuard Home connects to their respective servers. When this happens, nothing is sent to these servers. AdGuard Home periodically downloads a file containing all filter versions and their available updates. 31 | 32 | ### Browsing Security domain check (disabled by default) 33 | 34 | For each requested domain, AdGuard Home connects to the Browsing Security server and passes a 4-character prefix of the domain name’s SHA256 hash. The server responds with a list of full hashes and AdGuard Home checks if there’s a match. The sent prefixes are not stored and do not reveal any personal information. 35 | 36 | ### Parental Control domain check (disabled by default) 37 | 38 | For each requested domain, AdGuard Home connects to the Parental Control web service and passes a 4-character prefix of the domain name’s SHA256 hash. The service responds with a list of full hashes and AdGuard Home checks if there’s a match. The sent prefixes are not stored and do not reveal any personal information. 39 | -------------------------------------------------------------------------------- /adguard.com/privacy/ios.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard for iOS Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | --- 7 | 8 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. The information we collect includes no more than is crucial to provide the full functionality of AdGuard products. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | --- 11 | 12 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 13 | 14 | Please note that AdGuard for iOS and AdGuard Pro are nearly identical in functionality and user data processing. However, AdGuard for iOS offers the possibility to log in with your AdGuard account, whereas AdGuard Pro does not. This is reflected in several points of this Privacy Notice. 15 | If you are wondering why we have two almost identical apps, [check out this article](https://adguard.com/en/blog/updating-adguard-pro-for-ios.html). 16 | 17 | ## What data AdGuard for iOS and AdGuard Pro can collect and when 18 | 19 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 20 | 21 | ### Local VPN filtering 22 | 23 | To implement DNS filtering, AdGuard creates a local VPN connection. This means that there is no remote connection to any server and this is only a technical means of filtering DNS traffic. When creating a local VPN connection, no personal and identifying information is collected or sent to our servers. 24 | 25 | ### Checking for filter updates 26 | 27 | To check for filter updates, the app connects to its servers. When it happens, the following information is sent: 28 | 29 | - App language 30 | 31 | - App identifier 32 | 33 | Filter updates are checked at user-defined intervals in accordance with the application’s settings. We do not store the obtained data, but we do aggregate update requests in order to determine the total number of active users. 34 | 35 | ### Leave feedback 36 | 37 | Users can report bugs by clicking the “Send bug report” button in the app menu. When this happens, the following information is sent along with the message text and the entered email: 38 | 39 | - App identifier 40 | 41 | - App settings (language and enabled blocking filters) 42 | 43 | - App and OS versions 44 | 45 | - Device model 46 | 47 | If the “Attach application logs” option is enabled, the following information is sent along with the above information: 48 | 49 | - Log file contents 50 | 51 | - `.json` files containing rules for Safari 52 | 53 | **Why do we need this information:** This information is used by our team to diagnose and troubleshoot the problem. 54 | 55 | ### Sending a web page complaint 56 | 57 | The user can submit a report of a website problem directly from the app. The apps will automatically open the [reports.adguard.com](https://reports.adguard.com/new_issue.html) web page and forward some information about its configuration. The user can then alter or delete it. 58 | Unless the user agrees to submit this information by manually clicking the “Submit” button, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/adguardteam/adguardfilters/issues). 59 | 60 | ### Logging in to AdGuard account (only AdGuard for iOS) 61 | 62 | AdGuard for iOS users can use this option to activate features of the full version of the app. When you log in to AdGuard account via the app, the following information is sent: 63 | 64 | - Entered login/password pair or license key 65 | 66 | - App identifier 67 | 68 | - App version 69 | 70 | - Device type (iPhone X, iPad Pro, etc.) 71 | 72 | **Why we need this information:** To confirm the fact of the user’s login and to verify the user’s license. The login and app activation details are also displayed in the AdGuard account. 73 | 74 | ### Logging out of AdGuard account (only AdGuard for iOS) 75 | 76 | The following information is sent to our servers when you log out of your account via the app: 77 | 78 | - App identifier 79 | 80 | - App version 81 | -------------------------------------------------------------------------------- /adguard.com/privacy/mac.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard for Mac Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | --- 7 | 8 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | --- 11 | 12 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 13 | 14 | ## What data AdGuard for Mac can collect and when 15 | 16 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 17 | 18 | ### User authorization 19 | 20 | Users have the option to activate the license by logging into their personal account in the app. The following information is sent to our servers: 21 | 22 | - Login (email address) 23 | - Password 24 | 25 | Upon authorization, the app receives an active license for that account from the server. 26 | 27 | ### License status check 28 | 29 | To validate the license status, AdGuard connects to its servers. When it happens, the following information is sent: 30 | 31 | - Computer name 32 | 33 | - MAC address hash 34 | 35 | - Hardware ID hash 36 | 37 | - OS language 38 | 39 | - App identifier 40 | 41 | - App version 42 | 43 | - License key 44 | 45 | - Build identifier 46 | 47 | **Why we need this information:** We use this information to check the license status and display the user’s license keys in the AdGuard account. MAC and hardware ID hashes are also used to tie the license to the computer. 48 | 49 | ### License reset 50 | 51 | The license is reset upon user request. When it happens, the app identifier is sent. 52 | 53 | **Why we need this information:** In order to know which app to do the license reset for. 54 | 55 | ### Checking for program updates 56 | 57 | To check for app updates, AdGuard connects to its servers. When it happens, the following information is sent: 58 | 59 | - App identifier 60 | 61 | - Update channel 62 | 63 | - App name 64 | 65 | - App version 66 | 67 | - App language 68 | 69 | - Automatic update flag 70 | 71 | - OS version 72 | 73 | **Why we need this information:** This data is sent to our servers in order to return a correct response about what updates are available for the current version of the application. 74 | 75 | Updates checks are performed periodically or when prompted by the user. We do not store and use this data in future 76 | 77 | ### Checking for filter updates 78 | 79 | To check for filter updates, AdGuard connects to its servers. When it happens, nothing is being sent to our server. The application periodically downloads a file with all filter versions and their available updates. 80 | 81 | ### Trial period activation 82 | 83 | When a user activates the trial period, the following information is sent to our server: 84 | 85 | - Computer name 86 | 87 | - MAC address hash 88 | 89 | - Hardware ID hash 90 | 91 | - OS language 92 | 93 | - App identifier 94 | 95 | - App version 96 | 97 | - Build identifier 98 | 99 | **Why we need this information:** To keep track of when the app’s trial period expires. 100 | 101 | ### Sending a web page complaint 102 | 103 | The user can submit a report of a website problem directly from the app. The app will automatically open the [reports.adguard.com](https://reports.adguard.com/new_issue.html) web page and forward some information about its configuration. The user can then alter or delete it. 104 | Unless the user agrees to submit this information by manually clicking the “Submit” button, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/adguardteam/adguardfilters/issues). 105 | 106 | ### Sending a message to support 107 | 108 | Users can send messages to support right from the app. If they do, a special file containing some information about app settings and OS configuration will be sent. This data is often required to solve potential problems with the AdGuard app. Users also have an option to include a diagnostic report that contains additional information. Nothing will be sent unless the user manually confirms the submission. 109 | The following information is included in this report: 110 | 111 | - App identifier 112 | 113 | - App version 114 | 115 | - OS language 116 | 117 | - OS version 118 | 119 | - App settings 120 | 121 | **Why we need this information:** This information is used by the support team to understand whether they are dealing with a paid version user or not, and to perform minimal diagnostics. 122 | 123 | If the “Include a diagnostic report” option is enabled, the app will also send the contents of the AdGuard log file, which includes various app’s messages (errors, warnings). This more detailed information is used by the support team to help solve more complicated problems. 124 | 125 | ### App crash report 126 | 127 | In case of a malfunction that leads to an unexpected app crash, the user is prompted to send a special crash report. The report will only be sent if the user has previously agreed to send crash reports. We will receive the following information: 128 | 129 | - App identifier 130 | 131 | - Device hardware hash 132 | 133 | - Device model, its memory size and disk space 134 | 135 | - App version 136 | 137 | - OS and Kernel versions 138 | 139 | - Stack trace 140 | 141 | - List of components used by the app and their versions 142 | 143 | - OS’s last boot timestamp 144 | 145 | - App’s last boot timestamp 146 | 147 | **Why we need this information:** To troubleshoot critical issues. It keeps us aware of new problems not reported by users. 148 | Crash report data is stored only on our servers. We do not use any third party services to collect and store crash reports. All crash reports are stored for 30 days. 149 | 150 | ### App uninstall 151 | 152 | After AdGuard for Mac is uninstalled, the app identifier is sent. 153 | 154 | **Why we need this information:** We need to know that the app has been uninstalled. We use the received app ID when checking the license: for example, we do not count deleted programs when counting the number of programs activated with the license key. 155 | 156 | ### Browsing security website check 157 | 158 | If the “Phishing and malware protection” option is enabled, AdGuard checks every website before the user visits it. We use the [Safe Browsing API](https://adguard.com/kb/general/browsing-security/) for this purpose, and the information about visited websites is sent in the form of hash prefixes. This doesn’t allow us to determine which website is being visited. 159 | 160 | ### Help us with Browsing security filters development 161 | 162 | If the “Help us with Browsing security filters development” option is enabled, the app will periodically send anonymous security-related data: 163 | 164 | - URLs of visited websites that AdGuard identifies as potentially untrustworthy (access to them is blocked by the “Security” module) 165 | 166 | - Information about the nature of identified threats 167 | 168 | The information described above, when collected by AdGuard for Mac, is generally not correlated with any other personal information and is used anonymously in aggregation with similar information from other users of the AdGuard software for analytical purposes. 169 | -------------------------------------------------------------------------------- /adguard.com/privacy/safari.html.md: -------------------------------------------------------------------------------- 1 | 2 | # AdGuard for Safari Privacy Notice 3 | 4 | *August 7, 2024* 5 | 6 | --- 7 | 8 | **Keynote:** This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. We only collect essential information for AdGuard products to function fully and properly. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 9 | 10 | --- 11 | 12 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 13 | 14 | ## What data AdGuard for Safari can collect and when 15 | 16 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 17 | 18 | ### Checking for filter updates 19 | 20 | To check for filter updates, AdGuard connects to its servers. When it happens, the following information is sent: 21 | 22 | - Browser language 23 | - App identifier 24 | - Version of the extension 25 | 26 | By default, filter updates are automatically checked every 48 hours. Otherwise, it’s done according to the selected interval, or whenever it’s manually requested by a user. We do not store this data, but we do aggregate it in an anonymous form to count the total number of active users. 27 | 28 | ### Sending a web page complaint 29 | 30 | The user can submit a report of a website problem directly from AdGuard for Safari. The app will automatically open the [reports.adguard.com](https://reports.adguard.com/new_issue.html) web page and forward some information about its configuration. The user can then alter or delete it. 31 | Unless the user agrees to submit this information by manually clicking the “Submit” button, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/adguardteam/adguardfilters/issues). 32 | -------------------------------------------------------------------------------- /adguard.com/privacy/windows.html.md: -------------------------------------------------------------------------------- 1 | # AdGuard for Windows Privacy Notice 2 | 3 | *August 7, 2024* 4 | 5 | --- 6 | 7 | **Keynote**: This Privacy Notice lists all the information that we may collect and explains why we do it and how we use this information. The information we collect includes no more than is crucial to provide the full functionality of AdGuard products. We do not share or sell your personal information. We are strongly committed to protecting user privacy and being as transparent as possible. 8 | 9 | --- 10 | 11 | This Privacy Notice supplements the AdGuard Privacy Policy available at [adguard.com/privacy.html](https://adguard.com/privacy.html), which provides you with the necessary information regarding terms and conditions of data processing by AdGuard. 12 | 13 | ## What data AdGuard for Windows can collect and when 14 | 15 | Here we describe all cases when and what data is sent to our server, so you can be sure that we only collect the minimum necessary for the application to work properly. The information we collect about you depends on how you interact with our application. 16 | 17 | ### User authorization 18 | 19 | Users have the option to activate the license by logging into their personal account in the app. The following information is sent to our servers: 20 | 21 | - Login (email address) 22 | - Password 23 | 24 | Upon authorization, the app receives an active license for that account from the server. 25 | 26 | ### License status check 27 | 28 | To validate the license status AdGuard connects to its servers. When it happens, the following information is sent: 29 | 30 | - PC name 31 | - MAC address MD5 hash 32 | - Computer hardware ID hash 33 | - OS language 34 | - App identifier 35 | - App version 36 | - License key 37 | - App language 38 | - Build identifier 39 | - Flag indicating if you take part in the Browsing Security module development 40 | 41 | **Why we need this information:** To check the license status and display the user’s license keys in the AdGuard account. MAC and hardware ID hashes are also used to tie the license to the computer. 42 | 43 | ### License reset 44 | 45 | The license is reset upon user request. When it happens, the app identifier is sent. 46 | 47 | **Why we need this information:** In order to know which app to do the license reset for. 48 | 49 | ### Checking for program updates 50 | 51 | To check for app updates, AdGuard connects to its servers. When it happens, the following information is sent: 52 | 53 | - App identifier 54 | - Update channel 55 | - App name 56 | - App version 57 | - App language 58 | - Automatic update flag 59 | - OS version 60 | 61 | **Why we need this information:** This data is sent to our servers in order to return a correct response about what updates are available for the current version of the application. 62 | 63 | Update checks are performed periodically or when prompted by the user. We do not store and use this data in future. 64 | 65 | ### Checking for filter updates 66 | 67 | To check for updates of blocking filters, AdGuard connects to its servers. When it happens, no information is being sent. The program periodically downloads a file with all filter versions and their available updates. 68 | 69 | ### App crash report 70 | 71 | If AdGuard crashes, it creates an automatic crash report. Upon the next launch AdGuard will ask you to send it to us. In this report, the following information is sent: 72 | 73 | - Stack trace 74 | - Memory minidump (only in case of a crash in the native code) 75 | - Computer’s name 76 | - AdGuard version 77 | - AdGuard settings 78 | - App identifier 79 | - Active Windows user name 80 | - .NET Framework version 81 | - List of active processes 82 | 83 | **Why we need this information:** To troubleshoot critical issues. It keeps us aware of new problems not reported by users. 84 | 85 | Crash report data is stored only on our servers. We do not use any third party services to collect and store crash reports. All crash reports are stored for 30 days. 86 | 87 | ### Installer crash 88 | 89 | If AdGuard crashes during the installation process, it creates an automatic crash report and asks the user to send it to us. If the user agrees, the following information will be sent: 90 | 91 | - Stack trace 92 | - Computer’s name 93 | - AdGuard version 94 | - List of active processes 95 | - .NET version 96 | - App identifier 97 | - Active Windows user name 98 | - Installer logs 99 | 100 | **Why we need this information:*- The installer is a separate program from AdGuard and it can also have bugs and errors. The information received in crash reports allows us to understand the causes of problems and fix them in time. 101 | 102 | ### App uninstall 103 | 104 | After AdGuard for Windows is uninstalled, the app identifier is sent. 105 | 106 | **Why we need this information:** We need to know that the app has been uninstalled. We use the received app identifier when checking the license: we do not count deleted programs when counting the number of programs activated with the license key. 107 | 108 | ### Sending a web page complaint 109 | 110 | The user can submit a report of a website problem directly from the app. The app will automatically open [reports.adguard.com](reports.adguard.com/new_issue.html) and forward some information about its configuration. The user can then alter or delete it. 111 | 112 | Unless the user agrees to submit this information by clicking *Next*, none of this information is stored or sent anywhere. If the user agrees, the report will become public (but anonymous) on [GitHub](https://github.com/AdguardTeam/AdguardFilters/issues). 113 | 114 | ### Sending a message to support 115 | 116 | Users can send messages to support right from the app. If they do, a special file containing some information about app settings and OS configuration will be sent. This data is required for troubleshooting purposes. Users also have an option to include a diagnostic report that contains additional information. Nothing will be sent unless the user manually confirms the submission. 117 | 118 | The following information is included in this message: 119 | 120 | - App identifier 121 | - App version 122 | - App language 123 | - OS version 124 | - Version of Microsoft .NET Framework installed on the computer 125 | - The list of enabled filters 126 | - License key 127 | 128 | **Why we need this information:** This information is used by the support team to understand whether they are dealing with a paid version user or not, and to perform minimal diagnostics. 129 | 130 | If *Include the diagnostic report in the message* is enabled, the app will also send additional data: 131 | 132 | - List of running processes 133 | - Detailed information about AdGuard settings, including enabled filters and installed userscripts 134 | - Contents of AdGuard log file that includes the list of errors that occurred since the last launch of the program 135 | 136 | This detailed information is used by the support team to help solve more complicated problems. 137 | 138 | ### Browsing Security website check 139 | 140 | If *Phishing and malware protection* is enabled, AdGuard will check each website before the user visits it. We use the [Safe Browsing API](https://adguard.com/kb/general/browsing-security/) for this purpose, and the information about the visited website is sent in the form of hash prefixes. This doesn’t allow us to determine which website is being visited. 141 | 142 | ### Parental Control website check 143 | 144 | When *Parental Control* is enabled, AdGuard uses its own web service to check websites against the database. We use the [Safe Browsing API](https://adguard.com/kb/general/browsing-security/) for this purpose, and the information about the visited website is sent in the form of hash prefixes. This doesn’t allow us to determine which website is being visited. 145 | -------------------------------------------------------------------------------- /adguard.com/website-privacy.html.md: -------------------------------------------------------------------------------- 1 | 2 | # Privacy Policy of AdGuard Websites 3 | 4 | *March 19, 2025* 5 | 6 | **Keynote:** We are proud to say that we fight for users’ privacy, and we are strongly committed to this principle and to being as transparent as possible. 7 | 8 | We believe that privacy is a fundamental human right. That’s why we are transparent about what AdGuard does and explain the purpose of every little bit of information that may be gathered by our apps and services. 9 | 10 | ## Who we are 11 | 12 | ADGUARD SOFTWARE LIMITED (“We”, “Us”, “Our”) processes your data in accordance with this Privacy Policy and in compliance with the applicable data protection laws when you: 13 | 14 | - Visit websites related to AdGuard software and services (hereafter, the “Websites”): 15 | 16 | - AdGuard Ad Blocker website at [adguard.com](https://adguard.com), 17 | - AdGuard VPN website at [adguard-vpn.com](https://adguard-vpn.com), 18 | - AdGuard DNS website at [adguard-dns.io](https://adguard-dns.io). 19 | - AdGuard Mail website at [adguard-mail.com](https://adguard-mail.com). 20 | - Use AdGuard Account services at [adguardaccount.com](https://adguardaccount.com) (hereafter, the “AdGuard Account”). 21 | 22 | - Use AdGuard Affiliate Account services at [adguardpartner.com](https://adguardpartner.com) (hereafter, the “Affiliate Account”). 23 | 24 | ADGUARD SOFTWARE LIMITED is a company registered in Limassol, Cyprus, registered office is at Anexartisias and Athinon 79, Nora Court Flat/Office 203–205, 3040 Limassol, Cyprus. ADGUARD SOFTWARE LIMITED acts as the data controller when processing your data. 25 | 26 | This Privacy Policy provides you with the necessary information regarding your rights and our obligations and explains how, why and when we process your data. Our general principle is to collect only the information that is necessary to provide you with full functionality of our products and services. We strictly follow the principle of “minimization” when processing your data. 27 | 28 | This Privacy Policy does not apply to third-party websites or services that you visit, even if the Websites, the AdGuard Account, or the Affiliate Account have links to such third-party websites or services. You should familiarize yourself with privacy policies of third-party websites and services. 29 | 30 | If you have any questions about this Privacy Policy or if you want to exercise any of your rights, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 31 | 32 | PLEASE READ THIS PRIVACY POLICY THOROUGHLY. 33 | 34 | IF YOU AGREE AND ACCEPT THIS PRIVACY POLICY, WE WILL PROCESS YOUR DATA STATED BELOW FOR THE DECLARED PROCESSING PURPOSES IN ACCORDANCE WITH THIS PRIVACY POLICY. 35 | 36 | IF YOU DO NOT AGREE WITH OUR POLICIES AND PRACTICES DESCRIBED IN THIS PRIVACY POLICY, PLEASE DO NOT VISIT OR USE THE WEBSITES, THE ADGUARD ACCOUNT, OR THE AFFILIATE ACCOUNT, AND DO NOT PROVIDE YOUR INFORMATION TO US. 37 | 38 | ## What data we process 39 | 40 | We process different data depending on the situation. You can learn details about what data we process in this section. 41 | 42 | Some data that we receive and process may be treated as personal data (“Personal Data”) in accordance with the laws of certain territories and countries. When we use terms “personal data” or “personal information”, we mean any information relating to an identified or identifiable natural person, excluding any anonymized and depersonalized data where your identity is absent or has been removed and cannot be recovered. 43 | 44 | When you visit the Websites, the AdGuard Account, or the Affiliate Account and their subdomains, we process the following information obtained by our web server to provide you with the content you request: IP addresses in anonymized form, timestamp of the server request, type and version of your web browser, name and version of your operating system, requesting domain (URL), address of the previously visited page (referrer URL), host name. 45 | 46 | ### When you visit the Websites 47 | 48 | You can visit and use the Websites for informational purposes without having to provide any personal data. However, to provide you with certain functionality of our Websites listed below, we need to process some of your personal data. Without such processing, we will not be able to provide you with such functionality of our Websites. 49 | 50 | **Sending messages.** We may use your email address to communicate with you when we need to make announcements, inform you of updates and new features in our software or services, provide you with advice, and communicate with you when you report errors. 51 | 52 | You may also give us your consent to process your email to send you marketing messages about other AdGuard software or services. You may withdraw your consent at any time by unsubscribing from our newsletter via the AdGuard Account or by clicking the “Unsubscribe” button or link in the email itself. 53 | 54 | **Buying a license.** We process your email address for billing and payment purposes. If you buy a subscription to AdGuard software, we’ll use the email address you provide to send you information about the purchase, such as your subscription status and renewal notifications (if applicable), and to recover your license key if you request it. 55 | 56 | We conduct all transactions via two payment providers — [Paddle.com Inc.](https://www.paddle.com) and [PayPro Global](https://payproglobal.com) — to process payments when you purchase a subscription to use our software and services. Processed data: your email address, country of residence, zip/postal code, and if you use a bank card to make a purchase, the card number, name, expiration date and the security code associated with the bank card. Paddle privacy policy: [www.paddle.com/legal/privacy](https://www.paddle.com/legal/privacy). PayPro Global privacy policy: [docs.payproglobal.com/documents/legal/privacyPolicy.pdf](https://docs.payproglobal.com/documents/legal/privacyPolicy.pdf) 57 | 58 | The third-party service provider may transmit some of your personal data to us, but not including payment information, unless you specifically agree (as may be the case if you purchase a subscription with auto-renewal). We may use the information to verify your registration or subscription status, or for renewal of your subscription, if applicable. 59 | 60 | ### When you use the AdGuard Account 61 | 62 | To use our AdGuard Account, you need to register your account and sign in. 63 | 64 | **Registering your account.** We process your email address and a hash of the password you use for authorization. That ensures that you can retrieve your password if needed. 65 | 66 | If you choose to register your account using your third-party account, such as a Google, Apple, or Facebook account, we will process an authentication token to prove your identity. AdGuard does not request or have access to your third-party accounts. 67 | 68 | **Sending messages.** To keep you informed about the operation and new features of the AdGuard Account, we will process your email address. 69 | 70 | To receive newsletters and promotional emails about the AdGuard software, you can opt-in and subscribe to the newsletters. You can withdraw your consent at any time by unsubscribing in your account settings or by clicking on the appropriate link in the email you receive. 71 | 72 | Data processing during the use of the AdGuard software as well as the sections of the AdGuard Account related to the AdGuard software is governed by the privacy policies of the respective software. 73 | 74 | ### When you use the Affiliate Account 75 | 76 | To use our Affiliate Account, you need to register your account and sign in. 77 | 78 | **Registering your account.** We process your username, email address, and a hash of the password you use for authorization. 79 | 80 | **Processing your payouts.** To process payments via the payout method you have chosen, we will process the email address you indicate as an account identifier of a third-party payment service to which you want to receive your payouts. 81 | 82 | We conduct all transactions via third-party payment providers. To process payments via the payout method you have chosen, we will share some of your personal data with a third party payment service to which you want to receive your payouts. 83 | 84 | - (a) If you choose PayPal as your payout method, AdGuard will share the email address you indicate with [PayPal (Europe) S.à r.l. et Cie, S.C.A.](https://www.paypal.com). PayPal privacy policy: [www.paypal.com/cy/webapps/mpp/ua/privacy-full](https://www.paypal.com/cy/webapps/mpp/ua/privacy-full). 85 | - (b) If you choose Mellow as your payout method, AdGuard will share the email address you indicate with [TMS SolarWeb Ltd](https://www.mellow.io). Mellow privacy policy: [www.mellow.io/documents/privacy-policy](https://www.mellow.io/documents/privacy-policy). 86 | 87 | AdGuard does not request or have access to your accounts in third-party payment services. 88 | 89 | **Processing data of users referred by you and by your affiliate referrals.** To properly calculate your commission when a subscription to the AdGuard software is purchased or renewed by a user referred by you or by your affiliate referral, we will process the email address used to create the user’s account in the AdGuard Account and username and email address of your affiliate referral. 90 | 91 | **Sending messages.** To keep you informed about the Affiliate Account and the AdGuard affiliate program, we will process your email address. 92 | 93 | **Providing support.** To assist you, we process the information you share when submitting a support ticket. Please note that in most cases, we do not need any additional personal information to provide you with support. 94 | 95 | ### Use of cookies 96 | 97 | We use our cookies to personalize the content and facilitate your use of the Websites, the AdGuard Account, and the Affiliate Account, such as setting the default language. 98 | 99 | Cookies are small text files with parameters and their values that your web browser stores on your device. Some cookies are only stored for the duration of your current browsing session, some cookies may be stored for longer. 100 | 101 | None of the information we may collect through cookies is considered Personal Data as it does not allow us to identify you. You can always disable or clear cookies in your browser, but please note that some of our services may not function properly without the aid of cookies. 102 | 103 | We do not use any javascript-based tracking or cookies. Instead, we use our server logs (i.e. information about what pages were requested) to measure how people use our website. We do not use raw logs, instead raw logs are aggregated to build general reports for us. 104 | 105 | ## What legal bases we use to process your Personal Data 106 | 107 | We use different legal bases to process Personal Data, depending on the type of data involved and the purposes and circumstances of processing. 108 | 109 | **Consent.** We process your Personal Data if you have provided us with your consent to use your Personal Data for certain purposes. For example, to send you marketing emails. You can withdraw your consent any time without any detriment to your use of the Websites, the AdGuard Account, or the Affiliate Account. 110 | 111 | **Performance of a contract.** We process your Personal Data when it is necessary to fulfill our contractual obligations to you, including providing the functionality of our software and services or at your request prior to entering into a contract with you. 112 | 113 | **Legal obligations.** We process your Personal Data where it is necessary for compliance with our legal obligations, such as to exercise or defend our legal rights, or for taxation purposes. 114 | 115 | **Legitimate interest.** We process your Personal Data when we pursue our legitimate interests, except where such interests are overridden by the interests or fundamental rights and freedoms of data subjects. 116 | 117 | ## Where we process your Personal Data 118 | 119 | We store your Personal Data in our own data center located in Frankfurt, Germany. Your Personal Data may be processed by our employees, who can only access your data on a need-to-know basis as part of their job duties. If you have any questions or would like to know from which countries access may be possible, you can write to us at [privacy@adguard.com](mailto:privacy@adguard.com). 120 | 121 | When we transfer data to other countries, we always implement appropriate safeguards to ensure that your Personal Data always remains safe and that your rights are respected: 122 | 123 | - The country or the third party is recognized as providing adequate protection. 124 | - A valid transfer mechanism, such as the Standard Contractual Clauses, is applied. Additional measures are taken where necessary. 125 | - The transfer has your explicit consent. 126 | - The transfer is necessary to perform a contract with you or to take steps requested by you prior to entering into that contract. 127 | 128 | If you wish to obtain a copy of the Standard Contractual Clauses used, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). 129 | 130 | To determine if a non-EU country has an adequate level of data protection, please visit [commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en](https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en). 131 | 132 | ## How we use your Personal Data 133 | 134 | ### Retaining your data 135 | 136 | We will retain Personal Data for as long as necessary to provide you with our products and services, or until you revoke your consent to share this information. 137 | 138 | ### Your rights 139 | 140 | In some countries and regions, you may have certain rights in relation to your Personal Data under applicable data protection laws. 141 | 142 | If you wish to exercise your rights with respect to your Personal Data, please contact us at [privacy@adguard.com](mailto:privacy@adguard.com). We will consider and act upon any request in accordance with applicable data protection laws. We may ask you to further confirm your identity and will respond to you within the time period specified by applicable data protection law. Please note that we may charge you a reasonable fee for processing your request or refuse your request in certain cases specified by applicable data protection laws. 143 | 144 | You are entitled to exercise the following rights in relation to your Personal Data: 145 | 146 | **Right of access:** the right to obtain all your Personal Data we store. In some cases, the right of access may be limited for technical reasons, including if the data has been anonymized and cannot be linked to any data subject. 147 | 148 | **Right to erasure** or **right to be forgotten:** the right to have your Personal Data completely deleted. You can delete your data related to your AdGuard Account and Affiliate Account accounts yourself via the settings of these accounts. Alternatively, you can send us a request at [privacy@adguard.com](mailto:privacy@adguard.com). 149 | 150 | **Right to rectification:** the right to correct any incomplete or inaccurate Personal Data about you. We will do so as quickly as possible, unless there is a valid reason not to, in which case you will be notified. 151 | 152 | **Right to restriction:** the right to impose restrictions on processing of your Personal Data. 153 | 154 | **Right to object:** the right to object to processing of your Personal Data. 155 | 156 | **Right to data portability:** the right to receive provided Personal Data in a structured, commonly used and machine-readable format and to transmit that data to another controller. You can export all your Personal Data related to your AdGuard Account to a local file from in the AdGuard Account settings. 157 | 158 | **Right not to be subject to a decision based solely on automated processing**, including profiling. 159 | 160 | **Right to withdraw a consent** where the data processing is based on the consent. 161 | 162 | **Right to lodge a complaint** with a data protection authority. You can find the contact details of our data protection authorities here: [www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument](https://www.dataprotection.gov.cy/dataprotection/dataprotection.nsf/contact_en/contact_en?opendocument). 163 | 164 | If we receive your Personal Data from a third party, we will use reasonable efforts to inform you about it. 165 | 166 | ### Safeguarding measures 167 | 168 | We make every possible effort to protect you and your Personal Data from unauthorized access, alteration, disclosure, or destruction. We implement and maintain the following technical and security measures: 169 | 170 | - **System access controls:** We take reasonable measures to prevent Personal Data from being used without authorization. These controls shall vary based on the nature of the processing undertaken and may include, but are not limited to, authentication via passwords and/or two-factor authentication, documented authorization processes, documented change management processes and/or logging of access on several levels. 171 | - **Data access controls:** We take reasonable measures to ensure that Personal Data is accessible and manageable only by properly authorized staff. Direct database query access is restricted and application access rights are established and enforced to ensure that individuals entitled to use a data processing system only have access to the Personal Data to which they have access privileges; and that personal data cannot be read, copied, modified, or deleted without authorization in the course of processing. 172 | - **Storing data in a data center:** Personal information is stored in our own data center located in Frankfurt, Germany. This is secure: the data center does not demand that we collect any data about your traffic or your use of our products and services. If they request us to start doing so, we will stop working with them and find an alternative. 173 | - **Transmission controls:** We take reasonable measures to ensure that it is possible to check and establish to which entities the transfer of personal data by means of data transmission facilities is envisaged so personal data cannot be read, copied, modified, or removed without authorization during electronic transmission or transport. 174 | - **Input controls:** We take reasonable measures to make it possible to check and establish whether and by whom personal data has been entered into data processing systems, modified, or removed. 175 | - **Data backup:** Databases are backed up regularly. They are secured and encrypted to ensure that personal data is protected from accidental destruction or loss while hosted by us. 176 | - **Logical separation:** Personal Data is logically segregated on our systems to ensure that Personal Data collected for different purposes can be processed separately. 177 | 178 | ### Consequences of not providing your Personal Data 179 | 180 | You are under no obligation to provide your Personal Data to us. However, because this information is necessary for us to provide you with our services or respond to your requests, we will not be able to provide some or all of our services without it. 181 | 182 | ### Age limitations 183 | 184 | To the extent not prohibited by applicable law, we do not allow the use of the Websites, the AdGuard Account, or the Affiliate Account by anyone under the age of 18 years. If you learn that anyone younger than 18 has unlawfully provided us with Personal Data, please contact us and we will take steps to delete such information. 185 | 186 | ## Do Not Track 187 | 188 | We respect your right to privacy and therefore respect the Do Not Track (“DNT”) settings in your web browser. If you have DNT enabled in your web browser, any analytical tools, including first-party, will not be loaded and used on the Websites, in the AdGuard Account, and in the Affiliate Account. 189 | 190 | ## Changes to this Privacy Policy 191 | 192 | We may change this Privacy Policy from time to time and notify you of any important changes. Laws, regulations, and industry standards evolve, which may make those changes necessary, or we may make changes to our business. We will post the changes on this page and encourage you to review our Privacy Policy to stay informed. 193 | -------------------------------------------------------------------------------- /build-resx.js: -------------------------------------------------------------------------------- 1 | const fs = require('fs'); 2 | const path = require('path'); 3 | const {create} = require('xmlbuilder2'); 4 | 5 | const basePath = 'crowdin'; 6 | const outputFilename = 'docs.en.resx'; 7 | const filesToProcessExt = '.html.md' 8 | 9 | const KEYS_SEPARATOR = ''; 10 | 11 | const CROWDIN_MAX_STRING_LENGTH = 65535; 12 | const TRANSLATION_RATIO = 1.1; 13 | const MAX_BYTES_PER_CHAR = 2; 14 | const MAX_STRING_LENGTH = Math.floor(CROWDIN_MAX_STRING_LENGTH / (MAX_BYTES_PER_CHAR * TRANSLATION_RATIO)); 15 | 16 | const mappings = { 17 | 'adguard-mail.com': 'legal-github-docs-mail', 18 | 'adguard.com': 'legal-github-docs-adguard', 19 | 'adguard-dns.io': 'legal-github-docs-dns', 20 | 'adguard-vpn.com': 'legal-github-docs-vpn', 21 | 'adguardpartner.com': 'legal-github-docs-aff', 22 | }; 23 | 24 | const getPartialKeySuffix = (partIndex) => { 25 | return `.__part__.${partIndex + 1}`; 26 | } 27 | 28 | console.log('Starting document processing...'); 29 | 30 | if (!fs.existsSync(basePath)) { 31 | console.log(`Creating output directory: ${basePath}`); 32 | fs.mkdirSync(basePath); 33 | } 34 | 35 | for (const [sourceDir, crowdinDir] of Object.entries(mappings)) { 36 | console.log(`\nProcessing directory: ${sourceDir} -> ${crowdinDir}`); 37 | 38 | if (!fs.existsSync(sourceDir)) { 39 | console.log(`Skipping ${sourceDir} - directory does not exist`); 40 | continue; 41 | } 42 | 43 | const mdFiles = fs.readdirSync(sourceDir, {recursive: true}) 44 | .filter(file => file.endsWith(filesToProcessExt)); 45 | 46 | console.log(`Found ${mdFiles.length} files to process`); 47 | 48 | let xmlBuilder = create({version: '1.0', encoding: 'utf-8'}).ele('root'); 49 | 50 | for (const filePath of mdFiles) { 51 | const fullFilePath = path.join(sourceDir, filePath); 52 | 53 | console.log(`Processing file: ${fullFilePath}`); 54 | const content = fs.readFileSync(fullFilePath, 'utf8'); 55 | 56 | const baseKey = filePath 57 | .replace(filesToProcessExt, '') 58 | .replaceAll('/', '.'); 59 | 60 | if (content.length > MAX_STRING_LENGTH) { 61 | const parts = content.split(KEYS_SEPARATOR); 62 | 63 | if (parts.length === 1) { 64 | console.error(`Error: File ${fullFilePath} exceeds maximum length and no ${KEYS_SEPARATOR} comment found`); 65 | process.exit(1); 66 | } 67 | 68 | for (let i = 0; i < parts.length; i++) { 69 | const part = parts[i]; 70 | if (part.length > MAX_STRING_LENGTH) { 71 | console.error(`Error: Part ${i + 1} of file ${fullFilePath} exceeds maximum length`); 72 | process.exit(1); 73 | } 74 | 75 | const key = `${baseKey}${getPartialKeySuffix(i)}`; 76 | console.log(`Generated key: ${key}`); 77 | xmlBuilder = xmlBuilder.ele('data').att('name', key) 78 | .ele('value').dat(part).up() 79 | .up(); 80 | } 81 | } else { 82 | console.log(`Generated key: ${baseKey}`); 83 | xmlBuilder = xmlBuilder.ele('data').att('name', baseKey) 84 | .ele('value').dat(content).up() 85 | .up(); 86 | } 87 | } 88 | 89 | const resxContent = xmlBuilder.end({ 90 | prettyPrint: true, 91 | indent: ' ', 92 | }); 93 | 94 | const outputDir = path.join(basePath, crowdinDir); 95 | 96 | if (!fs.existsSync(outputDir)) { 97 | fs.mkdirSync(outputDir); 98 | } 99 | 100 | const outputPath = path.join(outputDir, outputFilename); 101 | console.log(`Writing output to: ${outputPath}`); 102 | fs.writeFileSync(outputPath, resxContent); 103 | } 104 | 105 | console.log('\nProcessing complete!'); 106 | -------------------------------------------------------------------------------- /crowdin.yml: -------------------------------------------------------------------------------- 1 | project_id: "365959" 2 | api_token_env: "CROWDIN_PERSONAL_TOKEN" 3 | base_path: './crowdin' 4 | 5 | preserve_hierarchy: true 6 | 7 | files: 8 | - source: '**/docs.en.resx' 9 | dest: '**/docs.resx' 10 | translation: '**/docs.%two_letters_code%.resx' 11 | update_option: 'update_as_unapproved' 12 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "legaldocs", 3 | "version": "1.0.0", 4 | "description": "This repository contains AdGuard’s legal documents, they are later synced to the website. The purpose is to be transparent about the history of their changes.", 5 | "main": "index.js", 6 | "scripts": { 7 | "lint": "markdownlint .", 8 | "build:resx": "node build-resx.js", 9 | "crowdin:upload:sources": "crowdin upload sources", 10 | "crowdin:upload:translations": "crowdin upload translations -l en --auto-approve-imported --import-eq-suggestions", 11 | "crowdin:upload": "npm run crowdin:upload:sources && npm run crowdin:upload:translations", 12 | "crowdin:upload:dryrun": "crowdin upload sources --dryrun && crowdin upload translations -l en --auto-approve-imported --import-eq-suggestions --dryrun" 13 | }, 14 | "author": "", 15 | "license": "ISC", 16 | "devDependencies": { 17 | "@crowdin/cli": "4.5.2", 18 | "markdownlint": "0.36.1", 19 | "markdownlint-cli": "0.43.0", 20 | "xmlbuilder2": "3.1.1" 21 | } 22 | } 23 | --------------------------------------------------------------------------------