1. Scope
This policy describes how DJcompanion for Browser handles information when you use the web app. DJcompanion is a training-focused DJ companion and does not require account registration to use core features.
2. Audio Files You Load
When you load tracks, files are processed in your browser to enable waveform rendering, BPM estimation, playback, pitch control, and EQ. DJcompanion does not intentionally upload your local track files to a DJcompanion backend service.
3. Microphone Access
Microphone BPM listening is optional and only starts after your explicit browser permission. Microphone input is used for live BPM detection in-session. DJcompanion does not intentionally store microphone recordings on a server.
4. Device and Browser Data
The app may use standard browser/runtime signals needed to provide audio functionality, capability checks, and responsive UI behavior. No user account profile is required for normal operation.
5. Third-Party Services
Hosting platforms or network infrastructure may process operational logs according to their own policies. Review your deployment provider terms for infrastructure-level processing details.
6. Data Retention
Core DJ training interactions are intended to run locally in-browser for active sessions. If you clear browser data, local session data and cached assets may be removed by your browser.
7. Your Controls
You can stop microphone access at any time in-app and revoke permissions in browser settings. You control which audio files are loaded during practice sessions.
8. Contact
For privacy-related questions, use the project repository contact channel: github.com/manelix2000/Mixer.