QuietView · Browser extension and Windows companion
Privacy Policy
QuietView processes the page and window information needed for immersive reading on your device. It does not upload this reading data to LuChen or third parties. Information involved in visiting websites, downloading files or contacting support is described separately below.
1. Scope and purpose
This policy covers the QuietView browser extension for Google Chrome and Microsoft Edge on Windows, and its Windows companion. It describes the local reading features in the 2.2 release series. After you give consent and activate the feature, QuietView temporarily hides unnecessary page controls and browser borders, preserves the visible window size and position, allows dragging, and restores the window when you exit.
Before enabling reading features for the first time, QuietView displays a local processing disclosure and asks for your explicit consent. No user account is required.
2. Information processed locally
- The current page: The current tab URL (primarily its scheme, domain and path), page structure, element roles and control identifiers, relevant attributes and layout coordinates. These are used to check compatibility and temporarily hide navigation, toolbars and floating controls. The original page title is held in memory, briefly replaced with a random marker to locate the window, and then restored. QuietView does not capture page screenshots or record form input values or your complete browsing history.
- Session and restoration state: Tab, document and window identifiers; tab order, pinned and group state, relevant split-view and private-window flags; and the original window type, normal or maximized state, position and size. These support compatibility checks and restoration.
- Feature interactions: Exit and element-picker shortcut events while reading is active, and pointer, click and element-position events while the picker is open. These support your selection of elements to hide. QuietView does not save these interactions as behavioral records or keystroke logs.
- Windows information: The companion enumerates visible, non-minimized candidate windows and reads their classes and candidate titles to match the temporary random marker. It checks the matching window's process identifier and executable path to confirm a supported browser. Window position and size, and monitor and scale information are used for cropping. While you drag the top strip, cursor position and left-button state are used to move the window. Matching and dragging data stays in local process memory; no window-title or drag-trajectory log is created.
3. Why permissions are needed
activeTab: Temporary access to the current tab after you activate the feature.scripting: Run packaged scripts and styles in the current page to identify, temporarily hide and restore interface elements.storage: Keep consent locally and temporary restoration state in browser session storage. Cloud sync storage is not used.nativeMessaging: Communicate with the separately installed Windows companion to provide borderless windows and dragging.
4. Local communication, uploads and sharing
The extension sends operation types, request numbers, random window markers, viewport dimensions and scale parameters to the companion on the same device. The companion returns status, protocol version, movement results or error codes. Page body content, original page titles and URLs are not sent through this channel. As described in section 2, the companion separately reads candidate window titles from Windows to match the random marker.
The reading feature does not connect to publisher servers or include analytics, advertising or tracking SDKs. It does not upload reading data to external services. LuChen does not sell this data, provide it to data brokers, or use it for advertising, profiling, credit decisions or purposes unrelated to immersive reading.
QuietView complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information obtained through browser extension APIs is used only for the immersive reading features disclosed in this policy.
5. Retention and deletion
- Temporary reading data: Page titles, element selections and companion window state are primarily held in the relevant processes' memory. Restoration records are held in browser session storage and normally removed after exit completes or the associated tab closes. A restoration error may leave temporary records until the browser session ends.
- Consent setting: Stored in the extension's local storage to check consent on later use. Withdrawing consent removes that setting and initiates exit from active reading sessions. Consent is required again before re-enabling. Removing the extension also clears its browser storage.
- Companion installation: Extracted program and configuration files, the generated native-messaging manifest, and current-user Windows registry entries containing its installation path remain until uninstalled or manually deleted. Run
Uninstall-QuietView.cmdto remove this installation directory's registration and generated manifest, then delete the extracted folder. Removing the extension does not uninstall the companion. - Errors: The extension or companion may output exception types and short error messages to the browser console or local standard-error channel. QuietView does not automatically upload them or create persistent diagnostic log files.
6. Websites, downloads and support
When you choose to open a privacy, installation, download or browser-store page, that website receives an ordinary web request. QuietView does not add the current reading page's URL, title or body to those links. Website and download providers handle their own access logs.
This policy page loads no analytics scripts, advertising, external fonts or tracking components. When you visit it on GitHub Pages, GitHub records visitors' IP addresses for security purposes. See the GitHub Pages data collection notice and GitHub Privacy Statement. This is separate from the extension's local reading features.
If you email the Gmail address below, LuChen receives and uses your email address, message and any files you choose to attach to respond to and resolve your support request. Google, as the email provider, also processes email-service data under its Privacy Policy. Share only what is needed to explain the problem, and avoid sending passwords or unrelated sensitive information. Support messages are retained only as needed to handle and follow up on requests and meet necessary security or legal obligations. You can contact LuChen to request access to, correction of or deletion of information you voluntarily provided.
7. Your choices and safeguards
Press Esc to leave reading mode. When the element picker is awaiting a selection, the first press cancels the picker and a second press exits. You may withdraw consent in the extension options, disable or remove the extension, and uninstall the companion as described in section 5. LuChen has no remotely stored reading-session records to retrieve; you control local information through your browser and device.
QuietView uses on-demand current-tab access and local storage. The Windows companion restricts native-messaging callers to store extension identifiers in its configuration. The operating system and browser provide local access controls, and the public policy page is served over HTTPS. Install the extension and companion only from browser stores and publisher download channels you trust.
8. Updates and contact
Changes to this policy will be posted here with an updated date. If future features change data handling, an explanation will be provided before those features are enabled, and renewed consent will be requested when needed.
Publisher: LuChen
Privacy and support contact: luchencoder@gmail.com