Privacy policy.
Effective August 6, 2026
What OPUS:6 collects
When you create or use a cloud account, Firebase Authentication processes the identifiers needed for sign-in, such as your email address, provider user ID, display name, and profile image. Google or Facebook may provide those details when you choose their sign-in button. OPUS:6 never receives your Google, Facebook, or email-account password.
Your music and audio
Your rack, sequences, synth settings, and projects are stored in your browser on the device you use. They are not uploaded to an OPUS:6 server in this version. Microphone audio is used only for the live visualization you request and is not recorded or uploaded by OPUS:6. MIDI input stays in your browser.
How data is used
Account information is used to sign you in, maintain your session, recover access, display your identity, and prepare account-linked studio features. OPUS:6 does not sell personal information and does not use account data for third-party advertising.
Storage and service providers
Authentication is provided by Google Firebase. Its processing is governed by Google’s applicable privacy and security terms. Device-local music data remains under your browser’s storage controls unless you export and share a project yourself.
Your controls
- Sign out from the account panel.
- Reset an email password from the sign-in panel.
- Delete your cloud account from the signed-in account panel.
- Clear local studio data using your browser’s site-data controls.
- Export a project before clearing or deleting anything you want to keep.
Children and changes
OPUS:6 is not directed to children under 13. We may update this policy as cloud sync and live collaboration are introduced; the effective date above will change when that happens.