DSIV Creator License Quickstart

Use this worksheet before checkout or before asking DSIV whether a project fits the standard creator license path. It is meant to keep the storefront simple while still giving creators, clients, and production teams a clean way to explain use.

Project snapshot

Project name:
Track title:
Product or order link:
Primary platform or release destination:
Expected publish date:
Creator, artist, client, brand, agency, broadcaster, game, film, TV, app, installation, or other:
Estimated reach, ad spend, media budget, or campaign size:
Will this be paid, sponsored, boosted, licensed to a client, broadcast, screened, embedded in an app/game, or distributed outside your own channel?

Quick path

Use this path when the project is your own creator, artist, podcast, social, YouTube, recap, trailer, livestream, or portfolio release and the music is not being resold, repackaged, broadcast, used in paid media, or transferred as exclusive work.

Ask before checkout when the use involves:
- A client, agency, brand, sponsor, label, broadcaster, network, game, app, film, TV, festival, or paid ad campaign.
- Raw audio redistribution, stem resale, template resale, sample-pack use, AI training, NFT/drop resale, or anything that implies exclusive ownership.
- A project where another company needs written clearance, invoice notes, cue metadata, or a custom license summary before release.

Use case check

Where will the music appear?
- Social video:
- YouTube or long-form video:
- Podcast, livestream, or intro sequence:
- Artist promo, trailer, or recap:
- Client work:
- Brand campaign:
- Paid ad or boosted post:
- Film, TV, festival, game, app, installation, or broadcast:
- Private pitch, deck, or proof of concept:

Approval-needed uses

Contact DSIV before relying on a standard creator path when the project involves paid media, broadcast, film, TV, games, apps, agency/client campaigns, exclusivity, resale, distribution as part of a template, raw audio redistribution, or unclear commercial use.

License fit checklist

Before checkout, confirm:
- The track title and product page match the music you plan to use.
- The final project type is allowed by the license path you are choosing.
- The final file will include DSIV music inside a finished project, not as a standalone audio product.
- The client or collaborator understands the license is tied to the described use.
- You know whether you need a receipt, invoice note, cue row, or custom clearance reply.
- You have a place to store the license summary with the project files.

Files needed

Standard master:
Instrumental:
Loop or edit:
Clean edit:
Stems:
Alt mix:
Custom music:
Exclusive or one-off use:
Invoice or receipt:
Cue metadata:

Delivery and recordkeeping

Save a folder named after the project and keep:
- The downloaded DSIV file or protected delivery package.
- The order receipt or invoice.
- The product page link and license page link.
- This worksheet or your approval email.
- The final project export and publish URL.
- Any cue sheet, metadata row, or client clearance note.

If a delivery link fails, do not repurchase immediately. Save the order number, product title, email used at checkout, and the exact delivery issue, then contact DSIV through the project request page.

Post-purchase record

Keep these with the project file:
- Purchased audio file or download receipt.
- Product/order link.
- License summary and usage limits.
- Track title, artist, writer/publisher, duration, and cue metadata when needed.
- Client approval notes or usage emails.
- DSIV contact path for future questions.

Client handoff notes

Client/project owner:
Final project title:
Final URL or release destination:
Music title:
DSIV order/reference:
Allowed use summary:
Anything excluded or needing separate approval:
Cue metadata needed: yes / no
Invoice note needed: yes / no

Decision tree

1. Is this your own creator, artist, social, podcast, livestream, or portfolio project?
   If yes, the standard creator path may fit.

2. Is a brand, client, agency, label, broadcaster, game studio, app, film, TV project, festival, or paid media buyer involved?
   If yes, ask DSIV before relying on the standard creator path.

3. Will the music be included only inside a finished project?
   If yes, keep the project notes and order receipt together.
   If no, do not use this path for raw audio redistribution, sample-pack resale, template resale, or model-training datasets.

4. Does another company need written clearance, invoice language, cue metadata, or a delivery summary?
   If yes, request a custom clearance reply before release.

Usage boundary

Allowed project summary:
Platform or destination:
Who publishes it:
Who owns the final edit:
Paid media, sponsored use, or client transfer:
Raw audio, stems, loops, or templates redistributed:
Need exclusivity:
Need custom invoice language:
Need cue metadata:

Before checkout

Before paying, confirm:
- Product title matches the selected track.
- License tier or variant matches the intended use.
- Delivery email is correct.
- Any approval-needed use has a written DSIV reply.
- Client/project notes are stored with the order.
- You have a backup plan if the delivery email lands in spam or a protected link expires.

Upgrade path

If the project grows after checkout, keep the original order reference and contact DSIV before expanding into:
- Paid advertising or boosted campaigns.
- Broadcast, film, TV, game, app, festival, or installation use.
- Client transfer outside the original scope.
- Label, publisher, distributor, or brand clearance.
- Exclusive music, stems, custom edits, or custom scoring.

Questions for DSIV

1.
2.
3.

Copy/paste request

Project name:
Track requested:
Where it will be used:
Who owns or publishes the final project:
Paid/sponsored/client/broadcast use:
Estimated reach or media spend:
Files needed:
Timeline:
Questions:

Note

This quickstart is not the final legal license. It is a planning worksheet for getting the right license answer and keeping the order/project handoff clean.