WaveTrace — Privacy Policy

1. Overview

WaveTrace is a browser extension whose single purpose is to identify music playing in the user's current browser tab. This Privacy Policy explains what information WaveTrace handles, why it is needed, and when information is sent to third-party music-recognition providers.

WaveTrace does not operate an advertising network, does not sell user data, and does not use browsing activity for advertising, profiling, credit scoring, or unrelated purposes.

2. Information WaveTrace Handles

Tab audio

WaveTrace captures audio from the current browser tab only after the user explicitly starts a recognition. The audio is used only for music identification. WaveTrace does not continuously record browser tabs in the background.

Recognition-provider credentials

Some supported providers require the user to supply an API key or other provider credential. These credentials are stored in the browser extension's storage so the user's configuration can persist. A credential is used only with the corresponding provider for recognition requests initiated by the user.

Settings and recognition history

WaveTrace stores configuration such as enabled providers, recognition duration, appearance, language, and recognition history in extension storage. These records support WaveTrace's music-identification functionality and user experience.

3. Third-Party Recognition Providers

When the user starts recognition, WaveTrace may send the audio data or derived fingerprint data required by the recognition providers that the user has enabled. Supported workflows can include providers such as AudD, ACRCloud, Shazam-based recognition, and AcoustID.

For AcoustID whole-song recognition, the WaveTrace Companion can process captured audio locally with Chromaprint to generate an audio fingerprint. AcoustID receives the fingerprint and recording-duration information required for lookup rather than the original full-song audio. If a partial whole-song recognition falls back to an enabled short-scan provider, the required short audio clip may be sent to that provider.

Third-party providers process requests under their own terms and privacy policies. Their availability, retention practices, quotas, pricing, and policies are controlled by those providers and may change independently of WaveTrace.

4. WaveTrace Companion

Some recognition features use the optional WaveTrace Companion for Windows. The Companion is a local Native Messaging application installed on the user's computer. Chromium launches it on demand when native functionality is required and it does not need to run permanently.

The Companion is used only to support WaveTrace recognition functions, including local audio processing required by supported recognition workflows.

5. What WaveTrace Does Not Collect for Its Own Purposes

• No names, postal addresses, health information, or financial information are requested by WaveTrace.
• No advertising identifiers are used.
• No keystroke, mouse-movement, or general browsing-behavior tracking is performed.
• WaveTrace does not sell user data.
• WaveTrace does not use user data for credit scoring or lending purposes.

6. Data Retention and Control

WaveTrace itself does not operate a remote account database for extension users. Settings, provider credentials, and recognition history stored by the extension remain in browser extension storage until the user changes or removes them, clears extension data, or uninstalls the extension, subject to the browser's own storage behavior.

Data sent to a third-party recognition provider is subject to that provider's retention and privacy practices. WaveTrace does not control third-party retention.

7. External Music Links

Recognition results may include links to external music services such as Spotify, Apple Music, MusicBrainz, or other metadata/music services. Opening an external link takes the user to that service, where that service's own privacy policy applies.

8. Security

WaveTrace limits data handling to what is needed for music recognition and related settings. Users should keep their provider API credentials private and revoke or replace a credential through the relevant provider if they believe it has been compromised.

9. Changes to This Policy

This policy may be updated when WaveTrace's functionality or data practices change. The effective date at the top of this page will be updated when material changes are made.

10. Contact

For privacy questions about WaveTrace, contact: wavetracelmt@gmail.com

Replace the placeholder above with the same verified publisher/support email you use for the Chrome Web Store before publishing this page.