This page describes only what this site's build has been confirmed to do when someone visits www.dunsford-village.org.uk. It covers visit counting, the pages themselves, and links to other sites. It does not cover any destination reached after following an outbound link.
What visit information does this site collect?
A small amount of visit data is recorded, but only when a visitor arrives from a search engine. The data recorded is the page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button.
- What it collects: page path, event type, referring search engine name, and clicked outbound button text.
- When it is triggered: only for visits arriving from a search engine.
- What it is used for: counting page views and counting clicks on outbound buttons, and nothing else.
- How long it lasts: a single flag is kept in the browser for the current session, so one page view is only counted once during that session.
How are pages delivered to a visitor's browser?
The site is a set of static files served by a content delivery network. That network processes the technical details of every request as the hosting provider. Fonts used on the pages are embedded locally rather than loaded from an outside source, and every file a page needs comes from this domain while the page is displayed.
- Pages are self-contained: nothing is fetched from an outside host while a page is shown.
- Fonts are built into the site rather than pulled from a third-party font service.
- Hosting is static, delivered through a content delivery network.
What happens when an outbound link is followed?
Outbound links on this site point first to a path on this same domain, which then redirects the visitor to the partner site. No stored visitor data is passed to the partner as part of that redirect. Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site does not control what a partner site does with that request.
Why doesn't this page describe cookies, accounts, or data sharing?
Several practices that many sites describe simply do not exist here, which is why this page does not mention them further. There are no forms anywhere on the site, so nothing is submitted by a visitor for anyone to store. There is no third-party analytics service; the only counting described above happens through the first-party mechanism already explained. There are no external subresources, meaning no images, scripts, or styles are loaded from other domains. There are no contact channels on the site. No cookies are set, no persistent identifier is created, and no personal data such as names, e-mail addresses, account identifiers, or payment details is collected or stored.
What should a reader keep in mind?
Because there is no login, no registration, and no account system, nothing here is processed or retained on a per-visitor basis beyond the single session flag described above. Anything found on a linked partner site is outside this site's records and outside its control. Readers should treat this page as describing only this domain's static pages and their first-party visit counting, and should not assume the same practices apply once they leave for a linked destination.