Why so many scores moved
Loading the latest movement data…
| Borough | Score then | Score now | Change | Price then | Price now | Price ±% | 12-mo trend | Explanation |
|---|
Policy notices
- - Privacy policy s2a and s4: the optional Book a demo links open a booking page run by Calendly, a US company, which receives the name, email address and booking answer you enter (what you would like from the call, and any postcodes you add) and any guest's email address; the invitation reaches our Google calendar and the call is held on Google Meet. Used only to arrange and prepare the call, and kept for up to 12 months after it.
- - Privacy policy s2d: server logs now record the ID of the API key used for each API call (an identifier, never the key itself), so API usage can be counted. Logs that previously wrote a full postcode or a precise location when a lookup failed now keep only the district (for example SW11) and a location to about 1 km. Still no IP addresses or user agents; still deleted after 30 days.
- - Privacy policy s2b corrected: postcode lookups go to api.postcodes.io from the website as well as the native app; the section had described it as native-only.
- - Privacy policy s2a: the optional score-update email list was added, a new data type (an email address and the postcode searched), consent-based, never used for anything else.