Data licence

Verified sustainability data on 336 independent properties, each field carrying the source it came from and the date we read it, so a claim you republish is one you can evidence. Independents are the segment certification schemes do not reach, which is where a platform sustainability filter runs thin.

Under the UK DMCC Act and the CMA supply chain guidance, repeating somebody else’s environmental claim can make you liable for it, and the evidence has to exist before the claim is published. From 27 September 2026 the EU Empowering Consumers Directive also bans sustainability labels that are not based on third party certification.

Both rules create the same requirement: somebody outside the company making the claim has to have checked it, and the check has to be evidenced and dated. We set out both rules in full, with sources, on the green claims law page.

336 published properties. An average of 6.6 of the 16 eco fields filled, median 6. 22 properties carry no score at all, because too little has been verified to place them. Counted on 8 August 2026.

Read that average before you buy. It means most records are partial: a property with four fields filled is a thinner record than one with fourteen, and the sample below contains both. We would rather you saw that now than found it yourself later. The always current figures are available as live JSON.

Every field in the eco checklist, what it holds, and where the value comes from. Fields marked as checkable against a register can be verified independently of the property. The rest are recorded as the property publishes them, which is why the source and date matter.

Each field also carries {field}_src for the URL the value came from and {field}_checked for the date we read it. Those fields exist on every record and are being backfilled, certifications first, because those are the ones a platform republishes.

Fifty real rows, behind no wall and no account. Stratified across the whole score range, so the weak records are in there by construction rather than by good intentions.

• Sample as JSON
• Sample as CSV
• Live coverage figures as JSON

• Refresh cadence. Quarterly, with certification fields re-checked on the same cycle.
• Delivery. JSON or CSV, or a read only endpoint against the live data.
• Attribution. Records carry the method version they were assessed under, so you can cite the assessment as at a fixed point.
• Corrections. Anything we correct is dated and logged in public, so a downstream record can be reconciled.

• The method is published and versioned at the Throne Standard, so it can be cited in a compliance file.
• Our commercial relationships are disclosed at independence, including a register of everyone who has paid us. Ratings are not purchasable.
• Every rating can be challenged, by anyone, through corrections.

Email info@holdthethrone.com with the territories and verticals you need, and we will come back with coverage for exactly that slice.