PRIVACY POLICY FOR SITESEARCH – SEARCH THE CURRENT SITE
Last Updated: October 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. OVERVIEW & COMMITMENT TO PRIVACY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SiteSearch ("the extension", "we", "our") is designed with a strict "privacy-first, local-only" architecture. We believe that privacy is a fundamental human right.
• We DO NOT collect, record, transmit, or monetize any personal data.
• We DO NOT track your browsing habits, history, clicks, or keystrokes.
• We DO NOT run remote analytics, tracking scripts, trackers, or advertisements.
• We DO NOT use external servers or cloud databases. All functionality runs entirely within your local browser.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2. WHAT PERMISSIONS DOES SITESEARCH REQUEST & WHY?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
To deliver the core functionality of searching the current website while maintaining maximum user safety, SiteSearch requests only the following four permissions:
1. `activeTab`
• Purpose: Needed only when the user explicitly interacts with the extension (clicking the toolbar icon or running the context menu command). It grants temporary access to read the URL and hostname of the current tab (e.g., "wikipedia.org") so the extension knows which website domain to search.
• Scope: It only activates on user interaction on the single active tab. It cannot view any other open tabs or background windows.
2. `storage`
• Purpose: Used solely to store your personal user preferences locally inside Chrome's built-in storage (`chrome.storage.sync` / `chrome.storage.local`).
• Scope: Stores your preferred default search engine (e.g., Google or DuckDuckGo), default search scope (root domain vs. subdomain), tab opening behavior, and optional local search history. This data remains on your machine (or within your private Chrome sync account).
3. `contextMenus`
• Purpose: Enables the convenient right-click browser menu items ("Search this site for '%s'").
• Scope: Only triggers when you right-click on a webpage or selected text and choose the menu item.
4. `scripting`
• Purpose: Used strictly in conjunction with `activeTab` to query `window.getSelection().toString()` when you open the popup. This allows the extension to automatically prefill the search field with whatever word or sentence you had highlighted on the page.
• Scope: Executes only upon your click, reads only the highlighted text snippet, and never modifies page contents or injects persistent tracking code.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
3. ARE ALL THESE PERMISSIONS REALLY NECESSARY?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
YES. Every single requested permission is strictly required to fulfill the extension's core features. More importantly, each requested permission represents the absolute LEAST-PRIVILEGED alternative available in Google Chrome (Manifest V3):
• Why `activeTab` instead of broad host permissions (`<all_urls>`)?
Many poorly designed extensions ask for `<all_urls>` or `http://*/*`, which gives them permanent access to read and alter every webpage you visit at all times. SiteSearch NEVER asks for host permissions or `<all_urls>`. By using `activeTab`, SiteSearch has zero access to your browsing until you explicitly click the button, guaranteeing complete safety.
• Why `activeTab` instead of the `tabs` permission?
The generic `tabs` permission would allow reading the URLs and titles of ALL open tabs and windows in your browser, even when you are not using the extension. We deliberately avoided the `tabs` permission to protect your privacy.
• Why is `scripting` necessary?
Under Chrome's Manifest V3 standard, extensions can no longer use legacy content injection mechanisms without the `scripting` permission. When combined with `activeTab`, `scripting` allows reading the user's selected text snippet ONLY on the active tab and ONLY at the moment the user clicks the extension. Without it, automatic prefilling of highlighted keywords would not be possible.
• Why is `storage` necessary?
Without `storage`, the extension would forget your preferences (such as your preferred search engine or tab opening preference) every time you close the popup or restart Chrome.
In summary: No unnecessary, excessive, or risky permissions are requested. SiteSearch is crafted to meet and exceed all Chrome Web Store privacy recommendations and "Featured" badge standards.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4. DATA PROCESSING & TRANSMISSION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
• Search Queries: When you perform a search, the extension constructs a standard web link with the `site:domain.com` query parameter and opens it in your chosen search engine (e.g., Google, DuckDuckGo, Bing). The query is processed directly between your browser and that search engine under their respective privacy policies. No data passes through any intermediary server.
• Search History: If the search history feature is enabled, query history is stored strictly in your local browser storage. You can toggle this feature off or wipe all stored history with a single click in the Settings menu at any time.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
5. THIRD-PARTY SERVICES & SHARING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SiteSearch does not sell, trade, rent, or transfer any user information to third parties, advertising networks, data brokers, or analytics platforms. There are no third-party SDKs, tracking pixels, or remote scripts embedded in this extension.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. CONTACT & INQUIRIES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If you have any questions, suggestions, or feedback regarding this Privacy Policy or the security practices of SiteSearch, please open an issue on the developer repository or reach out via the Chrome Web Store support page.