Cookie Policy

1. The short version

This website sets no cookies. There is nothing here to accept or refuse, which is why you were never asked. Two settings are kept by your own browser so the site opens the way you left it, and they never leave your device.

Nor is there anything else of that kind. No advertising, no tag manager, no pixel, no embedded video, no social widget, no third-party fonts. The fonts are served from this domain.

This page has said three different things, and the date at the top changed each time. It began by saying the site set no cookies; from 6 September 2026 it said it set two, because Google Analytics had been added; it now says none again, because that was replaced on 20 September 2026 with analytics that sets none. Each version was true when it was published, and the old sentences are gone rather than softened.

2. What is stored in your browser

Two entries, both the site's own settings, and both in your browser's local storage rather than in a cookie. The difference is not a technicality: a cookie is attached to every request to the server that set it, and local storage is never attached to anything. These two are read by the page you are on and by nothing else.

Your browser's cookie list for this site is empty. If you look and find something in it, it did not come from us, and we would like to hear about it.

That is the whole list. If it ever grows, this table grows in the same change: it is generated from the site's own storage registry, and the build fails when the site writes a name that is not declared there. The published page and the running code cannot disagree. The same registry is what decides whether you are asked for consent at all: declare a cookie in it and the question comes back, with the banner and the controls that go with it.

3. Cloudflare Web Analytics, and what it receives

We use Cloudflare Web Analytics to see which pages are read, roughly where in the world a visit came from, whether it arrived from a search engine or a link, and how quickly the page loaded. That is the whole of what we do with it. It is run by Cloudflare, Inc., which reads it as our processor.

What it receives is the page you are on, the address you arrived from, your browser and device type, an approximate country, and the page's own loading measurements. It sets no identifier, so it cannot tell your second visit from somebody else's first, and it cannot follow you between sites. We send it no name, no email address, no phone number and nothing you type into the demo form.

There is no advertising dimension to it at all. Cloudflare Web Analytics has no advertising product behind it, stores nothing on your device and builds no profile of you. We chose it over what we had for exactly that reason: the previous analytics needed your consent, a banner on every page and two cookies, and this needs none of the three.

That it stores nothing is not a promise about our intentions. Our build fails if any cookie appears on any page of this site, in either language, at any point in a visit. The check is not that the right cookies appear; it is that none does.

4. The assistant, and the limits of this page

This page is about goai.qa. It is not about a conversation you had with an assistant on WhatsApp, Instagram or the phone: that belongs to the business you were writing to, and our Privacy Policy explains who answers for what in that relationship.

Our client portal is a separate application with its own sign-in, and this page does not cover it.

5. Removing what is stored

Delete both entries at any time in your browser's settings, usually under a heading such as site data or storage, by clearing the data for goai.qa. Nothing breaks: the site goes back to following your system's light or dark setting, and the notice about what is stored appears once more.

Blocking storage for this site altogether works too, and so does turning JavaScript off, which stops the analytics beacon loading at all. The site is built to run without any of it.

6. Changes, and contact

If what this site stores changes, this page changes in the same commit, and the date at the top of it changes too. That is how the cookies arrived here in September and how they left again two weeks later. Questions: contact@goai.qa.