VIBE by HitFluence

Our AI Manifesto

Creativity belongs to the creator.

At VIBE, artificial intelligence is built to serve the artist — not replace them.

We believe musicians should remain in control of their sound, creative decisions, intellectual property, and relationships with listeners. Our goal is to make sophisticated creative tools accessible while preserving transparency, consent, artistic independence, and accountability.

AI is a collaborator. The musician is the decision-maker.

What that means in the apps today

A statement is only worth what the software does. These are the rules VIBE’s apps follow now. Where something is still being built, it says so.

You approve what Duke does

Duke is the assistant in VIBE Studio. He starts in Ask mode: he shows you the plan and waits for your click before anything runs. Studio has two other modes, Auto and Bypass, and choosing one is your decision, made in the app.

  • When Duke suggests a change to a mix, the answer goes onto your mix sheet only when you add it.
  • An invitation is never sent for you. Nothing goes to a listener until you press Send in Messages or Mail.
  • A paid video generation asks first, naming its price and any file it will send.In development

You hear an audio fix before it’s kept

Vibe AF, the audio repair app, is built around one rule: a repair can be approved only after it has passed its checks and you have played it. The original file is never written to. A finding that runs across a whole stem may be the sound you intended, so it is left alone unless you ask.In development

Changes can be undone

  • Saving a mix specification writes a new revision and keeps every earlier one.
  • Bringing repaired stems back into Studio puts them in a folder of their own. The originals are not touched.
  • Vibe AF keeps earlier versions of a repair on your Mac and never deletes anything from your iCloud.In development
  • Signing out of Studio is local. Nothing is deleted, and your work is there when you sign back in.

Data is sorted by how private it isIn development

VIBE’s runtime sorts data into four classes: public metadata, internal runtime data, private user data, and restricted data. Its default policy blocks the last two and replaces them with a redaction marker before an AI component can read them. This is built into the runtime and is not yet applied to every feature, so we list it as in development.

Where it runs

Not everything in VIBE runs on your device, and we won’t say it does. Here is each place a feature can run and what leaves your device when it does.

On your device

Nothing in this list sends your words or your music anywhere.

  • Duke’s conversation in Studio. Duke answers with Apple’s on-device model when Apple Intelligence is turned on, and with VIBE’s own model on your Mac when it is off.
  • Speech to text in Studio. Apple’s speech recognition, running on the Mac.
  • Vibe Melody. Sing or hum, and the notes and words are read on your Mac. Separating a vocal from a mix also happens on the Mac.
  • Lyric timing. In Studio and in the listener apps, lyrics are timed against the song on the device. The timing model is downloaded the first time it is needed; your audio is not uploaded.
  • Duke on iPhone and iPad. VIBE’s own model runs on the device. Voice input uses on-device speech recognition on devices that support it; on others, Apple’s speech service may process what you say.

Apple’s Private Cloud Compute

Private Cloud Compute is Apple’s service for running larger models on Apple’s servers. One VIBE feature uses it: the written explanations in Vibe AF.In development

  • What is sent: text only. The measurements Vibe AF took, the decisions and the checks.
  • What is never sent: audio, file names, song names or file paths.
  • Vibe AF’s permissions also allow it to send spectrogram images, which are pictures of a sound’s frequencies. The current build sends text only.
  • VIBE Studio does not use Private Cloud Compute.
  • The listener apps do not use it today.

iCloud and CloudKit

This is storage and sharing, not AI. When you publish, your catalogue is shared from your own iCloud through a private CloudKit share that only the iCloud accounts you invited can open. Messages, plays and likes travel the same way. Privacy & Security has the details.

Optional third-party services

These run only when you choose to use them.

  • Video generation. Vibe Video Studio and Vibe Creator Studio can send your prompt and the images you pick to WaveSpeed and OpenRouter, using keys you add yourself. Each paid run asks first.In development
  • Looking something up. When you ask Duke to search the web, your search goes to DuckDuckGo.
  • Posting to social networks. If you connect Facebook, Instagram or TikTok, the posts you approve are sent to that network.In development

Your music files

In the apps as they are today, your audio files are not sent to Private Cloud Compute or to a third-party AI service.

Questions about any of this? Ask us on the Support page. The rules about who owns what are in Music Rights & Responsibilities.