The short version: this website sets no cookies. Here is exactly what it does store, and where.
That is the whole policy, and the rest of this page exists to prove it rather than to qualify it.
Most cookie policies are long because most websites carry analytics, advertising tags and embedded widgets, each dropping something on your device. This one is short because this is a static website — pre-built pages served from a file host, with no application server, no accounts and no tracking. There was never a reason to set a cookie, so we never set one.
No cookie banner, and none needed. Consent banners exist to ask permission for non-essential cookies. We set none — essential or otherwise — so there is nothing to ask you about. A banner here would be theatre.
localStorage is not oneThese get conflated constantly, including in the earlier version of this page, so it is worth separating them.
A cookie is a small value your browser stores and then automatically attaches to every subsequent request to that site. That automatic transmission is the whole point of a cookie, and it is also what makes cookies a tracking tool: the value travels to a server without you doing anything.
localStorage is a separate browser feature. It stores a value on your device and never attaches it to a request. Nothing reads it except code already running on the page, and nothing transmits it unless that code deliberately sends it somewhere. Ours does not.
The practical difference: a cookie is something your browser tells us about. localStorage is something only your own browser knows.
Exactly one value.
| Name | theme |
|---|---|
| Mechanism | localStorage — not a cookie |
| Value | light or dark |
| Purpose | Opens the site in the colour scheme you chose |
| Set when | You use the theme toggle. Never before that |
| Expires | Never on its own — it stays until you clear your browser data |
| Sent to us? | No. It is read by the page to pick a colour and goes nowhere else |
| Third-party access? | None. Browser storage is readable only by this site's own origin |
You can verify this yourself in about ten seconds. Open your browser's developer tools, go to Application → Local Storage → https://aquisontechnologies.com, and look at what is there. Then check Application → Cookies for the same origin and find it empty.
None of the following exists on this site:
Our fonts are also served from this site rather than fetched from Google Fonts, so simply loading a page makes no request to a third-party domain at all.
Our contact page embeds a Google Map showing where our office is. That map is loaded from Google, and Google may set its own cookies when it loads. We do not control those cookies, cannot read them, and receive nothing from them.
Two things limit it:
What Google does with that is covered by Google's Privacy Policy. If you would rather it never loaded, blocking third-party content for google.com in your browser or an extension will stop it, and the rest of the contact page — including the address, the phone number and the email composer — works exactly as before.
Separately, our WhatsApp button is a plain link to wa.me. It is not an embedded widget, sets nothing, and contacts Meta only if you click it.
Because the only stored value is on your own device, you are in full control of it.
To clear it: clear your browsing data for this site in your browser settings, or delete the theme key directly under Application → Local Storage in developer tools. Either way the site simply reverts to its default light appearance the next time you visit, and nothing else changes. Nothing on this site breaks — there is no session to lose and no preference that matters beyond a colour.
To block it entirely: browsers that block site data will prevent the value being stored. The site still works; it just forgets your theme choice between visits.
For cookies from embedded third-party content such as the map, your browser's third-party cookie controls are the place to manage it. Chrome, Firefox, Safari and Edge all offer this in their privacy settings, and several now block third-party cookies by default.
If we later add something that sets a cookie — analytics, or a feature that genuinely needs one — we will update this page before it ships, change the effective date and version at the top, and implement a proper consent mechanism where the law requires one. We will not quietly add tracking under a policy that says we have none.
For the wider picture of what we do and do not collect, see our Privacy Policy.
Questions about what this site stores, or found something that contradicts this page? Please tell us.