Privacy Policy

Last updated: April 2026

Anonymous Usage Analytics

IronCurtain collects the following anonymous data to help understand how the extension is used and where to focus improvements:

• Random install ID — a randomly generated identifier with no connection to your identity, browser profile, or Google account
• Extension version — so we know which version is in use
• Block counts by category — aggregate counts of how many popups, overlays, ad scripts, redirects, etc. were blocked (e.g., "12 popups blocked today"). No URLs, site names, or page content are included
• Whitelist count — the number of sites you've whitelisted (not the site names themselves)
• Top blocked hostnames — the hostnames (domain names only) of sites where blocks occurred, along with block counts. This is sent as a separate anonymous request with no install ID, so it cannot be linked to any individual user

This data is sent once per day as an anonymous usage summary. It contains no personally identifiable information and cannot be used to identify you.

Opting Out

You can disable analytics at any time using the toggle at the bottom of the IronCurtain popup. When disabled, no data is collected or transmitted. The extension continues to function normally.

Issue Reports

If you choose to submit an issue report via the popup, the following is sent:

• The hostname (domain only, not full URL) of the site where the issue occurred
• Your written description of the problem
• The recent block log for that tab (block reasons only, no page content)
• Your anonymous install ID and extension version

Issue reports are voluntary and user-initiated. Nothing is sent without you clicking "Send."

What We Do NOT Collect

IronCurtain does not collect:

• Browsing history or page URLs (except domain-only hostnames in voluntary issue reports)
• Page content, cookies, or form data
• Personally identifiable information
• Data used for cross-site tracking or fingerprinting

We do not use IP addresses for tracking, identification, or analytics purposes. Note that our hosting provider may temporarily process IP addresses in standard server logs for security and operational purposes.

Network Requests

IronCurtain makes two types of outbound requests:

• Anonymous usage summaries — sent once per day (unless disabled)
• Issue reports — only when you manually submit a report

Ad blocking itself uses Chrome's built-in declarativeNetRequest API and does not require external requests.

Local Storage

The extension uses Chrome's storage APIs to store:

• Enabled/disabled state (boolean)
• Whitelisted sites (hostnames you manually add)
• Analytics opt-out preference (boolean)
• Random install ID (generated once and stored locally)
• Daily block counters (reset after each summary is sent)

Permissions

The extension requests the following permissions:

• activeTab — to access the current tab for the popup display and whitelist functionality
• scripting — to inject logic that detects and removes intrusive overlays
• storage — to save preferences and anonymous counters
• tabs — to track block counts per tab and update the badge
• alarms — to schedule the daily usage summary
• declarativeNetRequest — to block requests to known ad and popup domains
• host_permissions: <all_urls> — required to detect and remove intrusive overlays, popups, and scripts across websites. All processing occurs locally, and no page content is collected or transmitted

Third-Party Services

Telemetry and issue reports are sent only to IronCurtain's own servers. No third-party analytics services (such as Google Analytics or Mixpanel) are used.

Changes to This Policy

If this policy changes, the updated version will be published here with a revised date. Material changes will be noted in the extension's changelog.

Contact

For questions about this privacy policy, contact: ironcurtainapp@gmail.com