Privacy policy
How Boundary Index Ltd. handles data on the public Boundary Index website.
Last updated: 10 May 2026
This notice covers the public website. It does not replace product account terms, account agreements, billing notices, or support processes inside the signed-in app.
What this site collects
- Consent choices, so the site can remember whether you allowed optional analytics.
- Theme preference, if you choose a light, dark, or system setting.
- Anonymous postcode-search session data used to open a postcode result and hand it from the public site to the signed-in app.
- Analytics identifiers and page events only when Umami mode is enabled for the site and your consent allows event collection.
- Contact details and message text that you choose to send to [email protected].
How we use it
We use public-site data to remember your preferences, understand whether pages are useful when analytics consent is in place, respond to enquiries, and protect the site from spam or scripted abuse.
Analytics
We do not send analytics events by default. The first-party Umami collector has to be enabled for the site, and you need to allow analytics before events are sent. You can change that choice from Cookie settings in the footer.
Product account data
Signed-in postcode search history, saved areas, support tickets, billing records, account data requests, and provider data from Google Sign-In or any other enabled social sign-in are product data. They are handled by the signed-in product and support team, not by this public website.
Account closure, account data, and deletion requests are currently handled by support. Support may need to retain billing, security, legal, or fulfilment records where those obligations apply.
Security and hosting claims
We use browser security controls and access restrictions on the public site. We only publish hosting location, subprocessor, or retention commitments after they have been verified for the relevant environment.
Rights and contact
For access, correction, deletion, account closure, consent, or privacy questions, email [email protected]. We may need enough information to verify the requester and find the relevant enquiry, account, billing, support, or provider-link record before acting on a request.