Essential by design
The public site uses a short-lived session cookie for secure forms and does not depend on advertising cookies.
Corporate information
Cookies and local storage
The public website is designed to work with the minimum necessary browser storage. It uses an essential session cookie to protect forms and maintain security state.
No silent analytics
Optional analytics will not be introduced without an appropriate notice and consent mechanism where required.
Separate client service
The protected Client Area operates independently and may set cookies needed for authentication and billing.
01 / Corporate information
The cookie used by the public website
The Core PHP site sets an essential session cookie so it can issue and verify a security token, preserve validation messages and protect the enquiry form. The cookie is not designed to follow visitors across unrelated websites.
- Session-only lifetime unless the browser retains session state
- HttpOnly protection to prevent normal JavaScript access
- SameSite controls to reduce cross-site submission risk
- Secure transmission flag when the website is served over HTTPS
02 / Corporate information
Optional technologies and browser control
This release does not include advertising, profiling or non-essential analytics cookies. If an optional measurement service is added later, the policy and consent interface must be updated before it is activated.
- Browser settings can remove or block cookies
- Blocking the essential session cookie may prevent secure forms from working
- The Client Area has its own operational cookie requirements
- Material changes to cookie use will be described on this page
Who this information supports
Where this policy applies
The applicable order and service documents remain important where the enquiry or account relates to a purchased service.
Visitors browsing public pages
People using the enquiry form
Security-conscious users reviewing browser storage
Customers moving from the public site to the Client Area
Clear answers
Frequently asked questions
These answers explain the public policy at a practical level. Account-specific matters should use the secure Client Area.
Does the public website use advertising cookies?
No advertising or cross-site profiling cookies are included in this build.
Why is a cookie needed before I submit the form?
It allows the server to associate a unique CSRF security token and validation state with the browser session.
Is the Client Area covered by this exact cookie description?
Not necessarily. The Client Area is a separate service and uses the cookies required for secure login, account management and its own functionality.
Continue exploring
Related infrastructure and guidance
Need clarification?