Why this exists

If you release music or games, you end up with codes. A pile of them, pasted into an email from your label or your distributor, that you're now supposed to hand out to fans, reviewers and curators without giving the same one to two people or losing track of which ones worked.

Most people do this in a spreadsheet. It works until it doesn't — usually the moment a release goes well and a hundred people want a code at once.

Launcher Codes is the boring infrastructure for that job. You paste the codes in, share one link, and it handles the rest: one code per person, a captcha so bots don't drain the batch, a record of what's been claimed, and a way for someone to tell you when a code turned out to be a dud.

What it isn't

It isn't a shop, a key reseller, or a place to find free stuff. Codes on Launcher Codes are put there by the artist or studio that owns them, for people they want to give them to. There's nothing to buy, and nothing is generated or cracked.

It also isn't a middleman for anyone's money. When a creator adds a tip link, it points at their own Ko-fi, Buy Me a Coffee or PayPal — payments never pass through this service, and no cut is taken.

Who runs it

Launcher Codes is operated by Launcher Codes. If something is broken, if you think a release here shouldn't be, or if you just want to ask something, write to hello@launchercodes.com and a person will read it.

How it's built

Deliberately small. No third-party analytics, no tracking pixels, no advertising, no third-party scripts beyond the captcha that keeps bots out. Creators can see how many people visited their pages, counted in a way that can't follow anyone between days — the privacy policy explains exactly how. The fonts are served from this domain rather than from Google. There is no cookie banner because there are no cookies to consent to — only the one that keeps you logged in.

Where a creator has added a Bandcamp, Ampwall or YouTube player, it doesn't load until you press play. A page you merely visit tells those platforms nothing at all.

Codes are never readable through the public interface, and handing one out happens inside a single database transaction, so two people clicking at the same instant can't receive the same code. If you care about the details, the privacy policy spells out exactly what is stored and why.