Agreements and versions
The two documents you accept to use Run, where they are recorded, what happens when a version changes, and why the Privacy Policy is not one of them.
To submit releases, accept the current Terms of Service and Distribution Agreement. The first covers using Run; the second covers distributing your music.
Setup uses one checkbox for both documents. Later updates are accepted individually in Settings → Agreements, where you can also see your acceptance history.
The editions in force
| Document | Edition |
|---|---|
| Terms of Service | Edition of 28 September 2026 |
| Distribution Agreement | Edition of 28 September 2026 |
An edition is named by the date it was published. Both pages state their edition at the top, with the reference code Run records against your acceptance, 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.
After setup, open Settings → Agreements to review or update your acceptance:
- Compare the edition you accepted with the edition now in force.
- Open Read the full text to review the full document.
- Accept the current edition where the section asks you to.
Run records the edition, acceptance time and browser. Setup itself cannot be completed without the required agreements.
What a new version does
Run bumps a version when the meaning changes, not for a typo fix. When that happens:
- A banner appears across the top of the workspace, on every page, until you accept.
- Run emails you, naming the document, the edition now in force, and where to read it. That email only goes to accounts that accepted an earlier version.
- New submissions wait. Submitting a release is refused with a prompt to accept the current versions first.
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.