AI music for Reels, TikTok and Shorts: what Sume's Terms say

Sume's Terms of Service say Sume does not claim ownership of outputs created for your account, and that paid plans include commercial use as described on the pricing page. They also say you are responsible for reviewing outputs before you publish, distribute or use them commercially. That is all Sume states; the music docs say nothing about Reels, TikTok, Shorts or Content ID.

So the safe answer to "can I post it" has two parts: Sume's side is the Terms quoted here, and each platform's rules for AI audio sit outside Sume. This page lists what to check, using Sume's Music 1.0 and Music Router pages.

What do Sume's docs state about a track?

Music 1.0 returns an audio/mpeg artifact from Lyria 3.5 for a fixed $0.125. The docs describe prompts, the policy rejection path and metadata; they do not describe licence terms, a clearance database or fingerprint registration. If you need a signed statement for a client, ask Sume rather than assume one exists.

What should you do before posting?

Treat this like any commissioned asset. Listen to the whole track once for anything that sounds like a recognizable song; a clean prompt does not guarantee a clean result. Keep the prompt and the job result with the final video.

• Write a brief without artist names or lyrics from real songs.
• Keep the audio file and the request body together.
• Use a paid plan for commercial posts, per the Terms.
• Check each platform's AI disclosure setting at upload time.

How do platforms differ?

Each platform sets its own rules for audio and for AI labels, and those rules change. Sume's docs do not summarise them, so this post does not either. A related stored page compares label rules by platform; open it for the grade of each source, and re-check the platform page the day you publish.

What if a claim lands anyway?

If a platform flags a track, you will deal with it through that platform's dispute process. Your evidence is the prompt, the date, the job result and your plan at the time. A 59 second cut can help with Shorts length rules, which is covered in a stored page, but length does not change the licence question.

A practical pre-publish checklist

Write down five things for each track: the prompt, the date, the plan you were on, the job result and the platform you published to. If a client asks where the music came from, that record answers them in a minute. If you cannot fill one of the five, regenerate or replace the track before you publish.

Also decide the music's role. Background music under speech needs a lower level than a music-led montage; Sume's timeline audio can set duck_db on a soundtrack so it dips under speech, and a stored page covers how long to make the track relative to the video.

• Prompt and date.
• Plan and job result.
• Platform and upload time.