Agreements and versions

Two documents govern your account: the Terms of Service, which covers using Run at all, and the Distribution Agreement, which covers distributing music through it.

In the setup wizard you accept both in one act, one checkbox, because it is one decision. In Settings under Agreements each document is listed and accepted on its own. Run records which version you accepted, when, and the browser it came from. Nothing else about the acceptance is stored.

The versions in force

Both pages state the version and the date they were last changed at the top, so the page you are reading always identifies itself.

Where you accept them

The setup wizard asks on your way in, and it summarises what the two documents say before linking the full text. The summary is a summary: the published pages are the contract. See Onboarding, step by step.

If you skipped that step, or you are being asked again, the same acceptance lives in Settings under Agreements. The section lists each document with the version you accepted and the version in force, and accepts the current one in place.

What a new version does

Run bumps a version when the meaning changes, not for a typo fix. When that happens:

1. A banner appears across the top of the workspace, on every page, until you accept.
2. Run emails you, naming the document, the version now in force, and where to read it. That email only goes to accounts that accepted an earlier version.
3. New submissions wait. Submitting a release is refused with a prompt to accept the current versions first.

That last point is the whole of it. Your catalog keeps distributing, your live releases stay live, earnings keep reporting, and nothing is taken down while you read. The submit path is gated because submitting a release is a fresh promise made under the agreement, and the promise has to be made under the text in force.

Accepting again does not undo anything: acceptance history only ever gets longer, so re-running the wizard or accepting a new version leaves the older records intact.

If a new version was published while your tab sat open, the page reloads what it is asking about before it records anything. What you accept has to be what you read.

The Privacy Policy is not something you accept

The Privacy Policy is published, linked from the acceptance screens, and updated like the rest of the set, but there is no checkbox for it and there never will be.

Run does not process your data on the basis of your consent. It processes it to perform the contract you signed and on legitimate interests, which are different lawful bases with different rights attached. Asking you to “accept” a privacy policy would misrepresent that, and it would manufacture a consent record that nothing relies on. So the policy is published for you to read, and it tells you what is done with your data and how to object.

The rest of the published set

Worth reading, none of them click-wrapped:

• Acceptable Use Policy: what may and may not be distributed through Run.
• Anti-Fraud Policy: artificial streaming and what happens when it is found.
• GDPR: your data rights and how to exercise them.
• Cookie Policy: what the sites store in your browser.
• Legal Notice: who operates Run, in full.

Not the same thing: the rights confirmation at submit

Every release you submit carries its own confirmation that you own or control what is in it, and that anything needing clearance has been cleared. That is a promise about one release, recorded with that release, and it is separate from the account-level agreements above. See Rights and ownership.

Questions about the documents themselves go to legal@run.audio. Questions about your own account belong in a support request, where whoever answers can see the account.