The short version

  • This extension collects no personal information whatsoever.
  • No data is ever sent to any external server, including the developer's servers.
  • No analytics, telemetry, crash reporting, or tracking of any kind.
  • WebHID reads only physical button-press signals from your USB headset — not audio.
  • Content scripts run only on Amazon Connect domains — no other sites are accessed.
  • Nothing is stored beyond browser-native HID device permissions you explicitly grant.

1. Overview

Headset Control for Amazon Connect ("the Extension") is a Chrome browser extension that enables USB headset call-control buttons (answer, end, mute) to operate the Amazon Connect Contact Control Panel (CCP) softphone. The Extension acts as a local signal bridge between the Chrome WebHID API and the Amazon Connect Streams API running in your browser tab.

This Privacy Policy describes what information the Extension accesses, how it uses that information, and confirms that no personal data is collected or transmitted.

2. Information the Extension does not collect

The Extension does not collect, store, log, or transmit:

  • Your name, email address, phone number, or any account credentials
  • Call audio, call recordings, or voice data of any kind
  • Call metadata (caller ID, call duration, contact attributes)
  • Agent status, availability, or performance data
  • Browsing history, URLs visited, or page content outside Amazon Connect
  • Keystrokes, clipboard contents, or form data
  • Device identifiers, IP addresses, or geolocation data
  • Cookies or any persistent identifiers

3. What the Extension does access (and why)

3.1 USB Headset HID Reports (WebHID API)

The Extension uses the Chrome WebHID API to receive low-level USB Human Interface Device (HID) reports from your connected headset. These reports contain only button-state bitmasks — e.g., whether the call button is pressed or the mute button is toggled. This data is processed in memory solely to translate button presses into call-control actions within the Amazon Connect CCP.

HID data is never written to disk, logged, or sent anywhere. No audio data passes through the WebHID interface; audio is handled entirely by your operating system's audio stack and is outside the Extension's scope.

3.2 Amazon Connect CCP Page Context

To issue call-control commands (accept, end, mute/unmute), the Extension injects a small script into the Amazon Connect CCP iframe running in your browser. This script subscribes to the Amazon Connect Streams API for real-time call-state events and executes call actions. It reads only the call-state information needed to keep the headset LED and mute indicator in sync — no call content, contact data, or personally identifiable information is read, stored, or forwarded.

3.3 Active Tab and Tab List

The activeTab and tabs permissions are used to:

  • Identify which browser tab is an Amazon Connect Agent Workspace tab
  • Route call-control messages from the side panel to that tab
  • Open a temporary full-browser tab for the one-time HID device-picker (required by Chrome because WebHID device selection requires a full tab context)

The Extension does not read, store, or act on URLs or content of any tabs other than the active Amazon Connect tab.

3.4 HID Device Permission (Browser-Stored)

When you pair a headset, Chrome stores a HID device permission entry in the Extension's local permissions store. This is a browser-native mechanism — the Extension itself stores no device data. You can revoke it at any time via chrome://settings/content/hidDevices.

4. Data storage and retention

The Extension uses no chrome.storage APIs, no IndexedDB, no localStorage, and no cookies. All operational state (current call state, mute state, connected headset) is held in JavaScript memory for the lifetime of the browser session and discarded when the Extension's side panel or service worker is unloaded.

The sole persistent artifact is the browser-level HID device permission described in §3.4, which is owned and managed by Chrome, not by the Extension.

5. Data sharing and third parties

The Extension does not share any information with third parties because it does not collect any information to share. There are no third-party SDKs, analytics libraries, crash-reporting services, or advertising frameworks bundled in the Extension.

The Extension communicates with exactly two parties:

  • Your USB headset — via the browser-local WebHID API (no network involved)
  • The Amazon Connect page in your browser tab — via Chrome's local extension messaging APIs (chrome.runtime.sendMessage, chrome.tabs.sendMessage, window.postMessage)

No network requests of any kind are made by the Extension.

6. Permissions justification

The Extension requests the minimum permissions required to function. Each permission is scoped to Amazon Connect domains only:

Permission Why it's needed
sidePanel Renders the headset-control UI in Chrome's built-in side panel.
activeTab Identifies the active Amazon Connect tab for message routing.
scripting Injects the page-level CCP integration script into the CCP iframe.
tabs Opens the one-time HID device-picker in a full Chrome tab.
*.my.connect.aws *.awsapps.com *.connect.aws Limits content-script injection to Amazon Connect domains exclusively.

7. Children's privacy

This Extension is a professional tool designed for enterprise contact center environments. It is not directed at or intended for use by children under the age of 13. No personal data of any kind is collected from any user, including minors.

8. Changes to this policy

If the Extension's data practices change in a future release, this Privacy Policy will be updated and the effective date at the top will reflect the revision date. Material changes that introduce new data collection will be communicated in the Extension's Chrome Web Store release notes.

9. Open source

The Extension's source code is available on GitHub. You are welcome to inspect the code to verify the data practices described in this policy. The absence of any network-request code, analytics SDK, or data-persistence logic is verifiable by reviewing the source directly.

Questions or concerns?

If you have any questions about this Privacy Policy or the Extension's data practices, please open an issue on the GitHub repository or use the support link on the Extension's Chrome Web Store listing page.