Cookies

Nothing, until you submit a form.

No cookie of ours, and nothing in your browser’s local storage. This site has no login, no cart and no preference to remember — the look of it is fixed in the page, not saved on your device — so it has no reason to write anything down and does not. The exception is the bot check described below: submit the newsletter box and that check may leave a short-lived clearance token, so that passing it once is enough. It carries nothing about you. There is still no consent banner here, because a check that only runs when you submit a form is what makes the form work rather than something we learn from.

We count page views, with the counter our hosting provider offers. It is served from this domain, it sets no cookie, and it stores nothing on your device. What it reports is aggregate: which pages were read, which site sent you, the country and the class of device.

It is page counts, not people. Nothing it records is joined to your name, your email, or anything you have sent us — and if you would rather it did not count you at all, the section on controls below says how to stop it.

• ·Advertising cookies, retargeting pixels and conversion tags.
• ·Cross-site tracking of any kind, and any sale or sharing of data for behavioral advertising.
• ·Session recording, heatmaps and mouse-movement capture.
• ·Embedded third-party players and social widgets, which set their own cookies the moment a page loads. Our social links are links; they load nothing until you click them.

Two places on this site take something you type. One of them can leave something behind, and it is the bot check described below rather than the form itself. The newsletter box — in the footer, and on the M1 and store pages — sends your address to our own systems and mails you one message to confirm it before anything is added; what happens to the address itself is set out in the privacy policy. The terminal on the cybersecurity page is the other, and it is a toy: what you type into it is answered in your browser and never sent anywhere at all.

That submission sits behind a bot-check service — run by the same company that runs our DNS, not a new one — and it does its work without asking you to pick out traffic lights. It reads the request and some signals about the browser making it, tells our server yes or no, and can leave a short-lived clearance token on this domain so that passing it once is enough. It is not told who you are or what you typed, and it is the only thing on this site that can write to your device.

The newsletter itself is measured, and it belongs on this page because the measurement is a pixel and a rewritten link rather than a cookie: the provider that delivers it records whether a message was opened and which links in it were clicked, for each recipient. What we do with that is in the privacy policy. If you would rather not be counted, a mail client set to block remote images stops the open from registering, and clicking nothing stops the rest — neither costs you the newsletter.

Every browser can block and clear cookies. Do it here and the only thing you will clear is the bot-check token, which the next submission replaces — worth knowing only because a browser set to refuse it outright will make the newsletter box fail its check, and you would otherwise be left wondering why. What you can actually refuse with nothing lost is the measurement: block requests to /_vercel/insights with your browser or an extension, and the rest of the site behaves exactly as it did before.

Do Not Track we do not read, and we would rather tell you that than leave you assuming otherwise. The header exists to switch off tracking that follows a person between sites. There is none of that here to switch off, which is the only reason we can say the signal costs you nothing.

Our client and vendor portals are ours too, on another of our domains. They sign you in, so they set cookies to keep you signed in, and the notice you are shown there covers them. What we collect through this site is set out in the privacy policy. Anything unclear, ask us at intel@marshallmedia.io.

The project inquiry form sits on that same domain, and the link to it is where this site ends. What it writes to your device, and what it keeps, are covered by the notice on that form rather than by this page.