What Dialogue Guard processes
After you explicitly start it, Dialogue Guard temporarily processes the live audio output of the browser tab you selected. That processing happens in a packaged Chrome extension document on your computer and feeds your local audio output.
The extension briefly inspects the selected tab's current page address in memory to reject Chrome-protected pages and derive a normalized hostname. When you choose or change sound settings, Dialogue Guard may store that hostname, such as example.com, and the selected control values so the preference can be restored for that website. The full page address is not retained.
What it does not collect
Dialogue Guard does not record, save, upload, or transmit audio. It does not read page content or browsing history, and it does not store or transmit search terms, full URLs, paths, query parameters, fragments, media titles, microphone input, camera input, advertising identifiers, or analytics events.
Local storage and retention
Website preferences stay in Chrome extension storage on your device and use only the normalized hostname. A non-sensitive random operation token and runtime status may be kept in browser-session storage so the extension can recover safely if Chrome suspends its service worker. The one-time capture stream identifier is never stored.
You can reset the current site’s preference in the extension. Uninstalling the extension removes its Chrome-managed local data.
Sharing and network use
There is no Dialogue Guard server, user account, advertising system, payment code, or telemetry service in Phase 1. The production extension has no host permissions and no intended network requests, so there is no developer or third party receiving audio or browsing data.
Dialogue Guard's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Chrome platform processing
Chrome provides the extension APIs and local storage used by Dialogue Guard. Your use of Chrome remains subject to your browser provider’s own terms and privacy practices. Dialogue Guard does not control those platform practices.
Changes and contact
Any future feature that collects or transmits data would require a clearly disclosed policy update and a new product review; it is not part of this initial release. Questions about this policy or Dialogue Guard can be sent to straight.joseph@gmail.com.