Privacy Policy for Bulk Link Editor Chrome Extension

Last Updated: April 26, 2025

Thank you for using Bulk Link Editor (the "Extension"). This Privacy Policy explains how information is handled when you use our Chrome Extension. We are committed to protecting your privacy.

1. Information We Collect (and Don't Collect)

Bulk Link Editor is designed to operate primarily on your local machine and within your browser.

• We DO NOT Collect Personally Identifiable Information (PII): The Extension does not collect, store, or transmit any personal information such as your name, email address, physical address, location, authentication credentials, financial information, or web browsing history related to its core linking functionality.
• Website Content Interaction: To perform its core function, the Extension needs to interact with the content of the web page you are currently viewing when you activate the extension. This involves:
  • Detecting the type of editor (e.g., WordPress Classic, Gutenberg) present on the active page.
  • Reading the text and HTML structure within the detected editor to find keywords/phrases you specify.
  • Modifying the HTML structure within the editor to add, replace, or remove hyperlinks as requested by you.
  This interaction only happens on the active tab when you explicitly invoke the Extension via its toolbar button and only affects the content within the editor area.
• Locally Stored Data (via chrome.storage API):
  • Keyword/URL List (chrome.storage.local): If you use the "Bulk Add List" feature, the keyword and URL pairs you save are stored locally on your computer using the chrome.storage.local API. This data persists across browser sessions but is stored only on your device and is not transmitted to us or any third party.
  • Session Data (chrome.storage.session): To improve user experience, the values you temporarily enter into the Extension's popup form (Keyword/Phrase, URL, checkbox states) may be stored using the chrome.storage.session API. This data is automatically cleared when your browser session ends (e.g., when you close the browser) and is only used to restore the form state if the popup is accidentally closed. This data is not transmitted.
• Anonymous Usage Data: We do not currently collect anonymous usage statistics or analytics.

2. How We Use Information

The limited information the Extension interacts with is used solely for the following purposes:

• To Provide Core Functionality: Reading and modifying website content within the editor is necessary to add, replace, or remove links as requested by the user. Detecting the editor type allows the Extension to use the appropriate modification method.
• To Store User Configuration: Storing the keyword/URL list locally allows users to reuse their bulk lists efficiently.
• To Improve User Experience: Temporarily storing form state prevents data loss if the popup closes unexpectedly during use.
• To Manage Pro Features: If you upgrade to the Pro version, information related to your purchase status (provided by the Chrome Web Store) may be used locally within the extension to unlock Pro features.

3. Permissions Justification

The Extension requests the following permissions, which are necessary for its operation:

• activeTab: Grants temporary access to the currently active browser tab only when the user clicks the extension icon. This allows the extension to run on the specific page the user intends without needing broad, persistent access.
• scripting: Allows the extension to inject its JavaScript code into the active tab (when access is granted by activeTab) to interact with the page's content editor.
• storage: Allows the extension to use chrome.storage.local and chrome.storage.session to save the user's keyword/URL list and temporary form state locally on the user's computer.
• <all_urls> (Host Permission): This permission is required because the Extension needs to function on potentially any website where a user might be editing content (e.g., any self-hosted WordPress site). This permission is used in combination with activeTab, ensuring the extension only attempts to run its scripts on the specific page the user is viewing after they have clicked the extension icon. It does not grant automatic access to all sites.

4. Data Sharing and Third Parties

We do not sell, trade, or otherwise transfer any user data (including website content interacted with or locally stored data) to outside parties or third parties for purposes unrelated to the Extension's core functionality or payment processing. All processing and storage related to the core linking features happen locally within your browser.

Payment Processing: If you choose to upgrade to the Pro version of Bulk Link Editor, the payment transaction will be processed securely through Chrome Web Store Payments. We do not receive or store your full payment details (like credit card numbers). The transaction is handled directly by Google according to their applicable terms and privacy policies. Information necessary to validate your Pro status (such as an entitlement status provided by Google) may be associated with your Google account used for the purchase but is not shared further or used for other purposes by this Extension.

5. Data Security

Data stored locally by the Extension (keyword/URL lists) is protected by the security measures of your browser and operating system. Since no data is transmitted to external servers for the core functionality, the risk associated with data breaches is minimized. Purchase-related information is handled by Google's secure systems.

6. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date. You are advised to review this Privacy Policy periodically for any changes.