This site has no cookie banner, because there is nothing to ask about. There are no ad networks, no tracking cookies and no fonts from someone else’s server. I still want to know which pages are read, so I count visitors on my own server. Here is what it receives and what it does not. Everything I say is on the privacy page, where it is written out in full.
What I count
The counter receives three things: the address of the page you opened (without anything after a “?”), the name of the site you came from, and whether you read the page for at least 8 seconds. If you came through one of my advertising links, I also get its three tags: where the link was published, through what channel and for which campaign. From these I make daily totals: how many visitors came, how many read on, and how many reached a goal, such as sending an enquiry.
The counter’s script is served from this very site, and the data goes only to my own server. It sends nothing from a preview or a test run, only from sudievu.lt.
What I don’t count
I do not store your IP address or your browser’s name, and the counting uses no cookies. So that one person is not counted twice on the same day, a code is made from the IP address and the browser’s name with a secret salt. The salt changes every day and I delete the previous day’s, so the code can never again be linked to you or to another day. The counter does not know who you are, and it does not recognise you the next day.
The counter does not know who you are, and it does not recognise you the next day.
That means I cannot tell whether a person comes back a week later. The records are kept for 35 days, and after that only the daily totals remain. If you would rather not be counted, open any page with ?notrack and your browser will remember it.
What stays in your browser
The privacy page puts it this way: consent is needed for what is not necessary, and here everything is. There are only a few cookies, and each is there so that something can work. In the client area, once you sign in, there is a sign-in session cookie. In the demonstrations, when you press something, a cookie with a random number appears that points to your demonstration sandbox; it is deleted after a day.
In the browser itself stay the language you chose and a few notes about the demonstrations, such as that you have already seen an explanation. Whatever you changed in a demonstration also stays only in your browser. Every key in the browser’s storage is in the privacy page’s table, and when the code changes, a check looks for a key the table does not have.
What the counter does not cover
A server, like any other, writes ordinary access logs: the IP address, the time, the address opened and the browser’s name. They are kept for up to nine weeks, and the firewall’s log for 28 days. The counter does not use them, but they exist, and the privacy page does not hide it.
The counter’s data is sent nowhere further. Other services receive data only when you do something yourself: you pay an invoice through Paysera, or check a domain name on the pricing page (the .lt registry receives only the name). The privacy page lists the other recipients, such as the store for encrypted backups. The one outside thing is a map in a demonstration: until you press its button, no request goes out to OpenStreetMap.
What I have written is what this site’s privacy page says. Whether another site needs a banner depends on what it collects.