Desktop Application Privacy Addendum v3.2

AdBlock360 for Windows Last Updated: March 30, 2026

This Desktop Addendum describes ONLY desktop-app-specific processing and controls. For general disclosures (rights, retention, transfers, vendor list, legal bases), see the Privacy Policy.

1. System-Level Network Filtering (WFP)

AdBlock360 installs a Windows Filtering Platform (WFP) network driver that operates at the kernel level to block ads. This means filtering occurs at the operating system network layer and can apply to network requests made by browsers and other applications.

Important:
  • We design the app not to collect or transmit browsing history, visited URLs, or the content of your network traffic to AdBlock360 as part of providing ad blocking.
  • The filtering logic operates locally on your device.

2. Local Data Storage

The desktop app stores certain data locally (preferences, cached filter lists, update cache, limited logs). Some sensitive items (e.g., auth tokens) may be protected using Windows security mechanisms.

3. Premium Licensing (HWID)

If you use Premium, we process licensing data such as:

  • License key / subscription status
  • Activation timestamp and device associations
  • Pseudonymized Hardware ID (HWID) used for license binding and device management

A pseudonymized HWID can still be Personal Data under many privacy laws.

4. Diagnostics / Crash Reporting (Sentry)

Default setting: ENABLED (opt-out available)

4.1 Data Typically Included

  • Error messages and stack traces
  • Application version and Windows version
  • Available memory at time of error
  • Timestamp
  • Pseudonymous identifiers needed to diagnose recurring issues

4.2 What We Do NOT Collect

We configure error reporting to avoid collecting direct identifiers such as your name or email address, and we do not collect browsing history, visited websites, or network traffic content for error reporting.

However, crash reports may include pseudonymous technical identifiers and device/app signals needed to diagnose recurring issues. In some cases, stack traces may include technical file paths; we take steps to minimize and redact such data where feasible.

4.3 Retention

  • Individual reports: typically 90 days (then deleted)
  • Aggregated statistics: may be retained longer for trend analysis

4.4 User Control

To disable: Open AdBlock360 → Settings → Privacy → uncheck "Send anonymous error reports".

("Anonymous" in the setting name refers to minimizing direct identifiers; reports may still contain pseudonymous technical data as described above.)

Changes apply immediately.

5. Telemetry (Product Analytics)

Default setting: ENABLED (opt-out available)

If enabled, we collect limited product telemetry such as:

  • High-level feature usage events (not browsing content)
  • Performance metrics (update success/failure, stability signals)
  • Pseudonymous installation or device identifier(s) to understand recurring issues

We do not collect browsing history or the content of websites you visit for telemetry.

5.1 User Control

To disable: Settings → Privacy → uncheck "Send usage statistics".

Changes apply immediately.

6. Optional HTTPS Filtering / Local Certificate

If you enable optional HTTPS filtering features:

  • The app may create and install a local certificate on your device to enable local inspection and filtering of encrypted traffic.
  • You will be asked for explicit consent before any certificate is installed.
  • The certificate and private key are intended to remain on your device and not be transmitted to AdBlock360.
  • You can disable the feature at any time, and we provide guidance in-app to remove the local certificate if you choose.

7. Updates

The app checks for updates. Update requests may include:

  • App version, OS version, update channel, timestamps
  • Technical identifiers needed to deliver and secure updates (pseudonymous identifiers)

You can disable automatic updates in settings (note: this may reduce security).