Getting Started
1. Initial Setup
- Extension auto-starts upon installation
- Default settings provide balanced protection
- No configuration required for basic use
2. Using the Popup Interface
- Status Indicator: Shows if extension is active
- Statistics: Real-time blocking counters
- Recent Detections: Last 10 detected tracking domains
- Export Button: Generate network blocklists
- Options Button: Access advanced settings
3. Understanding Detection Types
- 🔴 3rd Party: External tracking domains (safe to block at network level)
- 🟡 1st Party: Self-hosted analytics (blocked in browser only)
- 🟣 Mixed: Multiple detection methods or unclear classification
Core Features
Blocking Modes
- Browser-Level: Blocks requests and deletes cookies in Firefox only
- Network-Level: Generate blocklists for router/DNS-level blocking
Export Formats
- Pi-hole: Plain text domain list
- NextDNS: JSON format with metadata
- Hosts File: Standard hosts file format
- AdGuard DNS: Filter rule format
Statistics Tracking
- Requests blocked today
- Tracking cookies deleted
- Unique domains detected
- Performance metrics
Advanced Usage
Settings Configuration
Access via popup → Options or right-click extension icon
Detection Settings
- Sensitivity: Low/Medium/High detection aggressiveness
- Self-hosted blocking: Detect same-domain analytics
- Debug logging: Enable detailed console output
Blocklist Management
- Max domains: Storage limit (100-5000)
- Auto-export threshold: When to suggest network migration
- Auto-cleanup: Remove old entries automatically
Network-Level Setup
Pi-hole Integration
- Export blocklist in Pi-hole format
- Upload to Pi-hole admin interface
- Add to Group Management → Adlists
- Update gravity:
pihole -g
NextDNS Integration
- Export in NextDNS JSON format
- Login to NextDNS dashboard
- Go to Denylist → Import
- Upload the JSON file
AdGuard DNS Integration
- Export in AdGuard format
- Access AdGuard DNS admin panel
- Go to Filters → DNS blocklists
- Add custom list with exported content