How to reuse our data, charts and images
Short version: the analysis and the diagrams are free to republish with a link. The underlying government data was always free. A few photographs belong to other people and carry their own terms.
Government data: Open Government Licence v3
Everything numerical on this site derives from public records — DfT STATS19 collision data, DfT road traffic estimates, police.uk street-level crime, DVSA test and MOT results, ONS population and boundaries. All of it is published under the Open Government Licence v3, which permits commercial reuse with attribution to the source. We did not create that data and we claim nothing over it.
What we add is the processing: cleaning the files, joining datasets that are published separately, normalising by exposure, and deciding what can honestly be said from the result. Our methodology sets out every rule and exclusion, and the free API names the source file behind each endpoint.
Analysis, tables, maps and diagrams
Our derived figures, rankings, tables, charts, maps and explanatory diagrams are © Crosscheck Ai Limited, and you are welcome to republish them free of charge, including commercially, on one condition: credit Swift Assist and link to the page the figure came from, not to our homepage. That link is the only thing we ask for and the only way this work pays for itself.
Attribution we ask for
Source: Swift Assist analysis of DfT data — swiftassistuk.co.uk/[the page you used]
Newsrooms, campaign groups, councils and academics do not need to ask permission. If you want a figure cut differently — by ward, corridor, junction or date range — we will usually do it free and same-day for community groups and press; see data services.
What we ask you not to do: present our derived figures as official government statistics, restate them without the caveats attached to them on the page, or republish a ranking with the reliability floors stripped out. The caveats are not decoration — they are the difference between a defensible number and a misleading one.
Images that belong to other people
Our illustrations and diagrams are our own. Photographs generally are not. Where we use a photograph taken by someone else, it is used under a Creative Commons licence that permits commercial reuse, and it is credited beneath the image with the photographer’s name and a link to the licence. Those images remain the property of their photographers, and if you reuse them you take them on their terms, not ours — share-alike licences in particular carry obligations that travel with the image.
| Image | Photographer | Licence |
|---|---|---|
| A real OBD-II socket in a car's footwell (Peugeot 208). Yours will look like this: a 16-pin trapezoid, usually below the steering column. | 0x010C | CC BY-SA 4.0 |
| The same socket in context, on a VW Golf: beside the ignition barrel with its cover flap open. This is the position and the clearance a port lock has to work around. | Filipograf | CC BY-SA 4.0 |
| A diagnostic dongle plugged into a car's OBD-II port. A thief's key programmer connects to the same socket in the same way — this is the connection a port lock physically denies. | Silicato | CC BY-SA 3.0 |
| A bar-type steering wheel lock fitted across the wheel of a right-hand-drive car in Manchester. Visible through the windscreen from outside, which is most of the point. | Mike Peel | CC BY-SA 4.0 |
| A locking wheel bolt beside its matching key adapter. The splined pattern is what an ordinary socket cannot grip — and what you cannot replace without the code card. | Raimond Spekking | CC BY-SA 4.0 |
We do not use manufacturer or retailer product photography, because those images are not licensed for reuse regardless of whether a page links to the seller. If you believe an image here is used in error, write to help@swiftassistuk.co.uk and we will remove it while we check.
Using this in a product
The API is free and open, including for commercial use, under the same attribution terms. If you are building something that depends on it, tell us at help@swiftassistuk.co.uk — not for permission, but so we warn you before a schema changes.