HEAVY MOOSE / CASE FILE 001 · Published October 29, 2026 · [Read the correspondence](#the-record) · [Read the legal sources](#the-rules-and-the-rights)
The injury, the music that helped me endure it, and the distribution decision nobody has explained.
Before Heavy Moose, there was pain.
I suffered a catastrophic injury. The experience changed the way I lived, slept, and processed what was happening to me.
Some of the pain was difficult to describe to anyone who hadn't lived through it. I spent months trying to get through it, including trying to keep things steady for my family over the holidays.
I did not start making music because I wanted to build a brand, satisfy a recommendation engine, or flood streaming services with tracks.
I started because I needed somewhere for what I was feeling to go.
I couldn't find music that captured what I was experiencing. So I began creating it myself. Under DJ Shariff, I made Glass and Ash, Yield, and Temper. These were not albums designed around what I imagined an audience would like. They accompanied emotions and experiences I was trying to survive.
Making them helped time pass. Sometimes it helped me finally sleep. That is not a claim that music cured my injury. It is the truth of what creating meant to me at the time.
Music was emotional expression when I struggled to find another outlet.
Somewhere in that process, Heavy Moose took shape: a larger-than-life artistic voice that could be dark, absurd, funny, angry, reflective, and thoroughly flippin strange. Not every song needs to sound like the worst day of my life. Some of them exist because humor belongs in the story, too.
Yes, AI tools are involved.
I write and develop lyrics, concepts, artistic directions, sound ideas and creative worlds. I also use AI-assisted music-production tools. I do not hide that.
But using generative technology is not the same as proving copyright infringement. What I wrote, what a tool generated, what I was licensed to use, and what a distributor will accept are different questions. They must be evaluated separately, recording by recording.
A platform can decide not to distribute a track. That decision does not, by itself, tell anyone whether the track infringes someone else's rights. Nor does my personal history entitle me to bypass platform policies. I ask only that an impactful decision be explained as far as reasonably possible.
The record
This timeline is based on the October 27–28, 2026 support thread, my October 29 formal dispute, and the legal-team acknowledgment received later that day. All times are Eastern Daylight Time as displayed in the messages. Quotes from DistroKid are short and attributed; the rest is an accurate summary. Private contact fields and tracking tokens have been omitted.
October 27, 2026 · 7:24 PM — I contacted support
My latest album appeared stalled. I reported a prior release delay that I understood to concern a suspected use of another artist's audio stem, which I disputed. I asked if that was happening again. DistroKid's automated support collected my contact information and asked for a UPC; I answered that the latest release had not been assigned one yet. The bot indicated an agent would review the request.
What I asked: What is causing another delay, and what can I do to resolve it?
October 28, 2026 · 8:16 PM — I followed up
I sent a friendly email, asking what had happened and explaining that I was happy to solve an identifiable problem.
In that message I said my concern was that the earlier issue implied I was using another artist's work; I disputed that implication. That was my characterization of the prior issue, not a verified claim that a specific rights holder had filed a complaint.
October 28, 2026 · 9:57 PM — DistroKid answered
In support ticket #5032743, a representative named Joel reported that one or more releases had been rejected for "editorial discretion" and that "stores are no longer accepting releases from you via DistroKid."
The email said DistroKid could not reverse the restriction, that several features were also restricted, and that the company had no further information or context.
The response did not identify the particular release, the originating streaming service, an infringement complaint, an audio match, or a specific policy violation.
Important: The message reports DistroKid's position. I cannot independently verify what each store communicated internally. The absence of stated reasons also does not prove that no valid reason exists.
October 29, 2026 — I sent a formal dispute
I requested individualized review and written answers about:
- The affected recordings, UPCs, ISRCs and available rejection identifiers.
- Which streaming services initiated the restriction versus what DistroKid decided.
- Whether the underlying issue concerns copyright, audio matching, samples, AI policy, metadata, artificial streaming or another category.
- Whether the earlier suspected stem issue is related, and whether a match was verified.
- Whether there has been a human review and whether reconsideration is possible.
- What happens to existing releases, records, accrued royalties and future accounting.
- Which paid services remain available and whether any refund or adjustment is appropriate.
I also requested preservation of relevant records, acknowledgement and a substantive response within ten business days. That letter was sent, not merely drafted.
Later October 29 — DistroKid Legal acknowledged receipt. Its legal-team inbox responded that the inquiry was received and is under review. Another support message referenced a legal reassignment under ticket #5046191. Neither message supplied a substantive explanation of the underlying restriction. I have also separately asked support about reimbursement. This update distinguishes an acknowledgment from an answer.
The rules and the rights
1. Human contributions do not disappear because AI was used. The U.S. Copyright Office's January 2025 report says original human expression may be protected even in works containing AI-generated material. Protection depends on actual human authorship. Prompts alone ordinarily do not suffice, and purely machine-generated material is not automatically protected. This page does not assert that every part of every Heavy Moose recording is copyrightable.
2. Commercial rights and copyright are different. Suno's September 2026 guidance describes commercial-use rights for songs downloaded while subscribed to a paid plan, but cautions that commercial rights do not guarantee copyright protection. Whether a particular Heavy Moose track is authorized depends on its creation/download history, applicable terms, inputs and any third-party rights. This article does not claim blanket authorization without those records.
3. DistroKid explicitly permits qualifying AI-assisted music. Its published AI-upload policy says AI-created music can be submitted subject to rights ownership, no impersonation, anti-spam rules, no infringement and store guidelines. Accordingly, the use of AI technology alone does not explain a specific rejection.
4. Stores and distributors have real discretion. DistroKid's distribution agreement permits stores to decline recordings and the distributor to decline or terminate distribution in specified broad circumstances. I am not claiming a right to compel any store to carry my work.
5. The missing explanation is a genuine customer-experience issue. DistroKid's rejection help page tells users that rejection details will be in the notification and suggests replying if the decision seems mistaken. In my October 28 message, the kind of detail needed to investigate or correct the problem was not supplied. This contrast is documented; it does not establish unlawful conduct.
Selected original correspondence
Below are the artist's own messages reproduced as sent, followed by short attributed excerpts or summaries of DistroKid's replies. Unnecessary personal details have been excluded. Original email records are retained by the artist.
October 27 — Original support request
It looks like this album is stalled in your processing system... again... this happened on my last release and the reason was that there was an issue with a store misperceiving that I leveraged another artist's stem in a song... I wonder if that's the case here? I didn't; my work is original... still... I wonder what could be at play to where this is the second meaningful delay in a row... where I have little course or information but to wait... without answers or reason... little UX nudge in a helpful spirit... anyhow, any insight?
The bot requested a release UPC; the artist replied: Latest release; no UPC assigned yet.
October 28 — Original email follow-up
Heyo, hope you're doing well!
Any update on why this album release has stalled? If I need to solve for something, happy to; I simply need to know what it is.
My concern is that on the prior album it was implied or suggested that I was leveraging another artist's work, which is simply false. Does someone out there just dislike my work so much that they don't want it released or what's the deal? :)
Thanks again for the review and any follow-up information. Hah; if you're hiring, I'd be happy to join forces to help solve for this customer experience gap as I'd imagine it keeps the CS inbox relatively full... meh; I digress. ;)
Thanks for the review and have a great week out there!
October 28 — DistroKid's answer (attributed excerpts)
DistroKid said the release decision was due to editorial discretion, that stores were no longer accepting releases through DistroKid, and that DistroKid lacked other information or context. This is a summary with short extracts rather than a full reproduction of the company's email.
October 29 — Legal acknowledgment
DistroKid Legal confirmed it had received the formal dispute and that the inquiry was under review. The acknowledgment contained no further explanation of the restriction. A separate support email referenced legal reassignment under ticket #5046191.
Questions that remain open
Which recording? Which store? Which rule? Which evidence? Which review process? And what happens to paid services and earnings?
Those are not unreasonable demands for special treatment. They are the questions an artist needs answered to understand a decision that may affect an entire catalog.
An open right of reply
I welcome a substantive clarification from DistroKid, including information that contradicts my understanding. If new verified information comes in, this case file will be corrected or updated with a visible date rather than silently rewritten.
I'm not asking anyone to harass a support representative or assign motives to a company without evidence. I'm asking for specificity.
I began making music because I needed to create it. That reason still matters, regardless of how a distributor ultimately exercises its contractual discretion.
Heavy Moose isn't finished. Not even flippin close.
Editorial disclosure: This is my first-person account supported by correspondence retained in my records. DistroKid's words are attributed, and interpretation is distinguished from documented events. No specific infringement, misconduct or unlawful action has been proven by the correspondence provided here. Email addresses and private contact information are omitted. This is commentary and documentation, not legal advice.