⚠ PROVISIONAL TEXT, PENDING LEGAL REVIEW. This is not a cookie policy.
What this page covers Cookies are small files a site stores in your browser and reads back later. European law —Article 5(3) of Directive 2002/58/EC and, in Spain, Article 22.2 of the LSSI— does not speak only of cookies, but of any data stored on your device or retrieved from it. That is why this page also lists what is kept in the browser's local storage without being a cookie.
There is no cookie banner here, and this is what that means You will not see a window asking for permission because there is nothing to consent to: this site uses no analytics, no advertising, no audience measurement, no profiling and no tracking of any kind. The only things stored are those strictly necessary to sustain a service you yourself asked for —signing in to your project workspace— and those are exempt from prior consent under the rules cited above and the guidance on the use of cookies of the Spanish Data Protection Agency.
If anything that is not exempt is ever added, your consent will be requested before it is installed, with refusing as easy to reach as accepting and the option to change your mind later. As long as this page says what it says, none of that exists.
The public site sets no cookies at all You can read about the service, browse the examples, calculate an estimate and send the contact form without a single cookie being written to your browser. The submission limit that keeps spam down is not run on cookies: it is run on the server, and the privacy policy explains how.
Cookies in the project workspace and the back office They are set only if you sign in. All of them are first-party cookies of this domain, technical and strictly necessary. None is used for advertising or shared with anyone for their own purposes.
· "ts_workspace" — Ours. It holds the value "1" and nothing else, and is written when you accept an invitation to a project. It lets us take you to your workspace instead of the sales page when you come back. It contains no name, no email address and no identifier. It expires after 90 days and is not renewed when you visit.
· "access_token", "id_token", "refresh_token", "access_token_payload", "id_token_payload", "user", "ac-state-key" and "post_login_redirect_url" — Written by our server through Kinde, the provider that handles authentication as our data processor. They keep you signed in, allow the session to be renewed without asking for your password again and return you to the page you came from. When a value does not fit in a single cookie, the browser shows several numbered ones ("access_token1"). They last 29 days at most, and less when the session is not persistent. They are unreadable by JavaScript (HttpOnly), travel over HTTPS only and are not sent on background requests made by other sites (SameSite=Lax). Signing out deletes them.
During the sign-in itself your browser passes through Kinde's own domain, which sets its own cookies there to complete authentication. Those are theirs, on their domain; we do not control them and they are governed by their policy. All that comes back to us is the result.
Kept in your browser without being a cookie · "ts-theme", in local storage. It exists only if you pick the light or dark theme by hand, and it holds that word and nothing else. Switching back to "automatic" deletes it. It is never sent to the server in any request: only the page itself reads it, so you are not shown a white flash before the theme you chose is painted. It stays until you delete it or clear the site's data.
What this site does not do There are no analytics or visit statistics, no advertising or remarketing cookies, no social network buttons or pixels, no A/B testing and no device fingerprinting techniques. Fonts are served from this same domain: your browser requests nothing from Google Fonts or any other delivery network.
Third-party content your browser does request On the observatory pages, the live camera frames and the timelapses are not hosted here: they are requested at the time from the observatory's platform, which belongs to the customer and sits on another domain. Your browser makes that request, so that platform sees your IP address and may note it in its own server logs, exactly as happens when you open any web page. We place no cookies through those images and receive no data back about you. Video posters and the site's photographs do come from our own storage.
The same applies to the maps under «Examples», which show where each installation's stations and cameras are. The map images are served by the OpenStreetMap servers (tile.openstreetmap.org), and your browser only requests them once the map appears on screen. That provider sees your IP address and may note it in its logs, just like any other server your browser requests an image from. It runs no code on this page: the site's security policy only lets it serve images.
How to block or delete them You can delete this site's cookies and local storage, or prevent them from being written, in your browser settings — "Privacy and security" in Chrome and Edge, "Privacy & Security" in Firefox, "Privacy" in Safari. Each browser's help pages explain the details.
What you lose by doing so: on the public site, nothing, because none are used. In the project workspace, signing in stops working: without those cookies the server cannot tell that it is still you from one page to the next.
Who is responsible The site owner, identified in the legal notice. Which personal data are processed, on what legal basis, for how long they are kept and how to exercise your rights is set out in the privacy policy. For anything about this page, write to us through the contact form.
Changes If what is stored in your browser changes, this page is updated before the change reaches the site.