Legal documents
What the service stores in your browser, when and why. In short: one technical cookie in the dashboard and nothing at all for the visitors of your campaigns.
Revised Aug 2, 2026
A cookie is a small piece of data that a site asks the browser to store and send back on subsequent requests. It is normally used to keep an account signed in, remember settings or track behaviour.
Technically similar mechanisms are the browser's local storage and session storage. Everything stated below applies to them as well.
The dashboard uses a single cookie — the session identifier. Signing in is impossible without it: the browser would have no way to tell the server that the request comes from an already authenticated user.
It contains nothing but a random identifier. No email address, no password and no information about the user is stored inside it — all of that lives on the server and is linked to the identifier.
The cookie is marked as secure-only and inaccessible to page scripts. Its scope is limited to the dashboard address.
It lives until the browser is closed, or for up to thirty days if "remember me" was explicitly chosen. Signing out deletes it immediately, on the server side as well.
The router sets no cookies for visitors whatsoever. The decision about where to send a request is made from the data of that request alone and requires nothing to be stored in the browser.
One practical consequence follows: the service cannot "recognise" a returning visitor between requests by browser means and builds no cross-site profiles.
If the destination page you send traffic to sets its own cookies, that happens outside the service and is governed by that page's own policy. Informing visitors about such cookies is the responsibility of the page owner.
The service embeds no third-party web analytics and no advertising pixels, neither on the public pages nor in the dashboard.
The service sets no advertising or tracking cookies. There is no consent banner on the site for the same reason: there is nothing to consent to.
Internal campaign statistics are built from the click log on the server — that is, from data that passes through the router anyway, not from data stored in the browser.
The public pages and the dashboard load fonts and utility libraries from third-party content delivery networks. Such networks receive technical details of the request — the address and the browser version — but no cookies are set in the process.
There are no other third-party resources on the pages: no external images, no embedded video players, no social network widgets and no chat tools are used.
The session cookie is technical and strictly necessary: blocking it stops the dashboard sign-in from working. There is no separate switch for it, because the dashboard does not function without it.
Cookies can be managed through the browser: you can view what is stored, delete it or forbid storage for a specific address. The exact steps are described in your browser's help.
The public pages of the site — the home page, pricing and the legal documents — can be read with cookies fully disabled.
If the set of cookies in use changes, this document will be updated with a new date.
Should any cookie that is not strictly necessary appear, the service will ask for consent before setting it.
