Cookie policy

This site sets no cookies of its own. Page-view numbers come from Vercel Analytics, which counts visits without storing anything in your browser. So on a normal visit, nothing is written to your device and there's no banner to dismiss.

There's one exception, and it's below.

A small text file a site asks your browser to keep, and hand back on your next visit. Some are genuinely useful — they're how a store remembers your basket, or how a site stays logged in. Others exist to follow you between sites and build an advertising profile.

The distinction matters more than the technology. It's why this page groups by what a cookie is for rather than by whether it's first- or third-party.

Strictly necessary

None. This site has no login, no basket and no personalisation, so there's nothing to remember between pages.

Analytics — Vercel

No cookies. Vercel Analytics counts page views and referrers in aggregate, without a device identifier or a profile.

Analytics — Google (conditional)

If Google Tag Manager is enabled on a deployment, Google Analytics sets _ga and _ga_* to tell a returning visit from a new one. They last up to two years and hold a random ID, not your name.

Advertising

None. No Meta pixel, no LinkedIn Insight tag, no remarketing lists. We don't retarget people who read a blog post.

Where Google Analytics is running, IP anonymisation is on and we've turned off data sharing with other Google products and ad personalisation. We use it to see which articles earn their place, nothing more.

Third-party embeds can set their own cookies, which is why we mostly avoid them. Case-study visuals on this site are drawn in code rather than pulled from an image host, and videos are served from our own domain.

If we ever embed something external — a booking widget, a map — this page gets updated with what it sets before it goes live.

You don't need our permission or a preference centre. Every browser lets you block or clear cookies directly:

• Chrome — Settings, then Privacy and security, then Third-party cookies.
• Safari — Settings, then Privacy, then Manage Website Data.
• Firefox — Settings, then Privacy & Security, then Cookies and Site Data.
• Edge — Settings, then Cookies and site permissions.

Blocking everything on this site costs you nothing — no feature here depends on a cookie. On other sites it may log you out or empty a basket, which is worth knowing before you block globally.

Global Privacy Control and Do Not Track are honoured in code, not just in a promise: if your browser sends either signal, the Tag Manager script never loads, so Google Analytics never runs and no cookie is written.

This policy covers quesiono.com only. Sites we build for clients are theirs, with their own analytics, their own tools and their own cookie policy.

What we do on every build: keep the tag list to what someone can name a reason for, load consent tooling where the audience needs it, and write the client's own cookie policy from what's actually installed rather than from a generator template.

If we add a tool that sets a cookie, this page changes before the tool ships, and the date at the top moves. Spotted something in your browser's storage inspector that isn't listed here? Email hello@quesiono.com — that's a bug on our side and we'd want to know.