Which licence do you need when you buy a digital product?

Buying a ready-made app, template or automation doesn't make you its owner. You're buying a licence: permission to use it in particular ways. What you're allowed to do is decided entirely by the licence on that listing, and the difference between them is the difference between a personal project and paid client work.

Start from the work you have in mind, not from the price. Three questions settle it almost every time.

1. Is money involved?

If the thing you're building earns anything — a product you sell, a site that takes bookings, work you invoice a client for — a personal-use licence is the wrong one, however cheap. Personal licences are for learning, private projects and things nobody pays for.

2. How many end products will it become?

Some licences cover one commercial end product: one app, one site, one client. If you build agency sites and want to reuse the same starter across clients, you need a licence that says so, and paying once for a broader licence is cheaper than buying the narrow one repeatedly.

3. Will it carry your name?

If the plan is to rebrand it and launch it as your own, you need a licence that permits rebranding and redistribution. Plenty of commercial licences let you use a product without letting you sell it on as a product of your own.

The licences you'll see on LaunchStock

Every listing states one of these, in the seller's own terms, next to the price:

Ready to Brand

Modify, rebrand and launch it under your own brand.

Commercial use

Use it in your own commercial projects and in paid client work.

Single-product commercial

Use it in one commercial end product.

Extended / multi-client

Use it across any number of end products and clients.

Personal use

For your own personal, non-commercial use.

A listing can also carry the seller's own custom terms: The seller's own licence terms — read them before you buy. Read those in full, because nothing else on the page overrides them.

What no licence here gives you

• Copyright or ownership of the work — a licence is permission, not a transfer, unless the listing is an exclusive acquisition.
• Exclusivity. A standard licence is non-exclusive: other buyers can license the same product.
• Rights over third-party parts. Fonts, images, libraries and APIs inside a product keep their own licences, and the listing should say which.
• A promise that nobody else will launch something similar.

Read the licence you'll actually get

Terms are snapshotted at the moment you pay. The version, licence, refund policy and support terms on the listing when you buy are the ones attached to your purchase, and a seller's later edit doesn't change them — it reaches buyers only once LaunchStock approves it as a new version. Your library keeps the copy you bought under.

If a licence is silent about the thing you want to do, treat that as a no and ask. It's easier before you pay than after a client's site is live.