Privacy Policy

1. The short version

• We do not sell your personal information, and we do not share it with advertisers.
• We do not sell your music or license it to anyone else. We may use a song to improve Voxen's own audio engine, but only if everyone on that song agrees, and you can withdraw at any time. Section 2 says how.
• We do not run third-party advertising or analytics trackers.
• We never see your card number. Stripe handles payments.
• Mixing and mastering run on our own servers. Your audio goes to outside services only to be stored or checked — listed in section 3.
• You can delete your account yourself, in Settings. Section 8 says exactly what goes and what stays.

2. What we collect

Your account

Your email address, your display name, your role — producer, artist, or both — and the identifier of the sign-in you use with us. Voxen does not store a password: signing in is handled by Microsoft Entra External ID (see section 3). We record when you sign up and when you were last active, which is how the platform knows an account is live.

Your profile

Whatever you choose to add: bio, genres, style, photo, links to your social or streaming profiles, and any sample audio you attach.

What you upload and make

Instrumentals, vocal takes, mixes, masters, artwork, release metadata and split sheets, along with the technical details the platform reads out of them — tempo, key, loudness, duration.

Your work on the platform

Claims and versions, reviews and revision notes, ratings you leave and receive, messages and connection requests, notifications, challenge entries and results, invite-link activity, and the recording sessions the studio uses to tell a redo from a new job.

Payments

We store the amount, the platform fee, the currency, the status, and Stripe's reference for each payment. Card numbers, bank details and identity documents go to Stripe and never reach our servers. If you connect a Stripe account to be paid, we store the account identifier Stripe gives us.

Fan emails

If you run a release page that invites fans to sign up, the addresses they enter are stored against that release and shown to you. Those people are your contacts; section 11 of the Terms covers your obligations to them.

Technical data

Ordinary server logs — request paths, timestamps, error traces — and your session cookie. Logs are for keeping the service running and investigating abuse.

Counting without identifying

Plays, invite-link visits, challenge listens and challenge votes are counted once per person so a refresh does not inflate them. To do that without accounts, we take your IP address, mix in a secret only our server holds, hash the result, and keep the first part of that hash. We do not store the IP address alongside it, and the value cannot be reversed into it. People sharing one connection, such as a household, count as one.

The same kind of hash is used to limit how many accounts, pre-saves and vocalist applications can come from one connection in an hour, so the platform cannot be flooded. Those records are kept for an hour.

Data for future features

When a claim is made we save a snapshot of both sides' public statistics at that moment, and later record whether the collaboration finished. This is kept so that any matching model we build in future is trained on honest historical data rather than on numbers that already contain the answer. It holds account identifiers and public statistics — no audio, no message content, and nothing private.

Once enough collaborations have finished, models are fitted from these snapshots to estimate how likely a pairing is to finish, and how likely it is to be a good collaboration (released, or the two of you making another song), and each is only switched on if it predicts better than simply assuming the average. When one is on (the good-collaboration one first), it orders the beats shown to a signed-in artist in the marketplace, and the estimate made when you start a version is saved so we can check the model against what actually happened. Until then the marketplace uses a plain rule: your genre first, then the producer's track record.

Improving Voxen's audio engine

We may ask the people on a song for permission to use it to improve Voxen's own mixing and mastering. A song is used only if everyone on it agrees, and the permission covers that one song. It can include the takes, the beat, the stems, the mix settings and measurements, and which mixes you kept. It is used only to make Voxen's audio engine better; it is never sold, never licensed to anyone else, and never used to make music. You can withdraw your permission at any time: that stops the song from being used in any training that has not already started, but cannot undo what an engine already released has learned. A song nobody has agreed for is never used this way.

We also suggest a vocal sound for re-mixes when finished mixes in that genre show one is clearly kept more often, and on a beat page we show other beats that at least two of the same artists also recorded on or listened to for 30 seconds or more. A suggestion never reveals what any one person did.

How you use Voxen

To make the product better we record how it is used, on our own servers only — nothing here goes to an analytics company:

• Which days you were active, one entry per day, so we can tell whether people come back.
• Pages and steps in the product: which beat, version and review pages and the sign-in and sign-up pages were opened (and, for sign-up, whether it opened as producer or vocalist), what was searched for and filtered on in the marketplace, the steps of the recorder set-up (asked for the microphone, the browser allowed or refused it and which kind of refusal, the level check passed, a take was started, finished or thrown away), the result of the take check, which notifications were opened, and when a share link was copied.
• How audio was listened to on beats, versions and release pages: how long it played, how far through it got, how many times it was started. This is how we learn whether a producer listened to a take before deciding.
• How a take reached us — recorded in the browser or uploaded as a file — as your browser reported it.
• What the mixing engine did to each recording (tempo, key, alignment, cleanup, loudness and its quality checks), and whether each of you said the finished mix sounds good or needs work, with any note you add.
• Where you first came from: the campaign named in the link you arrived on (for example from one of our emails), or the website that sent you, and the page you landed on. If you came through our home page (voxenmusic.com), which of its buttons you clicked; the home page passes the campaign or the sending website's name on in that button's link, so it needs no cookie of its own.
• Which website sent each page view, by its name only (for example instagram.com, never the address of the post), and which browser family you used (Chrome, Safari, Firefox, Edge, Opera or other — no version or device), so we can see when something breaks for one browser. A bug report or question you send us is different: it carries your full browser details, described under "Bug reports and questions" below.
• What you browsed before signing up, from the same connection, is joined to your new account so we can see what brought you here. People sharing a connection share this record, and we label it that way.
• Your answer to "what got in the way?", if you started a take and never sent it and chose to answer: one of six reasons and an optional note of up to 120 characters. "Not now" is recorded too, so we never ask about that version again.
• What happened to each finished mix: whether it was redone and with which vocal sound, whether you downloaded or edited it, and whether it was released — so we can learn which mixes people keep.
• Which beats were shown in the marketplace list each day, as a count per beat (not who saw them), so a beat shown often is not mistaken for a better one.
• Product experiments: when we test two versions of part of the product, which version you were shown (fixed for you, chosen by a one-way hash) and when you first saw it, so we can compare what each version led to. Some experiments include only artists or only producers; if you are outside one, you see the product as normal and nothing is recorded.

We read these records in two ways. As totals and rates, including a daily summary that compares this week with last week and flags changes too large to be chance. And, for a single member when something has gone wrong, as that member's timeline of the steps above, read by a Voxen administrator to find what got in the way.

If you told us what got in the way in your own words, or recorded a take and never sent it, a member of the Voxen team may email you once to ask about it. You can ignore it, and saying no changes nothing about your account.

For people who are not signed in, these records use the same one-way hash described below instead of an account. We do not record the audio of a take you throw away, or anything you type into the recorder.

Cue chats

Cue is the assistant in the corner of the page once you are signed in. Every message you send it, and every reply it gives, is stored on our servers with your account and the time. That is how your conversation is still there when you come back, and it lets the Voxen team see where Cue gets things wrong. Voxen staff may read these conversations to answer support requests and to improve the product. We keep them indefinitely, and they are kept after you delete your account (section 8).

Bug reports and questions

If you send us a bug report, a feature request or a question — from Cue, or from a Cue chat with "Send this to the team" — we store what you wrote and the kind of report you chose, together with details your browser adds so we can find the problem: the page you were on and its full address, your full browser string (which names the browser and its version, your operating system and often your type of device), the size of your browser window, and the last few errors the page ran into. If you send it from a Cue chat, it is linked to that conversation. We also save your name and email address as they were when you sent it, so we can reply. Reports are read by Voxen staff, kept indefinitely, and kept after you delete your account (section 8).

3. Who else receives it

These are the outside services Voxen uses, and exactly what reaches each one. Each has its own privacy policy, which applies to what they do with it.

• Microsoft Entra External ID — sign-in. Receives your email address and name, holds your password if you sign in with one (or the Google or Microsoft account you sign in with), checks one-time codes, and records sign-in attempts to stop passwords being guessed.
• Stripe — payments and payouts. Receives your email, payment amounts, and, if you are being paid, the identity information Stripe requires to verify you.
• Our email provider — sends account and collaboration emails over SMTP. Receives your email address and the contents of that email.
• Anthropic — the language model behind Cue, briefings, agent suggestions, release copy and studio edit commands. Receives the text of the request, which can include beat titles, your notes, and the figures shown on the page. For Cue, that is your messages in the conversation so far and a snapshot of your account — your display name, how many tracks you have, and the titles and details of your recent releases. It does not receive your audio files.
• ACRCloud — checks a recording against known released music. Receives a short portion of the audio.
• SightEngine — estimates whether audio appears AI-generated. Receives the audio being checked.
• Spotify — optional, only if you connect it. We read public profile and listener figures for your own artist page.
• Our hosting and file storage — the servers that run Voxen and, on production, our cloud storage provider, Microsoft Azure, which holds your uploaded and generated files in Azure Blob Storage in the United States (Azure's East US 2 region).
• Google Fonts — the site loads two typefaces from Google's font servers, so your browser makes a request there when a page loads.
• jsDelivr — a charting library used on the analytics, revenue and admin pages, loaded from a public CDN. Pages that use it work without it.

We will also disclose information where the law requires it, or where it is necessary to investigate fraud or protect someone's safety. If Voxen is ever sold or merged, account data would transfer with it and we would tell you before that happened.

4. What other people can see

Public — visible to anyone with the link, signed in or not: your display name, role, genres, bio, photo, links, your posted beats and their previews, your public release pages and smart links, challenge entries and the challenge board, and the credibility figures next to your name (average rating, number of reviews, plays, finished collaborations, and your reliability score).

Visible to people you work with: the versions you deliver, review notes, split sheets, and the messages you send.

Never shown to other users: your email address, your sign-in details, your payment details, and the contents of your private messages to anyone other than the recipient.

A shared Voxen link carries the invite code of whoever shared it. Following one tells that person their link was visited — as a count, not as your identity.

Voxen staff can see account data through an internal admin view, which is restricted to a fixed list of addresses and is used to run the platform, investigate failures and handle abuse reports. That includes your Cue chats and the bug reports and questions you send us (section 2).

5. Your microphone

The in-browser recorder asks for microphone access only when you use it, and your browser will ask you first. It captures only while a take is running.

Your recording is converted to an audio file inside your browser. Nothing is sent to us until you press upload. If you discard a take, it never leaves your machine — we record only that a take was started, finished or discarded, and how long it was, never the sound.

Once you upload, that recording is treated like any other file you upload — see sections 2 and 3.

You can withdraw microphone access at any time in your browser's site settings.

6. Automated decisions and ranking

Voxen ranks and suggests things automatically. Because those rankings affect who gets found, here is what they actually are:

• Reliability is a statistical lower bound on the share of your resolved collaborations that finished. It measures completion, not quality. A stalled collaboration is charged to whichever side stalled — and to neither of you when the platform itself failed.
• Marketplace and search ordering uses that score together with genre. It is a stated rule, not a learned model.
• Recommendations — "people to work with" — are a plain rule as well, and each one shows the reason it was suggested.
• Challenge boards rank by votes measured against distinct listeners, so an entry does not win on exposure alone.
• Mastering loudness is tuned in the studio by a self-adjusting choice among a small set of preset targets, based on whether people re-run a master. It only ever moves the loudness target, and only within the normal commercial range.

No learned model ranks or scores you today. The matching models described in section 2 switch on only once they predict better than the average. The audio engine does use machine-learning models to separate and analyse sound, but they work on audio, not on decisions about people. Where the product needs a prediction it does not have, it shows a stated fallback and records that it did so, rather than inventing a number. Nothing on Voxen makes an automated decision with a legal or similarly significant effect on you.

7. Cookies and counting

Voxen sets one cookie: the session cookie that keeps you signed in. It is signed, and it is required for the site to work. Your invite code, if you arrived through someone's link, is held in that same session until you register — and so is where you first arrived from, if the link named a campaign or another website sent you. A direct visit stores only a security token in that cookie, which protects your forms from being submitted by another site. Our home page at voxenmusic.com sets no cookie and stores nothing in your browser. Once you are signed in, Cue remembers which of its screens you last had open in your browser's session storage, which is cleared when you close the tab.

There are no advertising cookies, no third-party analytics scripts and no cross-site tracking on Voxen. Play counts, listens and votes are deduplicated using the one-way hash described in section 2 rather than by tracking you.

8. Keeping and deleting data

We keep your account data while your account exists. Uploaded audio, mixes and masters are kept so your collaborations and releases keep working.

When you delete an account we remove the personal fields on the account itself — your email, name, bio, photo, links and connected services — along with your profile, any beats nobody has claimed and their audio, your demo reel, and the messages you sent. From the usage records in section 2 we also remove anything you typed (searches, notes on a mix, your answer to "what got in the way?") and where you came from, including the browsing before signup that was joined to your account; what remains is a record of steps taken, attached to an account that no longer identifies you. Messages other people sent you are their words and their record of the conversation, so those stay with them.

Some things survive deletion, and you should know which:

• Payment records — amounts, fees and dates — are kept as long as tax and accounting law requires. Stripe keeps its own records under its own policy.
• Release passes, subscriptions and processing-cost estimates keep their amounts and dates for accounting, with the link to you removed. If you have an active Voxen Pro subscription, cancel it first: deleting the account is refused until you do, so your card is not charged for an account that no longer exists. A song you unlocked stays unlocked for your collaborator.
• Work your collaborator co-owns — a finished track, a signed split sheet, a published release — is not ours alone to erase. Your name comes off the platform; the record of what the two of you agreed remains available to them.
• Aggregate counts already added up — total plays on a beat, entries in a finished challenge — stay as numbers with nothing identifying in them.
• Security logs for a short period, for fraud and abuse investigation.
• Your Cue chats — every message you sent and every reply — are kept as they are, still linked to your account record. Delete your account and they stay, word for word.
• Bug reports and questions you sent us are kept unchanged, including the name and email address saved with each one when you sent it, and the browser details described in section 2.

Everything not on this list goes immediately when you delete your account.

Two consequences worth stating plainly, because they are easy to assume the other way round. Your uploaded audio is removed from our file storage as well as from the server's own disk, so deletion is not undone by a later restart. And your email address is released — it is not held in reserve, so that address can be used to register a new account afterwards, by you or by anyone else. The copy saved on a bug report you sent is never used to hold it back.

9. Your rights

Depending on where you live, you may have the right to see the data we hold about you, correct it, delete it, get a portable copy, object to some processing, or complain to a regulator.

You can edit most of your information yourself in your profile and settings. For anything else — a copy of your data, a correction you cannot make yourself, or deletion — email support@voxenmusic.com from the address on your account. We will respond within 30 days. We will not charge you for it, and we will not treat you differently for asking.

Where we need a legal basis to process your data: we process it to provide the service you signed up for, to meet legal obligations such as payment records, and for our legitimate interest in keeping the platform working and free of abuse. Where we rely on your consent — your microphone, connecting Spotify, letting a song be used to improve our audio engine — you can withdraw it at any time.

10. Security

All connections use HTTPS. Voxen does not store passwords: sign-in, password storage and password reset are handled by Microsoft Entra External ID. Access to production data is limited to the people who run the platform. Every page that serves your files checks that the file is yours, not just that you are signed in.

If you forget your password, reset it from the sign-in page: Microsoft Entra External ID emails a one-time code to the address on the account.

No online service is perfectly secure. Use a password you use nowhere else. If you believe your account has been accessed by someone else, or if you have found a security problem in Voxen, write to support@voxenmusic.com — a report made in good faith is welcome and we will not pursue you for it.

11. Children

Voxen is for people aged 18 and over and is not directed at children. We do not knowingly collect information from anyone under 18. If you believe a child has created an account, tell us and we will remove it.

12. Where your data lives

Voxen is operated from the United States, and our servers and file storage are there: your files are stored with Microsoft Azure in its East US 2 region. The services in section 3 operate internationally, so using Voxen means your information may be processed outside the country you are in — including in the United States.

Where the law requires a transfer safeguard for that, we rely on the standard contractual protections our providers offer.

13. Changes and contact

We will update this policy as the product changes, and the date at the top always reflects the current version. When a change materially affects how we handle your data, we will say so on the platform before it takes effect.

Anything at all about your data — questions, corrections, a copy, or deletion: support@voxenmusic.com.