Your information

Privacy notice

What the enquiry form collects

The form asks for a name, email address or phone number, contact preference, property postcode, service category and a description of the enquiry. Do not include payment information or sensitive personal details.

How we handle your enquiry

A successful submission is stored for authorised team members to review. A reference is shown only after the server confirms that it has saved the enquiry. Automated confirmation emails, text messages and marketing are not enabled.

The page keeps unsent details in memory while it is open. It does not save them to browser storage or queue them for sending while offline. Closing or reloading the page clears unsent details.

Customer chat

Opening chat creates a private browser session lasting up to seven days. Its essential security cookie lets this browser return to its conversation; only a digest of that random credential is stored on the server. Clearing cookies or using another browser removes access to that conversation. The seven-day access period is not a message deletion schedule.

Sent messages and an optional name are stored for authorised owners and managers. Messages refresh while chat is open. No background push or automated message delivery is enabled. Drafts and transcripts are not saved to browser storage or queued offline. Avoid sending payment details or sensitive information.

Postcode suggestions

When you type at least three characters in the property postcode field, the postcode query is sent directly to Mapbox for UK postcode suggestions. Mapbox also receives connection information such as your IP address. Your name, email, phone number and enquiry message are not sent with this lookup. You can ignore suggestions and enter the postcode manually. Only the final postcode is included in your enquiry; map coordinates and lookup results are not saved by this application.

Read Mapbox’s privacy information.

Active visitor count

The header shows an estimate of recent activity within the last 90 seconds. To reduce inflated counts from repeated tabs or rotating identifiers, activity is grouped by network using a keyed digest of the connection address supplied by our hosting provider. This grouping changes each UTC day. Shared connections may count once, and known automated clients are excluded; this is not a count of unique people. The application stores only the keyed digest and expiry for the count, not the raw connection address, browser fingerprint, page history or a link to an enquiry or chat. Expired entries are excluded immediately and removed when the next count or heartbeat runs. No visitor history or identifier cookie is created. Security rate limits also use keyed network identifiers to reduce automated abuse.

Privacy questions

For questions about how your enquiry details or chat messages are handled, contact the team.