Privacy Policy

• Loud runs in your browser. There is no Loud account and no Loud server storing your tabs.
• Tab titles, URLs, favicons, and audio state are read on-device through Chrome's standard extension APIs and used to populate the popup.
• Loud does not run analytics, crash reporting, or any other network calls. It makes zero outbound requests.
• We do not sell your data, run third-party advertising trackers, or share your information with anyone.

Loud only accesses what Chrome explicitly grants it through extension permissions. Each permission has a specific purpose:

• tabs: Loud queries Chrome for the list of tabs that are currently producing sound, plus their titles, URLs, and favicons, so it can show them in the popup. Tabs that aren't audible are not read.
• scripting: when you click the speaker icon on a tab, Loud injects a small script into that tab's page that calls media.pause() (or, on supported sites like Spotify Web, clicks the site's own play/pause button). The script does not read page content, form data, cookies, or storage. It runs once per click and returns nothing back to Loud beyond "did pause succeed."
• storage (session): when Loud pauses a tab, it remembers the tab's id, title, URL, and favicon in chrome.storage.session so the tab stays visible in the popup until you resume it. Session storage lives only in memory and is wiped when you close Chrome.
• host permissions <all_urls>: required so that the pause/play script can be injected into whichever tab you choose to silence. Loud never reads the contents of any site; it only invokes pause/play on media elements (or, on a small list of known music services, clicks the play/pause button by selector).

Loud writes a single thing, to one place:

• The paused-tabs map in chrome.storage.session. This is a JSON object that maps tab ids to a snapshot of { title, url, favIconUrl, windowId } for tabs you have paused. It exists so paused tabs (which Chrome no longer reports as audible) remain visible in the popup so you can resume them.
• This data is held in memory by Chrome. It is not written to disk and not synced to your Google account.
• The map is cleared automatically when you close Chrome, when a paused tab closes, or when you click "Resume" on a tab.

Loud writes nothing else: no cookies, no localStorage, no IndexedDB, no files on disk.

Nothing.

• Loud makes no network requests. It has no analytics provider, no crash reporter, no telemetry, and no "phone home" check.
• Tab titles, URLs, favicons, and audio state never leave your browser. Loud reads them, shows them in the popup, and that's the end of the trip.
• When you pause a tab on a music service, the click happens entirely inside that tab's page — exactly as if you had clicked the play button yourself. No data is sent to Loud as part of that action.

The only outbound network activity associated with installing Loud is whatever Chrome itself does when updating extensions, which is governed by Google's own policies.

• Loud does not require you to create an account. There is no username, no password, no cloud profile linked to your usage.
• There is no sign-in flow, no OAuth, no payment, and no paid tier.
• Settings (currently just the optional Alt+Shift+M keyboard shortcut for "mute all") are stored by Chrome in your local browser profile.

To run Loud we rely on a single standard provider, and only for distribution:

• Google distributes Loud through the Chrome Web Store. Google handles install/update delivery and may collect its own anonymous install/usage statistics about extensions on the store under Google's own privacy policy. Loud itself does not share any data with Google beyond what Chrome includes in the extension manifest.

We do not sell data, share it with advertisers, or use it to build profiles about you. Loud has no other third-party integrations.

Loud gives you controls in three places: the popup itself, the Chrome extensions page, and Chrome's keyboard shortcuts settings.

In the popup

• Resume any tab: click the speaker icon next to it. Loud removes that tab from its paused-tabs map immediately.
• Resume all: click "Resume all" when every audible tab is silenced. Clears the entire paused-tabs map.
• Close the popup without acting: nothing changes. Loud stops listening for tab updates as soon as the popup closes.

In Chrome

• Disable the extension at chrome://extensions. Loud stops running until you re-enable it.
• Remove the extension at chrome://extensions. All local Loud data (including chrome.storage.session) is deleted immediately by Chrome.
• Change the "mute all" keyboard shortcut at chrome://extensions/shortcuts.
• Revoke host permissions: Chrome allows you to restrict an extension's host permissions to "On click" or specific sites from the extension's details page. Loud will fall back to muting (instead of pausing) on sites where it can no longer inject the pause script.

If you're done with Loud

• Removing the extension at chrome://extensions is the complete uninstall. There is nothing else stored on our side because there is no server.
• For any other data request, email hello@kester.work.

• The paused-tabs map in chrome.storage.session lives only for the current Chrome session. Closing Chrome wipes it. There is no long-term retention.
• Loud has no servers, so there is no server-side retention of any kind.
• Support emails are kept while we work with you and for a reasonable period afterwards in case the issue recurs.
• Deletion requests for support correspondence are completed within 30 days of receipt.

• Loud is distributed through the Chrome Web Store, which sandboxes the extension and limits what it can touch in your browser.
• Loud uses Chrome's standard extension APIs and adheres to Manifest V3, which forbids remote code execution and enforces stricter content-security policies than the previous extension model.
• Loud does not transmit any data, so there is no transmission to secure.
• Support emails (the only data we ever receive) reach us over encrypted email transport.
• No system is perfectly secure. If we ever discover a security issue that affects you, we will tell you.

Loud is not directed at children under 13 (or the higher minimum age required by your local law). We do not knowingly collect data from children. We also don't knowingly collect data from anyone else, but it bears repeating.

If we make material changes, we'll update the "Last updated" date at the top and, where appropriate, note the change in the extension's Chrome Web Store listing. Continued use of Loud after changes means you accept the updated policy.

Questions, deletion requests, or anything else: email hello@kester.work. The publisher of Loud is Kester Atakere.

This Privacy Policy is governed by the laws of Nigeria, without regard to its conflict-of-laws rules.