Privacy — Zozimus Technologies

TL;DR

Our extensions run 100% locally. We have no servers, no analytics, and no idea who you are.

✓ No data collection ✓ No accounts ✓ No analytics ✓ No cookies ✓ Works offline

🔒

100% Local Processing

All data stays in your browser’s local storage. We never transmit anything to any server.

🚫

Zero Tracking

No Google Analytics, no Mixpanel, no telemetry, no beacons. We don’t measure anything about you.

📦

No External Requests

Our extensions make zero network requests. No CDNs, no APIs, no remote resources of any kind.

👀

Fully Auditable

All source code is unminified and public on GitHub. Read every line yourself.

How we compare

Practice	Zozimus	Typical Extensions
Collects usage data	Never	Often
Requires account	No	Usually
Sends data to servers	No servers	Yes
Uses cookies	Never	Frequently
Open source	Always	Rarely
Works offline	Fully	Partially

Permissions explained

We only request what’s strictly necessary. Here’s why each permission exists:

storage Save your settings and data locally inside your browser. Never synced externally.
sidePanel Display the extension interface in the browser’s side panel.
declarativeNetRequest Used by Site Blocker to block/redirect websites at the network level — handled entirely by the browser.
activeTab / all_urls Apply blocking rules or scan page content. Only activated when you explicitly use the extension.
contextMenus Used by Image Editor to add a right-click “Edit image” option on web pages.

What data do we store?

Only what you explicitly create, and only in your browser’s local storage:

Your blocklist (Site Blocker) — the domains you choose to block
Your settings — toggle states, preferences you configure
Nothing else. No history, no profiles, no identifiers

Changes to this policy

If we ever change our privacy practices, we’ll update this page and note the changes in our GitHub commit history. Since our extensions are open source, any change is publicly auditable.

Last updated: April 2026

Verify it yourself

Don’t take our word for it. Here’s how you can confirm our privacy claims:

Read our source code on GitHub
Open DevTools Network tab — you’ll see zero outgoing requests
Search the codebase for “fetch”, “XMLHttpRequest”, or any URL — you won’t find external calls
Check Application → Storage in DevTools to see exactly what’s stored