Cookie settings

Why this page has no switches

Most sites that show you a cookie banner are asking permission for analytics, advertising or tracking. This site has none of those. It is a static site: a set of pages sent to your browser that then do nothing further.

• We set no cookies of any kind: not necessary, not functional, not analytics, not advertising.
• We store nothing in your browser’s local storage.
• There is no consent banner, because there is nothing to consent to.
• There are no preference toggles, because there is no preference to record. A toggle here would be decorative, and we would rather tell you the truth than build a control that does nothing.

If you check your browser’s storage inspector after visiting this site, you should find it empty. We would encourage you to look.

What does happen when you load a page

1. Your browser fetches fonts from Google. The typefaces are loaded from fonts.googleapis.com and fonts.gstatic.com. Your browser makes that request directly to Google, which can therefore see your IP address, the date and time, your browser and operating system as reported in the user-agent string, and which font file you asked for. Google does not set a cookie through this request, but it does receive that connection information, as any server does from anyone who connects to it. This is the only third-party request the site makes.

2. Netlify records the request in its server logs. The site is hosted on Netlify, which keeps standard access logs: IP address, timestamp, page requested, user-agent. This is ordinary hosting infrastructure, present on essentially every website, and it exists so the host can keep the service running and secure. We do not use those logs to analyse visitors, and we have built nothing on top of them.

3. If you use the consultation form, what you type is sent to us. That is covered in full on the privacy policy page.

How to block the Google Fonts request yourself

You do not need our permission and you do not need a setting on this page. You can stop the request at your end, and the site will fall back to the default fonts on your device. Everything stays readable, the layout holds, and nothing breaks.

• A content blocker. Any reputable content-blocking extension blocks requests to Google-owned domains, usually by default. This applies to every site you visit, not just this one.
• Firefox: Settings → Privacy & Security → Enhanced Tracking Protection → Strict.
• Safari: Settings → Privacy → Prevent cross-site tracking. A full block of the font domains needs an extension.
• Chrome: Settings → Privacy and security. Chrome cannot block a specific domain’s requests without an extension.
• Brave and other privacy-focused browsers: the built-in shield usually handles it; several redirect font requests locally by default.
• At the network level. A DNS-level blocker such as Pi-hole can block fonts.gstatic.com and fonts.googleapis.com for every device on your network.

If you would rather not bother, that is a perfectly reasonable position too. We are telling you so you can decide, not because we think you must act.

What you cannot turn off here

Netlify’s server logs. They are generated by the host’s infrastructure when your browser connects, before any of our code runs, so there is no switch on our side that would prevent them. The only way to avoid appearing in a web server’s logs is not to connect to that server. If you feel strongly, you can do that by writing to us at info@ebesonline.org instead of using the site.

Questions

Email info@ebesonline.org. If you find something on this site making a request we have not listed here, please tell us. We will either remove it or document it, and we will say which.