Privacy docs
Local-First Audio Privacy
Local-first audio privacy means the product is designed so core analysis and mastering can run in the browser, reducing the need to upload unreleased songs for processing.
Key takeaways
- Clear privacy language increases trust.
- Audio content should not be used for telemetry.
- Any cloud service must be disclosed plainly.
What local-first means
Local-first means the application is designed to process audio on the user’s device when using the browser mastering workflow. This reduces exposure compared with cloud-only mastering workflows.
What users should still understand
A browser app still downloads code and assets. Users should only use official BASS MASTERING domains, keep their browser updated and avoid uploading confidential material into third-party pages.
How this supports creators
Unreleased tracks, client demos, sync submissions and AI-generated drafts are sensitive creative assets. A local-first workflow supports faster experimentation with less unnecessary data movement.
Operational boundary
This page is a public explanation, not a disclosure of internal engine thresholds, rule logic or license infrastructure.
FAQ
Does local-first mean no server exists?
Not necessarily. Licensing, account management and payments may use servers, but the core audio processing workflow is designed for browser-local operation.
Can I use BASS MASTERING for client demos?
The local-first design is intended to be suitable for sensitive creative workflows, subject to final legal terms and user policy.
Master AI-generated music with fifteen automatic outputs
Run a local-first analysis, receive five Impact, five Middle and five Refined finished outputs, compare raw-original A/B and export the selected release-ready master with BASS MASTERING.
Open BASS MASTERING app