Privacy Policy for Audio Studio
Effective Date: August 28, 2026
This Privacy Policy describes how the Audio Studio browser extension (the “Extension”) and its companion website (audiostudio.aymanelimam.com) handle user information. The Extension processes audio entirely on your device and sends nothing to any server operated by us.
1. Zero Data Collection or Transmission
We do not collect, store, transmit, or monetize any personal data, browsing history, audio recordings, or usage statistics.
- The Extension does not communicate with any server, API, database, or analytics platform operated by us or by any third party.
- There is no background tracking or data-logging of any kind.
- The only data that ever leaves your computer is your own settings, and only through Chrome’s own sync service under your own Google account, as described in section 3.
2. Explanation of Requested Permissions
To provide real-time audio manipulation securely and locally, the Extension requests the following permissions, used strictly as described:
tabCapture: Used to capture the active tab’s audio stream so it can be processed by the Web Audio API on-device. Audio processing happens entirely in-memory and is never recorded or saved.offscreen: Used to host the audio processing context in a secure offscreen environment, ensuring your sound amplification and equalization continue seamlessly while you navigate.storage: Used to save your custom equalizer presets, site-specific volume configurations, and theme selections, as described in section 3.activeTab: Provides secure, temporary access to capture the current tab’s audio stream only when you explicitly interact with the Extension.tabs: Used locally to query the name and favicon of tabs playing audio in order to display them in your multi-tab mixer console.sidePanel: Allows the Extension’s studio dashboard (EQ, mixer, and effects) to be displayed in Chrome’s side panel for a convenient side-by-side browsing experience.notifications: Displays a local notification prompt allowing you to quickly enable audio capture on previously saved sites.scripting: Used to inject two scripts into a page, and only into pages you have granted access to. The first detects when a video enters or leaves fullscreen, so the Extension can adapt its interface. The second is the audio bridge described below. Neither reads page content, and neither sends anything outside your browser.- Optional site access (
optional_host_permissions): Not granted at install time. The Extension asks for it one site at a time, and only when you click to enable it, so that it can attach directly to that site’s audio and video elements. This is what lets a boost survive a page reload. Granting it allows the audio bridge to run on that site; the bridge reads only the properties of media elements needed to attach to them (their source URL, cross-origin setting, and whether the media is DRM-protected) and never the page’s text, forms, or cookies. You can revoke it at any time from Chrome’s extension settings.
3. Data Processing & Storage
- Audio Processing: All audio effects (31-band EQ, bass boost, Haas spatial widener, dynamics compressor) are processed in real time using the native browser Web Audio API. Audio data is never cached, stored, or transmitted.
- Local Settings: Your preferences (active skin, custom presets, dismissed prompts, usage counter) are stored on your computer with the
chrome.storage.localAPI and never leave it. - Synced Settings: Your per-site profiles — the volume and equalizer settings the Extension remembers for each site — are additionally written to
chrome.storage.sync. This is Chrome’s own synchronization mechanism: the data travels to your own Google account, under Google’s terms, so that your settings follow you to your other signed-in Chrome installations. It never reaches any server of ours, and we cannot read it. If Chrome sync is turned off, this data stays on your device. Sync stores site hostnames and audio settings only — no page content, no browsing history, and no personally identifying information.
4. No Third-Party Integration
The Extension does not contain any third-party ads, trackers, analytics scripts, or external libraries that communicate over the network.
5. Data Retention & Deletion
Uninstalling the Extension permanently deletes all locally stored presets, settings, and saved site configurations from your device. Settings previously written to Chrome sync are removed through your Google account’s own data controls, the same way as any other Chrome sync data.
When you uninstall the Extension, your browser opens an uninstallation feedback page served by audiostudio.aymanelimam.com. Filling out this feedback form is entirely optional. The Extension itself does not transmit any data upon uninstallation: the browser opens the page with only your current display language in the path and the Extension version in the URL query string (?v=), and nothing else (no user identifiers, no timestamps, no counters, and no usage data).
6. Contact
If you have any questions about this policy or about how the Extension handles your data, you can reach the maintainer through the support link on the Extension’s Chrome Web Store listing.
7. Changes to This Policy
Any change to this policy will be published on this page with an updated effective date. Because the Extension collects nothing, no change can retroactively affect data already gathered — there is none.
8. Companion Website Data & Privacy
When you visit or interact with the companion website (https://audiostudio.aymanelimam.com), the following data retention policies apply:
| Data | Stored | Retention |
|---|---|---|
| Form responses | Yes | 24 months, then automatically purged |
| Email address (with consent) | Yes | 12 months, then erased even if response is kept |
| IP address fingerprint | Yes (rotating key) | 48 hours |
| Plaintext IP address | No | — |
| Full User-Agent | No (only chosen OS is kept) | — |
| Cookies on public pages | None | — |
| Audience measurement tools | None | — |
Purges run automatically every day. The extension itself continues to collect zero data.