Sever Privacy Policy

Last updated: 2026-05-14

Sever is a local-first content blocker. We design it to minimize data collection and avoid sending browsing data to external services.

What Sever Processes

Sever processes the following data locally in your browser:

• Requested URLs and request metadata needed to decide whether to block or allow a request.
• Filter list metadata and cached compiled filter data.
• User settings (enabled state, list selection, per-site preferences, custom rules).
• Local request logs shown in the Options page.

What Sever Does Not Collect

• No account system.
• No server-side user profile.
• No sale of personal data.
• No remote analytics pipeline for browsing history.

Network Access

Sever may fetch filter list and manifest updates from configured list sources/CDN endpoints. This update traffic is for list maintenance, not user tracking.

Permissions Rationale (high level)

• <all_urls>: required to evaluate and block requests across visited sites.
• webRequest and webRequestBlocking: required for request filtering decisions.
• tabs: required for per-tab status and UI interactions.
• storage: required to persist settings and local cache metadata.
• alarms: required for scheduled list update checks.
• contextMenus: required for extension context actions (for example, element picker workflows).

Data Storage

All settings, counters, and log data are stored locally using browser extension storage APIs.

User Controls

Users can:

• Disable Sever globally.
• Disable Sever per site.
• Clear local logs.
• Change enabled lists and privacy settings.

Contact

Email: supunhg@protonmail.com