Privacy and cookies
Your data on this site
What this site does with the data of the people who open it, spelled out: cookies, browser storage, the server, outside services. And what you can do about it, at any time.
Last revised: 28 October 2026.
Privacy by design
In short
This site was built to collect as little as possible: what we do not need we do not ask for, and what we do need stays with us. In practice:
- No tracking. No Google Analytics, no Facebook pixel, no visitor statistics of any kind, no profiling.
- Nothing comes from other sites. Fonts, images, scripts, the map: everything comes from our own server. A security rule sent to your browser (Content-Security-Policy) forbids it to load anything from anywhere else.
- Two cookies, both technical. One keeps the session, the other is a security token, and they expire 2 hours after the last page you open. That is why there is no banner: technical cookies need no consent.
- The room form keeps nothing. It prepares an email that you send yourself, from your own address.
- Your IP address is not stored. The site writes it nowhere, nor the name of your browser: your session row does not hold them, and what it does hold is encrypted. (Only Aruba, which hosts the site, sees it: see «What stays on the server».)
- Photos without a location. Before a photo is published, the site strips the GPS position and the other hidden camera data from the file.
- Nothing handed over. Visitors’ data are not sold or given to anyone.
- All in Italy. The site and its database live on Aruba’s servers, in Italy.
This is not a certificate: it is a description. What the code does (cookies, browser storage, security headers) you can check yourself with your browser’s developer tools, in the «Network» and «Application» tabs; the rest is a commitment by the cooperative.
Who we are
Data controller
The controller of the data collected by this site is the cooperative that runs the Stazione di Chiusaforte:
- Company
- LA CHIUSA Soc. Coop.
- Registered office
- Via Stazione 15, 33010 Chiusaforte (UD)
- VAT number
- 01625480304
- Phone
- +39 0433 52344
For any question about your data, or to exercise your rights, write to stazionedichiusaforte@gmail.com. We answer ourselves, with no middlemen, within one month, as the EU General Data Protection Regulation (GDPR) requires.
None of this
What we do not do
- We use no visitor statistics: no Google Analytics or anything like it, not even the «anonymous» kind.
- We embed nothing from anyone else: no «like» buttons, no YouTube videos, no Google maps. The links to Facebook and Instagram are plain links.
- We do not fetch fonts from Google Fonts or scripts from outside networks (CDNs): our server delivers them.
- We do not recognise your device by its characteristics (fingerprinting) and we build no profiles of anyone.
- We have no newsletter, we send no advertising, and we neither sell nor hand over data.
- We do not ask for your location. The site cannot even use your device’s camera, microphone, location or payments: it switches them off with a dedicated rule (Permissions-Policy).
On your device
What stays in your browser
Besides cookies, the site uses the browser’s storage (localStorage and sessionStorage) for three small preferences. They stay on your device and are never sent to the server.
| Key | Where and for how long | What it holds |
|---|---|---|
stazione-tema
|
localStorage, until you delete it | The theme you chose: light, dark or automatic. |
stazione-evento-…
|
localStorage, until you delete it | That you have already closed the window of an event, so it does not come back. One key per event, with its number. |
avvisi-chiusi
|
sessionStorage, until the tab is closed | The notices you closed on your phone. It deletes itself when you close the browser tab. |
If your browser allows it, the site also leaves a small program there, a “service worker”, which keeps a copy of the pages you open. While you are online the site is exactly as always; the copy is shown only when there is no network, with the date it was saved. It lives in the browser’s storage (Cache Storage), on your device, and is never sent to the server.
| Storage | Where and for how long | What it holds |
|---|---|---|
stazione-tasca-…
|
Cache Storage, until the next version of the site | The «In your pocket» page in the three languages — address, phone, opening hours — and the images that draw it. |
stazione-pagine
|
Cache Storage, the last 40 pages, for 60 days at most | The pages of the site you opened, to read them again offline. |
stazione-immagini
|
Cache Storage, the last 200 | The photographs of those pages. |
stazione-file
|
Cache Storage, the last 60 | The site’s stylesheet, script and fonts. |
You can delete saved pages and photographs whenever you like with the «Delete saved pages» button on the «In your pocket» page, or together with everything else by deleting the site’s data.
In the admin panel, the browser of whoever runs the site also remembers the theme and which menus are open or closed (theme, isOpen, isOpenDesktop, collapsedGroups).
On the «Your email is ready» page you can copy the text of the request with a button: it goes to your device’s clipboard, and from there nowhere else.
To remove everything, just delete the site’s data: see «How to delete cookies and site data».
On our side
What stays on the server
When you open a page, your browser sends the server what it sends to every site: your IP address, the page requested, the name and version of your browser and operating system (the «User-Agent»). This is where it ends up.
- The session row. The site’s database has one row per session, with the time of the last page opened and encrypted contents (the address of that page and the security token), readable only with the server’s key. The IP address and the User-Agent are not there: Laravel, the software the site is built on, would write them as standard, and the site stops it, because they serve no purpose. After 2 hours of inactivity the session expires, and the row is deleted by an automatic clean-up that runs while people browse the site, on average once every fifty pages opened.
- The form after a mistake. If you send the room form with a wrong field, what you typed (dates, guests, email address) stays in the session, encrypted, just long enough to put it back in the form, and is deleted with the next page.
- The error log. When something breaks, the site writes the technical details to a log so it can be fixed. The last 14 files are kept, one for each day on which an error happened. The site does not deliberately write IP addresses or emails there, but an error message may contain part of the request that caused it.
- Aruba’s logs. Like every hosting provider, Aruba logs the requests reaching its servers (IP address, date and time, address of the page or file) and runs the site through its own cache. These are its own logs, kept for as long as its rules say. Opening a photo or downloading a PDF leaves a trace only there: the site does not count who downloads what.
- Backups. Aruba copies the database every night. On top of that, whoever looks after the site for the cooperative regularly downloads a copy, together with the photos, so it can be rebuilt after a failure: sessions are left out.
Ask for a room
The form to ask for a room
The form keeps nothing: it is there to help you write the right email first time. This is how it works:
- Choose the dates and the number of guests, and type your email address.
- The server checks that the fields make sense and shows you the «Your email is ready» page, with subject and text already written. It saves nothing and sends nothing.
- You send the email yourself, from your own mail programme and address, after reading it through. Or you copy the text and send it however you like.
- The email reaches the Stazione’s mailbox, stazionedichiusaforte@gmail.com. It is a Gmail mailbox: Google stores it, under its own terms of service and privacy policy.
The form travels «by POST», inside the request rather than in the page address, precisely so that your email does not end up in the server’s access logs.
We use the details of the request only to answer you and, if you book, to organise your stay. The same goes for the emails you write to us and for phone calls.
During your visit: none
Outside services
While you browse, the site contacts no other service and makes your browser contact none. Even the map on the contact section is an image stored on our server, put together once and for all from the tiles of the OpenStreetMap map.
The server uses a few other outside services, and only when whoever runs the site presses a button in the admin panel. None of them receives visitors’ data:
- DeepL (DeepL SE, Germany). Suggests English and German translations of the texts written in Italian. It receives only the text to translate: texts meant for publication (titles, descriptions, notices), which may contain names that are already public, such as a speaker’s. If the text contains something that looks like an email address, a phone number, a tax code or an IBAN, the site refuses to send it. A person puts the suggestion into the form, and it goes on the page only when that person saves; a book summary translated automatically and not yet marked as «Riletta» (reread) appears on the site with a note saying so. on today
- Google Cloud Translation (Google, United States). A second translator, an alternative to DeepL, on the same terms. off today
- OSV.dev, Packagist and endoflife.date. An administrator can ask whether the software the site is built on has known security flaws. Only the names and versions of the software are sent, no data about people.
The site currently uses DeepL’s free plan, under which DeepL keeps the texts it receives: one more reason to send it only texts meant for publication.
Aruba, in Italy, is a different matter: it hosts the site, so it receives what your browser sends with every page (see «What stays on the server»). The few emails of the admin panel, such as the link to choose a new password, also leave from its mail server.
Links to other sites
The site links to Facebook, Instagram, Google Maps, Apple Maps, Mapy.com, OpenStreetMap, the cycle route’s sites and our partners’ sites. They are plain links: nothing happens until you press one. When you do, you enter someone else’s site, with its own privacy rules, and that site knows at most that you came from here, not from which page.
Images and documents
Photos, documents and people
- Cleaned photos. When a photo is uploaded, before saving it the site strips the GPS position, the camera data, the dates, the thumbnails and any other hidden data from the file. Only the orientation, the colour profile and, if the photographer wrote them in the file’s XMP metadata, their name and copyright remain.
- PDFs as they are. PDF documents (the menu, the public funding documents, event posters) are published exactly as they were prepared, unchanged.
- People in photos. A recognisable person appears in a photo on the site only with their consent, signed on a release form that is valid for this site only. If you are in a photo and want it removed, write to us: we remove it from the site and from the admin panel’s bin.
- Authors’ names. The site shows the names of the authors of the cooperative’s books, of whoever designed the logo and, on the Licences and credits page, of photographers who upload a photo with their own name: their work deserves credit.
- No counting. The site does not record who looks at a photo or downloads a document.
Restricted area
The people who run the site
The admin panel is used only by the cooperative’s people who look after the site. About them the site keeps:
- name, email address, role and the sections they may edit;
- the password, never in clear: only its cryptographic hash (bcrypt), from which the password cannot be worked out;
- which account created a notice or an event, edited a text or removed a file, so we know who did what. Removed files leave a log entry for one year: who removed them, when and from where, without the name of whoever photographed them.
Signing in takes a password of at least 12 characters; more than five attempts in a minute from the same address are stopped. The link to choose a new password is valid for 30 minutes and only once, and does not contain the email address: only a random code reaches the server’s logs, and it is useless once used. When the password is changed with that link, every open session of the account is closed and the other administrators receive a warning email.
Accounts do not expire and cannot be deleted from the panel: when someone stops working on the site, their account is switched off. On request we remove it from the database by hand; the name stays only in the log of removed files, for one year at most.
Protection
How we protect data
- The site opens only over an encrypted connection (HTTPS), and cookies travel only over it.
- The session cookie cannot be read by scripts on the page and is not sent to other sites.
- A security rule (Content-Security-Policy) stops the browser from loading or running anything that does not come from our server.
- The site cannot be shown inside another site, and it switches off camera, microphone, location and payments in the browser.
- Admin passwords are stored only as hashes; session contents, the keys of outside services and the mailbox password are encrypted in the database.
- Uploaded files get a name chosen by the server, and the server’s rules refuse to run them as programs. The database cannot be reached from the internet.
The rules
Why we process data, and for how long
The EU General Data Protection Regulation (GDPR, Regulation (EU) 2016/679) asks us to state, for every use of data, on what legal basis we do it and how long we keep the data.
| What | Legal basis | For how long |
|---|---|---|
| Browsing the site: session, technical cookies, logs | Legitimate interest in running the site and protecting it (art. 6.1.f GDPR); technical cookies, which need no consent (art. 122 Italian Privacy Code) | Session: 2 hours after the last page, then the automatic clean-up. Error log: the last 14 files. Aruba’s logs: according to its rules. |
| Room requests, emails and phone calls | Answering your request before a possible contract (art. 6.1.b GDPR) | As long as needed to handle the request and the stay; if you stay with us, as long as the law requires. |
| Photos with recognisable people | The consent given with the release form (art. 6.1.a GDPR), which you can withdraw at any time | While the photo is published. Once removed from the site, it stays in the admin panel’s bin for 90 days and then goes by itself; if you ask us, we remove it from there straight away. A removed photo leaves, for one year, a line in the panel’s log saying when and from where it was removed, without the image and without the name of whoever took it. |
| Names of the authors of the books, the logo and the photos | Legitimate interest in crediting the people who made them (art. 6.1.f GDPR) | While the work is on the site; if it is removed, the name may stay for one year in the log of what was removed. |
| Admin panel accounts | The relationship with the cooperative of whoever looks after the site (art. 6.1.b GDPR) and the panel’s security (art. 6.1.f GDPR) | While the person works on the site; then the account is switched off, and removed from the database on request. |
| Machine translations and software checks | Legitimate interest in publishing the site in three languages and keeping it safe (art. 6.1.f GDPR) | Suggested translations stay in a cache in the admin panel, so they are not asked for twice. |
We make no automated decisions about anyone and do no profiling (art. 22 GDPR).
Giving us your data is always your choice. Without an email address, though, we cannot answer you.
Where it lives
Data outside the European Union
The site and its database are in Italy, and no data leaves the European Union while you browse.
Data can leave it only in these cases, none of which concern browsing:
- the email you send to ask for a room reaches a Gmail mailbox, which Google may also process outside the European Union, with the safeguards the GDPR provides (standard contractual clauses and the EU-U.S. Data Privacy Framework);
Always yours
Your rights
The GDPR (articles 15 to 22, and article 7 for consent) gives you the right to:
- know what data of yours we hold and get a copy;
- have it corrected if it is wrong, and have it deleted;
- restrict its use or object to its processing;
- receive it in a machine-readable format, to take it elsewhere;
- withdraw a consent you gave, for example on a release form: it applies from that moment on.
To exercise them, write to stazionedichiusaforte@gmail.com. It is free, and we answer within one month.
If you think we handle your data wrongly, you can lodge a complaint with the Italian data protection authority, the Garante per la protezione dei dati personali: garanteprivacy.it
For visitors’ data, though, there is little to ask for: we do not know who you are. Your session row carries no name, and you can delete cookies and preferences yourself, as explained below.
Do it yourself
How to delete cookies and site data
The quickest way, in almost every browser: tap the symbol to the left of the address, next to www.stazionedichiusaforte.it, and choose to delete the site’s cookies and data. Otherwise:
- Chrome
- Settings → Privacy and security → Delete browsing data → «Cookies and other site data» → Delete data.
- Chrome on Android
- Menu ⋮ → Settings → Site settings → All sites → www.stazionedichiusaforte.it → Delete.
- Firefox
- Settings → Privacy & Security → Cookies and Site Data → Manage Data → search for the site → Remove Selected.
- Safari on Mac
- Safari → Settings → Privacy → Manage Website Data → search for the site → Remove.
- Safari on iPhone and iPad
- Settings → Safari → Advanced → Website Data → search for the site → Delete.
- Edge
- Settings → Privacy, search, and services → Clear browsing data → «Cookies and other site data» → Clear now.
The names of the menu items change a little from one version to the next. In any desktop browser, Ctrl+Shift+Delete (on a Mac ⌘+Shift+⌫) opens the window for deleting data directly.
Updates
When this page changes
When the site changes the way it handles data, this page changes with it: it is written next to the code and checked by automated tests that compare it with what the site really does. The date of the last revision is always at the top.