Cookie Policy

This is a working draft. What it says about the website was checked against the code that builds this site. It has not been reviewed by a lawyer or by a data protection adviser, and the open questions are marked in the text as [TO BE CONFIRMED].

What a Cookie is here

A small piece of information a website asks your browser to keep, so that the site or a company working with it can recognise your browser on a later page or a later visit. Local storage and session storage do the same job by a different mechanism, and this page covers all three.

What this site sets by itself

Nothing.

The site’s own code sets no cookies, and uses neither local storage nor session storage. This is checkable rather than asserted: the published files carry no instruction to write to any of the three.

What the published files do carry, since 24 September 2026, is a request to three other companies’ code, and two of those store something. Where the sections below say “first party”, they mean a cookie kept under thevoiceofbusiness.eu: the browser files it under this site’s name because it was written by code running on this site’s pages, even though the code is not ours. A browser cannot tell the two apart and neither should this page.

Nothing on this site depends on a cookie. No page needs one to display correctly, because there is nothing to log into and no preference to remember.

What Google Analytics sets

The live site at thevoiceofbusiness.eu loads Google Analytics 4 from www.googletagmanager.com, with the measurement ID G-DRPGK79MSP. That code belongs to Google, not to us, and it stores an identifier in your browser so that Google can tell one visit from another and a returning reader from a new one.

Until 19 September 2026 this was the only third-party code anywhere on the site. It is now one of three: the chat button and the booking page described below are the others.

[TO BE CONFIRMED: the exact cookie names, their purposes and their lifetimes, confirmed against Google’s own current documentation on the day this page is published. They are set by Google and can change without this website changing, so they are not written down here from memory.]

The review copy of this site, used to look at work before it goes live, does not load analytics and therefore stores nothing at all.

What the Chat button loads

Every page on this site shows a chat button in the corner. It was added on 24 September 2026 and it is FlowHunt’s, not ours: the page asks app.flowhunt.io for their code and runs it, which is a different arrangement from the booking calendar below and worth being plain about.

Two files arrive on every page, before you touch anything: a small loader from app.flowhunt.io, and the button itself from the same place. The conversation panel is a third file and it is fetched only when the button is clicked, so a visitor who ignores the button never loads it.

What the two store, read out of their own code on the day this was written:

A cookie named fh-chatbotOpen, first party under thevoiceofbusiness.eu. It records that the panel was left open, so that moving to another page on this site does not close it. It is read on every page load.

A session storage entry named flowhunt_chat_popup_messages_closed, also first party, recording that you dismissed the greeting bubble so it is not shown again. Session storage is discarded when the browser tab closes.

Because FlowHunt’s code runs on this site’s own pages rather than inside a frame, it can read anything this site could: the page you are on, and what you type into the chat panel. What it does with that on their side is theirs to describe, and the conversation is sent to them in order to be answered.

[TO BE CONFIRMED: what FlowHunt stores about a conversation on their own systems, for how long, and under which agreement with this business. That is a question for FlowHunt and for the business, not something readable from the code on this page.]

What the booking page loads

One page, /book-a-meeting/, shows Calendly’s own booking calendar inside a frame pointing at calendly.com. It was added on 19 September 2026.

That calendar is Calendly’s page, not ours, and it sets its own cookies under their domain when it loads. We do not read them, and we cannot: a browser keeps one site’s storage away from another’s, so nothing the frame stores is reachable by this site’s own code.

Two things about how it is built, because both are decisions rather than accidents. It is a frame and not Calendly’s own embed script, so no third-party JavaScript runs inside this site’s own pages. And their notice about their cookies is left switched on: Calendly takes a parameter that hides it, and this site does not pass it.

Every other page on this site loads nothing from Calendly. Not visiting /book-a-meeting/ means nothing of theirs loads at all.

[TO BE CONFIRMED: the names and lifetimes of the cookies Calendly sets, against their own current documentation on the day this page is published. As with Google’s, they are set by Calendly and can change without this website changing.]

Nothing loads until you agree

This section used to say the opposite, and the change is worth stating plainly rather than quietly editing: until 24 September 2026 this site showed no banner and asked no permission before the analytics code or the chat button loaded. It now asks first.

The gate is real rather than a notice. If a category is switched off, the request to that company is never made: no script tag, no frame, no empty ping. There is nothing to store, because nothing was contacted.

Two optional categories, and you can set them separately:

• Analytics covers Google Analytics.
• Chat and booking covers the FlowHunt chat button and the Calendly calendar on the booking page.

The switches are on Cookie settings, which is linked from the footer of every page. The first time you arrive, a bar at the foot of the page offers the same choice.

Withdrawing is as easy as agreeing. Turning a category off deletes the cookies it set where those are under this domain, and reloads the page so the code you turned off is no longer running. Cookies set by Calendly under their own domain cannot be reached from here, and their own policy covers those.

[TO BE CONFIRMED: the lawful basis recorded for each category now that consent is asked for, which is a decision for the business and its adviser rather than something this page can settle.]

How to refuse

The switches above are the direct route. Everything below still works and does not depend on this site behaving properly.

Every current browser can block or clear cookies for a single site from its own settings, and blocking them for this one stops the analytics identifier being kept and stops the chat button remembering an open panel. Most browsers also offer a private or incognito window, which discards everything a site stored when you close it. Google publishes a browser add-on that opts you out of Google Analytics on every site at once.

Because nothing here depends on cookies, refusing them does not break any page on this site.

Questions

Questions about this page, and about anything it describes, go to support@thevoiceofbusiness.eu. That is the same address the privacy policy names.