Web Helper Privacy Policy

Last updated: September 20, 2026. Applies to version 2.0.1.

Purpose and Developer

Web Helper provides page understanding, question answering, and related form-filling assistance using authorized website content, a local knowledge base, and a model service configured by the user. It is maintained by an independent developer. Contact: wangsenyan123@gmail.com.

Data We Process

The extension stores website preferences, model configuration and API keys, imported document text, captured page titles, URLs and text, knowledge-base excerpts, cached answers, feedback, and task state in local browser storage. Chat history is stored in browser session storage and is cleared when the browser closes.

To identify the target of an extension action, it locally updates the most recent web tab's ID, URL, title, window ID and update time on tab activation or page loading. This state is not limited to enabled websites. It is a latest-tab record rather than a complete browsing-history list.

User-initiated requests may include questions, selected text, field information, page excerpts, recent conversation context, knowledge-base excerpts, form-filling input, and attached screenshots. Imported documents and authorized signed-in pages may contain personal or business information.

Model Requests and Sharing

API keys are stored locally and sent to the user-configured endpoint for authentication when fetching model lists, testing connections, or making AI requests. Local storage does not mean these credentials never travel over the network. The extension does not provide an additional encrypted credential vault. Use trusted HTTPS endpoints.

Questions and relevant context are sent directly to the configured model service to fulfill the user's request. Image-capable models can receive attached screenshots when the user submits them. Other models receive available text context instead. The developer operates no data backend for receiving this content. The selected provider's terms govern its processing, retention and deletion of received data.

Form Filling and Sensitive Content

Field-hint icons are off by default and can be enabled per website. Password fields are excluded from filling assistance, and select or combobox controls do not display field-hint icons. Other inputs, including email addresses and phone numbers, may participate in filling assistance.

Text supplied by the user for automatic filling is sent to the selected model without uniform redaction so that it can be used to generate field values. Other text-processing paths attempt redaction, but cannot guarantee removal of every sensitive value. Screenshots are not guaranteed to have sensitive details masked. Only process content you are authorized to share.

Page Capture and Permissions

Page learning and deep capture start when the user activates the corresponding action; an additional confirmation dialog is not guaranteed for each operation. Capture may use the browser's existing signed-in session to read authorized pages. Content scripts are registered for enabled, authorized sites.

Storage permissions support local settings and knowledge bases. Tab access identifies the relevant page, maintains the recent-tab record, opens and closes background capture tabs, and restores the sidebar after initial setup. Scripting enables in-page functionality, context menus provide selected-text questions, and active-tab access supports user-triggered page operations. Unlimited storage accommodates larger local knowledge bases.

The package declares access to api.deepseek.com for users who configure that service. Access to other websites and model endpoints is requested as needed. The current screenshot workflow may request the broad optional <all_urls> permission when the user initiates capture; this optional permission is not granted at installation.

Retention and Control

Local knowledge bases and configuration remain until removed or replaced by the user or cleared with extension data. Cached answers expire after seven days; expired entries may remain stored until extension data is cleared. The latest-tab record is replaced as the relevant tab changes. Screenshots are not automatically archived into the knowledge base.

You can remove knowledge bases and websites and edit or delete model configurations in settings. There is no separate clear-cache button in the current settings screen. Uninstalling the extension removes its browser-managed local data, but does not delete information already received by a model provider. Contact that provider about its deletion procedures.

Limited Use

Data use is limited to the disclosed user-facing purpose, in accordance with the Chrome Web Store User Data Policy, including Limited Use requirements. User data is not sold or used for advertising, profiling, creditworthiness or lending decisions. The developer does not read page content, screenshots, knowledge bases or conversations unless the user voluntarily provides them and consents to troubleshooting. No remote executable code is downloaded as part of model requests.