A prompt, not a settings panel
The banner contains two buttons. Other pages do not have this banner in their current markup.
This cookie notice is a draft pending operator and legal review; it describes the current app code, not unverified hosting or future services.
CodeThe current code stores a choice called acg-cookie-choice.
The buttons save either essential or accepted.
No analytics service is configured in the current app code.
In the current app, cookie-choice banner markup exists only on the homepage. The shared script checks for that banner and shows it there when it cannot find a saved choice.
The banner contains two buttons. Other pages do not have this banner in their current markup.
The code looks for acg-cookie-choice. If it is absent, the homepage banner is shown.
The selected value is written as a browser cookie and the banner is hidden for the current page view.
The saved value records which banner button was pressed. It does not activate a collection of separately named cookie categories.
acg-cookie-choice is set as a same-site browser cookie, with SameSite=Lax and path=/.
The code sets max-age=31536000, which is one year.
The stored value is either essential or accepted, according to the button used.
These labels describe the two controls in this draft. They do not define additional settings or claim a particular legal status.
The buttons only save their corresponding value in the cookie. The current code does not use that value to switch analytics or third-party tools on and off.

This button stores essential in acg-cookie-choice and hides the banner.
This button stores accepted in the same cookie and hides the banner. It does not connect any analytics service.
The browser stores the choice; the app code uses it to decide whether the homepage banner should appear again.
This section describes the app code that has been reviewed. It cannot confirm what a hosting environment or a future integration might do.

No analytics service is configured in the current app code.
No other cookie or third-party tracking is implemented by the current app code.
Separately, app code can use sessionStorage for an enquiry-interest prefill. That is browser storage, not another cookie or an analytics service.
Browser menus differ, but their cookie or site-data settings can remove or block this site's saved choice.

Clearing or blocking cookies is controlled by your browser. The site has no separate preference centre in this draft.
The visible app code cannot establish the full behaviour of the live site, its host or services added later.

Review the hosting setup and any cookies, logs or other browser-side behaviour it may introduce; those details are not established by the app code alone.
If services are connected later, verify their actual behaviour and update this notice to match what is implemented.
The responsible operator and legal reviewer should compare the policy with verified practices before publication.
Actual hosting and any later integrations must be checked before this notice becomes final policy.