Cookie Policy
This site sets two cookies, both of them Google Analytics, and neither of them until you have said yes. Here is what they are, what else is kept on your device, and how to change your answer.
Last updated 6 September 2026
1. The short version
This website sets two cookies. Both belong to Google Analytics, both are set only if you allow them, and until you do, opening a page here tells Google nothing, because nothing of Google's has been loaded. Refuse, and it stays that way.
Everything else is as it was. No advertising, no tag manager, no pixel, no embedded video, no social widget, no third-party fonts. The fonts are served from this domain, and the two settings your browser keeps for the site itself never leave your device.
This page changed on the date at the top of it, in the same commit that added the analytics. It used to say this site set no cookies. That was true then and it is not true now, so the sentence is gone rather than softened.
2. What is stored in your browser
Four entries, of two kinds. The first two are the site's own settings and use your browser's local storage which, unlike a cookie, is never attached to a request and never travels to a server. The last two are the Google Analytics cookies, which do travel: a cookie is sent to the server that set it, which is what makes it a cookie rather than a setting.
The second analytics cookie's name ends in our own measurement ID, so your browser's cookie list shows it written out in full rather than in the shortened form used here.
- Name
- goai-theme
- Category
- Strictly necessary
- What it is for
- Remembers whether you chose the light or the dark theme, so the site opens the way you left it.
- How long it stays
- Until you clear this site's storage in your browser.
- Name
- goai-consent
- Category
- Strictly necessary
- What it is for
- Remembers your answer to the storage notice, so it does not ask again on every page. It records the answer itself, whichever way it went, because a refusal that is not remembered is a question you get asked for ever.
- How long it stays
- Until you clear this site's storage in your browser.
- Name
- _ga
- Category
- Analytics
- What it is for
- Set by Google Analytics once you allow it. It holds a randomly generated number that tells one browser from another, so somebody who reads three pages is counted once rather than three times. It carries no name, no email address and no phone number, and it is not set at all until you have said yes.
- How long it stays
- Two years from your most recent visit. Deleted the moment you refuse analytics, here or in the notice.
- Name
- _ga_<container>
- Category
- Analytics
- What it is for
- Set by Google Analytics once you allow it. It holds the state of the visit you are on: when it started and whether it is still going. The end of its name is our own measurement ID, so your browser will show it written out in full.
- How long it stays
- Two years from your most recent visit. Deleted the moment you refuse analytics, here or in the notice.
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.
3. The choice, and changing it
A notice at the foot of the page offers two buttons: Refuse and Allow. They are the same control at the same size, one click each, and Refuse comes first. Neither is a link, neither is greyed, and nothing is ticked for you in advance. A choice that is harder to refuse than to accept is not a choice, and we would rather have fewer numbers than pretend otherwise.
Until you press one of them, no Google code has been loaded and no cookie exists. Both answers are remembered on your own device, so the notice does not ask again.
You can change your answer here, at any time. Refusing after allowing deletes the two cookies listed above, and switches the measurement off for the rest of the page rather than merely stopping new cookies: Google's own opt-out flag is set, so the code already loaded sends nothing further, and it is not loaded again on any later page.
Your answer is stored on this device. The filled button is the one it holds now, and neither is filled until you have answered.
4. Google Analytics, and what it receives
We use Google Analytics 4 to see which pages are read, which of the two Book a demo buttons is pressed, roughly where in the world a visit came from, and whether it came from a search engine, a link or a phone. That is the whole of what we do with it. It is run by Google LLC, which reads it as our processor and holds the data on servers outside Qatar.
What it receives is the page you are on, the address you arrived from, your browser and device type, an approximate location worked out from your IP address, and the identifier in the two cookies listed above. Your IP address is truncated before it is stored, which is asked for explicitly in our configuration rather than left to a default. We do not send Google your name, your email address, your phone number or anything you type into the demo form; that form does not post to a server at all.
Google's advertising signals are switched off and stay off: this site asks for no permission to advertise to you, has no Google Ads account linked to it, and tells Google in every request that advertising storage, advertising data and personalisation are denied. Analytics is the only thing you are being asked about, because analytics is the only thing there is.
None of it can run before you have said yes. The code that sends an event has to be handed a consent token before it will run, and the only thing that can mint that token is your stored answer. That is not a promise about our intentions: our build fails if a cookie appears on any page before an answer is given, if a cookie appears after a refusal, or if any cookie appears that is not one of the two named above.
5. 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.
6. Removing what is stored
Pressing Refuse analytics above is the quickest way: it deletes both analytics cookies and stops any more being set. You can also delete all four 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 appears once more so you can answer it again.
Blocking storage for this site altogether works too, and so does turning JavaScript off, which stops Google Analytics loading at all. The site is built to run without any of it.
7. 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 analytics above arrived here: the cookies and this page were written on the same day. Questions: operations@goai.qa.