shortn

about

A shortener with
nothing hidden.

shortn is a link shortener that tells you what it does with your data, publishes every change it makes, and does not pretend to be something it is not.

Why it exists

Most shorteners are free because you are the product. They want your traffic profile, your click history and your patience while they show you an advert. shortn takes a different trade: it is small, it is honest, and it asks almost nothing of you.

There is no account to create, no email to hand over, no cookie banner to dismiss and no third-party script watching what you paste. The whole interface is a few static files and a handful of edge functions.

How it is built

PieceWhat it does
Static sitePlain HTML, one shared stylesheet and one small script. No framework, no build step required to read it.
Edge functionsServerless handlers on Cloudflare's network for the API and for redirects.
KV storeOne namespace. Slug to destination, a click counter per slug, rate-limit buckets and a short stats cache.
Rate limitingSliding one-minute windows in KV with a short expiry, so the counters clean themselves up.
Link lifetimeSeven days. Each link is written with a matching KV expiry and every read re-checks the deadline, so a link past seven days is treated as missing and deleted on the spot.
QR codesRendered by a single browser library. The content never reaches a server.
ThemesThree of them — dark, light and Halloween — as CSS variables on one root element.

What it deliberately does not do

Where the money goes

There is no charge for anything, so there is no billing page either. The rotating banners on the site exist to cover the hosting bill, which is the only cost involved. If they ever go away, the service keeps working.

What data exists

For each link: the destination, the slug, a creation timestamp and an integer click count, kept for seven days and then deleted. For each visitor: a rate-limit key built from their IP, which expires within two minutes and is never attached to a link. That is the whole list.

The details, including what Cloudflare sees in the process of serving a request, are in the privacy page.

Getting in touch

Reports of abuse, broken redirects or anything that needs correcting go to abuse@shortn.pages.dev. A link that needs to disappear before its seven days are up should include the slug so it can be found quickly — after that it deletes itself. For anything about how the service behaves, the documentation and API reference cover it in more detail than an email would.

Related

There is a second site, oursites-lol, which lists projects and tracks their live status. It shares this design system and nothing else.