Legal

Cookie policy

Last updated: August 2026.

1. Why there is no cookie banner

You did not get a pop-up asking you to accept cookies when you arrived. That is not an oversight and it is not a legal gamble: www.rentabilio.com sets no tracking cookies, no analytics cookies and no advertising cookies at all. There is nothing to consent to, so there is nothing to click away.

The whole cookie inventory of this site is one cookie, it exists only once you actually do something that needs it, and it is listed in full below. If you want the wider picture of what we collect and why, that is the privacy policy.

2. The only cookie we set

CookieWhat it doesHow long it lasts
PHP session cookie Holds the identifier of your server-side session. It is what remembers the seats in your shopping cart between pages, keeps you signed in to your account area after you type your one-time code, and carries the token that protects every form on the site against cross-site request forgery. Until you close your browser. It is a session cookie with no expiry date written into it, marked HttpOnly so scripts cannot read it, and SameSite=Lax so it is not sent from other people's sites.

That cookie is strictly necessary in the ordinary meaning of the phrase: the cart, the sign-in and the CSRF protection cannot work without it, and it does not track you across pages for any purpose beyond those three. It contains a random identifier and nothing else: no name, no email, no browsing history. It is not shared with anybody and it is not readable by any other site.

3. What we do not set

  • No analytics cookies. Our visit counter does not use cookies at all (section 4).
  • No advertising or retargeting cookies, and no pixels from any ad network.
  • No social media cookies. There are no share buttons or embedded feeds on this site.
  • No third-party captcha. The contact form uses a captcha we wrote ourselves, which runs on this server and sets nothing.
  • No chat widget, no session recorder, no heatmap, no A/B testing tool, no marketing automation tag.

4. How the visit counter works, since it is not a cookie

We do count page views, with our own software, and it is worth explaining because "we do not use cookies" is a sentence some sites say while doing something worse.

The counter stores a short random string in your browser's sessionStorage. That is a different mechanism from a cookie in the ways that matter to you:

  • It is never sent to our server automatically the way a cookie is. It only travels when the counter attaches it to a page-view message.
  • It is scoped to this site and to this tab. Another site cannot read it, and a different tab gets a different one.
  • The browser erases it when you close the tab. Come back tomorrow and you are a brand new visitor with a brand new string. It cannot be used to recognize you later, to follow you anywhere, or to build a profile.

Its only job is to tie together the three or four pages of a single visit so a number in our admin panel says "one visit, four pages" instead of "four visits". Alongside it we record the page path and title, the referring page, the browser language and time zone, the window width and how long the page stayed open. Your IP address is recorded only as a short hash mixed with the current date, which stops being able to identify anything the following day. The full detail is in section 4 of the privacy policy.

5. Stripe's cookies, on Stripe's pages

When you buy, the payment happens on Stripe's own checkout pages, not on ours. Stripe sets its own cookies there, for its own reasons (keeping the checkout session alive and detecting fraud, chiefly), and those cookies are governed by Stripe's cookie and privacy policies, not by this one. We do not control them, we cannot read them, and they do not follow you back onto www.rentabilio.com.

The distinction is worth being precise about: Stripe's checkout is not this site. While you are on it you are on Stripe's domain, under Stripe's terms. When the payment finishes you come back here, to a site that still has exactly one cookie.

6. Fonts and other embedded content

The site loads two typefaces from Google Fonts. Font files are not cookies and Google Fonts does not set one, but the request for the file does reach Google's servers with your IP address and browser, the way any request for a file on the internet does. There is nothing else embedded from anywhere else: no videos, no maps, no iframes, no external scripts of any kind on the pages of this site.

7. Blocking cookies anyway

Every browser lets you block or delete cookies, and clearing site data removes the session cookie described above along with the counter's sessionStorage string. Nothing here depends on your accepting anything, so blocking costs you very little. Be aware of what stops working if you block cookies for this domain specifically: the shopping cart will forget what you put in it, you will not be able to stay signed in to your account area, and forms will reject themselves because the CSRF token has nowhere to live. Reading the site works perfectly well with everything blocked.

8. Changes to this policy

If the site ever sets another cookie, it will be in the table in section 2 before it is in your browser, with the date at the top of this page updated to match. A change that introduced any non-essential cookie would come with a consent mechanism, because that is what the law requires and because a banner we do not need is worse than one we do.

In short: one session cookie, needed for the cart, the sign-in and the CSRF token, gone when you close the browser. The visit counter uses no cookie and forgets you when the tab closes. Stripe sets its own cookies on its own checkout pages, which are not this site. That is the entire story, which is why there is no banner.