The whole story. This site sets no cookies and, apart from your browser's ordinary cache of our pages, stores nothing else in your browser. It runs no analytics, no advertising and no tag manager, and it loads no scripts, fonts or images from other domains. So there is no consent to collect and no banner to click away.
What this site sets
None. This website sets no cookies, whichever page you open. It stores nothing else in your browser either: nothing in local storage or session storage, no browser database, and nothing that keeps running after you leave the page. The only copies kept are your browser's ordinary cache of our pages, described below.
Why there is no banner
The EU rule behind cookie banners (Article 5(3) of the ePrivacy Directive, 2002/58/EC, as each member state has put it into its own law) is about more than cookies. It asks for your consent before a website stores anything on your device or reads anything from it, unless that is needed to carry the page to you or is strictly necessary for something you have asked for. A banner is only a way of asking.
Apart from the copies your browser keeps in its own cache (below), this site stores nothing on your device. It reads from it only what is needed to show you the pages you open and, if you choose to write to us, to send your message. So there is nothing to ask, and a banner here would ask you to agree to something that does not happen.
What it does not load
There are no analytics, advertising or social-media tools, and no tag manager or third-party fonts. The site loads nothing from another domain, so no analytics, advertising or social-media company learns from this site that you visited.
The only requests your browser sends to another domain are the ones the enquiry form makes when you press its button to send a message. They are described under "Writing to us".
Your browser's cache
Your browser may keep copies of our pages, images, style sheet and scripts so they load faster next time. Your browser keeps these copies because our server tells it how long they stay valid; they are not cookies and you can clear them at any time.
Writing to us
The "Write to us" links take you to our contact page, which carries the enquiry form described below. Opening the contact page sets no cookie, like every other page here.
Wherever our address, support@orkestar.eu, is a link, clicking it opens your own email program. That sets no cookie, and nothing is sent until you send the email yourself. What you send us is covered by the privacy notice.
The enquiry form on the contact page sets no cookie, keeps nothing in your browser and loads nothing from another domain. Nothing leaves the page until you press the button; then the four fields you filled in, and the two things described next, are sent to us, to our own program at orkestarsitezokxgmvt-enquiry.functions.fnc.fr-par.scw.cloud and nowhere else, and the page says whether that worked. With JavaScript turned off the same form works the same way, and the answer arrives as a page of its own instead, sent from that same address. Your browser then also asks that address for a small icon to show in its tab, as it does with any page it opens.
The form carries two things you do not fill in: a field that is kept out of sight, which only an automated sender would complete, and the time the page was opened, which the page's own script reads from your device's clock when the page opens. Both are there to keep automated messages out. Neither identifies you, and neither is stored: they decide whether the message is passed on, and go no further. There is no CAPTCHA and no puzzle. What the form collects and how long it is kept are in the privacy notice.
Technical data
Loading any web page sends technical data, such as your IP address, to the server that delivers it. That is not a cookie. The privacy notice explains how it is handled.
If this ever changes
Some additions would change this: analytics, advertising or social-media tools, an embedded video or map, fonts loaded from another company, a CAPTCHA, a chat or booking widget, a tracking pixel, or a hosting or security setting that places a cookie. Each would store or read something on your device that is not needed to show you a page, and that needs your consent before it happens, not a banner that assumes it. If we ever add one, this statement changes first, and a choice appears with it in which refusing is as easy as accepting. Until then, there is nothing to consent to.
Questions: support@orkestar.eu.