Who is responsible for your data
Run is operated by Void Music Group (SASU), registered in France under SIREN 992 576 322, with its registered office at 25 rue de Ponthieu, 75008 Paris, France. For the personal data described here, Void Music Group is the data controller within the meaning of the General Data Protection Regulation.
The full registration record is on our Terms of Service page. We have not appointed a Data Protection Officer, which we are not required to do; data protection requests reach us directly at privacy@run.audio.
What we collect
Account and identity
Your email address, your password in hashed form, and, if you turn it on, your two-factor authentication setup. We record sign-in events, the plan your account is on, and the moment you accept a version of our terms, with the browser user agent used. We deliberately do not record your IP address against that acceptance.
Account security and abuse prevention
While you are signed in we record the IP address your session connects from and when we last saw it, and we keep the addresses seen on your account for as long as the account exists. They are part of the copy of your data you can download from Settings. If we close an account for breaking our rules, the addresses tied to it stay on an abuse denylist after the account itself is gone, so that a closure can be recognised rather than quietly restarted under a new sign-up. We rely on our legitimate interest in keeping the service safe and in preventing fraud, impersonation and circumvention of an enforcement decision. We use these addresses for nothing else: no advertising, no working out where you live, and no tracking of you on other sites.
Artist and release data
The artist profiles you create (name, photo, website and social links, and the store profiles you connect), and everything that makes up a release: titles, credits, contributor and writer names, roles and publishing splits, ISRCs and barcodes, release dates, AI disclosures, rights lines, the audio and artwork you upload, and any clearance document you attach. Credits and splits describe real people, so this includes personal data about your collaborators, which you provide to us.
Billing
Subscription state: your customer and subscription reference at our payment provider, your plan, its status and its renewal date, plus the invoices generated. Payment details are entered directly with our payment provider. We never receive or store your full card number.
Earnings and analytics
Statement, transaction and royalty data reported to us for your releases, and the streaming and engagement figures the platforms report, which reach us as aggregates by release, period, country, age band and gender band, not as data about identified listeners.
Your earnings ledger
A ledger of what your releases earn, kept under a financial reference number rather than under your name: the royalties reported for each of your releases and recordings by store, country and reporting period, the share of them that is yours for each period (recorded when the period first reaches us, so a later correction is worked out at the same share), and every amount credited to or paid from your balance.
Payouts
A record of each payout we make to you: the amount, the date, the reporting periods it covers, the provider’s reference for it, any fee it cost and whether it went through. The identity checks, tax details and bank or wallet details needed to pay you are collected by our payout provider, not by us. We never receive your bank or wallet details.
Communications and support
A record of the transactional emails we send you (template, subject and recipient, never the message body), whether they bounced or were marked as spam, the in-app notifications you receive, and the content of messages you send us. If you use Run Copilot, the assistant in the workspace, the question you type and the recent conversation are sent to our AI assistant provider to generate the answer. We keep a record of each request (when, from which section of the workspace, the outcome and its cost) and never the text of the question or the answer; the conversation itself stays in your browser tab.
Run Copilot without an account
Run Copilot also answers visitors on this website and in our Help Center, with no account and no sign-in. When you send it a message, the question you type, the recent turns of the conversation, the Help Center passages the question matched and the name of the part of the site you asked from (the Help Center’s releases section, for example) go to our AI assistant provider to generate the answer. The conversation stays in that browser tab: moving to another page starts a new one, and we keep no copy of it.
What we keep is a record of each message (when, from which part of the site, the outcome and what it cost), filed under a random identity rather than under you. The first time you send a message, our servers place a cookie in your browser that holds that identity, signed so it cannot be forged, and nothing else; on our side we store only a one-way hash of that identity, never the cookie itself. It is how we count your messages so the daily and monthly limits hold. We do not record your IP address against any of this, we do not fingerprint your browser, and nothing links the identity to a name, an email address or an account.
Before a new message leaves your browser, a bot check from our bot-protection provider runs, and if it needs you to do something, it appears inside the assistant’s panel. It is loaded only at that moment, never when a page loads or when you just open the assistant, and it looks at signals from your browser and device to tell a person from an automated script. Your browser connects to the provider directly to run it, as it does to fetch anything on the web; when we confirm the result with the provider, we send it the check’s own token and nothing about you, not even your IP address.
Technical data
Server and delivery logs kept for security, abuse prevention and debugging, which can include IP addresses, timestamps, browser and device information, and the actions taken in your account. Administrative actions and release state changes are written to an audit log.
Why we use it, and on what legal basis
- To run the service you asked for (performance of our contract, and the steps you ask us to take before you have one): creating and securing your account, checking and delivering your releases, connecting your store profiles, reporting delivery, earnings and analytics back to you, paying you your share of what your releases earn, taking payment, handling takedowns, answering support requests, and answering the questions you put to Run Copilot, signed in or not.
- To meet our legal obligations: accounting and tax records, invoices, the record of the payouts we make, and responding to lawful requests and to rights holders’ complaints.
- Our legitimate interests: keeping Run and its users safe, preventing fraud, impersonation and artificial streaming, screening submitted audio for unauthorised use, enforcing our terms and store policies, keeping Run Copilot’s use fair and its cost bounded (what its usage records, the visitor cookie and the bot check before a visitor’s message are for), and improving how the service works. We balance these against your rights, and we use the minimum data that achieves the purpose.
- Your consent, where we ask for it: non-essential cookies, and any optional message you opt into. You can withdraw consent at any time, which does not affect what we did before you withdrew it.
We do not sell personal data, and we do not use it for behavioural advertising or profiling for advertising purposes.
International transfers
Run is operated from the European Union, and your account database and uploaded files are hosted in the European Union. Some of the recipients listed above are established in the United States, as their regions show, so distributing your music and running the service involve transfers outside the European Economic Area.
Where that happens, the transfer is covered by the European Commission’s Standard Contractual Clauses or another mechanism recognised under Chapter V of the GDPR, together with the technical measures described elsewhere in this policy. Ask us and we will tell you which safeguard applies to a specific transfer, and to which company.
Our payout provider is established in Switzerland, which the European Commission recognises as giving personal data an adequate level of protection, so what we send it for your payouts needs no further safeguard.
How long we keep it
- Account, artist and release data: for as long as your account is open. Deleting your account in Settings schedules the erasure 14 days ahead and stays cancellable during those days. After that we erase your profile, your artist profiles, your drafts, the audio and artwork you uploaded and your notifications, and keep only what is necessary for the records below. What we keep no longer carries your name or your postal address, and it is no longer attached to an account: it is kept under a reference number instead. That is pseudonymous, not anonymous (see Your rights).
- Delivered releases: while the release is distributed, and afterwards for as long as the delivery and rights record has to be kept, since a release that has shipped may still be the subject of a claim or a royalty correction.
- Accounting and tax records, including invoices, statements, royalty records, your earnings ledger and the record of the payouts we make to you: ten years, as French commercial law requires. They outlive your account under their reference number, together with the list of your releases’ identifiers (release ids and ISRCs), so that royalties a store reports after your account has closed are still recognised as yours, at the share in force when the account closed. To pay them, we keep the email address we will settle through when your account is erased: for up to 12 months after it closes if your releases were delivered to the stores (royalties arrive months after the plays), and after that only while money is still owed to you. We delete that address once neither applies.
- Records of terms you accepted: for as long as the agreement can be relied on, since they are the proof that it was accepted.
- Email delivery records and the do-not-contact list: for as long as needed to keep honouring an unsubscribe or a complaint.
- Assistant usage records: 90 days, then deleted, and sooner if the account is erased. A visitor’s records are deleted after 90 days too. What outlives them is a daily and a monthly total of what the assistant cost us, one across every account and every visitor and one for visitors alone, and neither carries an account or a visitor reference.
- Sign-in addresses: the addresses seen on your account are kept while the account is open, and they go when it is erased. Addresses tied to an account we closed for breaking our rules stay on our abuse denylist afterwards, because outliving the closed account is the whole point of them; that entry holds the address and the reason it was added, and no name, no email address and no link back to the erased account. Write to us if you think an entry should go, and a person looks at it.
- Technical logs: short retention, in the order of weeks to months, except where an entry is part of a security or abuse investigation.
Automated checks on your releases
Releases you submit are checked automatically before they are delivered: metadata against store requirements, audio files against format and quality requirements, and audio against a fingerprint database to detect unauthorised use, impersonation and undisclosed reuse. Copies of the audio are sent to our matching provider for that check.
These checks can hold a release or send it back to you with reasons. They are not a decision taken solely by automated means about you as a person: anything flagged is reviewed by a member of our team before a release is rejected, you are told why, and you can correct the release and resubmit it, or write to us to contest the outcome.
Your rights
Under the GDPR you can ask us for access to your personal data, for a copy in a portable format, for correction of anything inaccurate, for erasure, for restriction of processing, and you can object to processing based on our legitimate interests. Where processing rests on your consent, you can withdraw it at any time.
Much of this is immediate in the workspace: your profile, artist details and releases are yours to edit, and Settings carries two controls for the rest. Download your data assembles everything we hold about your account into one machine-readable file and emails you when it is ready; you download it from Settings while signed in. That file is your personal data in one place, so store it somewhere private. Delete your account schedules the erasure 14 days ahead, stays cancellable in Settings until then, and requests a takedown for any release already at the stores.
For anything else, write to privacy@run.audio from the address on your account. We answer within one month, and tell you if we need longer because a request is complex. Both flows, and the limits on them, are set out step by step on our GDPR page.
Some requests have limits. We cannot erase records we are required to keep: billing and accounting records, for the ten years French commercial law asks for; the audit log; and the record that an agreement version was accepted. Those stay in pseudonymous form: no longer attached to an account and without your name, but not anonymous, because we can still link financial records to the releases they came from, and our payout provider can link a payout it made to the person it paid. Pseudonymous data is still personal data, so everything this policy says about protecting it keeps applying to them. We also cannot recall a release from a store’s own systems: we can request its removal from the stores, which they then action on their own schedule. If we closed your account for breaking our rules, the addresses tied to it stay on our abuse denylist, for the reason given under How long we keep it.
If you used Run Copilot without an account, the records of your messages are filed under a random identity that only the cookie in your browser carries, so we cannot find them from your name or your email address, and the controls in Settings do not reach them. They are deleted after 90 days on their own. Clearing the cookie in your browser ends the link between you and them at once, and your next message starts a new identity.
What our payout provider holds about you, the identity checks, tax details and payment details you gave it, is held under its own privacy policy, and deleting your Run account does not delete it. Ask Talentir directly, or ask us and we pass your request on.
If you gave us data about your collaborators (credits, writers, splits), you are responsible for having the right to give it to us and for telling them how it is used. Point them to this page, and they can exercise their rights with us directly.
Security
Access to your data is restricted at the database level so that an account reaches only its own records. Credentials for the services we use are held as server-side secrets and never shipped to the browser. Traffic is encrypted in transit, uploads are checksummed and validated, incoming webhooks are signature verified, and administrative access requires two-factor authentication. Administrative actions are recorded in an audit log.
No service can promise perfect security. If a breach affects your personal data, we notify the CNIL and, where the law requires it, you.
Children
Run is not intended for children. You must be at least 16 to hold an account, and under 18 you need a parent or legal guardian to accept our terms with you. If you believe a child has given us personal data, write to us and we will remove it.
Changes to this policy
We update this policy as the service changes. The version and date at the top of this page always tell you which edition is in force, and that line is how a new edition is announced: this policy is published rather than agreed, so there is nothing here for you to re-accept. Where a change also touches a document you did accept, our Terms of Service or the distribution agreement, we put the new edition in front of you in the workspace before it binds you. This edition has not been reviewed by external counsel, and it will say so here until it has been.
Contact and complaints
Privacy requests and questions:
privacy@run.audio
Void Music Group SASU, 25 rue de Ponthieu, 75008 Paris, France
If you are not satisfied with how we handled your request, you can complain to the French data protection authority, the Commission Nationale de l’Informatique et des Libertés (CNIL), 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, www.cnil.fr, or to the supervisory authority of the country where you live.