Cookie Policy

The current public website

This policy describes the local build reviewed on 27 October 2026. Public pages do not set first-party cookies or use localStorage or sessionStorage for enquiries, analytics or advertising. There are no contact forms, customer accounts, checkout, chat widgets, advertising pixels or analytics tags installed in this build. The page menus and expandable notes work without saving your answers or preferences.

Fonts, images, styles and scripts are served from the website itself. Browser caching may keep copies of these ordinary resources to improve loading; it is not used here to create an advertising identifier. The production host may add technologies that are absent locally, so the live configuration must be checked before publication and this policy updated if needed.

The optional OpenStreetMap map

The Southall map is supplied by OpenStreetMap and remains unloaded until you choose “Load Southall map”. Before that action, the map placeholder makes no request to that provider. Loading it creates an embedded frame and sends normal connection information, including your IP address and browser request details, to OpenStreetMap. No office location, business pin or device geolocation is requested.

The map choice is not stored by this site between visits. You can leave the map unloaded, call +44 20 3966 2383, or use your browser to leave the page. Provider behaviour can change; the OpenStreetMap Foundation privacy policy explains its handling of information. Third-party cookie restrictions in your browser may affect embedded content.

WordPress administration

WordPress administration is separate from ordinary public browsing. Visiting its login screen can set wordpress_test_cookie to check cookie support. Signing in can set wordpress_[hash], wordpress_sec_[hash] and wordpress_logged_in_[hash] authentication cookies. Administrative preferences may use wp-settings-[user ID] and wp-settings-time-[user ID]. These names are WordPress patterns, not cookies placed on every public visitor.

Their purpose is to provide the sign-in and administration requested by an authorised user. Authentication duration depends on the login choice and configuration; WordPress normally uses a shorter session without “Remember Me” and a longer period with it. Settings cookies can persist to remember administrative preferences. The deployed configuration should be checked before exact expiry periods are published.

Consent and your choices

No site-wide consent banner has been added to this local build because no non-exempt tracking technology is enabled on public page load. The optional map has a separate, informed loading action and is not preloaded. This assessment concerns the observed configuration, not a blanket permission to add analytics or marketing tools later.

If a new feature stores or accesses information without an applicable legal exception, it must remain blocked until valid consent is obtained. Users must be able to refuse and withdraw consent as easily as they give it. Necessary technology and any applicable exception still require clear information. See the ICO guidance on storage and access technologies.

You can inspect and remove site data in your browser settings. Blocking cookies may prevent an authorised administrator from signing in, while the ordinary public pages and telephone links remain available. Your browser may retain cache entries independently of cookies.

Questions and future changes

For questions, call the number above and ask for the person responsible for the website’s privacy information. The operator’s legal identity and privacy contact must be confirmed before launch. See the Privacy Policy for data handling and the outstanding operational details.

Adding a CDN, security service, analytics tool, booking system or different embed requires a fresh technical check. Categories, supplier names, purposes, expiry details and any consent controls must describe the technologies actually enabled, rather than a generic cookie list copied from another website.