Privacy Policy for Source Code Viewer Extension

Last Updated: 5/29/2025

This Privacy Policy describes how "Source Code Viewer" (the "Extension") handles information when you use it. Your privacy is important to us, and this policy aims to be transparent about our practices.

1. Information We Access (Not Collected or Stored Long-Term)

The Extension needs to access certain content from the web pages you visit to fulfill its core function. Specifically, when you activate the Extension on a webpage, it will access:

  • The HTML source code of the page.
  • The URLs of external CSS and JavaScript files linked by the page.
  • The content of these external CSS and JavaScript files.
  • The content of inline CSS (using the word 'style' in tags) and JavaScript (using the word 'script' in tags) blocks.

This information (collectively, "Website Content") is accessed ONLY when you explicitly click the Extension icon to inspect the current active page. The Extension does not access any information automatically or in the background without your direct interaction.

2. How We Use Accessed Information

The Website Content accessed by the Extension is used SOLELY for the following purposes:

  • To display the HTML, CSS, and JavaScript source code within the Extension's popup interface for your viewing.
  • To allow you to copy parts of this displayed code to your clipboard.

The Extension DOES NOT:

  • Store this Website Content persistently. It is only held in your computer's memory for the duration of your interaction with the popup on that specific page. Once the popup is closed or you navigate away, this information is discarded from memory.
  • Transmit this Website Content to any external server or third party. All processing and display occur locally within your browser.
  • Collect, store, or transmit any Personally Identifiable Information (PII). The Extension is designed to be entirely client-side and does not have the capability to identify or track individual users.
  • Track your browsing history or user activity beyond the immediate interaction of fetching and displaying code for the active page when requested by you.

3. Permissions

The Extension requires the following permissions in Google Chrome (and similar Chromium-based browsers) for the reasons stated:

  • activeTab: This permission allows the Extension to identify the current page you wish to inspect when you click the extension icon. It grants temporary access to the active tab only upon your explicit interaction (clicking the extension icon) and does not provide general access to your tabs or browsing history.
  • scripting: This permission is necessary to inject a content script into the active page. This script is responsible for reading the page's source code (HTML) and identifying linked resources (CSS, JavaScript) so they can be fetched and displayed.
  • host_permissions (): This permission is required to allow the injected script to fetch the content of external CSS and JavaScript files from any domain. Web pages often link to resources hosted on various Content Delivery Networks (CDNs) or different servers than the main page itself. Without this permission, the Extension would be unable to retrieve and display these essential parts of the source code. This permission is used ONLY when you activate the extension to fetch these resources for display and not for any other purpose.

We are committed to requesting only the minimum permissions necessary for the Extension to function as described.

4. Data Security

Since no user data or website content is stored persistently by the Extension or transmitted externally to any servers, the security of your information primarily relies on the security measures of your own browser and computer system. The Extension operates entirely within the sandboxed environment provided by your browser.

We encourage you to keep your browser and operating system updated to benefit from the latest security patches and protections.

5. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. We will notify you of any significant changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top. Minor changes or clarifications may be made without a formal announcement other than updating the date.

You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

6. Contact Us

If you have any questions, concerns, or suggestions about this Privacy Policy or the Extension's practices, please feel free to contact us. You can reach out via:

We value your feedback and are committed to addressing any concerns you may have.