GasSafety 247 Cookie Information for Website Visitors
Read GasSafety 247 cookie information before using this gas and heating website. Understand the published policy and where to ask about website cookies.
This notice describes the storage behaviour identified in the GasSafety 247 website implementation. Public pages provide service information and links for calling or opening WhatsApp. The current public layout does not mount the optional click-measurement component, and it does not present an active tracking-consent banner. A separate administrator session cookie supports authenticated administration. Hosting infrastructure and third-party services may have their own data handling, so the application description is not a claim that every network provider uses no cookies or logs.
Reading pages does not require an application account
The public site does not ask visitors to create a customer account before reading service pages, resources or policy information. In the implementation reviewed, the public navigation and mobile menu do not create an administrator session or save a marketing preference. You can use the services directory to choose a work category and read its scope without signing in. Website content remains distinct from the arrangements needed for an actual service enquiry.
A call link opens the visitor's calling facility
Selecting a telephone link passes the published business number to a supported dialling application. The website does not record the resulting telephone conversation through that link. Any later call handling or business record is a separate contact activity described in the privacy information. A button click is not proof that a call connected, a visit was accepted or a service was delivered.
WhatsApp opens a separate service
A WhatsApp contact link takes you to WhatsApp or its web service with a suggested enquiry message. That service has its own privacy and storage information. Read what you are about to send and remove unnecessary personal details before submitting it. Opening the link is not the same as sending the message, and GasSafety 247 does not operate WhatsApp's account, platform cookies or retention settings.
02
Administrator authentication storage
The session cookie has a restricted purpose
The Hostinger administrator login implementation uses a cookie named hostinger_admin_session after a successful administrator login. It supports the authenticated management session rather than public advertising or customer booking. The cookie is configured with Secure, HttpOnly and SameSite=Lax attributes. An ordinary visitor is not issued this administrator cookie merely because they read a public policy or service page.
Session duration depends on the configured deployment
The administrator session duration defaults to eight hours in the current server implementation. The supported configuration can change that duration, so the default is not a statement that every production session lasts exactly eight hours. Signing out instructs the browser to clear the session cookie. Closing a tab is not necessarily equivalent to an administrator sign-out and should not be described as one.
Necessary login storage differs from optional measurement
An authentication cookie serves a different function from analysing public contact-button use. Explaining that purpose does not justify adding unrelated tracking to public pages. If the administrator session is blocked or deleted, an administrator may need to sign in again; that does not turn public articles into account-only content. Private administration endpoints remain protected and are not intended as organic-search landing pages.
03
Optional measurement code and current behaviour
Available code is not an active visitor feature
The source contains an optional component for measuring contact interactions, but the public layout reviewed does not render it. Therefore this notice does not describe a working public consent banner, stored contact-measurement preference or active click counts as though visitors currently receive them. The distinction matters: the presence of a file in the codebase is different from a script actually running in the browser.
Any future activation requires a fresh notice and review
If that component is deliberately activated, its designed behaviour includes a contact-measurement preference in browser local storage and consent-aware requests containing a page path, event and placement. It is not a customer-message collection form. Before activation, the actual deployment, applicable storage rules, visitor controls and privacy wording need review together. The current upgrade does not enable it or create a new measurement category by implication.
There is no published list of verified hosting cookies here
A hosting service, reverse proxy or security layer may handle request information outside the application code. Those production-level details have not been established from this source review. Ask the business about a specific observed cookie, its name and the page where it appears. Describing uncertainty honestly is preferable to inventing cookie names, durations or a guarantee that an external hosting layer stores nothing.
04
Managing browser storage and related questions
Browser controls operate beyond this website
Most browsers provide settings to inspect, block or remove cookies and site storage. Use the controls appropriate to your browser; removing storage for one service may also affect that service's sign-in state. The website does not offer a public cookie preference panel that can alter WhatsApp's storage or the settings of an external telephone application. Do not confuse those platform controls with a GasSafety 247 booking preference.
Ask about the particular item you observed
For a storage question, give the cookie or storage key name, whether you were signed in as an administrator, and the relevant page. A screenshot of the browser storage list can help if it excludes confidential session values. Do not send an administrator session token or password. The contact page provides the business routes for asking about the website without publishing private authentication information.
Changes must be reflected in actual public behaviour
This notice should be reviewed when the site enables analytics, embeds a new third-party widget, changes authentication or adds a customer form. A statement that tracking is inactive must not remain in place after tracking is activated. The ICO's storage and access technology guidance is the authoritative reference for assessing the relevant rules; this short implementation notice is not a replacement for that assessment.
Will reading a service page create an administrator login cookie?
The administrator session cookie is issued by the login flow after successful administrator authentication. Public reading does not perform that login. If you are already signed in, the browser may retain a previously issued session independently of the public page you read.
Is there a working cookie-consent banner on the current public layout?
The optional consent component is not mounted in the public layout reviewed. This notice therefore does not instruct visitors to use a banner that is absent. Any future activation needs matching visitor controls and revised information.
Does the site currently save a contact-measurement choice for every visitor?
No active public component creates that preference in the reviewed layout. A preference name in dormant code is not evidence that all visitors have it in their browser. Actual production hosting storage should be checked separately if an unexpected item appears.
Why does WhatsApp show its own account or storage information?
The contact link opens a separate platform. Its account and browser-storage rules belong to that service, even when the link started on GasSafety 247. Review the platform's information before sending a message or changing its settings.
Can I use the public site after clearing its browser storage?
Public service information is not presented as an account-only feature. Clearing an administrator session may require another administrator login, but it should not require a customer account to read ordinary pages.
Should I send the value of a session cookie when asking a question?
Do not share session tokens or passwords. The item's name, the relevant page and whether you had signed in are normally more appropriate for an initial question. Redact confidential values from any screenshot.
Does this notice certify that the hosting provider keeps no request logs?
It does not. Application storage and hosting-level request handling are different matters, and the production provider details require confirmation. The privacy notice explains the distinction without inventing a universal no-logging claim.
When should this cookie information be updated?
Review it when a deployed feature changes storage, embeds, measurement or authentication behaviour. The wording should describe what visitors actually receive and the applicable controls, rather than what an unused source file could potentially do.