================================================================================
PRIVACY POLICY - STACKLENS TECHNOLOGY PROFILER
================================================================================
Last Updated: October 27, 2026
StackLens ("we", "our", or "the extension") is committed to protecting your privacy. This Privacy Policy details how StackLens handles information, clearly explains why specific browser permissions are requested, and addresses how our minimal-permission architecture guarantees that your browsing habits remain strictly confidential.
--------------------------------------------------------------------------------
1. OUR PRIVACY-FIRST PHILOSOPHY
--------------------------------------------------------------------------------
• ZERO Personal Data Collection: We do not collect names, email addresses, IP addresses, credentials, or browsing history.
• ZERO Remote Servers: StackLens operates 100% on-device. The extension does not maintain any external backend or tracking servers, and your visited URLs are never sent over the internet.
• ZERO Tracking & Analytics: We do not include third-party tracking scripts, telemetry, analytics SDKs, or advertising networks inside the extension.
• ZERO Data Monetization: We never sell, rent, monetize, or disclose your browsing activity to any third party.
--------------------------------------------------------------------------------
2. DETAILED EXPLANATION OF REQUESTED PERMISSIONS
--------------------------------------------------------------------------------
StackLens requests the absolute bare minimum set of browser permissions necessary to analyze website technology stacks. Below is a transparent breakdown of why each permission is required:
1. "activeTab"
• What it does: Grants temporary, on-demand access to the currently active browser tab when you click the StackLens icon in your toolbar.
• Why it is needed: When you open the popup, StackLens must read the current tab's hostname and title to perform the technology scan for that specific site.
• User Benefit: Access is strictly temporary and terminates automatically when you close the popup or switch tabs.
2. "scripting"
• What it does: Allows the extension to run a client-side inspection script in the context of the active webpage.
• Why it is needed: To identify web technologies, StackLens must inspect DOM elements (such as <meta name="generator"> tags), external script sources (e.g. React, Next.js, or Shopify libraries), and public JavaScript global objects.
• User Benefit: The script runs entirely in memory within your browser session and discards analyzed results once the popup is closed.
3. "storage"
• What it does: Grants access to Chrome's local storage API (chrome.storage.local).
• Why it is needed: Saves your local visual preferences (e.g. dark/light theme, toggle for the icon badge counter) and locally caches recent scan counts.
• User Benefit: Data stays exclusively on your local computer and is never synced to external servers.
--------------------------------------------------------------------------------
3. ARE ALL THESE PERMISSIONS STRICTLY NECESSARY? (PERMISSION MINIMIZATION)
--------------------------------------------------------------------------------
YES. Every single permission listed in StackLens has been audited and narrowed down to adhere to the Principle of Least Privilege:
• Why we DO NOT request "<all_urls>" or Broad Host Permissions:
Many competing extensions request permanent access to read all websites you visit in the background (`<all_urls>` or `*://*/*`). StackLens deliberately avoids this invasive permission. Instead, we use `activeTab`, which means the extension cannot see, read, or interact with any website until you explicitly click the extension button.
• Why we DO NOT request "webRequest" or Network Interception:
StackLens does not intercept or alter your network traffic or HTTP requests. All technology identification is achieved via safe, non-invasive DOM and resource timing inspection.
• Why we DO NOT request "cookies" permission:
StackLens does not access your sensitive session cookies or login authentication tokens. It only reads public DOM indicators and standard frontend framework globals.
• Why we DO NOT request "history" or "bookmarks":
StackLens has zero interest in your past browsing records, browsing history, or bookmarks.
In summary: No unnecessary permissions exist in StackLens. If an optional feature was deemed non-essential to core technology detection, it was excluded from the manifest.
--------------------------------------------------------------------------------
4. HOW INFORMATION IS PROCESSED
--------------------------------------------------------------------------------
When you click on StackLens while visiting a website:
1. StackLens executes a client-side scanner script inside your local browser tab.
2. The scanner inspects public HTML tags, script URLs, stylesheets, and JavaScript library names on that specific page.
3. The scanner cross-references those indicators against a local, built-in dictionary of open-source and commercial web technologies.
4. The matching technology names, categories, and version numbers are displayed inside the popup.
5. All calculations happen inside your local computer's memory. No external API calls are made.
--------------------------------------------------------------------------------
5. DATA RETENTION AND DELETION
--------------------------------------------------------------------------------
StackLens does not operate a database of users. Any preferences saved in Chrome's local storage (such as theme choice) remain on your local disk until you clear your browser cache or uninstall the extension. Uninstalling StackLens immediately and permanently removes all associated local configuration data.
--------------------------------------------------------------------------------
6. CHANGES TO THIS PRIVACY POLICY
--------------------------------------------------------------------------------
We may update this Privacy Policy from time to time to reflect technical enhancements or regulatory updates. Any changes will be posted alongside extension updates in the Chrome Web Store.
--------------------------------------------------------------------------------
7. CONTACT US
--------------------------------------------------------------------------------
If you have questions, feedback, or security inquiries regarding this Privacy Policy or the permissions utilized by StackLens, please contact us via the official Chrome Web Store support page or project repository.