Privacy and measurement

Product measurement

We count a small set of commercial-journey steps so we can tell whether the check, checkout, report and cockpit are working. This measurement is first-party and does not use an analytics vendor.

We do not set an analytics cookie, use local or session storage, fingerprint a device, or create a persistent browser identifier. Analytics rows do not contain an address, postcode, UPRN, email, user ID, IP address, full user-agent, referrer or page URL. The stored dimensions are the event, audience mode, match state, paid product, price, coarse device class and whether the result was below band C.

Raw aggregate events are automatically removed after 400 days. Because no user or browser identifier is stored, reported conversion rates are step-count ratios and cannot be used to reconstruct an individual journey.

Property checks and reports

An address or property reference is sent to our server to find the relevant EPC record and calculate the result. It is not copied into the analytics store. A paid report stores the submitted property details, assumptions, payment state and report snapshot so the buyer can return to the purchased output.

Accounts and cockpit records

Account and session records support passwordless sign-in and report ownership. The authentication session cookie is used to provide the signed-in service. Properties, spend and evidence added to the cockpit are stored for that account. Their raw values are not included in aggregate analytics; only the add/open event and a below-C boolean may be counted.

Payments, email and quote requests

Stripe processes checkout; Resend delivers sign-in and report-recovery email when configured. A quote request is stored and routed only after the user actively agrees to share the submitted contact and property details for that purpose.

Contact

For a privacy question or data request, email [email protected].