Cookies

Cookie Policy

This policy explains HouseDelve's cookieless analytics and the limited cookies used for security.

Our approach

HouseDelve uses Umami Cloud to understand basic use of public pages. Our integration does not set analytics cookies or store an analytics identifier in your browser, so there is no analytics cookie preference to manage.

Cookieless analytics

Analytics runs only in production and only on public pages. HouseDelve manually records pageviews and sends only the website ID, hostname, and pathname to Umami Cloud. We do not send query strings, URL fragments, page titles, referrers, custom events, or visitor identifiers of our own. Umami receives ordinary connection information, such as an IP address and browser request headers, and its tracker may keep a session cache in memory, not in cookies or local storage. Blocking the analytics script does not prevent use of HouseDelve. Umami describes its hosted service in its Cloud documentation and explains its practices in its Privacy Policy.

Necessary HouseDelve cookies

  • hd_property_report_csrf is an HttpOnly, same-site security cookie used to protect the property issue-report form. It lasts for up to 30 minutes and is removed after a successful submission.

This cookie is marked Secure in production. It is used for security, not advertising or public-site analytics.

Google reCAPTCHA

The property issue-report form uses Google reCAPTCHA to deter automated misuse. Google's official FAQ says reCAPTCHA sets the necessary _GRECAPTCHA cookie when it runs for risk analysis. Google explains its practices in its Privacy Policy and Terms of Service. It provides more detail about the cookie in the reCAPTCHA FAQ.

Changes to this policy

We may update this page if our analytics or cookie use changes. If we introduce a materially different non-essential cookie purpose, we will update this policy and request consent where required.

Last updated: 21 September 2026