This policy describes the current Densearch.co.uk application and its free, self-hosted CookieConsent v3 consent manager. Optional event analytics is available only after affirmative consent. Events are stored by Densearch and sanitized metrics are forwarded server-to-server to Google Analytics 4 and PostHog EU. No Google or PostHog script runs in the browser. We do not use advertising, browser analytics cookies, autocapture, heatmaps or session recording. The consent manager records your choice, but it does not guarantee compliance with data-protection law or control cookies set by the hosting platform, external sites or other providers.
1. What the app uses
Public pages use the first-party consent cookie densearch_consent. It is strictly necessary for the consent manager to store your category decisions and consent metadata, including the consent revision. It expires after 180 days. The current configuration is opt-in revision 3. Revision 3 adds PostHog EU as an analytics recipient, so choices saved under an earlier revision are prompted again before any analytics is shared. Only acceptance of the analytics category enables sharing. The cookie is not used for advertising or analytics.
Administrator sign-in and dashboard pages also use Clerk’s necessary authentication cookies and storage, such as __session, to maintain and secure sign-in. These are not optional analytics cookies. Their lifetime depends on the sign-in session and provider settings. They are not needed to browse or search the public directory.
After a successful practice contact-details access request, the necessary first-party cookie densearch_phone_session remembers the practices whose contact details you have unlocked for up to 30 days. It is HTTP-only and contains a random identifier, not your name, email or phone number. It is not an analytics or advertising cookie and is set only when you request contact-details access. Clearing it removes remembered access from that browser.
Submitting a dentist enquiry sets the necessary first-party cookie densearch_enquiry_session for up to one hour to limit spam and repeated submissions. It is HTTP-only, contains a random identifier rather than your contact details, and is not used for advertising or analytics.
If you accept analytics, the app creates densearch:analytics-session in sessionStorage. It is a random anonymous identifier limited to the current tab and is deleted when consent is withdrawn. The server-side Google and PostHog EU integrations do not set analytics cookies; no PostHog browser SDK is loaded, and PostHog autocapture and session replay are disabled. The app defensively removes matching legacy _gacookies if any remain from a previous integration. No analytics identifier is stored in localStorage. Our page-loading recovery safeguard uses sessionStorage under the key dentist-finder:module-recovery. It records a path and timestamp, permits a maximum of one automatic reload per page in a 60-second window, and clears after a successful load or when the tab closes. This is operational storage, not a tracking identifier, and it is not localStorage.
Browser settings can clear cookies and session storage. Clearing the consent cookie causes the consent prompt to appear again. Blocking essential browser storage may mean that your consent choice cannot be remembered or that a failed page download cannot recover automatically, but the directory can otherwise remain usable.
2. Network requests are different from cookies
Search location, postcode and radius can be visible in the URL and browser history; query state is held in memory. Analytics never receives those query parameters or coordinates. If you grant browser geolocation permission, coordinates are sent to the API and included in the URL for your requested search. Server-side postcode lookups use Postcodes.io and cache results in memory for up to 24 hours. Mapping requests use OpenStreetMap, and Google Fonts may receive normal network metadata such as an IP address. Those map and font requests are separate from optional analytics. Google Maps and practice websites are opened only when you choose those links.
These requests can involve provider-side cookies or logs controlled by those providers. External destinations have their own cookie and privacy controls; our consent manager does not control them. Replit hosting and the application database also process application requests and reviews. See our Privacy Policy for more about these services, stored information and your rights.
3. Your choices
The consent prompt lets you accept or reject analytics. Before acceptance, no analytics script, request, identifier or analytics cookie is created. If accepted, we send text-only events for canonical public page groups, searches and care-type choices to our own analytics endpoint. Our server stores the event and forwards sanitized event metrics to GA4. PostHog EU receives only the canonical page group, anonymous current-tab session, care type and a valid outward postcode district. Analytics events never include full search text, a full postcode, raw URL, query string, coordinates, IP address, user agent or user account. Our independent first-party event records remain retained for up to 90 days; GA4 and PostHog EU retention are managed separately.
You can also refuse device-location permission and use a postcode instead. Browser settings can clear or block storage and provide controls for third-party cookies. Clearing cookies causes the consent prompt to appear again. Blocking strictly necessary storage can prevent the consent choice from being remembered and can affect module recovery.
4. Updates and contact
We will update this page if the application introduces additional cookies, providers, advertising or materially different storage. Last updated 22 September 2026 (policy revision 4).
For privacy questions, corrections, or removal requests, write to Go Lead Generation Ltd at 128 City Road, London, United Kingdom, EC1V 2NX. Please say which page or information you mean and what you want changed.
