WEBSITE INFORMATION · UPDATED 28 OCTOBER 2026
Cookie Policy
Cookies store information in a browser. Similar rules can also apply to other device storage. This notice describes what was found in the current anonymous Ruislip pages and distinguishes that from WordPress administration and from a separate visit to an external website.
Legal review before public launch
Review required before public launch. This inventory describes the inspected local build, not future hosting or integrations. Recheck the live site and provider behaviour before relying on this as a final public notice.
What the public pages currently use
The audit inspected anonymous HTTP responses and the JavaScript delivered by the public site. No first-party Set-Cookie response, cookie-writing code, localStorage or sessionStorage use was found in the inspected build. There are no analytics, advertising, call-tracking, chat or newsletter scripts on these public pages.
The table records the actual inspected categories rather than importing a generic list of cookies. It is not an inventory of cookies already stored in an individual visitor’s browser by other websites or by a previous administrator login.
| Feature | Cookie or storage finding | Purpose and duration |
|---|---|---|
| Ruislip public page delivery | No first-party cookie or browser-storage setter observed | Page display; no cookie duration to list |
| Analytics and advertising | No scripts or associated cookies identified | Not implemented |
| Contact map load/hide choice | No cookie, localStorage or sessionStorage | In-memory control for the current page visit |
| Selected OpenStreetMap static embed | No Set-Cookie header or storage-writing marker observed in inspected resources | External map requests still involve provider-side network processing |
| WordPress administration | Separate from the anonymous-page audit | Login and editing behaviour depends on the requested administrator session |
External maps and your choice
The Contact Us map does not connect to OpenStreetMap until you select Load interactive map. You can select Hide map afterwards to remove that embed from the page. This choice is kept only in page memory: it does not set a preference cookie or use browser storage. Returning to the Contact page starts with the map unloaded again.
The existing homepage has a lazy-loaded OpenStreetMap embed. It can connect when its map section approaches the viewport. The inspected static embed response did not set a cookie, and its delivered script contained no cookie or storage-writing markers. That finding does not establish that every service offered by the map provider is cookie-free.
Loading a map still sends ordinary network information, such as an IP address and browser request details, to the external provider. Hiding an already loaded Contact map stops that embed making further requests; it does not undo information already received or clear cookies that a provider may have set in a separate visit. Opening the full map website is governed by that website’s own controls and privacy notice.
Consent and withdrawal
There is no Accept all marketing-cookies banner because no marketing or analytics cookies were identified in this build. Continuing to browse is not treated as consent to add tracking. The explicit Contact map controls manage that optional external connection; they are not an agreement to unrelated processing or to this website’s service terms.
There are currently no saved optional tracking preferences to withdraw. Use Hide map to remove the Contact embed during the visit. If non-essential storage or tracking is added later, it must be assessed and an appropriate choice and withdrawal mechanism implemented before it is used. This notice must then be updated to name the actual technologies, purposes and durations.
WordPress administration is separate
Public browsing does not require an account. Choosing to use the WordPress login or editor can involve WordPress authentication, test or settings cookies. Those are part of the administrator’s requested session and were not observed as cookies set by anonymous homepage browsing. The site does not display a public registration or customer login feature.
No custom authentication-cookie duration or identifier is asserted in this public-page inventory. Administrative behaviour should be reviewed separately if account access is made available to customers or additional plugins are installed.
Browser controls and questions
Your browser can show, block and delete cookies and other site data. Removing data created by a logged-in administration session can sign that administrator out. Blocking third-party content can prevent an embedded map from displaying, while the telephone contact and service text remain available.
For questions about the Ruislip website, call +44 20 3966 2607 and ask for the responsible operator and privacy contact. See the Privacy Policy for information handling and the outstanding business details. This technical inventory was checked on the live website on 28 October 2026. Changes to hosting, scripts or embeds require a fresh check.