Privacy policy
The short version
- We keep what the studio needs to make and store your music, and nothing for advertising.
- Your recordings and prompts go only to the services that do the work for you, named below.
- We never train models on your music, and we never sell anything about you.
- Two cookies, both needed to use the site. No ad trackers, no third-party analytics, nothing loaded from anyone else.
- An invitation from us is one email, with an image that counts opens. Unsubscribe and we never write again.
- Ask to see, correct, download or delete what we hold, and we answer within thirty days.
This summary is for reading; the full text below is what applies.
This is what Muzze knows about you, why, where it goes and how long it stays. Muzze is run by [Operator's legal name], who is the controller of this data. The short version: we keep what the studio needs to work, we send your recordings and prompts only to the machines that do the work for you, we do not train on your music, and we do not sell anything about you.
What we collect
Your account
- Your email address and handle, and when you confirmed the address.
- A one-way hash of your password. We cannot read the password itself.
- When you accepted the terms, and which version.
- For each engine whose terms you have accepted: which engine, which license, when, and the IP address the acceptance came from. This is the record that you chose it; see the engines page.
Your music
- The recordings you upload or record in the browser.
- The styles, negative prompts, lyrics, titles and settings you give each track.
- What is made: the audio, the score, the model's performance tokens, the stems, and the measurements the page draws from — peaks, loudness, beat grid.
- Notes the server writes about a render, such as what it changed and why.
How Muzze is used
- Ordinary server logs: IP address, browser, the pages and requests you make, and when. Kept for security and to find faults, and rotated within a few weeks.
- Job records: which tracks rendered, on which engine, how long they took. This is how we account for GPU time.
Invitations
Muzze is a private beta, and we write to some people to invite them: one email, never a second, to an address its owner published for people to contact them, such as on a channel or portfolio page. For each one we keep the address, the name and the public page we found it on, the line we wrote to them, and what happened: whether the email was opened (from a small image in it), whether its link was followed, and whether it made an account. If you asked for an invite, we keep your address and what you wrote until we answer. Unsubscribe from any invitation and we keep only the address, so that we never write to it again.
Feedback
What you send from the Feedback page, about one of your songs, or by email: the message, which song and how you judged it, the page you were on, your browser, and your account or the address you gave, so we can answer. We use what you say about songs to tune the engines; the songs themselves are not used to train anything. It is read by the people who make Muzze and kept while it is useful to them.
Payment
If you subscribe, our payment processor collects your card details and billing address and sends us a customer reference, the plan you bought and whether the payment succeeded. We never see or store your card number.
What we do not collect
Muzze sets two cookies, and neither is for tracking: one keeps you signed in, and the other holds what a single visit needs, such as the token that protects its forms and an invite code you followed a link with. There are no advertising trackers, no analytics scripts from third parties, and no fingerprinting. Pages, scripts and fonts come from Muzze itself and audio from our own storage provider, so opening a page tells no one else you were there. The only tracking image is the one in an invitation, described above; the emails about your account have none. We do not buy data about you or email lists from anyone.
Why we use it
- To run the studio for you — rendering, storing and playing your music is the service. This is performance of our contract with you.
- To bill you for a plan or credits and account for GPU time.
- To keep the beta for people — confirming that an email address is its owner's, so that accounts made by scripts do not take the places or the free credits.
- To keep Muzze safe — rate limits, abuse detection, and investigating misuse. This is our legitimate interest in running the service.
- To meet legal duties — responding to a proper copyright notice or a lawful request, and keeping the records of consent described above.
We do not use your recordings, prompts or music to train models, ours or anyone else's, and we do not let anyone else do so. We do not use your data for advertising.
Where it goes
Your data is processed by these kinds of providers on our behalf, under contracts that bind them to use it only for us:
- GPU compute: RunPod. When a track renders, the recording, prompts and settings for that job are sent to a GPU machine we rent, the engine runs there, and the result comes back. The working files are deleted from that machine within hours of the job finishing.
- Language model hosting, for the lyric writer and “Fill out the sound”: the theme, style or lines you ask them to work from are sent to the server that writes the draft.
- Hosting and storage for the app, the database and your files.
- Payments, if you buy a plan or credits.
- Email, for account messages (the link that confirms your address, and messages about your account and plan) and for invitations.
The Muzze v0.5 engine, and any other engine an account is offered, runs on machines we rent and control. Nothing you upload or make is sent to the authors of the models it is built on. Some providers may be in another country from you; where the law requires it, we rely on standard contractual clauses or an equivalent for the transfer.
Beyond that, we share data only when the law requires it, to respond to a proper copyright notice as described on the copyright page, or to protect Muzze or its listeners from harm.
How long it stays
- Your account and your music: until you delete them or close your account. Closing it is at the bottom of your plan page, and deletes your tracks, stems, uploads and credits at once.
- After an account is closed: the invite it joined with, so the same inbox cannot claim free credits twice, and any feedback you sent us, which we may still need to answer.
- Render working files on GPU machines: hours.
- Server logs: a few weeks.
- An invitation that was never used: its record is deleted within a year, except the address of anyone who unsubscribed, kept so they are never written to again.
- Backups: a short rolling window, after which deleted data is gone from them too.
- Records of accepted terms and engine licenses, and billing records: as long as the law requires us to be able to show them, which can be after the account is closed.
Your rights
Wherever you are, you can see what we hold about you, correct it, download your music, and delete your tracks or your whole account from inside Muzze. Depending on where you live you may also have rights to restrict or object to processing, to portability, and to complain to a supervisory authority. To exercise any of these, write to contact@muzze.ai; we answer within thirty days.
Children
Muzze is not for children. You must be at least 18, or the age of majority where you live, to have an account. If we learn that a younger person has one, we delete it.
Security
Connections to Muzze are encrypted. Passwords are hashed. Access to the machines is limited to the people who run them, and the GPU machines accept requests only from Muzze. No system is perfectly secure, and if a breach affects you we will tell you as the law requires.
Changes
When this policy changes, the date at the top changes with it and we will point it out in the studio. If a change would let us do something materially new with your data, we will ask first.
Contact
[Operator's legal name]
[Operator's street address]
contact@muzze.ai