Your session, your keys, your Mac.
Chorus works beside your DAW with your own accounts. Here is exactly what it reads, what it sends, and where.
Where everything goes
Chorus has no analytics, no tracking and no account. There is no Chorus server between you and your AI provider: requests go straight from your Mac with your key.
Training, keys and control
No training on your sessions
Chorus doesn't train models. By default, Anthropic and OpenAI don't train on API requests. Google doesn't on paid Gemini API keys, but may use free-tier requests to improve its products.
Your keys
Your API keys are encrypted with your macOS keychain and only ever sent to their own service. Chorus never sees them on a server, because there isn't one.
Nothing changes without you
Every change is a proposal until you apply it. History can undo anything Chorus applied, and tracks you lock are off limits to the agent.
Accessibility, for Logic and FL
Logic Pro and FL Studio need macOS Accessibility. Only Chorus Connect, the small helper inside Chorus, holds it, and only to make the changes you approve.
Spending limits
You set a limit per request and per day. Chorus stops before going over and shows what each request cost.
Signed and notarized
Chorus and its updates are signed with Apple's Developer ID and notarized by Apple, so macOS checks them before they open.
When paid plans start
Paid plans will include AI usage, so their requests will go through Chorus to the AI provider. This page will say exactly how before that happens, and using your own key will keep working directly, as it does today.
Questions about any of this: contact us.
Try Chorus on your next session.
Free to download for macOS, for Ableton Live 12, Logic Pro 12 and FL Studio. Bring your own AI key.
