Our promise
Your music is yours.
AI should mean more people making music, not fewer, and it should never take the work of the people it helps. So your audio stays on your computer: False Audio listens to your tracks inside the Link plugins, and when you make a request, the Hub sends text and numbers that describe them. Never sound.
Here is exactly what leaves your computer, what we keep, and what we don't.
When you make a request
What leaves your computer
The Hub sends the request over HTTPS to our server. Our server checks your account and credits, then passes the request to the Claude API, from Anthropic, to plan the move. The reply comes back to the Hub as a proposal or a question. A request includes:
Sent with a request
- The words you type, and the earlier messages in the same conversation.
- The names, labels and roles of the tracks that have a Link, such as “Gtr L, electric guitar”.
- Measurements of the tracks your request is about, as numbers: levels across the frequency range, resonant peaks, loudness (LUFS), peak level, crest factor, and stereo correlation and width.
- The current settings of those tracks’ Links.
Never sent
- Audio of any kind: no tracks, stems, bounces or recordings.
- Your project files.
- Tracks without a Link. The Hub doesn’t know they exist.
- The traffic between the Hub and its Links. That stays on your computer.
You can check this yourself. The Hub’s debug drawer shows the exact last request it sent.
Without a request
What works on your computer alone
Measuring your tracks, auditioning with A/B, applying a proposal and undoing a change all happen on your computer, with nothing sent. The Hub keeps its change history in the plugin’s state, so it’s saved with your project like any other plugin setting.
On our side
What we keep, and what we don’t
We keep
- Your account: your email address, and a display name if you set one.
- Your signed-in Hubs: a name for each, like “Logic Pro on MacBook”, and when it was last used. The Hub keeps its sign-in key in your Mac’s Keychain. We keep only a fingerprint of that key, not the key itself.
- Your credits: starter credits, purchases, and what each request cost.
- A usage record for each request: when it ran, which AI model handled it, how much text it read and wrote, its cost, and how long it took.
We don’t keep
- Anything to train AI on. We don’t build models from your music, your sessions or your requests.
- The text of your requests and of the replies.
- The measurements the Hub sends.
- Your card details. Stripe handles payments; we keep only the reference Stripe gives us for your account.
Your control
Disconnect a Hub at any time
Your account page lists every Hub you’ve signed in. Disconnect one and it can no longer make requests, within about a minute.
Who else is involved
The services we use
- Anthropic
- Its Claude API reads each request and writes the proposal or question.
- Vercel
- Hosts this website and the server the Hub talks to.
- Supabase
- Holds accounts, signed-in Hubs, credits and usage records.
- Stripe
- Takes payments.
The full policy is still being written. Read the draft privacy policy