Owner-operated · no tracking
Short links on a domain you own.Analytics that forget who clicked.
Create memorable links like /launch, change where they point without changing the link, and see aggregate counts — never an IP address, never a cookie, never a fingerprint.
Your links, at a glance
Every link shows its live destination, its state and its aggregate clicks.
A short link is a redirect you control
You choose a slug. Visitors who open go.arjav.is-cool.dev/launch are sent straight to the current destination with a single HTTP 302. Nothing is rendered in between — no interstitial, no tracking script, no wait.
Because the link is yours rather than a shared platform’s, the destination can change tomorrow without reprinting a QR code, and a link you no longer want can be disabled without leaving anything behind on someone else’s infrastructure.
What it actually does
Custom aliases
Any lowercase slug you want. Slugs that would collide with an application route are rejected, so a link can never be silently shadowed.
Change destination, keep the link
Repoint a link at any time. The short URL never changes, so anything already printed or shared keeps working.
Scheduled redirects
Different destinations during defined time windows, plus conditional routing by country or device category.
Weighted A/B redirects
Bucketing hashes the link with a server-side salt — deterministic and reproducible, while storing nothing about the visitor.
QR codes, generated here
Preview and download come from the same owner-gated endpoint. No third-party QR service ever sees your link.
Tags, folders, CSV export
Organise links privately, then export aggregate click history. Exports are server-built and formula-injection safe.
Aggregate analytics
Clicks by UTC day, referrer hostname only, coarse device category. Counts are clicks, not people.
A scoped API
API keys carry explicit read/write scopes. Rotatable, and revoked the moment you delete them.
How it works
A request arrives
The slug is resolved in a single database query, along with any schedule, rules and variants that apply.
The destination is resolved
Expiry, activation, schedule windows and conditional rules are evaluated. If an experiment is running, the variant is chosen by hashing the link id — never the visitor.
A 302 is returned immediately
The response is sent before analytics are written. If recording a click fails, the redirect still succeeds and the failure is logged.
What this service does not store
That is a real engineering decision with real consequences: there is no visitor-level record to subpoena, and no way to attribute abuse to an individual. Rate limiting uses a hash of the connecting address, which is a brake rather than an identity. The privacy page describes the behaviour precisely.
Private by construction
There is no public sign-up. Accounts are restricted to an explicit allowlist, and the service stores nothing that could identify who visited a link.