Terminal storage
Cookie Policy
Which cookies this website sets, when, and why no consent banner is shown today.
- Version
- 1.1
- Last updated
- Language
- English (binding version)
- Governing law
- Romanian law and directly applicable EU law
Legal documents
1. The short version
If you are here to read about European destinations, this website sets no cookie on your device at all. That is why you are not being interrupted by a consent banner: there is nothing to consent to. The only cookies this application can set are session cookies for people who sign in to a private area, and those are strictly necessary to make signing in work.
2. The rule we are applying
Storing information on your device, or reading information already stored there, is governed by Article 5(3) of Directive 2002/58/EC, transposed in Romania by Legea nr. 506/2004, art. 4 alin. (5). As a rule it requires your consent, given after clear and complete information.
Art. 4 alin. (6) lit. b) of the same law provides that this does not apply where the storage or access is strictly necessary in order to provide an information society service expressly requested by the subscriber or user. A session cookie that exists only so that a signed-in person stays signed in falls squarely within that exemption. Where personal data is involved, the General Data Protection Regulation applies in addition, and the relevant basis is Article 6(1)(f) — our legitimate interest in a working, secure authenticated area.
3. Every cookie this site can set
The list below is exhaustive. There are no others.
| Name | Set when | Purpose | Lifetime | Category |
|---|---|---|---|---|
ebg_sid |
Only after a member of staff signs in to the administration at /admin |
Keeps the administration session and carries the CSRF protection for it | Browser session; the session itself expires after 30 minutes of inactivity and after 8 hours in any case | Strictly necessary |
ebg_traveler_sid |
Only after a traveler signs in to the private planner. Traveler registration is currently disabled, so this cookie cannot be set today | Keeps the traveler session, separately from the administration, and carries its CSRF protection | Browser session; the session expires after 24 hours of inactivity and after 30 days in any case | Strictly necessary |
ebg_basket |
Only when you put something in the basket in the shop | Identifies your basket, so it is still there when you come back, and carries the token that proves a checkout form came from your browser | 14 days from the last time you touched the basket | Strictly necessary |
ebg_lang |
Only when you click a language in the language switcher (EN or RO) in the page header | Remembers the language you chose, so that opening the bare homepage later takes you to the Romanian version if that is what you picked. It holds the two letters en or ro and nothing else |
12 months, or until you choose the other language | Functional, set only at your explicit request |
The basket cookie is strictly necessary in the ordinary sense of the exemption: it is the input cookie that remembers what you chose. Without it there is no basket to check out, so it is exempt under art. 4 alin. (6) lit. b) and no consent is asked for it. It holds a random identifier and nothing else — no name, no email address, no record of what you looked at.
The two session cookies and the basket cookie are HttpOnly (unreadable by scripts), SameSite=Lax, and
Secure when the site is served over verified HTTPS. None of them contains personal data:
each holds an opaque random identifier, and the session data itself is stored on the server,
outside the public web directory.
The language cookie is different in one respect: it is written by the language switcher itself,
in your browser, at the moment you click a language, so it is not HttpOnly. It is
SameSite=Lax and Secure over HTTPS, holds no identifier and no personal data,
and exists only to carry out the choice you made. It falls under the same exemption as the cookies
above (art. 4 alin. (6) lit. b): it provides the language you expressly requested.
4. What we do not set
- No analytics cookies. There is no analytics on this site — no Google Analytics, no Matomo, no Plausible, nothing.
- No advertising or marketing cookies. No ad networks, no retargeting, no conversion pixels, no social tracking pixels.
- No preference cookies beyond the one you ask for. The only thing the site remembers between visits is the language you explicitly chose with the language switcher (
ebg_lang, above). It is never set by visiting a page, and the site never picks a language for you from your address or your browser settings. - No third-party cookies of any kind. The site loads its fonts, stylesheets, scripts and map library from its own domain. A Content Security Policy restricts scripts, styles, fonts and network connections to this origin, so a third-party cookie could not be set even by accident.
5. Similar technologies
The rule is about storing or reading information on your device, whatever the technique. For completeness: we use no local storage, no session storage, no IndexedDB, no web beacons, no fingerprinting and no tracking pixels. The map page loads a self-hosted map library; the map tiles it requests are images fetched from the OpenStreetMap tile service and do not place a cookie on your device from this site. What that request does disclose to that service is explained in section 3.2 of the Privacy Policy.
6. Controlling cookies yourself
Every browser lets you see the cookies a site has set, delete them, and refuse them. Look for “Cookies and site data” or “Privacy” in your browser's settings. Because this site sets no cookie for ordinary reading, blocking cookies here changes nothing about your visit. If you block cookies and then try to sign in to a private area, signing in will not work — the session cookie is the mechanism that keeps you signed in.
7. If a non-essential cookie is ever proposed
We would rather promise a process than a good intention, so here is the process. Before any cookie that is not strictly necessary — analytics being the realistic candidate — is introduced, all of the following must happen first:
- A consent mechanism is implemented that asks before the cookie is set, refuses by default, offers rejecting as prominently as accepting, and records what was chosen and when.
- Withdrawing consent is made as easy as giving it, and remains reachable from every page.
- The non-essential cookie is loaded only after consent, and not at all if consent is refused.
- This policy is updated with the cookie's name, purpose, provider, lifetime and category, and re-versioned.
- The Privacy Policy is updated with the new purpose, legal basis and recipient.
Until that is done, the application is configured with consent handling switched off because there is nothing that requires it, and the codebase carries an automated check that fails the build if a cookie other than the two strictly necessary session cookies above is introduced. The check exists so that this promise cannot be broken by accident.
8. Changes to this policy
Changes are published here with an increased version number and a new “last updated” date, both shown at the top of this page. Any change that introduces a cookie follows the procedure in section 7 before it goes live.
9. Contact
LAVALI ONLINE SHOP SRL · Popești-Leordeni, Str. Oituz nr. 80, jud. Ilfov, Romania · contact@europebygiddo.com