Cookie Policy

• 1.1 The pages of the Site set no advertising, analytics, social media or cross-site tracking cookie.
• 1.2 The page code stores a few preferences and caches in your browser, listed below. None of them holds an identifier, and none is sent to a third party.
• 1.3 Maps, imagery and research tools request data from the open services named below when you use them. Those services receive your IP address and browser details and handle them under their own terms.

The WordPress software that publishes the Site sets cookies for signed-in editors. A feature a visitor uses that needs a cookie, such as a form, sets it for that feature only and as a strictly necessary cookie. Nothing else is stored on your device by the Site.

These requests carry no cookie from the Site, and the live water map sends no referrer. Links to other services, such as Zenodo, ORCID, DOI resolvers and social sharing, make no request until you follow them. Services that were removed from the Site are not requested.

• 4.1 Preferences and caches can be cleared at any time in your browser settings; the pages work without them.
• 4.2 Blocking the third-party hosts above in your browser leaves the text of every page readable; the maps or tools that need them show a static view or a message instead.
• 4.3 If the Site ever adds a cookie that is not strictly necessary, such as for measurement, it will ask for your consent first where the law requires it, record your choice and let you change it at any time.

• 5.1 Storage that is strictly necessary for a service you request is used without consent where the law allows, including under the ePrivacy rules of the European Union and the United Kingdom and Canadian privacy law. Anything else needs your consent.
• 5.2 Questions go to contact@therisk.global. How personal information is handled is set out in the Privacy Policy.

• GatewayGW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
• ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Nexus Reports community. Curators review it there; the DOI stays yours.
• Nexus ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.

Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.