Deiniolen Trust Fund

Cookie policy.

A short policy on the small number of cookies and similar technologies we use at deiniolentrust.org. We do not run advertising cookies. Last updated: 22 May 2026.

In short.

  • We use one essential preference cookie to remember that you have seen the cookie notice.
  • We do not run advertising trackers, social-media pixels, or third-party analytics that profile you.
  • You can clear the preference cookie at any time from your browser settings.

1. What is a cookie?

A cookie is a small text file that a website asks your browser to store on your device. Cookies are commonly used to remember preferences (e.g. that you have dismissed a notice), to keep you logged in, or to track your behaviour across the web for advertising. This website only uses the first kind, and only one of them.

2. Cookies we use.

Strictly speaking, the only thing we use is a small entry in your browser’s localStorage (a closely related technology to cookies, which the UK ICO treats under the same Privacy and Electronic Communications Regulations).

Name Purpose Type Lifetime
dtf-cookies Remembers that you have seen the cookie banner so we do not show it again. Essential preference Persistent (localStorage); until you clear browser data.

3. What we do not use.

  • No Google Analytics, no Plausible, no other third-party analytics.
  • No Facebook pixel, no LinkedIn Insight Tag, no advertising network.
  • No third-party share buttons that load tracking code (our social icons are plain links).
  • No A/B testing tools.

If at some point in the future we add an analytics tool, we will update this policy first, and we will use one that does not require consent (e.g. a self-hosted privacy-friendly tool) or we will add a granular consent banner.

4. Third-party content.

The website embeds the following third-party resources, each of which is loaded over HTTPS and may, by virtue of your request to their server, see your IP address:

  • Google Fonts — for the typefaces Cormorant Garamond, Inter and JetBrains Mono.
  • Cloudflare CDN — for Font Awesome icons.
  • OpenStreetMap — for the embedded map on the contact page.
  • Tailwind CSS CDN — for the design system underlying the page styles.

None of these are used for tracking or advertising. Each provider has its own privacy policy, which you can read on their respective websites.

5. How to clear our cookies.

To clear the dtf-cookies preference, simply clear your browser’s site data for deiniolentrust.org. In most browsers this is found at Settings → Privacy → Cookies and site data → See all cookies and site data. The next time you visit, the cookie banner will reappear.

6. Changes to this policy.

If we add or remove cookies we will update this policy and the Last updated date at the top of the page. Substantive changes will be flagged on the homepage for one full quarter.

7. Contact & complaints.

Questions about our use of cookies? Write to [email protected]. You also have the right to complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113.

What we do differently from larger charities.

Most larger charity websites you have visited recently will load a granular consent banner that asks you to opt in to advertising cookies, social-media tracking, analytics, and so on. We do not do this because we do not run any of those technologies; the consent banner would, in our case, be cosmetic. We are not opposed to analytics for charities that need them; we have, as a four-trustee village trust, no real need to know how many people visited the FAQ page last Tuesday.

A sheet of printed paper with the heading 'Cwcis · DEINIOLEN TRUST FUND · Polisi 2025' and a fountain-pen tick in the margin.
The cookies policy in printed form, with one fountain-pen tick from the July 2025 board meeting.

If we ever add analytics, this is how it will go.

If, at some future point, the trustees agree that a small amount of analytics would help us understand whether the website is helping the village (rather than helping us look good on the Charity Commission’s register), we will: first, agree it at a board meeting and minute the decision; second, choose a privacy-friendly self-hosted tool that does not require consent (e.g. Plausible or Umami); third, update this policy with the Last updated date and write about the change in the quarterly dispatch. We will not switch to Google Analytics or any tool that profiles individual visitors.

We do not need a dashboard to know that the village is using the website. The village writes to us. From the November 2024 AGM notes
Read also

Privacy & terms.