Short links.
Honest numbers.
A URL shortener that shows you what happens β without putting a cookie banner in front of your visitors. Because it sets no cookies.
This address
https://www.beispiel.de/kampagnen/2026/sommer/aktion?utm_source=newsletter&utm_medium=email&utm_campaign=sommer26
becomes this short link
Style: Random β short and unmistakable
What it looks like
Not a mocked-up screenshot: the chart and QR code on this page come from the same building blocks as the dashboard.
Clicks over time
Sample data. The dashboard adds a comparison to the previous period.
Hover the chart for individual values
QR code
Fully designable, as SVG, PNG and print-ready PDF. This one works β scan it.
Live view
That is the whole row β no IP address, no device identifier, nothing that would recognise the same person tomorrow.
Analytics worth reading
Clicks over time, countries, devices, referrers, QR scans counted separately from link opens. Unique visitors without recognising anyone.
Links that expire
Expiry date, click limit, start date or single-use links. After that a 410 β or a fallback destination of your choosing.
Destination by context
iOS to the App Store, Android to Play, France to the French page. Plus weighted A/B splits.
QR codes worth printing
Colours, logo, corner styles, export as SVG and PDF. Scans are counted separately.
Your own link preview
Title, description and image per link β independent of the destination. Your link looks the way you want in WhatsApp and Slack.
Your own domain
Serve short links under your own domain β in CTX's design. Set up with two DNS records, certificate included.
No consent banner
The redirect domain sets no cookie and never touches device storage. That puts it outside the scope of the ePrivacy consent rules.
How to get numbers without collecting data
Most shorteners store IP address and user agent and call it analytics. We don't β and still get numbers you can act on.
- The IP address is never stored
- It is resolved to country and city, folded into a hash in truncated form, and then gone. Out of the logs too β the reverse proxy never writes it.
- Unique visitors without recognition
- The visitor hash is built with a random value that rotates daily and is then destroyed. After 24 hours the hash can no longer be tied to anyone β not even by us.
- No tracking across links
- The link ID goes into the hash. The same visitor appears as two different values on two different links. A profile spanning multiple links is technically impossible.
- The referrer is truncated
- Only the hostname is kept. Search terms, tokens and addresses sitting in the path or query are discarded before anything is written.
- Gone after 90 days
- Individual click events are deleted, the anonymous totals remain. Your analytics lose nothing, the raw data disappears anyway.
Verifiable, not just claimed: an automated test fires a click with marked values on every deploy, then searches every text column in the database for them. If it finds the IP, the user agent or the full referrer, the deploy fails.