Overview

Extension Bridge is committed to protecting your privacy. This privacy policy explains how our Chrome extension handles data and what information is accessed during normal operation.

Our Privacy Commitment

What Data Does Extension Bridge Access?

Extension Bridge accesses the following data locally in your browser to provide its core functionality:

Chrome Extension Information

The extension reads your installed Chrome extensions list, including:

• Extension names
• Extension descriptions
• Extension IDs
• Extension icons and metadata

Important: This data is processed entirely locally in your browser and is never transmitted to any external server or third party. The extension only accesses this information when you explicitly click the "Scan Extensions" button.

External API Usage

Mozilla Firefox Add-ons API

Extension Bridge makes requests to Mozilla's public Firefox Add-ons API (https://addons.mozilla.org/api/) to search for and retrieve publicly available Firefox addon information.

What Data is Received from Mozilla?

Mozilla's API returns publicly available information about Firefox add-ons, including:

• Add-on names and descriptions
• Developer/publisher information
• User ratings and review counts
• Download counts
• Add-on URLs and icons

This is all public data that anyone can access through Mozilla's website.

Local Storage

Extension Bridge uses Chrome's local storage API to cache search results and store user preferences:

Cached Search Results

• Firefox add-on search results are cached locally for 24 hours
• This improves performance by avoiding redundant API calls
• You can manually clear cached data in the extension settings

User Preferences

• Dark mode preference
• Extension settings and configurations
• Ignored extensions list (if you choose to ignore certain extensions)

All data is stored locally in your browser only. It never leaves your device and is not synchronized or backed up to any external servers.

Permissions Explained

Extension Bridge requires the following permissions:

1. Management Permission

Why needed: To read the list of your installed Chrome extensions.
How used: Only when you click "Scan Extensions" to find Firefox alternatives.
Data collected: None - data is processed locally only.

2. Storage Permission

Why needed: To cache Firefox addon search results locally.
How used: Stores API responses for 24 hours to improve performance.
Data collected: None - only caches public Firefox addon information.

3. Host Permission (addons.mozilla.org)

Why needed: To fetch publicly available Firefox addon information.
How used: Makes API requests to Mozilla's public addon database.
Data sent: Only search terms (extension names).

Third-Party Services

Extension Bridge only communicates with one external service:

• Mozilla Firefox Add-ons API - For retrieving publicly available Firefox addon information. Mozilla has its own privacy policy available at mozilla.org/privacy.

We do not use any analytics services, advertising networks, or tracking services.

Data Security

Since Extension Bridge does not collect or transmit personal data, there is minimal security risk. However, we follow best practices:

• All external API requests use HTTPS encryption
• All data processing happens locally in your browser
• No authentication tokens or credentials are stored
• The extension follows Chrome's security best practices and Manifest V3 standards

User Control

You have complete control over Extension Bridge:

• Clear Cache: Use the extension settings to clear all cached data
• Revoke Permissions: Chrome allows you to remove extension permissions at any time
• Uninstall: Uninstalling the extension removes all locally stored data
• Review Code: The extension is source-available on GitHub for transparency

Children's Privacy

Extension Bridge does not collect any personal information from anyone, including children under 13. The extension is safe for all ages.

Changes to This Privacy Policy

We may update this privacy policy from time to time. Any changes will be posted on this page with an updated "Last Updated" date. Continued use of Extension Bridge after changes constitutes acceptance of the updated policy.

Open Source & Transparency

Extension Bridge is source-available software. You can review the code on GitHub to verify our privacy practices: github.com/michaelnyc17/extension-bridge

Compliance

Extension Bridge complies with:

• Chrome Web Store Developer Program Policies
• Chrome Web Store User Data Policy
• General Data Protection Regulation (GDPR) principles
• California Consumer Privacy Act (CCPA) requirements