Verified against the source code
As this website is currently built, it writes nothing into your browser and there is nothing for you to consent to.
That is a statement about the code, not a marketing position. It is also why you are not looking at a consent banner.
If a future release changes this, the change will be described here before it ships, not after.
Most cookie notices explain what cookies are and then list a dozen of them. This one skips both steps. Pages here are generated ahead of time and served as static files, and the site has no login, no basket, no personalisation and no advertising, so nothing in it needs to remember you between one page and the next. What follows describes what the browser does fetch, what two dormant integrations would add if switched on, and how you would find out.
Cookies this site sets
None. As published, abansmart.ae sets no cookies of any kind, whether strictly necessary, functional, analytical or advertising.
Concretely, and checkable by anyone reading the source: no code writes to document.cookie, no response from the site attaches a Set-Cookie header, and nothing is placed in localStorage or sessionStorage. There is no session identifier because there is no session. Because there are no non-essential cookies to refuse, there is no banner and no preference centre to maintain.
The one piece of state the site does hold is short-lived and stays inside the page. While you are filling in an enquiry form, the values you have typed and the form's progress live in the browser tab's memory. Reload the page and they are gone. Nothing is written to disk, and nothing survives closing the tab.
What your browser actually loads
Every request a page makes goes to abansmart.ae and nowhere else. There is no content delivery network domain, no font host, no tag manager, no embedded video or map, and no social widget.
- Typeface. The site uses Inter, loaded through the framework's built-in font handling. The font files are downloaded once at build time and served from this domain, so your browser makes no request to Google's font servers and Google receives no record of your visit.
- Images, icons and PDFs. All served from this domain. Manufacturer datasheets you open are files hosted here, not links out to a third party.
- Scripts. The framework's own page code, plus a small inline block of structured data that helps search engines interpret the page. Neither identifies a visitor.
- Enquiry submissions. Sent to an endpoint on this same domain. The privacy policy covers what happens to them afterwards.
Last reviewed 9 August 2026, against the code as it stands. A qualified adviser has yet to sign this text off. It describes engineering facts that can be verified, and it is not offered as legal guidance.
Third-party services and what they would add
Two optional integrations exist as configuration hooks. Neither is connected to any code in the published site, so neither runs, and neither is a cookie today. They are listed here because being open about a dormant switch is more useful than pretending it does not exist.
| Integration | Status in the published site | What enabling it would introduce |
|---|---|---|
| Visitor analytics | A configuration value sits in the example environment file. No component reads it; no analytics script appears on any page. | Depends on the tool chosen. A cookie-free product would count page views without storing an identifier. A cookie-based one would store one, and would not be enabled without detailing it here and adding a consent step first. |
| Cloudflare Turnstile bot check | Verification logic sits on the enquiry endpoint and activates only with a secret key configured. No challenge widget is rendered on any form, and the public key is read nowhere. | A script from Cloudflare's challenge service, which may set its own cookies or storage entries during bot-detection checks, as Cloudflare documents. Its purpose would be blocking form abuse, not tracking. |
One further possibility sits outside the application. Putting this site behind a content delivery network, firewall or bot-management layer would let that infrastructure set a cookie before a request ever reaches this code. Adopt that, and the table above gains a row.
Keeping this page honest
The commitment is narrow and testable. A release that introduces browser storage of any kind updates this page in the same release, moves the review date, and puts anything non-essential behind a consent choice.
Check it yourself, too. Open developer tools on any page here, compare the storage and network panels against the description above, and if the two disagree, tell us.
Frequently asked questions
Because a banner would be asking permission for something that is not happening. Consent requirements attach to storing or reading information on your device beyond what is strictly necessary, and this site does neither. Adding a banner anyway would train visitors to click through a meaningless dialogue, which makes real consent requests less effective everywhere.
Related pages
Turn your requirement into a defensible architecture
Share the workload, capacity, retention, access, and resilience requirements. Aban Smart will identify the next discovery inputs and the appropriate engagement path.