Cookie Policy

A cookie is a small file that a site stores in the browser of the person visiting it and that the browser returns on subsequent requests. It serves to let the site remember something between one page and the next: typically, that the session is already signed in.

On the same basis, the equivalent local storage technologies of the browser are covered here as well, where they serve the same function.

This public site — the page where Behemoth is presented and where these documents are published — installs no third-party cookies.

We use no analytics tools, no tracking pixels, no advertising tags, and no social media buttons that track browsing. We do not measure audiences, we do not build profiles, and we do not share browsing behavior with anyone.

Accordingly, this site has no need to display a consent banner: there is nothing to consent to, because there is no tracking to authorize.

The application, which is reached after signing in, does use cookies, and only those strictly necessary for it to work:

• Session cookies: they keep the session signed in while the user works, so that the credentials do not have to be entered on every page, and they allow the session to be closed securely.
• Basic preference cookies: they remember presentation options such as the language chosen, so that the application does not revert to the default value on every visit.

All of them are first-party cookies: they are issued by Behemoth and are not shared with third parties. None of them is used for advertising, marketing, or profiling.

Cookie regulations require prior consent for cookies that are not essential: those used for analytics, advertising, or tracking. They expressly except those strictly necessary in order to provide a service the person has requested.

The cookies described in the previous section fall entirely within that exception: without the session cookie there is no way to keep a user authenticated, and without the preference cookie the application cannot honor a choice the user made.

Since we install no cookie outside that exception, there is no consent to request. Were that to change, we would publish the corresponding consent mechanism before installing the first cookie that required it.

Every browser allows cookies to be viewed, blocked, and deleted from its privacy settings, either generally or site by site. That decision always belongs to the user and requires nothing to be asked of us.

It is worth knowing what it entails in this case: blocking this public site’s cookies affects nothing, because there is nothing that depends on them.

Blocking the application’s cookies, by contrast, prevents signing in. Without the session cookie the server cannot recognize the user between one page and the next, so access is closed. Blocking only the preference cookies still allows work to proceed, but the application will forget the language chosen on every visit.

The Spanish version of this Policy is the binding one. This English version is provided as a courtesy translation; in the event of any discrepancy, the Spanish text prevails.