SOUND FLIPPER GUIDES
Private browser audio conversion: the actual data flow
See what stays on your device, why the page still makes hosting requests, and how temporary audio, saved settings and privacy choices work.
By Singularity Shift Ltd · Updated · Preview guide
The audio processing happens on your device
Sound Flipper reads a file you select through the browser and processes it in a local WebAssembly worker. The conversion flow does not upload that audio or its tags to a conversion server. The verified result is offered as a download, or can be shared through a device feature you choose.
That promise is specifically about audio processing. It does not mean the website makes no network requests. Your browser still downloads the page, scripts, styles and audio engine from the host. Opening an external reference or sending an email is a separate action.
Temporary files are local data
Where available, the browser's origin-private filesystem stores intermediate and completed outputs until they are cleared. These files belong to the site in browser storage; they are not ordinary downloads in your chosen folder. The fallback uses a smaller memory budget when private filesystem storage is unavailable.
Sound Flipper gives each tab a temporary session. With browser locking available, cleanup skips active sessions and can remove abandoned ones. A crash can interrupt deletion, and a filesystem operation can fail. If cleanup cannot be confirmed, the app reports that condition rather than pretending the data disappeared. Browser site-data removal is the fallback for abandoned local data. MDN describes how OPFS works.
Presets and links contain settings, not audio
Saved presets use your browser's local storage. They can remember output format choices, metadata policy and profile labels, up to thirty entries. Clearing site data removes them. They do not sync to an account, and saving a preset does not save a recording.
A settings link uses a URL fragment containing validated format choices and policy settings. It excludes source filenames, audio, tags and per-file edits. Anyone you send the link to can read its settings, so do not put sensitive information in a custom name elsewhere in your workflow.
Optional services are a separate choice
On the public site, Google Analytics is optional and runs only if you allow analytics in Cookie settings. It receives basic visit and browser information and the page path. Sound Flipper does not include URL queries or settings fragments in the page address it sends, and its configured events do not include your audio, filenames, tags or support text. The original audio conversion remains on your device.
Advertising is a separate choice. Ads require site approval and an appropriate Google-certified consent setup before they can run. Optional choices are off by default, expire after up to 180 days and can be changed from the footer. If preference storage is blocked, optional services fail closed. Hosting requests still reach the host; support emails contain what you choose to send. See the privacy notice.
What has actually been checked
Automated desktop conversion tests with optional services off inspect network traffic and permit only local page/engine assets and local Blob reads. They do not send audio or tags. This is evidence for the tested build, not a guarantee about every browser extension, shared computer or external app. Avoid selecting confidential material on a device you do not trust, and keep a separate copy of important originals.