Cookies and browser storage

Why there is no banner

A consent banner is needed when a site stores something in your browser that is not technically necessary: a visit counter, an advertising profile, a piece of third-party code that recognises you from one site to the next. Alessandria does none of those three, so there is no consent to ask for.

This is not a shortcut: it follows from having no analytics. If analytics ever arrived, the banner would appear — and this page would change first.

The only cookie there is

It is called alessandria entrato, and it holds the number 1. Not your name, not your email, no identifier of any kind: only «this browser has an account».

1. 1

   Who sets it

   The app, after you have signed in. This introduction page sets nothing: it only reads it.

2. 2

   What it is for

   Alessandria has one name but two doors: this page explains what the service is, the app is where the work happens. Someone who already has an account does not need to reread the introduction every time they type the address — with that marker they go straight to the app.

3. 3

   How long it lasts

   A year, and it is deleted the moment you sign out. If you want to see this page while having an account, add ?vetrina to the address: the choice holds for the current visit.

Preferences that stay in your browser

These are not cookies — they are never sent to any server, they stay in the browser you are using — but it is fair to know they exist. Inside the app, these are kept locally:

• Light or dark theme, interface language and text size: these belong to the device rather than the person, because in the dark on a phone people often want something different from what they want on a laptop.
• The last course you were looking at and your recent searches, so you do not start over.
• Which account last used this browser: it keeps the local data of two people sharing one computer from mixing.
• Whether you already dismissed the invitation to add Alessandria to your Home screen, so it is not offered again.

All of it clears when you clear this site’s data in your browser settings, and nothing important goes with it: notes, courses and material do not live there.

Sign-in cookies

The app uses an outside service for sign-in, and that service needs its own technical cookies to keep you signed in from one page to the next: without them you would have to authenticate on every screen. They are strictly necessary and measure nothing. They clear when you sign out.

This introduction page has no sign-in inside it, and those cookies never reach it: you only meet them on the app.

The anti-bot check on the contact form

At the bottom of this introduction there is a form for writing to us. So that an automated program cannot use it to send thousands of messages, the form is protected by a Cloudflare check that almost never asks anyone for anything: at most you see a tick that resolves on its own. That check may leave a technical marker in your browser to remember that you just passed it.

It measures nothing, builds no profile and does not follow you across other sites. And it never loads on its own: it arrives the first time you touch a field in the form, so if you never write to us you never meet it.

How to remove everything

• Sign out: the marker and the sign-in cookies go.
• Clear this site’s data in your browser settings: the rest goes too.
• Block cookies for this site: the introduction keeps working, but the app will not be able to keep you signed in, because that is what they are for.