Content & Quality Policy

Content & Quality Policy

DIMBER doesn't gatekeep based on taste, genre, or how big your following is. We do check that every release meets the technical, legal, and platform standards required to distribute safely and successfully — because a release that gets pulled or flagged by a DSP hurts you far more than it hurts us.

This policy applies to everything you deliver through DIMBER to any digital service provider (DSP). It'll be updated as needed to keep our platform relationships healthy, and where a DSP's own rules are stricter than what's written here, theirs win.

Violating this policy can lead to a release being pulled, royalties being withheld, or your account being restricted or closed. Repeat or serious violations escalate faster.

Rights & Ownership

  • You must own or control every right required to distribute what you submit — the master, the composition, and anything sampled, interpolated, or featured within it.
  • If your track uses someone else's material, you need documented clearance for it before you upload — not after a DSP flags it.
  • Full mixes built from multiple tracks (DJ mixes, compilations) need you to either control every track inside them or hold a license covering commercial release of the whole thing.

Content We Won't Distribute

AI-generated material. If a track is wholly or largely built by an AI model trained on someone else's copyrighted recordings, we need a license from that copyright holder before it goes anywhere — no license, no distribution. Where a platform requires AI content to be labeled as such, that label needs to be there.

Voice cloning and impersonation. Music built around cloning a real, identifiable artist's voice — the "AI (Artist Name)" genre of release — isn't something we'll distribute, licensed or not.

Anything that isn't really yours to release, including:

  • Tracks with hidden or uncleared samples, or audio that's secretly (or not-so-secretly) someone else's recording
  • Remixes, mashups, sped-up/slowed-down/reverbed edits, or other derivative versions — unless you also control and deliver the original, or hold a license to create and distribute the derivative
  • Soundalikes built to pass as another artist's work
  • Karaoke tracks, unless you control the original recording
  • Live recordings, unless you control the studio original
  • Remasters, unless you control the original recording

Re-records are allowed, but only if all of the following hold:

  • You control or have properly licensed the underlying composition
  • The track is clearly marked as a re-record in the metadata — via the version/subtitle field or the title itself (e.g. "(Re-record)," "(2026 Version)")
  • The artist name, title, and artwork can't be mistaken for the original release or artist
  • It gets its own unique ISRC — never the original's
  • You can produce the full rights chain (composition and master) if we or a DSP ask for it

Misleading identity. Artist names that could pass for a well-known act — even with a deliberate misspelling — aren't allowed, and neither is artwork that borrows another artist's or brand's visual identity, logos, characters, or imagery in a way that could confuse listeners about who or what they're hearing.

Unlawful or harmful content, including anything that incites violence or hatred, is defamatory, promotes sexual violence, or promotes the exploitation or abuse of minors.

Explicit Content

If a track contains explicit language and is otherwise compliant with this policy, mark it "Explicit" using the checkbox at upload — don't add "(Explicit)" or similar directly into the track title.

Metadata Standards

Required:

  • Accurate, non-misleading artist names, titles, and contributor roles, with each artist listed in their own field
  • Correct release dates, country availability, and language set at both album and track level

Not allowed:

  • Advertising, URLs, prices, or SEO keywords anywhere in titles, artist names, or artwork
  • Generic placeholder-style artist names (e.g. "Relaxing Music," "Sleep Sounds")
  • Emojis anywhere in metadata
  • Artist names stuffed into the title field, or keyword-stuffed titles

Incomplete or inconsistent metadata is the single most common cause of release delays — double-check spelling and credits before you submit.

Artwork Requirements

Required: high-resolution, square format, and entirely original — nothing that infringes someone else's copyright.

Not allowed: URLs, barcodes, QR codes, price stickers, promotional callouts, references to specific DSPs ("Available on Spotify"), explicit sexual content or graphic violence, or unauthorized third-party logos, brands, or characters.

Audio Requirements

Required: final, correctly encoded masters only — no watermarks, no promo stamps.

Not allowed: more than 10 seconds of silence at the start or end of a track, corrupted or incomplete audio files, or tracks that are actually advertising dressed up as music.

Content DSPs May Deprioritize

Some content is technically allowed but gets deprioritized, demonetized, or rejected outright by individual platforms:

  • Functional/noise audio: meditation tracks, sleep sounds, white noise, ambient rain or environmental recordings. This category is blocked entirely on Deezer and Meta, and may earn reduced royalties elsewhere.
  • Duplicate or artificially inflated content: the same tracks re-released under a new UPC after already being delivered elsewhere, a UPC that repeats the same track more than once, tracks carrying more than one ISRC, an old ISRC reused on new audio to inherit its stream history, or near-identical versions of the same track uploaded repeatedly to game play counts.

What Happens If a Release Doesn't Pass

If something doesn't clear these standards, you'll hear back with specific, fixable feedback — not a blanket rejection. Most issues get resolved and resubmitted quickly.

Serious or repeated violations — rights infringement, prohibited content, fraudulent metadata — can lead to release takedown, account restriction, or termination of your DIMBER agreement.

Questions?

Not sure if something clears this policy before you submit it? Ask DIMBER Support first, it's faster than waiting for a delay to tell you.