Welcome — and thank you for looking after your privacy (we look after it too).
You won't find a cookie banner on this website, and that's quite deliberate. We don't use tracking cookies, advertising cookies, or analytics cookies — in fact, we don't set any cookies at all. There's nothing to accept, nothing to decline, and nothing quietly following you around. You can simply enjoy exploring Martham's history in peace.
What are cookies, anyway?
Cookies are tiny text files that a website can place on your device. They're often used to remember things about you — what's in your shopping basket, whether you've logged in, or which adverts you've looked at. Some are harmless and helpful; others exist mainly to follow you across the internet and build a profile of your interests.
Because our website is a quiet place for reading about village history rather than selling things or tracking visitors, we have no need for any of that.
What this website doesn't do
To put your mind at ease, here's a short list of things this site will never do while you're browsing:
- Set any cookies on your device
- Run analytics or count you as a "tracked visitor"
- Show you adverts, or share anything with advertising networks
- Embed third-party content (such as YouTube players) that follows you elsewhere
- Store anything about your visit on our servers for marketing purposes
Even our fonts are kept at home
Many websites load their typefaces from Google's servers, which means your browser quietly tells Google every time you visit. We host all of our fonts ourselves, on the same server as the rest of the site. When you read a page here, your browser talks only to us — nobody else is listening in.
About the links to other websites
Throughout the site you'll find links to other organisations we admire — archives, museums, and fellow local history groups. Once you click one of those links and leave us, other websites' own rules and privacy practices take over, and some of them may use cookies of their own. We'd always encourage you to check their policies too.
If anything ever changes
If we ever introduce a feature that genuinely needs a cookie, we'll update this page first, explain in plain English what the cookie does and why, and ask for your permission properly before anything is stored. Until then, you can assume this page tells the whole story.
Any questions? We'd be delighted to hear from you via our Contact Us page, or you can browse our Frequently Asked Questions.