Privacy Policy for Browser Extensions (浏览器扩展隐私政策)

0. Scope and Introduction 适用范围与简介

English: This Privacy Policy ("Policy") applies to each browser extension and related service published by us that links to this page. In this Policy, "Extension" means the specific extension from whose store listing, installation flow, settings page, or user interface you accessed this Policy. A provision concerning a particular feature applies only when the Extension includes or uses that feature. More specific privacy disclosures shown inside the Extension supplement this Policy.

Where applicable law or a browser store policy requires separate notice or consent, the Extension will provide that notice or request through its user interface or the browser's permission system before the relevant collection or transmission begins. Declining an optional permission may disable the related optional feature.

Content responsibility notice: If the Extension provides access, extraction, search, download, export, or processing tools for third-party content, this Policy describes data handling only. It does not grant or confirm any right to access, crawl, download, copy, use, or distribute third-party content. Users independently select the target, scope, frequency, content, and purpose of each operation and are responsible for obtaining any required authorization and complying with applicable laws and target-site rules.

0.1 Feature-Based Applicability 按功能确定适用条款

English: The Extension may contain one or more of the feature categories below. Features not present in the Extension do not cause the corresponding data handling to occur.

Feature Category	Data Used	Where Processing Occurs
Local utilities and settings	User preferences, locally created records, task state, and other settings needed for the displayed feature	On the user's device
Webpage or media processing	Relevant page structure, text, resource URLs, images, videos, or identifiers needed to perform a user-requested action	Primarily on the user's device; disclosed online actions are described in Section 3
QR code creation, recognition, and export	User-entered text or URLs; current-page or selected open-tab URLs, titles, and favicons; optional logo and style settings; user-selected local or webpage images; and locally decoded QR code results	On the user's device as described in Section 0.2; a webpage image may be requested directly from its source only when the user invokes image recognition, and limited remote configuration requests are described in Sections 0.2 and 3.8
New Tab or local workspace	Local records, shortcuts, bookmarks, top sites, browser history, search input, favicons, and workspace preferences	Primarily on the user's device; user-submitted searches and optional weather requests are described in Section 3
History management, sessions, and local time tracking	History URLs, titles, visit times and counts; active-tab URLs; visit-session timestamps and durations; active, idle, and media-playback state; and recently closed or device-session information	On the user's device; time tracking begins only after the required optional browser permissions are granted
Technical and interaction analytics	A random installation identifier, environment information, limited feature activity, aggregated main-domain statistics, and sanitized error reports	Locally and, when enabled or permitted, on our analytics server
User-initiated online features	The search term, selected image, page or product identifier, URL, or other input required to complete the requested action	Sent to the relevant service only when the user initiates the feature
Feedback and support	Email address, message, request category, Extension version, installation date, and an optional user-selected screenshot	Sent to our support submission server only when the user submits the form
AI-assisted features	User-submitted messages and the conversation context needed to generate a response	Sent to the identified AI service only when the user uses the feature
Online weather	A selected city, coordinates, or an approximate location	Sent to the weather or location providers described in Section 3.4 after the feature is enabled

0.2 QR Code Creation, Recognition, and Export 二维码生成、识别与导出

English: This subsection applies only when the Extension provides QR code creation, recognition, styling, copying, or export features. It is intended to give browser-store reviewers and users a direct, feature-specific description of the QR code tools while all other provisions of this Policy remain in effect according to the feature-based scope above.

• Local QR code generation: The Extension may use text or URLs entered by the user, the URL and title of the current or user-selected open tab, a favicon displayed in the interface, optional user-selected logo image data, and QR style or output settings to create individual or batch QR codes. QR rendering is performed on the user's device with code bundled in the Extension. The QR content, logo, style, and generated image are not uploaded to us or to a third-party QR generation service.
• Local QR code recognition: The Extension may process image files that the user selects or drops into the Extension and webpage images for which the user actively invokes the QR recognition command. Image pixels and decoded results are processed on the user's device with a decoder bundled in the Extension. If the browser cannot read the pixels of the copy already displayed by a webpage, the Extension may request the image bytes directly from the image's original resource URL with website credentials omitted. The Extension does not upload the selected image, its pixels, or the decoded result to our servers or to a third-party recognition service.
• Current-page, open-tab, and webpage integration: Where included, the Extension uses browser permissions and APIs only for its disclosed QR code workflow: activeTab and tabs obtain the current page or user-selected open-tab URL, title, and favicon; webNavigation detects URL changes needed to refresh a QR code for a single-page application; contextMenus exposes user-invoked QR actions; scripting injects the bundled image decoder and result panel when the user requests webpage-image recognition; downloads saves generated or exported files; storage saves local settings and cached configuration; and alarms schedules configuration checks. A bundled content component may run on ordinary HTTP or HTTPS pages to display a configured QR shortcut and return the page URL and title to the Extension interface. These integrations are not used to read passwords, authentication cookies, page form entries, or unrelated page content, and are not used to create an advertising or browsing profile.
• Clipboard, files, and navigation: Copy actions write a generated QR image or recognized text to the clipboard only after the user activates the corresponding control; the QR feature does not read existing clipboard content. Download and export actions create files through the browser's download mechanism only at the user's direction. If the user chooses to open a URL contained in a recognized QR code, the browser navigates to that destination and the destination then handles the resulting network request under its own terms and privacy policy.
• Local storage and temporary state: Saved styles, an optional logo included in a saved default style, output settings, floating-button position, and validated configuration cache may be retained in Extension-scoped local storage. User-entered QR content, batch input, selected scan files, and scan results are otherwise held for the active interface session and are not intentionally persisted by the QR feature unless the user chooses to copy, download, or export the result.
• Remote configuration only: The QR code Extension may retrieve JSON configuration for its floating shortcut and context-menu behavior from https://addp.yueding168.com/ over HTTPS and cache the validated configuration locally. The configuration request does not include user-entered QR content, selected images, decoded results, current-page or open-tab URLs and titles, browsing history, or downloaded files. Retrieved configuration is treated only as structured feature and interface data and is not executed as remote JavaScript, WebAssembly, or other remotely hosted executable code. Standard network metadata associated with the request is addressed in Section 3.8.

1. Information Handled 数据处理

1.1 Data Processed Locally 本地处理的数据

English: Depending on the features included in the Extension, the following information may be accessed or stored locally:

• Preferences and local records: Interface settings, feature settings, shortcuts, dismissed notices, recent records, processing task state, and other information required to restore the user's local workspace.
• Page and media data: Page structure, visible content, media URLs, images, videos, and related identifiers needed to identify, preview, process, or download resources requested by the user.
• QR code inputs and outputs: Where the QR feature described in Section 0.2 is present, user-entered content, current-page or selected open-tab metadata, optional logo and style settings, selected image pixels, generated QR images, and decoded results are processed locally for the requested creation, recognition, copy, download, or export operation.
• Bookmarks and top sites: Used only for user-facing bookmark organization, shortcuts, or local site suggestions when those features are present. This data is not uploaded to our analytics server.
• Browser history: When the Extension includes a history feature and has the required browser permission, it may locally read page titles, URLs, visit times, visit counts, and related history identifiers to display, search, export, or manage history. At the user's direction or under user-configured blacklist, retention, and cleanup rules, the Extension may also delete matching entries from the browser's own history. This data is not uploaded to our analytics server.
• Local time tracking: If enabled and granted the required optional permissions, the Extension may locally record active-tab URLs, visit-session start and end times, calculated duration, active or idle state, and whether media is playing. These records are used only to provide local activity and time-analysis features and are not uploaded to our analytics server.
• Tabs and browser sessions: When the relevant feature is present, the Extension may locally display active or recently closed tabs and sessions from the browser, including device name, tab title, URL, and favicon, and may reopen tabs selected by the user. This information is not uploaded to our analytics server.
• Search and favicons: Search input is used when the user submits a search. Favicons are used to display site icons and are not used to track browsing paths.
• Weather cache: When online weather is enabled, the selected location and returned weather information may be cached locally.
• Feedback preferences: If a feedback feature is present, an email address previously submitted by the user and a limited local submission counter may be saved locally to prefill the form and prevent excessive submissions.

1.2 Data Transmitted When the Relevant Feature Is Used 使用相应功能时传输的数据

English: Only when the relevant feature is included, enabled, permitted, or actively used, the Extension may transmit the following limited information:

• Random Installation ID: A randomly generated UUID used as a pseudonymous technical identifier. It is not a name, email address, phone number, account credential, or advertising identifier.
• Environment Information: Extension version, browser type, operating system, and language setting.
• Aggregated Main-Domain Statistics: The main domain, date, and daily action count generated when the user performs a relevant action. Specific page paths, query parameters, page content, and selected or downloaded media are excluded from these analytics.
• Low-Frequency Feature Activity: Feature type and timestamp used to measure reliability and general usage. These reports exclude search terms, browser history, bookmarks, page content, and downloaded files.
• Sanitized Error Reports: Technical error information with page URLs and local file paths removed before storage or transmission.
• Uninstall Event: If supported by the browser, an uninstall request may include the random installation ID, Extension version, browser type, operating system, language, approximate usage duration, and limited feature counts.
• User-Submitted Feature Input: A search term, selected image, identifier, URL, city, approximate location, message, or conversation context required to complete a feature the user actively requests.
• Feedback or Support Submission: When the user actively submits a feedback or support form, the Extension may send the entered email address, message, request category, Extension name and version, installation date, and an optional user-selected screenshot to our support submission server.

1.3 Information We Do Not Intentionally Collect 我们不会主动收集的信息

English: Except for information explicitly requested in an optional feedback or support form, or information a user voluntarily includes in content submitted to an online feature, we do not intentionally request or collect names, email addresses, phone numbers, government identification numbers, payment or financial information, passwords, authentication credentials, cookies or session data from visited websites, or hardware fingerprints. We do not upload browser history, local time-tracking records, browser-session contents, bookmark contents, top-site lists, or New Tab search terms to our analytics server for advertising or profiling.

For the local QR code features described in Section 0.2, we do not transmit user-entered QR content, selected logo or scan-image data, decoded QR results, current-page or open-tab URLs, titles, or favicons, or generated and downloaded QR files to our analytics, support, or configuration servers. This statement does not prevent a user from independently submitting selected content through an optional online feature described in Section 3, including placing it in a support message, or from navigating to a destination encoded in a QR result.

2. How Information Is Used 信息使用方式

English: Information described in this Policy is used only as applicable to the Extension and for the following purposes:

• Providing the user-facing feature requested by the user;
• Maintaining local settings, records, shortcuts, and workspace state;
• Completing searches, media processing, link generation, AI-assisted requests, weather requests, or similar actions initiated by the user;
• Responding to feedback, support requests, bug reports, and feature requests submitted by the user;
• Maintaining security, diagnosing failures, fixing bugs, and measuring reliability;
• Understanding limited aggregate usage patterns to prioritize compatibility and feature improvements; and
• Complying with legal obligations and enforcing applicable terms.

We do not sell, rent, trade, or disclose user data to data brokers or third parties for personalized advertising, credit assessment, or unrelated commercial profiling. Information obtained through browser APIs is used and transferred only as necessary to provide or improve the Extension's disclosed, user-facing purpose, maintain security, comply with law, or complete a transaction initiated by the user. Our handling of such information is intended to comply with applicable browser store user-data policies, including the Chrome Web Store User Data Policy and Limited Use requirements, Microsoft Edge Add-ons policies, and Mozilla Add-on policies.

3. Services and Data Transmission 服务与数据传输

English: A subsection below applies only when the Extension contains and uses the described feature.

3.1 Our Analytics Server 我们的分析服务器

English: When technical and interaction analytics are enabled or permitted, limited statistics described in Section 1.2 may be sent to our analytics server over HTTPS/TLS. These analytics exclude direct identity information, browser history, bookmarks, specific page URLs, search terms, page content, and selected or downloaded media. If the browser supports an uninstall URL, the limited uninstall event described in Section 1.2 may be sent when the Extension is removed.

3.2 AI Service Provider AI 服务提供商

English: If the Extension includes an AI-assisted feature, user-submitted messages and the conversation context required to generate a response are sent over HTTPS/TLS to the AI service only when the user submits a request. Where Google Gemini is the displayed provider, Google LLC processes the request under the Google Privacy Policy. We do not store those chat messages on our own analytics server.

3.3 Search Providers 搜索服务提供商

English: If the Extension includes a search feature, a query is sent only when the user actively submits it. The browser may handle a default-search request through the user's selected search provider, or the Extension may open the results page of the provider selected by the user. We do not upload these search terms to our analytics server.

3.4 Online Weather and Location Providers 在线天气与定位服务提供商

English: If online weather is included, it is an optional feature. Where the browser provides a dedicated location-data permission, the Extension requests that permission before transmitting weather-related location information. If the permission is declined or revoked, requests requiring that permission stop.

• Forecast and air quality: The selected city's latitude and longitude may be sent over HTTPS to Open-Meteo forecast and air-quality endpoints.
• City search: A city name entered by the user may be sent over HTTPS to Open-Meteo's geocoding endpoint.
• Automatic approximate location: Only when the user enables automatic location, the Extension may contact ipapi.co and, if necessary, ipwho.is over HTTPS to derive an approximate city and coordinates from the network address.
• Limits: These requests are used only to provide weather. We do not send bookmarks or browser-history data with them and do not store the request data on our analytics server. Each provider handles network requests under its own terms and privacy policy.

3.5 Feedback and Support Submissions 反馈与支持提交

English: If the Extension includes a feedback or support form, no submission is sent until the user completes and submits the form. The submission may include the user's email address, message, selected request category, Extension name and version, installation date, and an optional screenshot selected by the user. The information is sent over HTTPS to our support submission server and used to respond to the request, investigate reported problems, prevent abuse, and improve the Extension. Users should avoid including unrelated sensitive information in messages or screenshots.

3.6 Other User-Initiated Online Features 其他由用户主动使用的在线功能

English: An online search, image search, link-generation, content-processing, or similar feature may require the Extension to send the input necessary to complete the user's request to the relevant service. This may include a search term, selected image data, page or product identifier, URL, or other submitted content. The transmission occurs only when the user invokes the corresponding feature and is not used to transmit unrelated browser history, bookmarks, downloaded files, or local workspace data.

The Extension may also retrieve configuration, compatibility rules, supporting content, or visual resources needed to provide its disclosed interface and features. Routine retrieval requests do not include browser history, bookmarks, downloaded media, or user search terms unless the user actively invokes a feature that requires such input.

3.7 Advertising and Tracking Services 广告与追踪服务

English: We do not use Google Analytics, Facebook Pixel, or third-party advertising or cross-context behavioral tracking SDKs inside the Extension. If the Extension displays an external link that may generate a commission, that relationship will be disclosed in the Extension or near the relevant feature and does not authorize unrelated tracking.

3.8 Remote Configuration Delivery 远程配置下发

English: If the Extension retrieves remote configuration, compatibility rules, or feature-display settings, it makes an ordinary HTTPS request to the configuration endpoint disclosed for that Extension. Like other internet requests, the endpoint and its infrastructure may automatically process standard network and HTTP metadata, such as the requester's IP address, request time, user agent, language or cache headers, and request status, for delivery, security, abuse prevention, and operational logging. Unless a more specific feature disclosure states otherwise, the configuration request payload does not include user-entered feature content, selected local files, page content, specific browsing history, bookmarks, downloaded files, or local workspace records.

Retrieved configuration is validated and used only as structured data for feature availability, compatibility, scheduling, interface text, layout, visual resources, or predefined actions. It is not treated or executed as remotely hosted JavaScript, WebAssembly, or other executable code. Validated configuration may be cached in Extension-scoped local storage until it is replaced, cleared, or removed when the Extension is uninstalled. Server-side request logs are retained only as reasonably necessary for delivery, security, reliability, abuse prevention, and legal obligations, after which they may be deleted, de-identified, or aggregated.

4. Cookies and Local Storage Cookie 与本地存储

English: The Extension does not use traditional HTTP cookies for its own local state. Depending on included features, it may use browser extension storage, IndexedDB, or other local browser storage to save preferences, the random installation ID, telemetry settings, cached statistics, local workspace records, shortcuts, recent records, time-tracking sessions, blacklist and whitelist rules, cleanup settings, a previously submitted feedback email, a local submission counter, weather cache, and task state. Daily main-domain statistics are retained locally for no more than 30 days and are removed after successful upload. Browser history displayed by a local history feature is read from the browser as needed; the Extension may separately store local time-tracking records associated with URLs when that feature is enabled.

Local Extension storage is protected by the browser's extension security model and is not intentionally exposed to websites or unrelated extensions. Its security also depends on the security of the user's browser, operating system, device, and installed software.

5. Data Security 数据安全

English: We use reasonable technical and organizational safeguards appropriate to the data handled by the Extension, including:

• HTTPS/TLS for transmissions to our server and the identified service providers;
• Browser sandboxing and extension-scoped local storage;
• Random pseudonymous identifiers instead of direct identity information for limited analytics;
• Removal of page URLs and local file paths from error reports before storage or transmission where implemented; and
• Validation of messages exchanged between Extension components.

No security measure can guarantee absolute protection. Users should keep their browser and operating system updated and protect access to their devices.

6. Data Retention 数据保留期限

• Local QR code data: Unsaved QR content, batch input, selected scan files, and decoded results are normally held only for the active interface session. Saved QR styles, an optional logo included in a saved default style, output settings, floating-button position, and cached configuration remain until changed, deleted, cleared with Extension data, or removed when the Extension is uninstalled. Files copied, downloaded, or exported at the user's direction remain under the retention and deletion controls of the clipboard, browser, operating system, or storage location selected by the user.
• Local statistics: Daily main-domain statistics are retained locally for no more than 30 days and removed after successful upload. Pending sanitized error reports are removed after successful upload or local cleanup and are subject to storage limits.
• Local preferences and workspace records: Retained until the user clears Extension data, resets the relevant settings, deletes the record, or uninstalls the Extension.
• Local history and time-tracking records: Retained according to the user's selected retention and cleanup settings, or until the user exports, deletes, clears, or uninstalls the Extension. History remaining in the browser is subject to the browser's own retention behavior.
• Browser history: History read for a local Extension page is held only as needed for that page and is not persistently copied by the feature. The browser retains its own history according to the user's browser settings.
• Server-side analytics: Retained only for as long as reasonably necessary to produce aggregate service statistics, maintain security and reliability, and meet legal obligations. Data may then be deleted, de-identified, or aggregated. A user may request deletion of server-side records associated with a random installation ID where technically identifiable.
• Random Installation ID: Retained locally until the Extension is uninstalled or the user clears Extension data.
• Third-party services: Information sent to a search, AI, weather, location, or other user-selected service is retained under that provider's applicable privacy policy and terms.
• Feedback and support: Submitted messages, email addresses, request metadata, and attachments are retained only as reasonably necessary to respond, investigate issues, prevent abuse, maintain support records, and meet legal obligations, after which they may be deleted or de-identified.

7. User Choices and Controls 用户选择与控制

• Permissions: Optional browser permissions may be declined or revoked through the browser's Extension settings. Features that depend on a revoked permission will stop using that permission.
• Local data: Users may clear Extension data, reset available settings, delete records through available controls, or uninstall the Extension.
• QR code controls: Where the QR feature is present, users choose the text, URL, tab, logo, image, style, copy action, download, export, and recognized destination involved in each operation. Available controls allow users to clear scan results, remove saved styles or logos, and clear Extension data. Downloaded or exported files must be deleted through the browser, operating system, or selected storage location.
• Browser history: Users may manage history through the browser. If an Extension history feature offers a delete action, using it may remove the corresponding URL from the browser's own history. Uninstalling the Extension does not delete the browser's existing history.
• Time tracking and cleanup: Where available, users may enable or disable local time tracking, grant or revoke its optional browser permissions, select a retention period, configure blacklist or whitelist rules, export local records, and run or disable automatic cleanup.
• Access, deletion, and questions: Users may contact us to request access to or deletion of server-side data that can be associated with their random installation ID, subject to technical and legal limitations.

8. Children's Privacy 儿童隐私

English: The Extension is intended for a general audience and is not designed to solicit personal information from children. If we learn that personal information from a child has been collected contrary to applicable requirements, a parent or guardian may contact us so that we can take appropriate action, including deletion where required.

9. Contact Us 联系我们

English: For privacy questions, complaints, access requests, or deletion requests, contact:

Email: service@downpictures.com

Please identify the relevant Extension and, where applicable, provide the random installation ID or other information reasonably necessary to locate the requested record. We generally respond within 30 days, subject to applicable law and the complexity of the request.

10. Changes to This Policy 政策变更

English: We may update this Policy to reflect changes in Extension features, data practices, browser store requirements, applicable law, or security measures. The revised Policy will be posted on this page with an updated "Last Updated" date. Where required, material changes will also be disclosed in the relevant Extension or browser store listing before the changed practice begins.