Data attributions
How Boundary Index handles source notices for public, official, licensed, and partner data.
Last updated: 10 May 2026
Boundary Index Ltd. uses official, public, and licensed data sources in Boundary Index. This page records the public notices that apply today. Some product screens and future exports may need their own source line where the data appears.
Open Government Licence sources
Many sources are public-sector datasets licensed under the Open Government Licence v3.0. Where a publisher provides a specific attribution statement, we use that statement. Where several notices apply, this page or the relevant product screen carries the source list.
HM Land Registry Price Paid Data
Contains HM Land Registry data © Crown copyright and database right 2021. This data is licensed under the Open Government Licence v3.0. HM Land Registry notes that Price Paid Data covers England and Wales property sales lodged for registration and that third-party address rights may sit outside the OGL.
Geography, boundaries, and postcodes
Geography and boundary context may use Office for National Statistics geography products and Ordnance Survey OpenData. ONS geography products require source accreditation to ONS; some products also require OS, Royal Mail, or GeoPlace notices depending on the dataset used. We keep those year-specific notices with the output when they are needed.
OpenStreetMap-derived inputs
Where a screen uses OpenStreetMap-derived data, it should credit © OpenStreetMap contributors and link to the Open Database Licence. Map tiles or map-derived outputs may need the notice next to the map or output, not only on this page.
Other public-sector sources
Data may include Police.uk crime data, NaPTAN transport data, NHS Organisation Data Service records, Open EPC data, Food Standards Agency food hygiene data, Department for Education school performance data, Ofsted data, and ONS statistics or geography. We check each source before public reuse and keep any source-specific notice with the relevant output.
Licensed and partner data
Some coverage comes from licensed feeds, partner datasets, or contract-governed sources. We do not publish those commercial terms here, but we can answer source questions when the request has enough detail.
Coverage and corrections
For the current coverage summary, review coverage and methodology. For security, privacy, and source-claim boundaries, review security and trust.
If a public claim looks wrong, or if you need a licensing clarification for a named source, contact us with the page, output, or dataset in question. Source, licence, and correction questions can be sent to [email protected].