Plain-language summary
Each dataset is delivered under a defined licence that lists permitted and prohibited uses. The standard licence framework focuses on testing, validation and demonstration use cases; specific datasets narrow or widen those bounds, and the listing tells you which.
This page describes the framework. The executable licence is signed at the access request step and prevails for that specific dataset.
Licence framework
All datasets share a common structure: permitted uses, prohibited uses, delivery terms, version policy and responsibility split. Reviewers can compare datasets like-for-like instead of decoding a different licence each time. Bespoke clauses, where they exist, sit on top of the shared structure — never instead of it.
Permitted uses
Default permitted uses include testing, validation, demonstration, evaluation and internal research. Training and commercial use are permitted where the specific dataset's licence allows it; the listing is the source of truth. Reviewer notes may attach to permitted uses where context requires [to confirm — reviewer-notes mechanism].
Prohibited uses
Always prohibited: automated decisions about real individuals; re-identifying or inferring identities of real people; redistribution outside the licence; any use that violates the Acceptable Use Policy. Dataset-specific prohibited uses may extend this list and are written into the dossier.
Delivery and access
Datasets are delivered via secure links bound to the approved access request. The licence covers the named licensee and the recipients the request identifies. Adding recipients later means a new request, not a new copy of the file.
Versions and changes
When a dataset is updated, the version manifest records what changed. Existing licences continue to cover the version delivered to you; material posture changes require an updated licence acknowledgement [to confirm — re-acknowledgement window].
Responsibility split
The provider is responsible for the documented origin, generation method and accuracy of the dossier as published. waiser data is responsible for the verification process and platform operation. The licensee is responsible for the use of the dataset under the licence. The executed licence sets the limits of each role [to confirm — liability caps and indemnities].