Plain and specific

The short version

MaestroSuite is local-first. Controlling Ableton happens entirely on your iPad, your Mac, and the network cable or WiFi between them. The only data that can ever leave your devices comes from optional features you choose to use — and we name the services involved.

Core control data stays local

Session control data — track names, clip states, BPM, mixer values, MIDI/OSC control data, and device parameters — moves between your iPad and Mac over your local network or USB cable. It is not sent to us or to anyone else.

Your project files are never touched

MaestroSuite does not copy or upload Ableton project files, audio, or stems. The Remote Script reads and controls your live session through Ableton's Live Object Model; it does not harvest your work.

Voice and AI features (optional)

Core control-surface use never requires voice or AI. If you enable cloud voice or AI features, voice audio and/or text prompts may be sent to external processing services. The services currently named in our documentation are Deepgram (speech-to-text) and Anthropic (language interpretation).

Honest note: the final wording for voice and AI processing — including exactly what is processed on-device versus in the cloud — is being reconciled before launch. This page will state it plainly once resolved. Until then, assume enabled voice/AI features may use the cloud services named above.

Diagnostics are yours to send

Nothing is reported automatically. When you choose to send a diagnostics report, MaestroSuite can package:

• Crash reports
• Session breadcrumbs
• MaestroBridge logs
• The Ableton Remote Script log tail

The package is assembled for manual sharing — you see what's in it and you decide whether it goes anywhere.

Questions

Setup details live on the Setup page; common questions are answered in the FAQ.