Cookie policy
Ordered by who puts them there: our own server, the traffic filter, the visit count — and what nobody puts there at all
Who puts what on your device
Most cookie pages are sorted into categories — “strictly necessary”, “functional”, “statistics” — and the category is precisely the part you cannot check. The order here is a different one: who puts them there. First the server of this site, then the service that filters the traffic, then the visit count — only if you accept it — and at the end a list of everything that never goes on by any route whatsoever.
In every table the last column says what you lose if you delete it, which is the piece of information anyone actually decides on. In the first two groups the answer is nearly always “almost nothing”.
1. What the server of this site puts there
They are ours, first-party, and they travel to no other site.
| Name | What it stores | How long it stays | If you delete it |
|---|---|---|---|
cmplz_* | Your choice in the cookie banner (Complianz): which groups you accepted, which you refused and when | Up to 1 year | We will ask you again on your next visit |
PHPSESSID | A random session number, with no content and no name in it | Until you close the browser | Nothing you would notice; a form half filled in would start again from the top |
wordpress_* | The sign-in to the admin area — for the editor only | Until you sign out | As a visitor you never get it: it has nothing to do with you |
Not one of the three reads what you do on other pages, and not one of them holds your name or your email address.
2. What the service that filters the traffic puts there
In front of the site stands Cloudflare, which keeps malicious automated programs out. Its cookies are technical ones and it is Cloudflare that sets them, not us — we do not even decide how long they last:
| Name | What it stores | How long it stays | If you delete it |
|---|---|---|---|
__cf_bm | A technical sign that the request looks like a human one | About 30 minutes | The next page may put you through a check |
cf_clearance | That you passed the “I am not a robot” check | As long as the check holds — Cloudflare decides that | The check will keep coming round |
These two ask for no consent, because without them the site can neither be protected nor served. This is the distinction that article 4(5) of Greek Law 3471/2006 draws for whatever is strictly necessary.
3. What the visit count puts there — only if you accept it
Measurement is done with Google Analytics from Google Ireland Limited and shows how many people read a page and from which country, in aggregate. It is not switched on until you press “accept” in the cookie banner; if you do not, none of the following is set at all:
| Name | What it stores | How long it stays | If you delete it |
|---|---|---|---|
_ga, _ga_* | A random number, so that the same visit is not counted twice | Up to 2 years | Absolutely nothing: the pages work the same, the visit simply goes uncounted |
This is the only group on this page that hangs on your consent, and the only one you can refuse without any consequence at all.
4. What nobody puts there
The list that is usually left out:
- Advertising cookies. There are no adverts on these pages and no advertising space is sold.
- Social network buttons. Not one of them is loaded, so that no network gets to learn you were here.
- Device fingerprinting. If you refuse the cookies, we do not go on to recognise you by some other technique — article 4(5) of Greek Law 3471/2006 forbids it outright, since it speaks not of cookies but of any storing of, or access to, information held on your device.
- Embedded third-party maps or videos. The network map is an image of our own plus a PDF, not an embedded service.
Why we ask you first
How you change your mind
_ga cookies are deleted on the spot.When this table changes
This page was last checked on 29 October 2026. Changes are published here, with a new date.
On this page
