Effective date: June 12, 2026

The short version

TalkSound processes the audio of the browser tab you choose, entirely on your device, using the Web Audio API. It collects nothing, transmits nothing, and contains no analytics or tracking code of any kind.

What TalkSound processes

When you enable TalkSound on a tab, the tab's audio stream is captured and passed through a local audio-processing chain (EQ, stereo widening, reverb, loudness leveling), then played back. The audio exists only in memory during playback and is never recorded, stored, or sent anywhere.

What TalkSound stores

• Preferences (preset, intensity, per-site settings, platform list) are stored in Chrome's storage.sync, which Chrome may sync within your own Google account. TalkSound has no access to this sync infrastructure.
• Custom impulse-response files you load are stored only in your browser's local IndexedDB.

What TalkSound never does

• No network requests — the extension makes zero connections to any server.
• No collection of audio, browsing history, or personal data.
• No analytics, telemetry, fingerprinting, or advertising code.
• No remote code — all code is contained in the packaged extension.

Permissions

Permission	Why it is needed
tabCapture	Captures the audio of the tab you invoke TalkSound on, so it can be processed and re-output. This is the core functionality.
offscreen	Manifest V3 service workers cannot run an AudioContext; an offscreen document hosts the audio-processing engine.
storage	Saves your preferences. No personal data is involved.
activeTab	Identifies which tab to enhance when you click the icon or use the keyboard shortcut.

Changes & contact

If this policy changes, the update will be published on this page with a new effective date. Questions or concerns: please open an issue on the project's GitHub repository.