Cookie Policy

Most cookie policies are long because the site behind them is doing a great deal to its visitors. This one is short for the opposite reason. Everything below is either an explanation of terms or a description of what we do instead.

• No cookies are set by this site, so no consent is requested and no banner appears.
• Nothing about your visit is kept in your browser, either between pages or between visits.
• No analytics, advertising, remarketing or profiling script runs on any page.
• No script is loaded from any third-party domain, so no other company is told that you were here.

What we do receive is the contact form you choose to send us and the ordinary technical data any web server gets when it answers a request. Both are described in our Privacy Policy at /privacy rather than here, because neither one involves a cookie.

A cookie is a small piece of text that a website asks your browser to keep and hand back on every later request to that same site. It is the standard way a site recognises that two separate page loads came from the same person, which is what makes logins, shopping baskets and visitor analytics possible.

The word covers several different things, and the differences matter more than the label does:

Session cookie

Held only until you close the browser. Typically used to keep you signed in while you move between pages.

Persistent cookie

Given an expiry date and kept until then, so the site still recognises your browser on a visit weeks later.

First-party cookie

Set by the site you are actually looking at, and sent back only to that site.

Third-party cookie

Set by another organisation whose code the site has embedded — an advertising network, an analytics provider, an embedded video player. This is the kind that allows your behaviour to be followed from one website to the next.

Local and session storage

Not cookies, but the same idea: space in your browser where a site can keep data. Storage is not sent automatically with every request, which is the main technical difference, and it falls under the same consent rules when it is used for tracking.

None of the above is used on this website. We have listed them because you cannot judge a claim like ours without knowing exactly what is being ruled out.

This is a public site that describes an agency and invites you to get in touch. It has none of the features that normally require a cookie, so nothing had to be given up to reach zero.

• There is no login, no account and no members' area, so there is no session to remember.
• There is no shopping basket, no checkout and no payment flow.
• Nothing is personalised. Every visitor is served exactly the same pages, so there is no preference worth storing.
• We do not count you. There is no visitor analytics on the site at all, so there is no identifier to keep.

The one place a site like this is tempted to reach for storage is filtering. On the case studies page the filters you choose are written into the page URL instead of into your browser. It costs nothing and it is genuinely the better behaviour: a filtered view is a real address, so you can bookmark it, send it to a colleague, or open it in another browser and see the same thing.

Fonts are served from this domain rather than from a font provider. Loading a font from a third-party network would disclose your IP address to that network on every page view, which is a form of tracking even though no cookie is involved. Serving the files ourselves removes the request entirely.

The contact form does not rely on a cookie either. What you type is sent to this site's own server when you press submit, and nothing about the form is left behind in your browser afterwards.

We are not promising never to measure anything. We are promising not to do it quietly. If cookies, browser storage or analytics are ever introduced to this site, the following applies.

• This page is updated before the change goes live, not afterwards, and the effective date at the top changes with it.
• The update names what is set, who sets it, what it is for and how long it lasts — in that order, in plain language.
• Where the law requires consent, we ask for it first, and the site still works properly if you decline. Declining is a single action, not a menu of pre-ticked boxes.
• Anything strictly necessary to deliver a page you asked for is described here even though it does not require consent, because you should still know it exists.

The reason to write this down now is that it is easy to make the promise before there is any commercial pressure to break it. If you are reading this page and it still says the site sets no cookies, the promise has held.

The site embeds nothing from anyone else. There are no video players, no maps, no chat or support widgets, no social media buttons, no comment systems and no share buttons. Every page is assembled from files served by this domain, which is why no advertising or analytics company learns that you were here.

Links out to client websites, project pages and other external destinations are ordinary links. They are not tracking redirects and they carry nothing about you.

You do not have to take our word for any of this. Every mainstream browser ships with developer tools that list the cookies and storage a page has used, and opening them on any page of this site should show an empty list. Being able to verify a privacy claim in about thirty seconds is a reasonable thing to expect, and we would rather you did.

For the web in general, the controls sit with your browser rather than with any individual site:

• Browsers group cookie and storage settings under a privacy or security section, where you can see what is stored, delete it, and block future cookies — either all of them or third-party cookies only.
• Blocking third-party cookies is the single most effective setting for reducing cross-site tracking, and it rarely breaks anything.
• Private or incognito windows discard cookies and storage when the window closes, which is useful for a one-off visit to a site you do not trust.
• Browser vendors publish their own current instructions, and those are the ones worth following — menu layouts change far more often than any policy page does.

Blocking cookies entirely will not affect this site, because it does not set any. For the same reason, signals such as Do Not Track or Global Privacy Control have nothing to act on here: there is no tracking to switch off.

This policy describes how the website behaves today. It is maintained alongside the code rather than as a separate document, so a change in what the site does is meant to arrive together with a change in what this page says.

The effective date and the last updated date at the top of this page are the record. For any change that affects what is stored on your device, the update here is published before the change reaches the live site.

If something on this page does not match what you observe in your own browser, we would like to know. That would be either a bug in the site or an error in this document, and both are worth fixing. Write to us and tell us what you saw.

Our registered details, the governing law and the competent authority for any formal complaint are listed on the Imprint page at /imprint. Broader questions about the information we hold are answered in our Privacy Policy at /privacy.