BTR Music · Partners · Legal

Partner Terms.

These Partner Terms are a general legal and operational framework between OUTERMARK GROUP PTY LTD (ACN 699 247 277), trading as BTR Music and BeatsToRapOn (BTR), and the company or legal entity that applies for or uses BTR Partner Services (Partner).

Version 1.0 · 23 September 2026 · New South Wales, Australia

Important. These Terms govern onboarding, sandbox access, the Partner Portal, API, catalogue delivery, rights, takedowns, reporting, security and general operating rules. Commercial terms are agreed Partner by Partner. Revenue model, settlement, currency, launch scope, catalogue scope, payment timing, service levels and any other negotiated terms are recorded in a separate Partner-Specific Agreement.

Reusable framework

One baseline for distributors, labels, aggregators and other authorised rights holders.

Partner-specific economics

No universal royalty rate, settlement method, minimum guarantee or payment threshold is created by signup.

Precedence

If a Partner-Specific Agreement conflicts with these Terms, the Partner-Specific Agreement prevails to the extent of that conflict.

You accept these Terms when an authorised representative accepts them through the Partner Portal, uses Partner credentials after acceptance, or signs a Partner-Specific Agreement that incorporates them. Acceptance of these Terms alone does not require either party to enter into a production commercial relationship.

1. Definitions

Approved Artist Identity means an artist identity, BTR account or BTR-managed artist record approved for delivery by Partner.

Artificial Streams means plays or engagement generated or inflated through bots, scripts, stream farms, paid-for-play services, compromised accounts, coordinated manipulation or other non-genuine listener activity.

BTR Artist ID means the identifier BTR assigns or approves for an artist identity used in Partner delivery.

Deal Terms means rights, territory, start/end dates, use type and other rights metadata supplied with Partner Content.

Delivery means a catalogue submission through the Partner API, DDEX ERN, Partner Portal or another BTR-approved channel.

Partner Content means recordings, artwork, metadata, credits, identifiers, lyrics, images and other materials delivered by or for Partner.

Partner Services means the Partner Portal, Partner API, sandbox, documentation, credentials, reporting and related partner tooling.

Partner-Specific Agreement means an Order Form, DSP agreement, distribution agreement, commercial schedule, side letter or other written agreement that states terms specific to Partner.

Production Access means BTR's activation of credentials or channels allowing catalogue to be processed for live availability.

Service means BTR Music and the BTR-operated consumer surfaces on which Partner Content is made available under these Terms and the applicable Partner-Specific Agreement.

2. Scope and relationship

2.1 These Terms establish the baseline legal and technical framework for Partner onboarding and use of the Partner Services.

2.2 The relationship is non-exclusive unless a Partner-Specific Agreement expressly states otherwise.

2.3 BTR receives catalogue as a digital music service. BTR is not Partner's distributor to third-party DSPs and does not act as Partner's agent.

2.4 Partner remains responsible for its relationships with artists, labels, licensors and other rights holders and for accounting to them.

2.5 No minimum guarantee, advance, royalty rate, revenue-share percentage, catalogue minimum, promotional obligation, exclusivity, launch date, settlement schedule or service credit arises merely because Partner applies, creates an account or accepts these Terms.

2.6 Partner-Specific Agreements may add to, replace or vary these Terms for that Partner.

2.7 Sandbox and evaluation access do not authorise public exploitation of Partner Content. Production rights begin only when Production Access has been enabled and any required Partner-Specific Agreement is in force.

3. Onboarding, accounts and security

3.1 Partner must be a business or legal entity that owns, controls or is authorised to license catalogue to digital music services.

3.2 BTR may request company, ownership, tax, sanctions, rights, payment or other reasonable verification information before enabling Production Access.

3.3 Partner is responsible for its Partner Users, credentials, API keys and activity under its account.

3.4 Credentials are confidential. Partner must keep them secure, rotate compromised credentials and remove users promptly when authority ends.

3.5 Partner must notify BTR without undue delay of a security incident materially affecting Partner credentials, unreleased content or the Partner Services.

3.6 BTR may approve, reject, pause, restrict or revoke onboarding or access where reasonably required for technical, legal, compliance, security or commercial reasons.

4. Artist identities and authority

4.1 Partner may deliver only for artist identities BTR accepts for that Partner through an applicable mapping or approval workflow.

4.2 BTR may link Partner to an existing BTR artist account, approve a managed artist identity or use another supported identity workflow.

4.3 Partner warrants it holds a current written chain of authority sufficient to license each Delivery to BTR. That authority may come directly from an artist, label, catalogue owner, licensor or other person entitled to grant the rights.

4.4 Partner must retain reasonable evidence of its authority and provide it if required for rights verification, certification or a dispute.

4.5 Partner must use the applicable BTR Artist ID in the manner described in current technical documentation.

4.6 If Partner's authority ends, narrows or is credibly disputed, Partner must promptly update or take down affected catalogue.

5. Delivery and technical standards

5.1 Partner may deliver using the Partner API, DDEX ERN through a BTR-approved delivery channel, the Partner Portal or another method BTR approves in writing.

5.2 Current supported formats, ERN versions, metadata fields, rate limits, validation codes and certification requirements are published at partners.btrmusic.com/developers.

5.3 Current developer documentation is the authoritative implementation contract for purely technical details unless a Partner-Specific Agreement expressly overrides it.

5.4 Partner must provide accurate identifiers, metadata, rights periods, territories, use types, artwork and media required by the technical contract.

5.5 BTR may reject or hold Deliveries that fail technical validation or require rights, compliance, quality, fraud or artist-mapping review.

5.6 BTR may require sandbox certification before Production Access is granted.

6. Licence to BTR

6.1 For Partner Content accepted for Production Access, Partner grants BTR a non-exclusive, royalty-bearing licence, during the applicable rights period and in the authorised territories, to:

6.2 Partner retains ownership of Partner Content.

6.3 Any materially different exploitation requires authorisation under Deal Terms, a Partner-Specific Agreement or other written approval from Partner.

7. Restrictions on BTR

7.1 BTR will not deliver Partner Content to third-party DSPs as Partner's distributor.

7.2 BTR will not use Partner Content, stems or derived features to train or fine-tune generative models that produce music, vocals or lyrics unless Partner separately opts in in writing.

7.3 BTR will not offer downloads, sync licensing, creator remixing or another materially different exploitation unless authorised.

7.4 BTR may retain fingerprints, logs and archival copies reasonably required for security, fraud, rights, reporting, legal and audit purposes.

8. Partner warranties and responsibilities

8.1 Partner represents and warrants that it has authority to enter these Terms and any Partner-Specific Agreement and sufficient rights to license each Delivery for the supplied territories, rights period and use types.

8.2 Partner warrants that Partner Content and metadata are accurate and, to Partner's knowledge after reasonable checks, do not infringe third-party rights or applicable law.

8.3 Partner is responsible for obtaining required clearances for recordings, artwork, samples, performers, contributors and other third-party materials.

8.4 Partner is responsible for payments and accounting it owes to artists, labels, licensors and other rights holders unless a Partner-Specific Agreement expressly reallocates an obligation.

8.5 Partner must keep rights and metadata current and promptly send updates or takedowns when they change.

8.6 Partner must not knowingly deliver malware, fraudulent catalogue, manipulated metadata or catalogue intended to generate Artificial Streams.

9. Review, publication and rejection

9.1 BTR retains the final publication gate.

9.2 A technically valid Delivery may still be held, restricted or rejected for rights, compliance, fraud, quality, artist-mapping, safety or legal reasons.

9.3 BTR provides available status and validation information through the Partner Services.

9.4 Availability on the Service is not a legal finding that Partner Content is non-infringing.

9.5 BTR does not guarantee editorial placement, recommendation, chart position, promotion, listener numbers or revenue unless a Partner-Specific Agreement expressly provides otherwise.

10. Updates and takedowns

10.1 Partner may update supported metadata, artwork, audio, rights periods and territories through the applicable update or redelivery workflow.

10.2 Partner may initiate takedowns through the Partner API, supported DDEX takedown or PurgeReleaseMessage flow, the Partner Portal or another approved channel.

10.3 Valid automated takedowns are processed without waiting for manual commercial approval.

10.4 BTR may initiate or accelerate removal where required by law, a credible rights complaint, sanctions, fraud, safety concerns or material breach.

11. Usage reporting

11.1 BTR provides Usage Reports for production catalogue according to the cadence agreed with Partner or the standard cadence then supported by the Partner Services.

11.2 BTR's standard reporting capability may include recording/ISRC, release identifier, territory, reporting period and eligible usage, with formats described in the developer documentation.

11.3 Dashboard or near-real-time analytics are indicative operational data. Settlement is governed by the applicable Usage Report and Partner-Specific Agreement.

11.4 BTR may correct reports for fraud, invalid usage, duplicate catalogue, metadata corrections or manifest error.

11.5 Usage Reports do not provide listener-level personal information to Partner.

12. Commercial terms and settlement

12.1 There is no universal default DSP economic model under these Terms.

12.2 Revenue share, royalty-pool participation, per-stream rates, minimum guarantees, payment thresholds, settlement timing, invoicing, currency, payment method, tax treatment, reserves, clawbacks and related commercial terms are agreed Partner by Partner.

12.3 Those terms may be recorded in a BTR Order Form, a Partner's standard DSP agreement, a negotiated distribution agreement, a commercial schedule or another Partner-Specific Agreement.

12.4 BTR may permit onboarding, sandbox certification and technical assessment before commercial terms are finalised.

12.5 BTR is not required to activate Production Access or incur payment obligations merely because Partner accepts these Terms or completes technical testing.

12.6 Once Production Access and the applicable commercial terms are active, BTR will report and settle according to the Partner-Specific Agreement and applicable Usage Reports.

13. Fraud, artificial streaming and compliance

13.1 Artificial Streams are excluded from payable usage unless a Partner-Specific Agreement or applicable law requires otherwise.

13.2 BTR may investigate, hold, exclude, reverse or claw back usage reasonably identified as fraudulent, manipulated or otherwise ineligible, subject to the applicable Partner-Specific Agreement.

13.3 BTR may suspend content, artist identities or Partner access while investigating credible rights, fraud, sanctions, security or legal concerns.

13.4 Partner will reasonably cooperate with such investigations.

14. Rights complaints and disputes

14.1 BTR may remove or disable Partner Content while a credible rights complaint or ownership dispute is investigated.

14.2 Partner must provide reasonable evidence of authority or submit a takedown when requested.

14.3 BTR may hold disputed amounts where reasonably necessary pending resolution.

14.4 BTR may require competing claimants to resolve ownership disputes between themselves or through an appropriate legal process.

15. Data, confidentiality and privacy

15.1 Each party must protect the other's non-public commercial, technical, security and unreleased information using reasonable care and use it only for the relationship.

15.2 Confidentiality does not apply to information that is public without breach, already lawfully known, independently developed or lawfully obtained from another source.

15.3 Listener-level usage data, service logs and recommendation signals remain under BTR's control. Partner receives only data made available through the Partner Services or required by a Partner-Specific Agreement.

15.4 Personal information is handled in accordance with the BTR Partner Privacy Notice.

16. Term, suspension and termination

16.1 These Terms begin when accepted and continue while Partner maintains a Partner Account or uses the Partner Services, unless terminated.

16.2 Either party may terminate these Terms on 30 days' written notice unless a Partner-Specific Agreement specifies another period.

16.3 Either party may terminate immediately for serious uncured breach, insolvency, sanctions restriction or unlawful conduct where immediate termination is reasonably required.

16.4 BTR may suspend access or catalogue while investigating security, rights, fraud, sanctions or compliance concerns.

16.5 On termination, BTR stops accepting new production deliveries and removes Partner Content in accordance with applicable takedowns and the Partner-Specific Agreement. Accrued reporting, payment, confidentiality, dispute and liability obligations survive as required by their nature.

17. Liability and indemnities

17.1 Neither party is liable for indirect or consequential loss, or loss of profit, revenue, goodwill or anticipated savings, except where such exclusion is not permitted by law or a Partner-Specific Agreement says otherwise.

17.2 Subject to clause 17.3, each party's aggregate liability under these Terms is limited to the greater of AUD 10,000 and the amount paid or payable by BTR to Partner in the 12 months preceding the event giving rise to the claim.

17.3 The limitation does not apply to fraud, wilful misconduct, confidentiality breaches, infringement indemnities, Partner's lack of rights or authority, BTR's properly due payment obligations or liability that cannot lawfully be limited.

17.4 Partner indemnifies BTR and its related bodies corporate, officers, employees and contractors against third-party claims and resulting reasonable losses arising from Partner Content, Partner's breach of rights warranties or Partner's lack of authority.

17.5 BTR indemnifies Partner against third-party claims that the Partner Services themselves, excluding Partner Content and Partner materials, infringe third-party intellectual property rights.

18. General

18.1 These Terms, the Partner Privacy Notice and each applicable Partner-Specific Agreement comprise the agreement concerning the Partner Services and Partner Content.

18.2 Order of precedence: a Partner-Specific Agreement prevails to the extent of any conflict; these Terms then prevail on legal matters; current developer documentation governs implementation details unless expressly overridden.

18.3 The parties are independent contractors.

18.4 Either party may factually identify the other as a partner once the relationship is live, subject to reasonable brand guidelines and confidentiality obligations. Neither may imply endorsement beyond the actual relationship.

18.5 BTR may update these Terms on at least 30 days' notice for material changes. A general Terms update does not amend separately agreed commercial terms unless the Partner-Specific Agreement permits it.

18.6 These Terms are governed by the laws of New South Wales, Australia. The courts of New South Wales have exclusive jurisdiction, subject to any alternative dispute process in a Partner-Specific Agreement.

18.7 Partner operational notices may be sent to partners@btrmusic.com. Formal legal notices should also be copied to info@beatstorapon.com.

18.8 Electronic acceptance and electronic signatures are binding. BTR may retain the accepted version, user identity, timestamp, IP address and user agent as evidence of acceptance.

Schedule 1 — Partner-specific commercial terms

This Schedule intentionally sets no default economics. The following are agreed separately for each production Partner.

ItemTreatment
Commercial modelPartner-specific: revenue share, royalty pool, per-stream rate, minimum guarantee or another agreed model.
Payable usage definitionPartner-specific, including eligibility, fraud exclusions and territory rules.
Reporting cadencePartner-specific; BTR's standard reporting capability is monthly.
Settlement timingPartner-specific.
CurrencyPartner-specific.
Payment methodPartner-specific.
Threshold / reservePartner-specific, if applicable.
Invoicing / self-billingPartner-specific.
Tax treatmentAs required by law and the Partner-Specific Agreement.
Catalogue scopePartner-specific: full eligible back catalogue, new releases, selected catalogue or another agreed scope.
ExclusivityNone unless expressly agreed.
Marketing commitmentsNone unless expressly agreed.

Schedule 2 — Technical delivery baseline

The current developer documentation is authoritative for exact request/response formats and validation behaviour.

AreaCurrent baseline
APIREST over HTTPS with partner API keys. Documentation: partners.btrmusic.com/developers.
DDEXERN 4.3.x currently certified. Other versions require BTR approval before use.
Artist IDUse the BTR Artist ID. Where several DDEX PartyIds exist, BTR prefers ProprietaryId Namespace="BTR".
IdentifiersUPC/EAN/ICPN at release level and ISRC per recording as required by the technical contract.
AudioCurrent validation accepts WAV, FLAC, AIF/AIFF, MP3 and M4A, subject to documented hash and technical requirements.
ArtworkJPEG or PNG, square within validation tolerance, minimum 600×600; 1400×1400 or greater recommended.
RightsTerritories, rights periods and authorised use types are supplied using applicable Deal Terms.
IdempotencyDDEX MessageId is used for message idempotency. Redelivery with a new valid MessageId updates the existing catalogue record according to documented rules.
TakedownsPartner API, supported DDEX takedown/PurgeReleaseMessage flow and Partner Portal controls where available.
ReportsMonthly reporting capability through the Partner API, including TSV/CSV outputs.
CertificationBTR may require sandbox testing before Production Access.

Schedule 3 — Operational baseline and contacts

These are operational targets, not service credits or guarantees. A Partner-Specific Agreement may replace them.

ItemBaseline
API acknowledgementImmediate HTTP acknowledgement where a request is accepted for processing; final processing state is available through polling and, where configured, webhooks.
Automated takedownApplied on successful processing without manual commercial approval; BTR targets propagation across BTR-controlled consumer surfaces within approximately 5 minutes.
Rights / legal takedownActioned according to law and the circumstances; Partner informed where lawful.
Partner supportpartners@btrmusic.com.
Developer documentationhttps://partners.btrmusic.com/developers.