This page separates audio processing from ordinary website delivery so you can understand what stays in the tab and what a web host may still receive.
The thirteen Live tools use browser APIs to read and decode a file you select. Decoded samples are processed in memory, and results are encoded into temporary local URLs for preview and download.
The current SoundTools application has no account system, media upload endpoint, or storage bucket for source and processed audio. Closing or refreshing the tab releases the in-memory working state and temporary preview URLs.
Your browser must request the HTML, CSS, JavaScript, icons, and other site assets required to display SoundTools. The hosting and content-delivery providers may process standard request information such as IP address, browser details, requested path, time, and security signals.
The current design also loads font files through Google Fonts. Those font requests are separate from audio processing and do not include the audio file selected in the workbench.
You do not create an account or provide a name to use the audio tools. The current application code does not set advertising, personalization, or application-account cookies.
Operational hosting systems may use short-lived security or delivery mechanisms outside the audio workbench. If analytics, advertising, accounts, or cloud processing are added later, this page should be updated before those changes are presented as part of the product.
Noise removal runs through RNNoise WebAssembly. Transcription and music separation download Whisper or Demucs model files, then perform inference on the device through WebGPU. These asset requests do not contain your selected media.
WebGPU tools state their compatibility and model size before processing begins. SoundTools does not fall back to a remote transcription or separation service when local inference is unavailable.