diff --git a/pages/policy.html b/pages/policy.html index aa2a19e..578951c 100644 --- a/pages/policy.html +++ b/pages/policy.html @@ -28,92 +28,100 @@

Policy

EasyList policy

-
-
-

EasyPrivacy policy

+
+

EasyPrivacy policy

+
+
The goal of EasyPrivacy is to block tracking and improve end user privacy. By blocking the following:
+
    +
  • Analytics
  • +
  • AntiBot or Bot checks
  • +
  • Telemetry
  • +
  • Tracking Pixels or cookies (being set, checked or get)
  • +
  • Referrers
  • +
  • Beacons
  • +
  • Fingerprinting
  • +
  • Email tracking
  • +
  • Impressions / Event / Perf / Pageview logging
  • +
  • User agent checks or monitoring
  • +
  • Resource miners
  • +
  • Hit counters
  • +
  • CNAME trackers
  • +
  • Notification servers / popups including any tracking covered by Easyprivacy policy
  • +
  • Linking, loading or initialising to known tracking servers, or scripts
  • +
  • Some unnecessary 3rd-party scripts/images
  • +
  • "Consent messages" using any of these tracking techniques, covered by Easyprivacy policy
-
- -
  • -
    Syntax
    -
      -
    • Domains specifically serving tracking should be blocked on all third-party websites.
    • -
    • Filters must be as efficient as possible.
    • -
    • Allowed blocked items should be specific enough to avoid protecting unwanted items.
    • +
      When a site is attempting to track, it'll be put into one of 4 categories.
      +
        +
      • Generic blocks (common URL/tracking filter patterns) used by 1st/3rd-parties.
      • +
      • 1st-party tracking. Self-hosted trackers and CNAME trackers.
      • +
      • 3rd-party tracking. Hosted by another provider, which hosts a tracking script, but not actually a tracking company.
      • +
      • Tracking-servers. Where the server has only one purpose to track/analyze user, will be blocked at the url level.
    -
  • -