Privacy and data use

What is stored

The service stores your Google account identity, private profile, tracks, notes, versions, invitation state, assistant requests and proposals, bounded usage totals, and support-safe operational metadata. Operational events contain only a correlation reference, route category, outcome, status, latency, and configured model when relevant. They never contain account email, track source, notes, full prompts, credentials, or provider payloads. Tracks are private to their owner and protected by database row-level security.

For private-beta access support, the project administrator can see invitation state, display name, username, last successful sign-in, onboarding state, active-track count, and latest active-track time. This view does not expose track names, source, notes, prompts, audio, live presence, or a behavioral timeline.

What leaves your device

Editing and playback run in your browser. Saved source and track metadata are sent to the hosted Supabase project. Audio playback is never rendered or recorded by this service. When you explicitly ask the assistant, the saved track source, name, notes, and request are sent to OpenAI to produce a reviewable proposal.

Control and retention

You can export track source from the workspace. For an access, correction, deletion, or account-closure request, use the Beta support page and identify only your account and a safe correlation reference. Never send API keys, passwords, or private track source in a support message.

Raw operational events remain only within the hosting provider's configured log-retention window. Privacy-safe weekly counts and percentiles may be retained for 90 days for beta reliability review; they cannot be used to reconstruct your music or identity.