Acceptable Use Policy

REGULATORY PURPOSE:

These Rules establish the minimum legitimacy, security, and quality requirements for using UMW Core, submitting Phonographic Content, administering Metadata, requesting payments, operating a white-label integration, or accessing an application programming interface. The person using the Services is referred to as the “User.” Music Platforms, social networks, video Services, and other enabled destinations are referred to as the “Platforms.” The User must understand and comply with these Rules before uploading, delivering, claiming, monetizing, or removing content.

Single Entry Rule: Use UMW only for music, catalogs, identities, and operations for which you have verifiable authorization.

This page operates as a conduct and preparation manual. It is not a condensed copy of the Service Terms.

Review it before:

• creating an Account;
• uploading a release;
• activating Content ID;
• connecting an integration.

‍FIRST.— PRINCIPAL RULE.

These Rules describe what may be submitted to UMW Recordings and how UMW Core, DSP deliveries, Content ID, UMW Song Assets, tools, and business integrations must be used.

Use UMW only for music, catalogs, businesses, and operations for which you have authorization.

Do not attempt to create a false appearance of:

‍SECOND.— AUTHENTIC ACCOUNTS.

• ownership;
• identity;
• audience;
• revenue;
• a relationship with another person.

Each Account must identify its actual holder and the persons acting as part of its team.

The following is prohibited:

• opening an Account using another person’s identity;
• using false or altered documents;
• concealing the ultimate beneficial owner when verification is required;
• selling, renting, or lending an Account;
• creating new Accounts to evade a suspension;
• registering as a representative without authorization;
• allowing a former collaborator to retain access after authorization has been withdrawn.

‍THIRD.— WHAT MUST BE READY BEFORE SUBMITTING A RELEASE.

The administrator of a label or company must assign minimum necessary roles and periodically review access.

The User must have confirmed:

• the final master recording;
• authorized cover artwork;
• accurate artists and roles;
• composers and lyricists identified by their complete names when required by the DSP;
• producers, performers, and other material credits;
• the owner of the phonographic copyright and composition copyright;
• explicit-content status;
• release date and Territories;
• licenses for samples, beats, covers, remixes, or adaptations;
• splits and internal authorizations;
• previous identifiers when the release is being migrated.

‍FOURTH.— PROHIBITED AUDIO.

Do not submit a demo, provisional file, or reference cover artwork as the final product.

The following may not be distributed:

‍FIFTH.— COVERS, REMIXES, AND DERIVATIVE WORKS.

• a master recording copied or downloaded without authorization;
• another artist’s audio renamed by the User;
• a version altered solely to evade a match;
• pirated, leaked, or stolen material;
• an unauthorized sample when a license is required;
• a beat used beyond the scope of the purchased license;
• a remix or mashup without the necessary permissions;
• a recording that infringes a person’s likeness, voice, or performance;
• damaged, silent, spam-manipulated, or non-musical files when the Platform does not permit them.

A cover license does not authorize the User to:

• modify lyrics;
• translate the Work;
• sample the original master recording;
• use the original artist’s name in a misleading manner.

‍SIXTH.— COVER ARTWORK AND IMAGES.

A remix requires authorization covering the master recording and, when applicable, the composition. A beat license does not necessarily provide exclusivity or Content ID eligibility. The User must accurately disclose the nature of the version.

‍SEVENTH.— METADATA.

Cover artwork must not:

• use photographs, logos, or characters without authorization;
• create the appearance of affiliation with a DSP;
• include false or misleading information;
• display incompatible codes, prices, or other information;
• sexually exploit minors;
• contain malicious instructions or misleading QR codes;
• violate communicated technical specifications.

Visual acceptance by UMW does not constitute a license to use the image.

‍EIGHTH.— ARTISTS, COMPOSERS, AND PROFILES.

Metadata must accurately describe the delivered audio.

The following conduct is prohibited:

• adding popular artists who did not participate;
• using playlist names, trademarks, or search terms as titles to divert traffic;
• concealing collaborators;
• deliberately changing spelling to create duplicate artist profiles;
• declaring a false historical release date;
• marking explicit content as clean;
• assigning an ISRC or UPC belonging to another recording;
• dividing the same audio into repetitive releases;
• uploading automated translations that alter legal names.

UMW may request links to existing profiles and composers’ legal names.

‍NINTH.— UPC, ISRC, AND ISWC.

The User must distinguish between:

• primary artist;
• featured artist;
• remixer;
• producer;
• composer;
• lyricist;
• label.

‍TENTH.— ARTIFICIAL INTELLIGENCE.

The use of Various Artists or generic terms to conceal identities is prohibited when the Platform requires credits.

Do not reuse an ISRC for a materially different recording. Preserve the ISRC when migrating the same master recording, when applicable. Do not present a UPC or ISRC as evidence of copyright ownership. Do not claim that UMW Recordings assigns ISWCs. UMW Song Assets may prepare and transmit registrations through an authorized route. The competent entity assigns the code.

‍ELEVENTH.— STREAMING AND PROMOTION.

Content created or modified using artificial intelligence may be submitted only when:

• the User has the necessary rights to the inputs and outputs;
• the content does not deceptively imitate a person;
• the content does not clone a voice without authorization;
• the content complies with DSP policies;
• required credits and notices are accurate;
• the content is not generated at scale to saturate catalogs or manipulate systems.

‍TWELFTH.— CONTENT ID AND UGC.

UMW may request:

• an explanation;
• identification of the tools used;
• source files;
• authorizations.

Do not purchase or coordinate:

• streams;
• followers;
• saves;
• searches;
• repeated playback through controlled devices;
• guaranteed playlist placements;
• artificial TikTok creations;
• automated comments or engagement;
• incentivized traffic presented as organic audience activity.

‍THIRTEENTH.— UMW SONG ASSETS.

The following is permitted:

• legitimate advertising;
• public relations;
• social content;
• editorial pitching without guarantees;
• campaigns directed at real persons.

Content ID requires sufficient control and, ordinarily, exclusivity over the reference.

Do not submit:

‍FOURTEENTH.— UMW PROTECT.

• a non-exclusive beat;
• a commonly available loop;
• stock music;
• shared-library audio;
• a public-domain recording used identically by others;
• generic ambient sound;
• content containing incompatible samples;
• material already administered exclusively by another company.

Do not dispute a claim when you know that the third party has superior rights. Do not claim channels authorized by the Rights Holder.

A publishing application does not authorize registrations.

‍FIFTEENTH.— UMW CORE.

Do not submit:

• splits exceeding one hundred percent (100%);
• nonexistent authors;
• Works administered exclusively by another publisher without authorization;
• an ownership interest you do not control;
• false Society information;
• conflicting instructions from co-authors.

Each activated composition must appear in Annex A of an accepted Publishing Order.

‍SIXTEENTH.— WHITE-LABEL SERVICES.

UMW Protect may create a timestamped record of a file and its related information.

The User must not present it as:

• a government certificate;
• a registration from SENADI, the U.S. Copyright Office, or another government office;
• a determination of authorship;
• a transfer of rights;
• conclusive evidence against a third party.

Do not use UMW Protect to register material belonging to another person.

‍SEVENTEENTH.— API.

The following conduct is prohibited:

• testing another person’s credentials;
• altering balances or statuses;
• interfering with uploads or delivery;
• extracting databases;
• performing unauthorized scraping;
• introducing malware;
• circumventing limits;
• using exposed tokens;
• manipulating webhooks;
• abusing forms;
• sharing another Account’s private information.

A vulnerability must be reported to legal@umwrecordingsinc.com or through the security channel published by UMW, without exploiting the vulnerability or disclosing personal data.

‍EIGHTEENTH.— PAYMENTS AND WALLET.

A white-label Client must:

• clearly identify its own company to its Users;
• publish its own prices and agreements;
• establish valid legal bases for processing personal data;
• perform the agreed KYC procedures and controls;
• refrain from promising deliveries or relationships not included in its agreement;
• keep its Clients’ Accounts separate;
• protect credentials and roles;
• communicate incidents;
• retain evidence of acceptance;
• refrain from presenting UMW as directly responsible for its own commercial obligations.

The white-label Client may not resell access beyond the limits of the agreement.

The production API is available only to approved partners.

The following is prohibited:

• using sandbox credentials in production or production credentials in sandbox;
• sharing secrets;
• deliberately exceeding limits;
• creating fictitious Users or releases for testing in production;
• querying unauthorized Accounts;
• retaining responses beyond the agreed necessity;
• ignoring webhook signatures;
• developing an unapproved feature using royalty or identity data.

UMW may rotate or revoke credentials when a risk exists.

‍NINETEENTH.— SUPPORT.

Do not attempt to:

• change a beneficiary through impersonation;
• request payment for another person’s catalog;
• submit a duplicate request;
• conceal chargebacks;
• use a bank Account without authorization;
• alter tax documents.

A balance displayed in a mockup, demo, or sandbox environment is not real money.

During checkout, do not attempt to:

• bypass verification;
• manipulate the Order;
• alter the total;
• reuse a payment authorization;
• automate payment card attempts;
• submit payment information you are not authorized to use.

‍TWENTIETH.— MARKETING, NAMES, AND TRADEMARKS.

UMW never requires the User to send the following by email or chat:

• a password;
• PIN;
• CVV;
• authentication token;
• banking credential;
• complete payment card number.

Use one ticket for each matter and provide, when applicable:

‍TWENTY-FIRST.— UNLAWFUL CONDUCT.

• the Account;
• UPC;
• ISRC;
• release;
• Platform;
• screenshot.

The following conduct is prohibited:

• threatening personnel;
• sending complete payment card information;
• flooding communication channels to manipulate priority;
• impersonating a lawyer, DSP, or authority;
• publishing personal data belonging to employees or Clients;
• submitting fabricated information.

A firm complaint or criticism does not, by itself, constitute abuse.

Do not use UMW, DSP, or third-party trademarks in a manner suggesting:

• sponsorship;
• certification;
• an official Account;
• a partnership;
• publishing authorization;
• a guarantee.

A white-label Client may use only the assets and references permitted by its agreement.

‍TWENTY-THIRD.— NOTICE AND CORRECTION.

Do not use UMW for:

• child sexual exploitation;
• credible threats;
• extortion;
• money laundering;
• sanctions evasion;
• the sale of personal data;
• malware or phishing;
• unlawful discrimination;
• intentional infringement;
• any activity prohibited by law.

The User must also not use UMW to:

TWENTY-SECOND.— HOW UMW RESPONDS.

• collect, publish, combine, or commercially exploit personal data belonging to artists, employees, Clients, Claimants, or third parties without a valid legal basis;
• disclose identification documents;
• direct harassment using information obtained through the dashboard.‍

‍TWENTY-FOURTH.— IMMEDIATE MEASURES.

UMW may:

• request a correction;
• change a status to Action Needed or Documents Needed;
• reject a delivery;
• restrict a feature;
• suspend Content ID;
• protect an Account;
• transmit a takedown;
• apply a related reserve;
• suspend credentials;
• terminate the Account in serious cases.

The measure must correspond to the conduct and follow the Anti-Fraud Policy when an investigation exists.

‍TWENTY-FIFTH.— APPEAL.

When an issue may be corrected, UMW will identify:

• the applicable Rule;
• the content or feature;
• the required correction;
• the applicable period;
• the consequence of failing to respond.

For a release in Action Needed or Documents Needed, the operational period may be up to thirty (30) days before the submission is closed.

A specific anti-fraud period is governed by the Anti-Fraud Policy.

‍TWENTY-SIXTH.— PRIORITY AND CHANGES.

UMW may act without prior notice when necessary to:

• stop clearly pirated content;
• comply with an order;
• prevent immediate loss;
• block compromised access;
• prevent payment fraud;
• protect minors;
• respond to a technical threat.

‍TWENTY-SEVENTH.— PERSONAL DATA, COMPLAINTS, AND EVIDENCE.

UMW will provide notice afterward when permitted by law and the applicable risk.

The User may respond to the ticket or write to legal@umwrecordingsinc.com, identifying:

• the case;
• the decision;
• the alleged error;
• supporting evidence.

An appeal concerning invalid activity follows the Anti-Fraud Policy.

A DMCA counter-notification follows the Copyright and DMCA Policy.

These Rules supplement the Service Terms. An Order may impose stricter controls on a B2B Service, but it may not reduce mandatory rights. Material changes will be notified and applied prospectively. An urgent DSP rule may apply to affected content from the time it becomes mandatory, without converting previously lawful conduct into fraud.

Access, review, fraud, and payment controls process personal data in accordance with the Privacy Policy. An automated alert does not authorize a final sanction without human review. The User may review applicable decisions through:

Account → Privacy and Security → Privacy and Acceptance History

The User may request a structured data download or submit a complaint to the DPO through the same center.

Those features do not permit the download of:

• anti-fraud trade secrets;
• data belonging to other Clients;
• information whose disclosure would prejudice third-party rights.

Any exclusion must be explained.

‍