DropSearch
Privacy Policy
This page explains how DropSearch handles selected text, settings, permissions, and optional bug reports.
Core Privacy Statement
DropSearch does not send selected text to the developer, analytics services, ad networks, or any developer-controlled server.
Selected text history is not saved. Text selected inside supported input and textarea fields can be used for search, but password inputs are excluded.
When the user explicitly chooses a search target, selected text may be included in the generated URL and sent to the destination site selected by the user.
Default targets may include Google, Google News, Wikipedia, Weblio, Google Maps, Amazon, Rakuten, YouTube, Shikiho, Kabutan, Minkabu, Nikkei, IRBANK, Kabumap, and other user-configured destination sites.
Examples
- Dropping text onto a Google target may send the query to Google.
- Dropping text onto an Amazon target may send the query to Amazon.
- Dropping a stock code onto a Shikiho, Kabutan, Minkabu, Nikkei, IRBANK, or Kabumap target may send the code to that site.
- Dropping text onto a custom target may send it to the custom URL configured by the user.
Data Stored Locally
DropSearch stores local configuration in chrome.storage.local, including Profiles, Targets, Rules, URL templates, Placeholder definitions, panel position, open behavior, language setting, and imported configuration JSON.
DropSearch does not store browsing history, full page content, input field contents, password input contents, login information, personal identity information, location information, payment information, selected text history, or analytics events.
Permissions
storage is used to save local configuration and runtime settings.
contextMenus is used to provide right-click search commands for selected text.
DropSearch injects content scripts into normal http:// and https:// pages so it can detect selected-text drag operations and show the drop panel. It also uses all_frames so iframe pages can provide the same experience. This access is not used to send selected text to the developer.
Permissions Not Requested
DropSearch does not request tabs, history, webRequest, cookies, downloads, bookmarks, scripting, activeTab, or unlimitedStorage.
External Communication
DropSearch has no developer-controlled external API, no analytics SDK, no ad network, and no tracking service.
The only external communication caused by selected text happens when the user chooses a target and the browser opens the generated URL.
Optional Bug Reports
DropSearch may provide a link to an external bug report form. If you choose to use that form, the information you submit will be sent to Google Forms and may be reviewed by the developer for support and improvement purposes.
Please do not include passwords, personal information, private URLs, or confidential information in bug reports.
Import Safety
When importing configuration, DropSearch validates the config and shows destination origins included in URL templates before saving. Only http: and https: URL schemes are accepted. javascript:, chrome://, and other non-http/https schemes are rejected.
Non-Affiliation
DropSearch is not an official extension from Google, Amazon, Rakuten, YouTube, Wikipedia, Weblio, Toyo Keizai, Kabutan, Minkabu, Nikkei, IRBANK, Kabumap, or any other destination service. Service names are shown only as examples of user-configurable search targets.
Affiliate Policy
DropSearch does not insert affiliate tags into user URLs.