← Back to Audio Alchemy FX

Privacy Policy

Last updated: July 2026

Privacy first: Audio Alchemy FX is designed to run mostly in your browser. Local audio, local images, tab capture audio, and visualizer processing are handled client-side whenever possible.

Information We Do Not Collect

Audio Alchemy FX does not intentionally collect, upload, sell, or share:

Connected Services

Audio Alchemy FX may let you connect external services such as Dropbox, Google Drive, OneDrive, or Spotify. These connections are handled in your browser using the permissions you approve with that service.

Audio Alchemy FX does not receive, store, or collect your cloud account password, full account contents, or cloud files on its own servers. Your browser may temporarily use authorization tokens, file metadata, selected files, playback metadata, or album artwork only to provide the connected feature you requested.

For example, a cloud storage integration may show supported audio files you can choose to import, and a Spotify integration may show current playback details or send playback controls if you enable remote control. Audio Alchemy FX does not download, copy, or store Spotify songs.

You can revoke connected-service access through the external service’s account settings. External services are governed by their own privacy policies, permissions, and terms.

Local Files

When you import local audio or image files, those files are used in your browser session so Audio Alchemy FX can play, process, and visualize them. Local files are not uploaded to an Audio Alchemy FX server.

Studio Mode

Studio Mode may let you load multitrack projects, import local stems, record audio, record MIDI, edit MIDI notes, adjust mix settings, and export supported audio or MIDI files. Local files, local recordings, user-loaded samples, and MIDI performances are handled in your browser unless a feature clearly tells you it is uploading or sharing them.

Shared demo or direct-link Studio projects, such as hosted multistem sessions, are downloaded or streamed from Audio Alchemy FX hosting so they can play in your browser. Those hosted project assets are separate from your private local files.

Studio saves, mix settings, MIDI mappings, recorded-take metadata, project metadata, and diagnostic state may be stored in browser storage on your device. Exporting, downloading, copying a report, saving a mix, or sharing a project is a user-initiated action.

Built-In Sounds, MIDI, and User Samples

Studio Mode may include built-in MIDI instruments, drum sounds, generated one-shot samples, and browser-based MIDI tools. These sounds are served by Audio Alchemy FX so they can play in the app.

If you load your own samples, MIDI files, recordings, or audio files, they are handled in your browser session and are not uploaded to an Audio Alchemy FX server unless a feature clearly tells you it is uploading or sharing them.

The app may store MIDI settings, mappings, selected sound choices, project metadata, or session state in browser storage so Studio Mode can remember your work within the browser.

Tab Capture

Tab capture only starts after you explicitly approve it through your browser. Captured audio is used live for visualization and audio processing. Audio Alchemy FX does not intentionally record, upload, or store captured tab audio.

Browser Storage

The app may use browser storage such as session storage, local storage, IndexedDB, temporary object URLs, or browser cache for app settings, connected-session state, playlist behavior, or playback features.

Studio Mode may also keep a local Session Log or diagnostic history in browser storage. This can include reload or crash classifications, browser and device capability details, project/session state, feature counters, timing information, and error messages used to troubleshoot playback, recording, export, or mobile stability.

Session Log reports are not automatically uploaded to Audio Alchemy FX. If you copy, screenshot, or send a Session Log report for support, you are choosing to share the diagnostic text it contains.

You can clear this data through your browser’s site settings.