Cookie policy

This page explains that in full: what a cookie is, the categories a website can use, exactly what this site does and does not store in your browser, how you stay in control, and what would change if analytics or an embedded video were ever added. It is written plainly, so you can check the claim for yourself rather than take it on trust.

A cookie policy has one honest job. It tells you what a website places on your device, why it does so, and what you can do about it. Many cookie policies quietly fail that job. They are written to look thorough while saying as little as possible, and they describe a general category of website rather than the specific site you are actually reading.

This one is different in a way that leaves it short on substance and long on explanation. There is very little to disclose here, because the site is built to work without watching you. So most of the page is spent explaining how cookies work in general, what the standard categories are, and how you keep control, so that the small factual claim at the centre of it all, that nothing on this site tracks you, is something you can verify rather than simply believe.

Where this page describes the technology or the law in general terms, it is background, not advice. Where it describes what this particular site does, it is a plain statement of fact that you can test in your own browser, using the tools every modern browser already gives you. If a claim on this page and the behaviour in your browser ever disagree, believe your browser and tell us, because it means this page has fallen behind the site.

A cookie is a small text file that a website asks your browser to store. The next time you load a page from the same site, your browser sends that file back, so the site can recognise the browser and remember something about it. Cookies were invented to solve a genuine problem, which is that the web forgets. Without some form of memory, a site cannot keep you logged in from one page to the next, remember what you have put in a basket, or hold a simple preference such as your chosen language.

That memory is neutral in itself. The same mechanism that keeps you logged in can also be used to follow you from site to site and build a picture of what you read and what you buy. The difference is not the cookie. It is what the cookie stores, who is allowed to read it, and how long it is kept.

A cookie set by the site you are visiting is a first-party cookie. A cookie set by another company whose code happens to run on the page, an advertising network or an embedded video player, for example, is a third-party cookie. First-party cookies are usually about making the site work for you. Third-party cookies are the ones most often used for tracking, which is why both browsers and the law now treat them with suspicion. A cookie can also last for very different lengths of time. A session cookie disappears when you close the browser, while a persistent cookie stays for a set period, or until you delete it, so a site can remember you across visits.

It helps to know that a cookie is only one of several ways a website can keep information on your device, because a policy that talks only about cookies can miss the point. Modern browsers also offer local storage and session storage. These let a site keep small amounts of data on your device much as a cookie does, with one difference: they are not automatically attached to every request you make back to the server. That can make them a little more private in practice, but the data is still yours and still sits in your browser, so this policy treats it exactly the same way it treats cookies.

There is also the ordinary browser cache, which stores copies of images, fonts and scripts so pages load faster on a second visit. The cache is about speed, not identity, and it is cleared with the same controls you use for cookies.

Finally, it is worth naming the technique that needs no stored file at all. Fingerprinting tries to recognise a browser by combining the details it reveals, such as screen size, fonts and settings, into a signature. It is more intrusive than a cookie precisely because there is nothing for you to delete. This site does none of this. It does not fingerprint, it loads no third-party code that could, and the only data it keeps on your device is the small, ordinary WordPress cookies described further down, and only in the two cases where they apply.

To understand why a site setting no third-party cookies is meaningful, it helps to see how tracking is usually done. Imagine the same advertising network has code running on hundreds of unrelated websites. When you visit the first of them, that network sets a cookie in your browser with a unique identifier. When you later visit the second, the third and the fortieth site, each of them loads the same network’s code, and your browser politely hands back that same identifier every time. The network has not followed you around the room. It has simply been waiting in forty different rooms, and recognised you in each.

Over time this builds a profile: the sites you read, the products you looked at, roughly where you are and when you browse. None of it required the sites themselves to share anything directly. The shared third party did the joining up. This is the quiet mechanism behind most online advertising, and it is why third-party cookies have been restricted by browsers and questioned by regulators.

The defence against it is straightforward. If a site loads no third-party code on its pages, there is no shared party to recognise you, and no identifier to hand back. That is the position here. Reading a page on this site adds nothing to any profile anywhere, because nothing on the page is talking to anyone but the site you chose to visit.

Neither the theme nor the plugin behind this site sets a cookie of any kind. Reading these pages, moving between them, and sending an enquiry all happen without a single cookie being written for that purpose.

WordPress, the software the site runs on, sets cookies in two situations, and neither applies to an ordinary visitor. If you log in to the site as an administrator or editor, WordPress stores session cookies so that it can keep you logged in as you move around the dashboard. If you leave a comment on a post, WordPress may store your name, email address and website in your own browser so that you do not have to type them again next time. That is a convenience for the person commenting, not a tracker, and it is stored on your device rather than sent away to build a profile.

If you are doing what almost everyone here does, reading pages and perhaps sending an enquiry, neither of those situations arises and nothing is stored. There is no visitor cookie, no session identifier for ordinary browsing, and no profile assembled in the background. The absence is the whole point: the ordinary experience of this site leaves nothing behind in your browser.

Loading a page here does not quietly tell anybody else that you visited. This matters, because on a great many sites the cookies that follow you are not set by the site at all. They are set by the other companies whose code the site chose to load: fonts pulled from one provider, analytics from another, an advertising pixel from a third, a chat bubble from a fourth. Each of those is a request to a different server, and each request is a chance for a third party to set a cookie and note your visit.

This site avoids all of that by simply not making the requests. Fonts are self-hosted, which means they are served from the same place as the rest of the site, so no request goes to Google to fetch them. There is no embedded analytics script, no advertising pixel, no social media widget, and no comment or chat service loaded from another domain. The page you are reading is served from one place and depends on no one else to appear.

If a video is ever embedded on a page, that provider may set its own cookies when the video loads, and this page will be updated to say so before the change goes live. Until that happens, there are no third-party cookies to disclose, for the plain reason that there are no third parties on the page to set them.

The two situations above are worth spelling out, because they are the only cookies this site is capable of setting, and both exist for the people who run or take part in the site rather than for visitors passing through.

The first is the logged-in session. When an administrator or editor signs in to manage the site, WordPress sets session cookies that keep that person authenticated as they work. Without them, the person would be logged out on every single click. These are a textbook example of strictly necessary cookies. They exist only to make a secure, signed-in session possible, they are tied to a specific account, and they are of no use whatsoever to someone who is simply reading the site.

The second is the comment convenience. If commenting is enabled and you choose to leave a comment, WordPress may store your name, email address and website in your own browser so those fields are ready for you next time. This is kept on your device, for your benefit. It is not sent anywhere to build a profile, and if you never comment it is never set. You can clear it whenever you like using your browser’s ordinary controls, which are described below. Neither of these cookies is used to advertise to you, and neither is shared with anyone outside the site.

None of this happened by accident. It is easier, not harder, to bolt an analytics tag and a few widgets onto a site, and most sites do exactly that. Building one that works without them is a deliberate choice, and it is worth explaining the thinking, because it tells you what to expect from this policy over time.

The principle is privacy by default. Data that is never collected cannot be lost, leaked, subpoenaed, or quietly repurposed later. A visitor reading about filming in Nepal has no reason to be entered into an advertising profile, and an enquiry is a private message between you and us, not an event to be measured and shared. So the site is arranged to gather nothing it does not need, to keep what little it does hold on your own device, and to depend on no outside service to render a page.

There is a practical side too. A page with no third-party scripts loads faster, breaks less often, and behaves the same whether or not you run a tracker blocker or turn JavaScript off. The privacy and the reliability come from the same decision. When a site is built to need trackers in order to work, both you and the site are worse off, and this one is built the other way round on purpose.

Every browser lets you see, block and delete cookies through its settings, and you should feel free to use those controls however you wish. On this site, they will cost you nothing. Because the site sets no cookies for ordinary visitors, blocking cookies will not change anything you can see or do here. Pages load the same, navigation works the same, and the enquiry form behaves the same.

That last point is deliberate. The enquiry form works with cookies blocked, and it works with JavaScript disabled. It does not depend on a tracker being present, on a session being remembered, or on any script running quietly in the background in order to function. You can lock your browser down as tightly as you like and still read every page and send an enquiry.

If you use a browser extension that blocks trackers, you will notice it has nothing to do on these pages. That is the intended result, not a coincidence. A site that needs its trackers unblocked before it will work has arranged things the wrong way round, and this one has not.

Consent only matters when there is something to consent to, and on this site there is not. That is why you see no cookie banner. A banner asking permission to set cookies the site does not set would be theatre, and the more banners people click through without reading, the less any of them mean.

The site is nonetheless built so that analytics could be added later without personal data leaking into them, and so that nothing non-essential is loaded until consent is given where consent is required. In other words, the default is off. If analytics or any other non-essential technology is ever introduced, it will not fire the moment you arrive. A consent mechanism will be put in place first, and only a clear, freely given yes will load it. Choosing no, or simply ignoring the request, will leave nothing loaded.

If that day comes, this page will be updated to name the provider, to say what it stores and for how long, and to describe how you give or withdraw consent, all before anything goes live. Until then there is nothing to disclose, and the honest thing is to say so plainly rather than pad the page with permissions you will never be asked for.

Beyond cookies, your browser can send a general signal that tells sites how you would like to be treated, without you having to set anything site by site. Two of these are worth knowing about, because they show where the wider web is heading, even though neither changes anything here.

The older one is Do Not Track, a header your browser can attach to every request, asking sites not to track you. It was well meant, but it never became binding. Sites were free to ignore it, and most did, so browsers have largely retired it. Its successor is Global Privacy Control, a signal designed to carry legal weight in places whose laws recognise it, so that switching it on counts as a formal request not to have your data sold or shared. Support is growing, and some regulators now treat it as a valid expression of your choice.

On this site, both signals are academic. There is nothing here to track, sell or share, so there is no behaviour for either one to change. They matter on the sites that do collect data, and it is worth turning Global Privacy Control on in your browser for exactly those sites. Naming them here is simply part of giving you the full picture rather than the narrow one, so that you leave this page knowing your options across the web, not only on this corner of it.

It is worth separating two things that are easy to confuse, because a policy that talks only about cookies can leave a false impression. Cookies are stored on your device. Server logs, by contrast, live on the server and are a normal part of how the web works.

Whenever any browser requests any page from any web server, the request itself carries some basic technical information, such as the address it came from, the time, the page asked for, and the kind of browser making the request. A server can record that in an ordinary access log. This is not a cookie, it stores nothing on your device, and it is not the same as advertising tracking. It is closer to the way a telephone exchange has always known that a call was placed, without listening to it. Logs of this kind are used to keep a site running, to spot faults, and to defend against abuse, not to follow you from site to site or to build a marketing profile.

The honest position is that this is a matter of general web infrastructure rather than something this cookie page can settle for your specific case, so how any such information is handled belongs with the privacy policy rather than here. What this page can say plainly is the thing it exists to say: no cookie is set for ordinary visitors, and nothing on these pages is loaded from a third party that could turn a routine request into cross-site tracking.

Cookie notices exist because of the law, so it helps to know the shape of it, kept general and offered as background rather than advice. Different places regulate cookies differently, and the rules that apply depend on where you are and where the people contacting a site are, which is one reason a policy like this points you to your own adviser rather than pretending to settle the question.

In the European Union, the ePrivacy Directive, often called the cookie law, is what requires consent before non-essential cookies are set, while the General Data Protection Regulation sets the wider standard for how personal data is handled, including what valid consent must look like: informed, specific, freely given, and as easy to withdraw as it was to give. The United Kingdom keeps a close parallel through the Privacy and Electronic Communications Regulations, sitting alongside its own version of the data protection rules. Across the Atlantic, laws such as the California Consumer Privacy Act take a different route, leaning on your right to opt out of the sale or sharing of personal information rather than on permission asked in advance.

The common thread is straightforward, and it is the reason this site is arranged the way it is. Wherever you happen to be, the safest position is to collect no more than you need, to be honest about what you collect, and to make consent real where consent is required. A site that sets no non-essential cookies has very little to ask permission for under any of these regimes, which is exactly the point of building it this way. None of this is legal advice, and your own adviser should confirm what applies to you and to the people who contact you.