Effective Date: May 18, 2025
Thank you for using Ultimate CMS Detector for Search (referred to as “the Extension”). This Privacy Policy describes how your information is handled when you use my Extension. I am committed to protecting your privacy and ensuring transparency.
1. Information I Access and Use
The Extension is designed to identify ten popular Content Management Systems (CMS) used by websites found in your Google Search and Google Images results, and, when you choose to use the AI-Powered Detection feature, on other webpages you visit. To provide this functionality, the Extension accesses and processes the following information:
- URLs from Search Results: When you perform a search on Google Search or Google Images, the Extension identifies the URLs of the websites listed in the search results.
- Website Content (HTML): For each URL identified from the search results that the Extension processes, the Extension will make a request to that URL to fetch its HTML content. This HTML content is then analyzed locally within your browser to detect signatures of CMS platforms (like WordPress, Shopify, Wix, etc.) and other web technologies.
- User Configuration Settings: The Extension stores your preferences, such as which specific CMS detectors are enabled, whether the global detection feature is active, and whether image scanning is enabled. It also stores your OpenAI API key if you provide one for the AI-Powered Detection feature, and your selected AI model preference for this feature. These settings are saved locally on your computer using
chrome.storage.local. - Detected CMS Data (Locally): Information about detected CMS platforms (name, confidence, source URL, and detection details) is processed and displayed within your browser. For the Google Images scanning feature, this detected data is temporarily held in your browser’s memory to allow you to view it and optionally export it as a CSV file directly from your browser.
- Remote Configuration File (Selectors): To ensure the Extension can accurately interact with Google Search and Google Images pages as they evolve, it periodically fetches a configuration file (e.g.,
selectors.json) from a trusted, predefined external source (https://markob17.github.io/extension-config/selectors.json). This file contains CSS selectors that help the Extension identify elements on the search results pages. This file is cached locally in your browser to improve performance and reduce requests. - User-Provided OpenAI API Key (for AI-Powered Detection Feature): To use the AI-Powered Detection feature, you must provide your own OpenAI API key. This key is stored locally in your browser’s extension storage (
chrome.storage.local) and is never transmitted to me (the developer of Ultimate CMS Detector). Your API key is used exclusively to authenticate requests made directly from your browser to the OpenAI API when you initiate an AI analysis. - Page Content for AI Analysis (for AI-Powered Detection Feature): When you activate the “Analyze Current Page with AI” feature on a webpage you are viewing, the Extension will collect specific signals from that page’s HTML structure directly from your active tab. This includes: meta tags, script tags (including their
srcattributes), link tags, footer content, HTML comments, attributes of the<html>and<body>tags, a snippet of the body’s inner HTML (up to 1000 characters), and JSON-LD structured data. This extracted information (collectively up to a maximum of 20,000 characters) is then sent, along with your OpenAI API key and the URL of the page you are analyzing, directly from your browser to the OpenAI API to perform the technology detection. I do not store this page content on my server. OpenAI processes this data according to their privacy policy and terms of service. - AI Analysis Results (for AI-Powered Detection Feature): The technology platform and explanation text returned by the OpenAI API are displayed to you within the Extension’s AI floating box interface. To enhance performance and reduce redundant API calls (and potential costs to you), the AI-generated result for a specific website domain is cached locally in your browser’s extension storage (
chrome.storage.local) for 90 days.
2. How I Use Your Information
The information accessed by the Extension is used solely for the following purposes:
- To Provide Core Functionality:
- Fetching website HTML content to analyze and identify the CMS and other technologies used by those websites.
- Displaying the detected CMS information directly on the Google Search and Google Images results pages, and within the Extension’s floating box interface.
- Allowing you to export a list of detected CMS from image search results as a CSV file.
- To Store Your Preferences: Your configuration settings (including your OpenAI API key, if provided) are stored locally so the Extension can function according to your choices.
- Local Processing: All analysis of website content (HTML) for CMS detection occurs locally within your browser. The HTML content of the websites fetched from search results is not sent to my servers or any third-party servers for this core detection purpose.
- To Enable AI-Powered Detection (User-Initiated):
- When you choose to use the AI-Powered Detection feature, your OpenAI API key, your chosen AI model setting, and the extracted page signals from your current webpage are sent directly to the OpenAI API to identify a broader range of web technologies.
- The results from OpenAI are then displayed to you and may be cached locally for the specific domain as described above.
3. Data Storage and Security
- Local Storage: User preferences, your OpenAI API key (if provided), cached AI analysis results for specific domains, and a cached version of the remote configuration file (selectors) are stored using
chrome.storage.local. Data related to detected CMS for CSV export (from image search) is held in browser memory during your session and is not persistently stored by the Extension unless you choose to download the CSV file. - No Server-Side Storage of Fetched Content or User Data: I do not store the HTML content of the websites you visit, the page signals collected for AI analysis, or your OpenAI API key on any remote servers.
- Security: While I do not transmit or store sensitive personal data, I am committed to ensuring that the Extension itself is secure. User settings and your API key stored locally are protected by standard browser security measures provided by
chrome.storage.local. However, no method of electronic storage is 100% secure.
4. Data Sharing and Disclosure
I do not sell, trade, or otherwise transfer any personally identifiable information or the content of the websites fetched by the Extension to outside parties, with the specific exception outlined below for the AI-Powered Detection feature.
- No Third-Party Sharing for Core CMS Detection: The URLs fetched from search results and their HTML content (for non-AI features) are processed locally and are not shared with any third-party services for the purpose of CMS detection.
- Sharing with OpenAI (for AI-Powered Detection Feature):
- If you choose to use the AI-Powered Detection feature, the extracted page signals from your active webpage and your OpenAI API key are sent directly from your browser to OpenAI’s API. This is necessary for the feature to function. OpenAI’s handling of this data is governed by their respective privacy policy and terms of service. We are not responsible for OpenAI’s data practices.
- I, the developer of Ultimate CMS Detector, do not receive or store the data sent to OpenAI or the detailed responses beyond what is displayed to you and cached locally in your browser.
- Future Services (Hypothetical): If I were to introduce features in the future that involve data sharing with third parties (e.g., analytics, premium features requiring account management), I would update this Privacy Policy and provide clear disclosure. Currently, the Extension is self-contained for its core detection features.
5. Your Choices and Rights
- Enabling or Disabling the Extension:
- You can enable or disable the Extension at any time through your browser’s extension management page.
- Configuring the Extension’s Behavior:
- You can configure the Extension’s behavior, including enabling/disabling specific CMS detectors, the overall functionality, and the AI-Powered Detection feature, through the Extension’s options page.
- OpenAI API Key Management:
- You can add, view, update, or remove your OpenAI API key at any time from the Extension’s options page. The AI-Powered Detection feature will not function without a valid API key provided by you.
- AI Analysis Initiation:
- The AI-Powered Detection feature is entirely optional and is only activated when you explicitly click the “Analyze Current Page with AI” button within the extension’s AI interface. You can clear data stored by extensions, including
chrome.storage.localdata (which would include your settings, API key, and cached AI results), through your browser’s settings.
- The AI-Powered Detection feature is entirely optional and is only activated when you explicitly click the “Analyze Current Page with AI” button within the extension’s AI interface. You can clear data stored by extensions, including
6. Permissions Requested by the Extension
The Extension requests the following permissions in manifest.json:
storage: To save your user preferences, OpenAI API key, and cached AI analysis results locally.activeTab: To allow the AI-Powered Detection feature to access the content (URL and HTML signals) of the page you are currently viewing, but only when you initiate an AI analysis on that specific page.scripting: To enable the AI-Powered Detection feature to inject necessary code into your active tab to collect page signals for analysis by OpenAI, only when you initiate an AI analysis.https://www.google.com/search?*: To interact with Google Search and Google Images results pages to display CMS information for the core detection features.https://api.openai.com/: To allow the Extension to communicate directly with the OpenAI API when you use the AI-Powered Detection feature.<all_urls>:- For core CMS detection on Google Search/Images: To fetch the HTML content from any website URL that appears in those results. This permission is essential for detecting the CMS of those sites, as search results can point to any domain. The content is processed locally for this purpose.
- For the AI-Powered Detection feature: To allow the AI analysis interface to be available and function on any webpage you choose to analyze (outside of Google Search/Image pages where it’s excluded).
- For Remote Configuration: To retrieve a necessary configuration file (selectors.json) from a trusted external source (https://markob17.github.io/extension-config/selectors.json) to ensure the Extension works correctly with Google’s page structures and other site interactions if needed.
7. Changes to This Privacy Policy
I may update this Privacy Policy from time to time. I will notify you of any significant changes by updating the policy linked from my Chrome Web Store listing and potentially through an in-extension notification. I encourage you to review this Privacy Policy periodically.
8. Contact Me
If you have any questions or concerns about this Privacy Policy or my data handling practices, please contact me through my Contact Page.