Cookie Policy

What a cookie is

A cookie is a small text file a website asks your browser to store. On your next visit the browser sends it back, which is how a site recognises a returning visitor or remembers a setting. Related technologies do the same job by other means, including local storage, session storage, pixels, and web beacons. Where this page says "cookie" it covers all of them.

A first-party cookie is set by the site you are visiting. A third-party cookie is set by another company whose content is embedded in the page, such as a video player or a booking widget.

Cookies this site sets

The site itself has no sign-in, no shopping basket, and no personalisation. The one cookie we set for visitors is we_consent. It records whether you allowed analytics and advertising, and when you answered the cookie banner. It belongs to workflowengine.io, so the same answer applies on docs.workflowengine.io and api.workflowengine.io, and it expires after a year, when the banner asks again. The contact form sends your message and stores no cookie in the process. The other cookies come from the tags in the Google Tag Manager container. In the European Economic Area they arrive on the page where you accept them. In the United Kingdom and Switzerland the analytics cookies arrive on the first page you open and the advertising cookies on the page where you accept them; everywhere else all of them arrive on the first page you open, before you click anything. Measured on August 28, 2026, before the banner existed, one page load left _gcl_au (Google Ads conversion linker) and _rdt_uuid (Reddit), and also _twpid from the X tag, which has since been removed. Google Analytics, Microsoft Clarity and LinkedIn set their own once their tags run.

Our web fonts are served from our own servers. They are built into the site when it is compiled, so loading a page sends no request to Google Fonts and sets nothing.

One exception applies to staff rather than visitors. The editing tool at /admin/ keeps a sign-in token in the browser of whoever is logged in to publish content. It is not reachable from any public page and it plays no part in an ordinary visit.

The servers and content network that deliver the site may set a strictly necessary cookie to route requests or block abuse. A cookie of that kind carries no marketing data and cannot be used to build a profile of you.

Third-party services that can set cookies

Everything below runs on our pages but belongs to another company. Each sets its own cookies under its own policy, and none of them gives us access to those cookies. The first five are loaded by the Google Tag Manager container rather than written into the site, so the list reflects what that container ran on August 28, 2026, without the Quora and X tags removed from it since. Those five wait for the cookie banner. Google Analytics and Microsoft Clarity form its analytics category, and Google Ads, LinkedIn and Reddit its advertising category. Calendly and YouTube are outside the banner, because the booking calendar and the video player cannot work without them.

Their own policies explain what each one stores and for how long:

• How Google uses cookies, which covers Analytics, Ads and YouTube
• Microsoft Clarity privacy and cookies
• LinkedIn cookie policy
• Reddit cookie notice
• Calendly Cookie Policy

What we do and do not do

We do run advertising tags. Google Ads, LinkedIn and Reddit can each recognise a visit and use it to measure a campaign or to build an advertising audience, which is what makes it possible to show you an advertisement elsewhere later. We also run session replay through Microsoft Clarity, which records mouse movement, scrolling and clicks on the page and lets us watch that back. An earlier version of this page said we ran no advertising or retargeting tags. That was wrong, and it is corrected here.

We do not sell cookie data, and we do not ask any of these services to identify you by name. What we get back from them is campaign measurement and page behaviour, not a customer record.

A cookie banner asks before these tags run, with two categories, analytics and advertising. In the European Economic Area both start switched off. Microsoft Clarity, LinkedIn and Reddit then do not load at all, and Google Analytics and Google Ads set no cookies until you accept. In the United Kingdom and Switzerland analytics starts switched on and advertising switched off, and "Reject all" turns analytics off as well. Everywhere else both start switched on, so the tags run on the first page you open, and "Reject all" turns them off. Google works out your region from your connection, so a VPN can change which rule applies. The site works fully with both categories off.

Google Tag Manager was added on August 11, 2026. The full list of tags in its container was measured in a live browser and written into this page on August 28, 2026. The Quora and X tags were removed from the container by September 26, 2026, and this page stopped listing them on October 2, 2026. The cookie banner went live on workflowengine.io on October 2, 2026, and on docs.workflowengine.io and api.workflowengine.io on October 3, 2026. Since October 6, 2026 analytics starts switched on in the United Kingdom and Switzerland. Because the container is configured outside the website code, this list is accurate as of those dates; if you are checking us against a questionnaire and the date is old, ask us to re-measure.

The documentation sites

docs.workflowengine.io and api.workflowengine.io show the same cookie banner and read the same we_consent cookie, so one answer covers all three sites. Each loads its own Google Tag Manager container (GTM-WH5TSKC4 and GTM-KKQKSTB3) with Google Analytics 4 and Microsoft Clarity, both in the analytics category and under the same rules as above. Each also shows a Calendly "Get a Demo" button on every page, outside the banner. Neither runs advertising tags.

How to control cookies

The cookie banner is the first control. "Reject all" and "Accept all" answer for both categories, "Choose" sets each category on its own, and the gear icon after "Cookie Policy" at the bottom of every page on workflowengine.io, labelled "Cookie settings", opens the banner again. Allowing a category starts its tags on the page where you allow it; refusing one stops them from the next page you open. Cookies a tag set earlier stay until they expire or you delete them in your browser.

Your browser is the second control, where you can block cookies for a single site or for all of them, and delete anything already stored. Tracking protection built into Firefox, Safari and Edge already blocks most of the advertising tags above, and a content blocker will stop the rest. Blocking them on this site costs you only the booking calendar and in-page video playback; measurement, session replay and advertising tags simply stop seeing you.

• Chrome cookie settings
• Safari cookie settings
• Firefox cookie settings
• Edge cookie settings

Browser-level tracking protection, private browsing, and blocking extensions all work normally here. Nothing on this site tries to detect or defeat them.

Do Not Track signals

Browsers can send a Do Not Track signal, but no agreed standard says how a website must answer it, so we do not act on it, and neither do the third-party tags described above. If you want the tracking to stop, "Reject all" in the cookie banner or blocking in your browser does it. This matches section 11 of the privacy notice.

Changes to this policy

When what the site loads changes, this page changes with it, and the date at the top moves. It is worth re-reading if you are checking us against a procurement or security questionnaire.

How to contact us

Questions about cookies, or about anything else on this page, go to hello@optimajet.com. Requests about your personal data are covered by the privacy notice, which explains what we hold and how to ask for a copy or a deletion.