Current position: The website does not set non-essential cookies, write a consent preference to local storage or load advertising, behavioural profiling or third-party analytics technology. Hosting and security providers may create server-side technical logs when delivering and protecting the site.Explore this topic
1. What cookies and browser storage are
A cookie is a small text value that a website can ask a browser to store. Similar technologies include local storage, session storage, pixels and software development kits. They can support essential functions, remember preferences, measure use, personalise content or enable advertising. The effect depends on what is stored, who can access it and how it is combined with other information.
Britixo does not treat every storage technology as harmless simply because it is small. Before adding a service, the business should understand its purpose, data recipients, duration, legal basis, security and effect on user choice.
2. Cookies and browser storage currently used
The current public pages do not need a cookie banner because they do not set optional cookies or write a consent choice into browser storage. Navigation, nested menus, content disclosures, location filtering and the enquiry preparation workflow run without creating a marketing profile or a persistent visitor identifier.
This position must be checked against the deployed hosting environment. A content-delivery network, security service or future form processor may use its own technology, and any such behaviour should be documented before launch. Server-side logs are covered separately because they can exist without placing a value in the visitor's browser.
3. Technologies not currently used
The site does not currently load third-party analytics, advertising networks, social-media tracking pixels, embedded video players, live chat, heatmaps, cross-site personalisation or affiliate tracking. It does not create a marketing profile from the pages you visit. Fonts, scripts, styles and artwork are served locally so a remote font or design provider does not receive a request simply because a page is opened.
The absence of analytics means Britixo may rely on aggregate hosting information, enquiry feedback and direct usability review when improving the website. A future measurement tool should be selected only where the questions cannot be answered in a less intrusive way.
4. Hosting and security logs
Web servers and security services may create technical logs when they deliver a page. A log can include an IP address, time, requested path, browser details, response status and referrer. Logs are not necessarily cookies because they can be created on the server rather than stored in your browser.
Britixo expects those records to be used for availability, fault diagnosis, abuse prevention, incident investigation and capacity. The hosting provider, location, retention and access should be confirmed and documented before launch. Logs should not be repurposed for unrelated marketing without a separate assessment and appropriate information to visitors.
5. Managing browser controls
You can inspect or clear cookies and site data through the privacy controls in your browser. With the current Britixo website, clearing browser storage should not remove a Britixo consent preference because the public pages do not create one. Your browser may still show cached files or data created by infrastructure outside this static website, so the deployed environment should be verified.
Browser menus differ, and clearing all browsing data may remove preferences and sessions for other websites. Blocking optional storage should not stop you reading Britixo content, opening nested navigation, filtering the location directory or preparing an enquiry.
6. What happens before another tool is added
Before adding analytics, chat, embedded media, testing or marketing technology, Britixo should document the business purpose, information collected, recipients, storage duration, international access, legal basis, consent requirement and available lower-data alternatives. The privacy notice, cookie information and user interface should be updated before the new code is released.
A consent tool should not be used to create the appearance of control while non-essential technology loads before a choice. Refusing optional storage should be as clear as accepting it, and the core website should remain usable.
7. Contact
Questions about the website's storage or a technology you observe can be sent to hello@britixo.com. Include the page, approximate time, browser and a description of the behaviour. Do not send unrelated sensitive information.
See the privacy notice for information about business enquiries, hosting logs, providers, retention and individual rights.