Cookie Policy
Last updated: 20 July 2026
This policy explains the cookies and similar technology used on here4claims.uk. It should be read with our Privacy Notice.
What are cookies?
Cookies are small text files stored by a website in your browser. Similar technology includes server-side session records, URL campaign identifiers and local browser storage. Some are needed for security or reliable delivery; others help attribute visits or enquiries.
First-party cookies used by Here4Claims
| Cookie | Typical duration | Purpose |
|---|---|---|
here4sessid | Up to 30 days | A signed first-party identifier that remembers the original landing page, referrer and available campaign or click source so a later outbound link or callback can be attributed correctly. |
h4_visit | 7 days | Records the time of the first recent visit. It is used for visit and anti-abuse logic. |
here4_dwell_tracker | Usually 2 to 31 minutes when used | A short-lived token used only on eligible tracked journeys to confirm that a visitor remained on the intended page for the configured period. |
PHPSESSID | Browser session, only if set | Supports a server-side session where a page or security feature needs one. It was not set during the ordinary anonymous-page check used for this update. |
_lscache_vary | Varies, only if set | Helps the hosting cache deliver the appropriate version of a page. It was not set during the ordinary anonymous-page check used for this update. |
Campaign and click identifiers
Links to the site may contain identifiers such as gclid, gbraid, wbraid, fbclid or msclkid. These are URL parameters rather than cookies, but the site may record an available identifier in the signed session and referral records. When you submit the callback form, any available identifier may be sent to the secure relay with the submission so the source can be reconciled. The form does not itself place an additional advertising-platform cookie.
Google Maps on directory pages
Some solicitor directory pages contain an embedded Google Map. When the map loads, your browser connects to Google. Google can receive your IP address, browser information and the page context and may set or read its own cookies or similar identifiers. Those technologies are controlled by Google, not Latitude60 Ltd. You can read Google’s Privacy Policy.
Server-side records
The website and its technical relay also create server records that are not stored as cookies in your browser. These can include IP address, user agent, requested page, referrer, timestamps, source identifiers, security signals and callback-delivery status. The Privacy Notice explains how these records are used.
Managing cookies
here4sessid and h4_visit are currently set automatically on an ordinary first page request. You can delete or block cookies in your browser settings. Blocking all cookies may prevent some security, session or attribution functions from working as intended. Browser controls do not remove information that has already been included in a submitted callback request or a server security log.
A browser setting can also be used to block third-party content or cookies. See the Contact and Help page for the postal privacy-rights route.
Changes to this policy
This policy will be updated if the cookies, embedded services or referral technology change. The date at the top shows the latest substantive update.