Cookie policy

Last updated 22 September 2026

1. Purpose of this policy

This cookie policy explains how the website at https://neuvex.live uses cookies and similar technologies. It is published by NEUVEX LTD, Unit 82a James Carter Road, Mildenhall, Bury St. Edmunds, IP28 7DE, United Kingdom. Questions about it can be sent to info@neuvex.live or made by telephone on +44 7781 492018. It should be read with the privacy policy, which describes personal data more broadly. This page is specifically about information stored on, or read from, your device when you use the site.

The site is a business website for an IT engineering and consulting company. It describes services and offers a contact form. It does not run a shop, a user account, or an advertising network. The practical consequence is that the storage we use is small and easy to describe. We would rather say plainly what is present than publish a long table of tools we do not use and then bury the real item. The sections below still explain the wider categories, because visitors often arrive with questions formed by other websites, and a useful policy answers those questions as well as listing our own practice.

2. What a cookie is, and what is similar

A cookie is a small text file, or an equivalent piece of data, that a website asks your browser to store and to send back later. Cookies can be session cookies, which the browser drops when you close it, or persistent cookies, which remain until a date written into the cookie or until you delete them. They can be first-party, set by the site you are visiting, or third-party, set by another domain, often because a page loads a resource from that domain.

Similar technologies include local storage, session storage, and pixels. Local storage is a small store that sits with the browser for a particular site. Unlike a cookie, it is not automatically attached to every request the browser makes to the server. A script on the page reads it or writes it. Session storage works in a similar way but is cleared when the tab or the browser session ends. A pixel is a tiny resource, sometimes an image, whose request tells another server that a page was opened. We do not use pixels for advertising or measurement on this site.

The law that applies to storing or gaining access to information on your device in the United Kingdom is the Privacy and Electronic Communications Regulations, usually called PECR, read with the UK GDPR and the Data Protection Act 2018 where the information is personal data. PECR requires clear information and, for storage that is not strictly necessary, consent. Strictly necessary storage is the kind of storage without which a service the user asked for cannot be provided. A preference that remembers a choice you just made about a notice can fall into a narrow band. We describe our own item below so that you can judge it, and we do not rely on a vague claim of necessity for tools we have not installed.

3. What this website actually stores

When you press Acknowledge on the notice at the foot of a page, the site writes one item into local storage. The key is neuvex-cookie. The value is the word acknowledged. The purpose is to remember that this browser has dismissed the notice, so that the notice does not cover the page on every visit. The item does not include your name, your email address, the content of a message, or an identifier that we later match to a server log. It is not transmitted as a field of the contact form.

If you do not press Acknowledge, we do not write the item. The notice stays on the page. You can still read every page and you can still use the contact form. The notice is information, not a barrier. If you clear local storage for neuvex.live, or if you use a different browser or a private window, the notice appears again, because the item is no longer there to be read.

We do not set a cookie to record that acknowledgement. We chose local storage because the item only needs to be read by the page itself, not sent to the server with each request. From your point of view the practical effect is similar to a preference cookie: a small memory of a choice, kept on your device. That is why it belongs in a cookie policy even though, strictly, it is not a cookie.

The contact form does not store your draft in a cookie. If you leave the page before sending, the browser may or may not keep what you typed, depending on its own form history. That is a feature of the browser, not a cookie we set. The form’s hidden field, which is there to catch automated submissions, is not a cookie either. It is an input on the page. You are not asked to fill it in.

4. What we do not use

We do not use analytics cookies. There is no Google Analytics tag, no Matomo cookie, no Mixpanel identifier, and no similar measurement product writing an identifier into your browser for this site. We do not count you as a member of an audience. We do not build a report of which paragraphs you hovered. If we later need aggregate traffic information, we will choose a method that does not identify visitors, or we will ask for consent before any non-essential storage, and we will update this policy.

We do not use advertising cookies. There is no retargeting pixel, no social-media advertising identifier, and no cookie that follows you from this site to other sites in order to show you an advertisement. We do not participate in a real-time bidding system. A link on a page, if it points at another site, does not by itself set a cookie of ours. If you follow a link to the Information Commissioner’s Office or to another organisation, that organisation’s policy applies from the moment you arrive there.

We do not use cookies to remember a login, because there is no login. We do not use cookies to remember a shopping basket, because there is no shop. We do not use cookies to personalise a news feed, because there is no feed. The absence of those features is a design choice of this website. It also keeps the storage story short enough to be true.

5. Categories you may have met elsewhere

Many policies divide cookies into strictly necessary, functional, analytics, and advertising. Strictly necessary cookies make a service work: a load balancer remembering which server is handling you, or a security cookie that keeps a form from being forged. Functional cookies remember choices that are convenient but not essential, such as a language. Analytics cookies measure how a site is used. Advertising cookies build or read a profile for marketing. On neuvex.live the only storage we write ourselves is the acknowledgement item described above. We class it as a functional preference for the notice. We do not class it as analytics or advertising, because it is not used for those purposes and it does not leave a trail we analyse.

A strictly necessary cookie would be one the site cannot function without. The pages of this site render without the acknowledgement item. The form submits without it. For that reason we do not call the item strictly necessary in the strong sense. We also do not hide it. The notice tells you what it does, and the button is the moment it is written. If you would rather not store it, do not press the button, or clear the item afterwards. Nothing else on the site breaks.

Some browsers and extensions offer a “block all cookies” setting, or a setting that blocks third-party cookies while allowing first-party ones. Those settings are useful on the wider web. On this site, blocking cookies will not block the local storage item, because local storage is a different store. If you want to block that as well, use the browser’s site-data controls, which are described in outline below. Blocking third-party cookies may affect the loading of fonts, which is discussed in the next section, but it will not stop the words of the page from being delivered.

6. Fonts and other requests

The pages ask your browser to load typefaces from Google Fonts so that headings can be set in Antonio, body text in Charis SIL, and small labels in Geist Mono. That request is made to Google’s servers. It is not a cookie we set, but it is a connection to another organisation, and that organisation may process the IP address and the fact that a font file was requested, under its own rules. We use the typefaces because the site is designed around them. If your browser blocks the request, the page uses fallback typefaces and remains readable. We do not receive a report of whether your browser loaded the font.

We do not embed videos, maps, or social-media timelines. Those embeds are a common way for a third party to set cookies, and they are absent here. The address of NEUVEX LTD is written as text. There is no interactive map widget. The contact details are the address, the telephone number +44 7781 492018, and the email info@neuvex.live.

7. How long the item lasts

The local storage item does not carry an expiry date of its own. It remains until you delete it, until you clear site data for this website, or until your browser removes it under its own storage policy. We do not refresh it in the background. We do not extend it when you visit another page, except that a page which finds the item present will continue to hide the notice. There is no separate server record of the moment you pressed Acknowledge. We cannot look up a list of people who dismissed the notice, because we do not keep one.

If we ever replace the item with a cookie that has a defined lifetime, this policy will state the lifetime in plain language, in months or in days, and will say whether the cookie is first-party. We will not describe a duration we have not configured.

8. How to control storage in your browser

You are in control of the device. The instructions below are a general guide. Browser makers move menus, so the labels on your version may differ slightly. The aim in each case is the same: to see site data for neuvex.live and to remove it, or to block storage before it is written.

Chrome and other Chromium browsers

Open the browser settings and look for privacy and security, then for cookies and other site data, or for site settings. You can block third-party cookies, block all cookies, or clear cookies and site data when you close the browser. To remove data for one site, open the site settings for the page, or use the lock or information icon in the address bar, and clear data for that site. Clearing data removes local storage as well as cookies. You can also use developer tools, if you are comfortable with them, and inspect the local storage entry named neuvex-cookie. Deleting that key is enough to bring the notice back.

Firefox

Open Settings, then Privacy and Security. Under cookies and site data you can delete data for individual websites, clear data when Firefox closes, or choose a stricter tracking protection setting. Enhanced tracking protection may block some third-party content. It does not, by itself, stop a site from writing its own local storage when you press a button on that site. To remove the acknowledgement, delete site data for neuvex.live. Firefox’s storage inspector, in the developer tools, will show the same key if you want to remove only that item.

Safari

On a Mac, open Safari settings and the Privacy tab. You can prevent cross-site tracking and block all cookies. Manage Website Data shows stored data by site, and you can remove neuvex.live. On an iPhone or iPad, the controls live in the system Settings app under Safari, including a control to block all cookies and a control to clear history and website data. Private browsing does not keep local storage after you close the private session. A normal tab will keep the item until you remove it.

Edge

Microsoft Edge places cookie controls under Settings, then Cookies and site permissions, then Manage and delete cookies and site data. You can block third-party cookies, see cookies and site data for a particular site, and clear them. The acknowledgement item, being local storage, appears with the site data rather than only in the cookie list. Clear the site if you want the notice to return.

Other browsers, including Brave, Vivaldi, and mobile browsers built on the same engines, follow a similar pattern: a privacy or site-settings screen, a list of sites, and a command to clear data. If you use an extension that blocks scripts, the acknowledgement button may not be able to write the item, and the notice may remain. The pages underneath remain usable. If a setting you choose stops the contact form from submitting, try the form with the extension relaxed for this site only, or email info@neuvex.live directly. We would rather receive the email than ask you to weaken a setting you rely on everywhere.

9. Do not track and global privacy control

Some browsers send a Do Not Track signal or a Global Privacy Control signal. There is no single legal switch in the United Kingdom that forces every site to interpret those signals in one specific way for all technologies. Our position is simpler than a signal parser. We do not run analytics or advertising storage, so there is no optional tracker to turn off in response to the signal. The acknowledgement item is written only when you press the button. We do not write it because a signal was absent. If a future version of the site adds an optional tool, we will treat a Global Privacy Control signal as a refusal of that optional tool, and we will say so in this policy at that time.

10. Consent, where it would matter

PECR consent, where it is required, must be a clear positive act, freely given, specific, informed, and unambiguous. A pre-ticked box is not consent. Continuing to scroll is not, by itself, consent. We do not use a banner that says the site “uses cookies” and then sets a range of advertising cookies when you arrive. The only positive act on this site is the Acknowledge button, and the only storage it triggers is the preference described in section 3. If we add a non-essential cookie later, we will ask before it is set, we will say what it is for, and we will give you a way to refuse it without losing the ability to read the site or to contact us.

You may change your mind about the preference item by deleting it, as section 8 describes. There is no account page on which to toggle it, because there is no account. Deleting the item is the whole of the withdrawal, and it is effective immediately on that browser.

11. Relationship to the contact form

Submitting the contact form is a separate act from acknowledging the notice. The form sends your name, email address, and message to NEUVEX LTD so that we can reply. That transmission is described in the privacy policy. It does not depend on the local storage item. We do not attach the acknowledgement value to the email we receive. We do not refuse the form if the notice is still visible. If validation fails, the page explains which field needs attention. That explanation is part of the page, not a cookie.

Server logs, discussed in the privacy policy, may record that a page was requested. A log line is not a cookie. It is a record on the server. We mention it here only so that the two ideas are not confused. You cannot delete a server log by clearing cookies. You can ask us about personal data in logs by using the rights described in the privacy policy, where those rights apply.

12. Changes to this policy

The date at the top of this page is the date of the current text. If we start to use a new cookie or a new store on the device, we will update this page before we rely on it, and the notice on the site will be changed so that it still describes what is true. A change that only clarifies language, without adding storage, may be made by updating the page and the date. The current policy is the one at https://neuvex.live/cookie-policy.html. Older copies are not stored as a public archive on this website.

Questions about cookies and similar storage can be sent to info@neuvex.live or posted to NEUVEX LTD, Unit 82a James Carter Road, Mildenhall, Bury St. Edmunds, IP28 7DE, United Kingdom. Please use the subject line Cookies so that the message is read against this policy. You may also read the privacy policy and the terms of service, which deal with personal data and with use of the website as a website. Client engagements are dealt with in the terms and conditions, not in this cookie policy.