Cookies and Analytics

This site uses no advertising cookies, no analytics cookies, and no tracking that follows you between websites. Here is exactly what it does use.

Short version: this site uses no advertising cookies, no analytics cookies, and no tracking that follows you between websites. The few cookies it does use are technical ones needed to serve the site.

Cookies

We set no cookies for advertising, analytics, or profiling. We do not use Google Analytics or Google Tag Manager, and there are no marketing pixels or social media trackers.

Three kinds of technical cookie can appear:

Your language choice. A cookie named NEXT_LOCALE records whether you are reading the guide in English or Italian, so that the site can show you the right language. It holds nothing but the language code.
Security and traffic management. Our host, Cloudflare, may set short-lived technical cookies to tell real visitors from automated traffic and to keep the site available. These exist to protect the site, not to learn about you.
Sign-in sessions. There is nothing to sign in to. Pilgrim accounts are switched off, and every account page — including the sign-in form itself — is unavailable. If we offer accounts later, signing in would set a session cookie so that the site knows who you are, and we will update this page before that happens.

What we store in your browser

The site uses your browser's own storage for two things. This is not a cookie: it stays on your device, and the site does not send it to us.

Your saved trip plan — in local storage, so that your plan is still there when you come back.
Sidebar open or closed — in local storage, so that the layout stays as you left it.

While pilgrim accounts are switched off, neither of these reaches our servers.

You can clear both at any time through your browser's "clear site data" settings. Nothing breaks — you will simply start with an empty plan.

Analytics

We use Cloudflare Web Analytics to count page views.

It sets no cookies and stores nothing in your browser.
It does not use a persistent identifier, does not identify you, and does not follow you to other websites.
It records the path of the page viewed, the referring site, and general technical details such as country, browser, and device type.

So we can see how often a page was read. We cannot see who read it, and we cannot join one page view to the next.

The site's code also contains optional custom events — things like "GPX downloaded" or "added to plan". They are switched off in the current production configuration and send nothing. If we turn them on, we will update this page first.

Maps

When a map loads, your browser fetches map tiles directly from the OpenStreetMap Foundation. That request reveals technical details to them — your IP address, your browser, and which tiles you asked for — as it would on any site that uses OpenStreetMap. They handle it under their own privacy notice, and we receive nothing back from them about you.

Services contacted automatically

When you read the guide, these are the only services your browser contacts, as of the date above.

Cloudflare — hosting, security, and cookieless page statistics. May set short-lived technical cookies.
OpenStreetMap Foundation — map tiles, under their own privacy notice.
Supabase — image, media, and data delivery.

There is one exception, and we would rather name it than let you find it. A handful of unlinked design-preview pages, left over from building the site, load fonts from Google's servers. They are not part of the guide, nothing links to them, and we are removing them.

Separately, when you choose to follow a link — to a booking platform, a transport operator, a sanctuary, or a GPS app — that site receives your request and applies its own rules. We limit what we pass on: those sites see that you came from walkwithsaintfrancis.com, not which page you were reading.

Do Not Track and Global Privacy Control

We do not track you across sites, so there is nothing for these signals to switch off.

Questions

Write to hello@footstepswithstfrancis.com.