CyberPeace Privacy Policy

CyberPeace · Privacy

CyberPeace Privacy Policy

CyberPeace Browser Extension  ·  Effective: June 6, 2026  ·  Version 0.13.1

← Back to CyberPeace

🚫

CyberPeace Collects Zero Personal Data

The CyberPeace extension never transmits any information to Secrecy Evolution or any third party. All processing happens locally inside your browser. Nothing leaves your device.

1. What This Policy Covers

This Privacy Policy covers the CyberPeace browser extension for Google Chrome and Microsoft Edge, developed and maintained by Secrecy Evolution Inc. It applies to all versions of CyberPeace, starting from v0.1.

This policy does not cover the Secrecy Evolution website (secevol.com), which has its own Privacy Policy, or any third-party websites that CyberPeace helps you browse more privately.

CyberPeace is free and open source. The source code is publicly available at github.com/SatvirMatharu/cyberpeace. Anyone can independently verify every claim in this policy by reading the code.

2. What CyberPeace Does NOT Do

We want to be completely explicit. CyberPeace:

  • ❌ Does not collect your browsing history
  • ❌ Does not record what websites you visit
  • ❌ Does not collect your search queries
  • ❌ Does not collect your IP address
  • ❌ Does not track clicks, sessions, or time on site
  • ❌ Does not require an account or email address
  • ❌ Does not send any data to Secrecy Evolution servers
  • ❌ Does not sell, share, or monetise any data
  • ❌ Does not use advertising or analytics SDKs
  • ❌ Does not phone home to check for updates (updates go through the browser store)

3. What CyberPeace Accesses & Why

CyberPeace reads certain browser APIs to perform its privacy protection functions. This is entirely local — no data leaves your device.

What is accessed Why Sent anywhere?
Page URLs (current tab) To apply URL parameter stripping and trust-level rules for that domain No — processed locally only
Network requests (declarativeNetRequest) To match requests against 82,413 blocking rules before they are sent No — Chrome blocks matching requests before they leave the browser
Canvas, WebGL, AudioContext APIs To randomise fingerprinting outputs on the current page No — values are modified locally
Navigator properties (screen, timezone, WebRTC) To reduce fingerprint entropy and block local IP exposure No — modified locally before any page script can read them
Extension local storage To remember per-site trust levels you set No — stored in browser local storage only
declarativeNetRequest rule count To display the blocked tracker count badge on the extension icon No — read from Chrome’s internal API, displayed locally

4. Local Storage

CyberPeace stores the following information in your browser’s local extension storage (not on any server):

  • Per-site trust levels: If you whitelist a domain, that preference is saved locally so CyberPeace remembers it on future visits.
  • Extension settings: Any settings you configure in the popup are stored locally.

This data never leaves your browser. It is not synced to any cloud service, Secrecy Evolution, or any third party. You can clear this data at any time by removing the extension or clearing your browser’s extension storage.

5. Network Requests

CyberPeace makes zero outbound network requests from its popup, background service worker, or content scripts. It does not connect to any API, server, or external service at runtime.

The only external connections associated with CyberPeace are:

  • Chrome Web Store / Microsoft Edge Add-ons: Your browser may automatically check for extension updates through the store. This is standard browser behaviour handled entirely by Google or Microsoft, not by CyberPeace code.
  • GitHub: If you visit the GitHub repository, GitHub’s own Privacy Policy applies.

🔎 You can independently verify this claim. Open Chrome DevTools → Network tab → filter by the CyberPeace extension ID. You will see zero requests initiated by the extension at runtime.

6. Permissions Explained

CyberPeace requests the following browser permissions. Each is required for a specific, stated purpose:

Permission Why it is needed
declarativeNetRequest Required to apply the 82,413 network-level blocking rules that stop trackers before they load. This is Chrome’s privacy-first API for ad/tracker blocking.
storage Required to save your per-site trust level preferences locally in your browser.
tabs Required to read the current tab’s URL so CyberPeace can apply per-domain trust levels correctly.
scripting Required to inject the fingerprint shield and URL parameter stripping scripts into page contexts.
webNavigation Required to detect navigation events so fingerprint randomisation is applied consistently on every page load.
host_permissions: <all_urls> Required for network-level blocking to work across all websites. Without this, the extension can only block on specific domains you pre-list.

No permission is requested beyond what is functionally necessary. CyberPeace does not request permissions to read your cookies, bookmarks, passwords, or any stored credentials.

7. Third-Party Services (GitHub)

CyberPeace’s source code is hosted on GitHub. If you visit github.com/SatvirMatharu/cyberpeace to view the code, submit issues, or contribute, GitHub’s own Privacy Policy applies to that interaction. GitHub is operated by GitHub Inc., a subsidiary of Microsoft. Their Privacy Policy is available at docs.github.com.

Secrecy Evolution does not receive any personal data about GitHub visitors or contributors through our GitHub repository.

8. Open Source Verification

Every privacy claim in this policy can be independently verified by reading the CyberPeace source code:

  • No analytics library is imported or used
  • No fetch() or XMLHttpRequest calls are made from background.js or popup.js
  • The manifest.json contains no external service URLs or analytics endpoints
  • All data written to chrome.storage is limited to trust-level preferences

📄 View the source: github.com/SatvirMatharu/cyberpeace — every file is public and readable.

9. Children’s Privacy

CyberPeace does not collect any personal information from anyone, including children. Because we collect nothing, there is no special risk to users under 18. The extension is safe for use by anyone with a compatible browser.

10. Changes to This Policy

If we make changes to CyberPeace that affect its data practices, we will update this policy and the extension version number. Material changes will be noted in the GitHub repository changelog.

Because CyberPeace collects no data, the likelihood of meaningful policy changes is low. Any future version that changes data collection practices will go through a full security review and public changelog entry before release.

11. Contact

Questions, concerns, or feedback about CyberPeace privacy can be sent to:

Satvir Matharu
Secrecy Evolution Inc.
info@secevol.com
+1 (365) 333-2377

Bug reports and feature requests are also welcome on GitHub Issues.

Try CyberPeace

Free, open source, zero telemetry. Every claim in this policy is verifiable in the code.

📄 View on GitHub — Free