Chrome

Compatible with

your browser

Privacy Policy

Last updated: July 8, 2026

Applies to: Deep Max AdBlocker browser extension and the website deepmaxblocker.com.

Operated by: DeepMax LLC ("we", "us", "our").

This policy explains what data the Deep Max AdBlocker extension and our website handle, where it goes, and why. We have written it to reflect the actual behavior of the extension. We collect the minimum data needed to operate, and we do not sell your data or share it with third parties for advertising.

1. Summary

  • The extension blocks ads and trackers locally in your browser using filter lists.
  • It contacts our own servers to download and update filtering rules and configuration, to register installs and uninstalls, and — only when you choose to use them — to deliver your optional feedback or broken-page reports. It does not download executable program code that changes how the extension works.
  • It stores a randomly generated identifier (UUID) assigned by our server. This UUID is not linked to your name, email, or any personally identifying information, and is used to deliver rule updates and to count installs and uninstalls.
  • The extension can read and modify cookies and page content on the sites you visit only to block ads and trackers. This processing happens inside your browser; the cookies and page content are not transmitted to us.
  • We do not collect your browsing history in bulk, your form inputs, your passwords, or your personal files.

2. Who we are

The Deep Max AdBlocker extension and the website deepmaxblocker.com are owned and operated by DeepMax LLC.

3. Data the extension processes

3.1 Data processed locally in your browser (never sent to us)

To block ads and trackers, the extension needs broad access to the pages you visit (this is why it requests access to all websites). On the pages you visit, the extension may:

  • Read and modify web page content (HTML, CSS, elements) to hide or remove ad and tracker elements.
  • Read, modify, or delete cookies to remove tracking cookies, in accordance with the active filter rules.
  • Observe and filter network requests made by the pages you visit, to block requests to ad and tracker servers and to neutralize known tracking scripts (by redirecting them to harmless local placeholder files bundled inside the extension).
  • Apply the Global Privacy Control (GPC) signal on your behalf.

All of the above happens on your device. The page content, the cookies, and the request data are processed in real time inside your browser and are not collected, stored on our servers, or transmitted to us or to any third party.

3.2 Data the extension sends to our servers

The extension communicates with servers we operate. The following is an exhaustive list of what is sent and when.

(a) Filtering rules and configuration updates

Sent to https://api.deepmax-analytic.com/gyr. The extension transmits your assigned UUID (once one exists) as a query parameter, plus the extension version and extension ID in request headers. In response, our server returns updated lists of domains and URL patterns to block, together with configuration values used by the filtering engine (for example, selectors used to detect ad players on supported video sites). This is a data and rules update — not a download of new program logic.

(b) Installation and uninstall events

On first install or update, the extension ID, the event type, and your existing UUID (if any) are sent to https://api.deepmax-analytic.com/gap so we can count active installations and receive a UUID. When you remove the extension, the browser opens a URL on https://api.deepmax-analytic.com/gap/w containing your UUID and the extension ID, so we can count uninstalls. This is a standard browser "uninstall URL" and fires only at the moment of removal.

(c) Optional feedback (only when you choose to submit)

Sent to https://api.deepmax-analytic.com/gap/rt. The extension transmits your rating, the page URL, the extension ID, and your UUID. This happens only when you actively submit a rating through the extension's feedback dialog.

(d) Broken-page reports (only when you choose to submit)

Sent to https://api.deepmax-analytic.com/gap/rpts. The extension transmits the reported page URL, the extension ID, and your UUID. If you opt to include a screenshot, the screenshot and an optional message (which may include the report category and an email address if you provided one) are sent to the same service. This happens only when you actively submit a report through the extension's "Report an issue" flow.

If a request to our servers fails, the extension may temporarily store that request locally and retry it later. Retried data is limited to the items described above.

3.3 The UUID (installation identifier)

The first time a conversion or rules fetch succeeds, our server assigns a random UUID to your installation. The UUID is just an installation identifier: it is a random value, it is not derived from and not linked to your name, email address, account, or any personally identifiable information, and it does not reveal any of your data. The UUID is not visible in the extension's user interface — we mention it here only so you know it exists. It is stored locally by the extension and included in the requests described in section 3.2, where it is used to deliver rule updates and to measure installs and uninstalls. You can clear it at any time by removing the extension. We do not combine it with personal data and we do not use it for cross-site advertising.

3.4 Local storage on your device

The extension uses the browser's local storage and IndexedDB to keep your settings, the downloaded filter rules, counters (for example, the number of items blocked), per-tab statistics, and the UUID. This data stays on your device and is only transmitted to us as described in section 3.2.

4. Permissions and why we need them

The extension requests the following permissions strictly to perform ad and tracker blocking:

  • host_permissions (access to all HTTP, HTTPS, WebSocket, and secure WebSocket URLs): required to detect and block ads and trackers on any site you visit.
  • declarativeNetRequest: to block and redirect ad and tracker network requests using filter rules.
  • webRequest: to observe requests for blocking statistics and in-popup logging. In Manifest V3, actual blocking is performed by the browser's declarativeNetRequest layer, not by the webRequest API.
  • cookies: to remove or modify tracking cookies locally, as described in 3.1. Cookies are not sent to us.
  • scripting: to apply cosmetic filtering (hiding ad elements) on pages.
  • tabs, activeTab, webNavigation: to know which page is active and apply the correct rules per site or tab.
  • storage: to store settings and the filter rule sets locally.
  • alarms: to schedule periodic refresh of backend filter rules.
  • contextMenus: to add optional context-menu entries for blocking elements or managing the extension.
  • offscreen: to perform limited auxiliary work outside the service worker when required by the browser.

We do not use these permissions to read your browsing history in bulk, capture form inputs, capture credentials, or access your files.

5. What we do NOT do

We do not:

  • sell, rent, or trade your data;
  • share your data with third parties for advertising or marketing;
  • inject ads, affiliate links, or sponsored content into the pages you visit;
  • change your search engine, homepage, or new-tab page;
  • collect your browsing history in bulk, your keystrokes, your form data, your passwords, your financial or health information, or your files;
  • transmit the cookies or page content processed for ad-blocking to our servers or to anyone else.

6. Third-party services

The extension sends data only to servers operated by us (api.deepmax-analytic.com), as described in section 3. The extension itself does not embed third-party analytics SDKs.

The website deepmaxblocker.com separately uses cookies and analytics (see section 8). Website analytics are distinct from the extension and do not receive the extension data described above.

7. Data retention and deletion

Settings, rules, counters, and the UUID stored on your device are deleted when you remove the extension.

Data sent to our servers (install and uninstall counts, optional feedback, broken-page reports, the UUID) is kept only as long as reasonably necessary for the purposes described above, after which it is deleted or de-identified.

8. Data we collect on our website (deepmaxblocker.com)

This section applies to the website only, not to the extension.

When you visit our website, our server may place cookies on your device. We use cookies and analytics to understand site usage, remember preferences such as language and currency, and infer approximate location from your IP address to show the correct language and region. We currently use Google Analytics for this purpose, which relies on cookies. You can disable cookies in your browser to opt out of this website tracking. Website cookies typically expire within 30–60 days.

9. Security

We apply technical, administrative, and physical safeguards to protect the limited data we hold. Server access is restricted to authorized personnel over secured connections, and all transmissions between the extension and our servers use encrypted (HTTPS) connections.

10. Chrome Web Store Limited Use disclosure

Deep Max AdBlocker's use of information received from browser APIs and from data observed via browser permissions adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information observed locally for the purpose of ad and tracker blocking is processed on your device and is never transferred to us or to any third party, except as needed to provide or improve the single user-facing purpose of ad blocking. We do not use or transfer this information for serving advertisements, including personalized, retargeted, or interest-based advertising. We do not allow humans to read this information, except with your explicit consent for specific data, where required for security purposes (such as investigating abuse), or where required to comply with applicable law.

11. Children's privacy

Deep Max AdBlocker is not directed at children and does not knowingly collect data from children.

12. Changes to this policy

We may update this policy to reflect changes in the extension or in legal requirements. The "Last updated" date at the top indicates the latest revision. Material changes will be reflected in the extension's store listing.

13. Your rights

Depending on your location, you may have rights to access, correct, or delete data we hold about you.