What happens to your links

A short link is a promise that a click lands where you said it would. This page is the written version of what a link on Urlicer is, and is not, subject to. If any of it stops being true, this page changes first.

A redirect is a redirect

A click on a link here is answered with the destination and nothing else. There is no preview page, no advertising on the way through, no consent dialog and no wait, on every plan including the free one. We earn nothing from a redirect. Clicks are counted on the server, so nothing runs in the visitor's browser and a plain link sets no cookie; privacy and cookies names the two link types that set one.

Links do not expire unless you say so

A link in a workspace has no expiry date until you give it one. Nothing switches it off after a period of inactivity, a plan change or a quiet year. The only way a workspace link stops working is that someone with the right role deletes it, or you set an expiry yourself, per link.

The one exception is a link made on the home page without signing in: it lasts 30 days unless you keep it in an account, which is free.

You can take your links out at any time

Your links are yours to leave with. On the paid plans, the Short URLs page exports the list as a CSV, filtered the way you are looking at it. On every plan, the free one included, the API lists your links with their destinations, aliases and names. There is no notice period, no request to make and nothing to ask permission for.

Your own domain keeps the exit in your hands

Links on the shared short domain can only ever be answered by us, the same way a bit.ly link can only be answered by Bitly. Links on a domain you own are different: the domain is yours, its DNS is yours, and if you ever want those links answered by someone else, that is a DNS change and an import of the list above, not a reprint. For anything that goes on paper, that is the setup we recommend, and it is the reason custom domains start on the entry paid plan rather than the top one.

What protects the shared domain

A shared short domain has one structural risk: somebody else's abuse gets it flagged, and every link on it suffers. Every destination here is checked before a link goes live and re-checked afterwards, a link whose content turns bad is stopped, and anyone can report a link from its warning page. Why short domains get blocklisted explains the risk and the checks in detail.

Where things run

The application, the database and the click analytics run on a server in Amsterdam, in the Netherlands; email is sent from Helsinki. The database is backed up automatically. The privacy policy names every third party that receives anything, and what.

If you still have a question

Ask it: contact support. Questions about permanence are the ones we most want to hear, because the answer belongs on this page.