Last updated 29 July 2026.

The short version

Proudly Thame stores nothing whatsoever on your device. Not a cookie, not a tracking pixel, not a scrap of local storage. Nothing about your visit is recorded in your browser, and nothing follows you to any other website.

Why there is no cookie banner

UK law — the Privacy and Electronic Communications Regulations — requires a website to ask for your permission before storing or reading information on your device. It only applies if the site actually does that. This one does not, so there is nothing to ask permission for. A banner here would be theatre.

What this site genuinely does not have

• No Google Analytics, or any other analytics.
• No advertising or retargeting pixels — no Meta pixel, no Google Ads tag.
• No social media embeds, share widgets or like buttons.
• No embedded videos, maps or fonts loaded from someone else’s server.
• No chat widget, no A/B testing tool, no session recorder, no heatmaps.
• No consent-management platform — because there is no consent to manage.

Every font, image and script on this site is served from our own server. Your browser is never asked to contact a third party, so no third party ever learns that you visited. This is enforced technically by a Content Security Policy, not just promised in a document.

What the server records

Like every web server, ours keeps a short technical log of requests — IP address, page requested, time, browser type. This is not a cookie and it is not stored on your device. We use it to keep the site working and to spot abuse, and it is overwritten within days. More detail is in our privacy notice.

The registration form

If you fill in the form to apply for the mark, what you type is sent to us and stored so we can process your application. That is the form doing its job, not a cookie, and it is explained fully in the privacy notice. Simply reading this website leaves no record on your device at all.

If this ever changes

If we ever add something that does store data on your device, we will update this page, say plainly what it is and why, and ask your permission properly before it loads — with a real refuse option that works. We would rather not, and have built the site so we do not have to.