What cookies are
A cookie is a small text file a website stores in your browser. It lets the site remember things between visits, or between steps of a single visit — that you are signed in, for example, or which language you chose.
Alongside cookies there are other technologies that store data on your device, such as localStorage. For simplicity this document refers to all of them as cookies.
What cookies do not do here
This is the most important part of this document, which is why it comes first.
Treto uses no analytics and no advertising cookies. There is no Google Analytics, no Meta Pixel, no cross-site tracking tool of any kind, and we pass no data to advertising networks. We do not follow where you go after you leave Treto.
That is also why you see no cookie consent banner on Treto. Under § 89(3) of Act No. 127/2005 Coll., consent is required for anything that is not necessary to provide the service. We store nothing of that kind, so there is nothing to consent to. If that changes, this document changes with it and the banner appears — see the last section.
What we store on your device
Strictly necessary
The service does not work without these. They cannot be switched off and no consent is required for them.
| Name | What it does | How long |
|---|---|---|
treto_session |
Keeps you signed in as you move between pages. The session contents are stored inside this cookie in encrypted form, not on our server | 2 hours |
XSRF-TOKEN |
Protects forms against cross-site request forgery (CSRF) | Until the browser session ends |
i18n_redirected |
Remembers your chosen language so you do not have to pick it again | 1 year |
treto_theme |
Remembers your chosen appearance (light / dark) | 1 year |
Security
| Name | What it does | How long |
|---|---|---|
_GRECAPTCHA |
Google reCAPTCHA Enterprise — detects automated attacks against the sign-in and registration forms | 6 months |
This cookie is set by Google, not by us. It loads only at the moment you submit the sign-in form, the registration form, the password reset form, or a report of unlawful content. It does not load at all while you browse the catalogue, profiles or services.
How reCAPTCHA processes data is described in the Privacy Policy.
Cookie consent
There is nothing here today, because there is nothing to ask you about.
When there is, your decision will be kept under the key treto_consent. It is not a cookie but a localStorage entry, which means it has no expiry date and is not sent to our server — it stays in the browser until you clear the site's data. Nothing writes it at present.
Requests to third-party servers that store nothing
Some parts of Treto load content from third-party servers without storing anything on your device. No consent is required for these, because § 89(3) of Act No. 127/2005 Coll. concerns storing and reading data on a device, and that does not happen here. Your IP address does necessarily reach the operator of that server, because no request on the internet can be delivered without it.
This applies to:
- Mapy.com (Seznam.cz a.s.) — the map tiles on a service page. These are images, not a script.
- Sentry — application error reporting. Sent only at the moment an error occurs.
Both are described in more detail in the Privacy Policy.
Controlling cookies yourself
You can delete or block cookies at any time in your browser settings. The steps differ by browser — look for the "Privacy" or "Privacy and security" section.
If you block the strictly necessary cookies listed above, Treto stops working: you will not be able to sign in and form submissions will fail. That is not a deliberate restriction, only a consequence of the browser having no way to remember who you are without them.
When this document changes
This document describes what the application actually does, not a general intention. If any analytics or advertising tool is added to Treto:
- the table above gains the specific names and retention periods,
- a consent banner appears, on which refusing is as easy as accepting,
- your decision can be changed at any time afterwards.
The effective date and version number are in this document's header.
Contact
Questions about this document, or about data protection generally, go to the addresses on the Contacts page.
