Privacy policy
This extension does not collect your data
DySearch has no backend. Everything you would call sensitive — the questions you ask, your groups, prompts, history and API key — is written only to your own browser’s local storage.
Last updated 2026-10-25
What we collect
Nothing. There is no code path in the extension that sends data to a developer server, and no analytics, telemetry or advertising SDK.
The extension has no account system and no backend that could receive data, so there is no channel that could tie a question to who you are.
The page content it can reach is only the part you deliberately search — the text you selected or the current page title, as the permission notes below spell out.
What stays in your browser
All of the following lives in your browser’s local storage (storage.local), on this machine only.
Clear your browser data or uninstall the extension and all of the above disappears with it. We have no copy and nothing to restore from.
A settings backup is handed to you as a single JSON file. Saving and importing it is entirely your decision; it never passes through an intermediary.
- Search groups and the URL templates of custom sites
- The prompt library and quick-site configuration
- Layout preferences and appearance settings such as dark mode
- Search history (can be turned off; once off, no question is recorded)
- The API key you enter for the one-click AI summary
Where the requests go
Only to the destinations you chose yourself. The extension is the one doing the sending, and it keeps nothing.
To the search and AI sites
Questions are sent by your browser directly to each site on the compare page, through the account you are already signed in to. The extension does not proxy those requests, and does not copy the answers it receives into anywhere else.
To your AI provider
The one-click summary uses your own API key. Requests go from your browser straight to the provider you specify, and cost and data terms are governed by the agreement between you and that provider.
The stores and updates
When you install from the Chrome or Edge store, installation and automatic updates are handled by the store. That behaviour falls under the store’s own privacy policy, not this extension’s.
What each permission means for privacy
Every permission exists only to deliver a feature stated on this site. Here they are one by one.
activeTab
Reads the current tab only when you deliberately click the extension icon or start a selection search. No site-wide scanning.
host_permissions: <all_urls>
This is what makes parallel search possible: you need to be able to send a question to any site, including the custom ones you added with a URL template. Having it does not mean something is being uploaded — a request leaves only when you ask to search.
declarativeNetRequest
Handles the sites that refuse to be embedded, so the compare page can embed them anyway. The rules are declared locally, and the extension cannot read the rewritten response content.
storage
Writes groups, prompts, layout and history to your browser’s local storage. That is the only place that data goes.
tabs · windows
Opens and arranges the several site windows on the compare page, which needs tab and window positions and sizes. It is not used to look through your browsing history.
contextMenus · selection
The context menu and the selection bubble take only the text you selected or the current page title, and both entries can be turned off in settings.
alarms
Keeps the scheduled work of the background service worker running. Alarms fire inside your own browser and point at no server.
downloads
Writes the Markdown file you download, and only when you press export yourself.
Content from third-party sites
The answers shown side by side belong to the sites that produced them.
The compare page embeds what those sites return while you are signed in. Each has its own content and privacy policy, and a question you ask on a site is handled by that site under its own policy.
Some sites produce answers containing personal information — a summary of your own earlier conversations, for instance. Whether you use them is your call; the extension does not move that content anywhere else.
Minors
The extension has no account system and builds no user profile, so there is no additional collection of minors’ data to speak of. Whether installation is allowed on a supervised device is decided by that device’s management policy.
Changes to this policy
Last updated 2026-10-25.
If how data is handled changes — any form of data reporting added, for example — this page is changed first, and the release notes in the repository say so too.
The extension is released under GPL-3.0: every read or write of local storage, and the target of every network request, can be read in the source. That is a stronger guarantee than the words on this page.
Contact
If you doubt why a permission is necessary, or find a data flow that does not match this page, say so.
Open an issue in the repository with your browser, the extension version and the exact situation. The repository address and version number are still placeholders on this site.
This page covers only what the extension itself does with data. Each AI and search site, and the browser stores, have their own policies — please read them where they live.