Licensing and Use - Road Risk

Use at a glance

What this licence page means first

Educational review

Viewing, judging, and demonstrating the Road Risk project is permitted for public review and assessment.

Reuse requires permission

Code, model logic, visuals, case structures, and written project materials may not be reused without permission.

Third-party terms remain separate

External datasets, map services, APIs, packages, fonts, and references keep their own licences and attribution rules.

Rights Holder

Public-Facing Project Ownership

The public-facing rights holder for repository, website, model, and project materials is Road Risk / R.I.S.K. Project.

Road Risk / R.I.S.K. Project

No permission is granted to copy, modify, distribute, sublicense, publish, host, commercialise, reproduce, or create derivative works from the project or any substantial part of it without prior written permission from the rights holder.

Restricted-use project materials

Road Risk is provided so it can be viewed, assessed, demonstrated, and reviewed in an educational research context. That availability does not grant permission to reuse the code, case structures, model logic, interface, diagrams, written materials, or visual assets in another project, service, hosted site, commercial product, or derivative work.

Use Restrictions

What May Not Be Reused Without Permission

These restrictions apply to project-authored Road Risk materials. They do not claim ownership of third-party libraries, APIs, datasets, fonts, or referenced sources.

source code and scripts

model logic and calculation structure

user interface code and layouts

written project materials and explanatory pages

diagrams, visual assets, and project text

exported case structures and reviewed case dataset

Evidence Boundary

Reviewed Cases and Model Outputs

Reviewed case data is included as Road Risk project demonstration and research evidence only.

Third-Party Materials

External Licences Still Apply

Road Risk uses and references external tools and data sources. Those components remain governed by their own licences, terms, and attribution requirements.

Examples

OpenStreetMap and public map data
Road Safety Authority recorded-collision context and source acknowledgement where RSA-derived outputs are used
Leaflet, Next.js, React, Tailwind CSS, shadcn/ui, Radix UI, Lucide, Zod, Recharts, KaTeX, and other packages
map, routing, isochrone, font, API, and hosting providers
road-authority guidance, cited references, and external datasets

No endorsement implied

Use of Road Risk / R.I.S.K. material does not imply endorsement by any third-party service, data provider, road authority, competition, sponsor, or cited reference.

Nothing in the Road Risk restricted-use licence grants ownership of public map data, external APIs, open-source packages, fonts, services, or referenced source material.

Observed Data Attribution

RSA Recorded Collisions

RSA-derived outputs require source acknowledgement and a data-current date when they are used in App V2, exports, evidence packages, or reports.