Contact the RiverShot NZ editors

Last updated: April 2026

This contact page exists because rivers are communal systems, and good journalism about them should be accountable to the people who use those corridors responsibly. We read messages from readers, land managers, regional council staff, club volunteers, and scientists who can point us toward better primary sources. We prioritise corrections, safety caveats, and access context that protects both anglers and habitat.

What belongs in your message

If you are writing about a factual issue, include a link or citation to an authoritative source when you can: a council hydrology page, a DOC notice, a published monitoring dataset, or another durable reference. Screenshots help, but URLs help more because they let us verify context. If you are writing about a hazard, describe location at the resolution of a public reach or landmark, not a secret social spot. We will not publish GPS pins to sensitive areas.

If you are a manufacturer or PR representative, know that we do not guarantee coverage, and we do not accept pre-written “expert” articles. Gear requests go through the same field-testing queue as everything else. If we accept a loan unit, we disclose it on the page and return or donate the unit according to a published policy so samples do not accumulate into hidden bias.

Response expectations

We are a small team with field seasons of our own, so we cannot promise same-day replies. We aim to acknowledge safety-critical corrections quickly, even if a full rewrite takes longer. General feedback may take longer during peak runoff weeks when editors are, appropriately, away from keyboards and standing in cold water wearing questionable hats.

We do not provide personalised medical, legal, or rescue advice by email. If you are experiencing an emergency, contact local emergency services and follow the guidance of trained responders in your district.

Privacy in brief

Emailing us reveals your address to our mail client. We do not sell contact lists. For more detail, read the privacy policy. If you need postal correspondence for legal reasons, state that explicitly in your message and we will route it appropriately.

Mail form

This form uses a simulated backend response for demo mode. You will see a sending state and a success confirmation after submit.

Tip: include “Correction:” in the subject line if you are flagging a specific sentence.

Media and reprint requests

We occasionally grant reprint permission for educational non-profits and search-and-rescue training materials when attribution is clear and the excerpt does not remove safety caveats. Commercial reprints require a written agreement so context cannot be trimmed to imply endorsements we did not make. We do not authorise large language model vendors to treat our archives as a free training corpus without a contract; if you represent such a vendor, lead with licensing terms rather than a vague “partnership”.

Accessibility of this page

If the mailto workflow is inaccessible in your environment, request an alternate channel in plain text through any working email client you control, and include the same fields you would have used in the form. We will route it manually.

Harassment and abuse

We do not respond to threats, slurs, or coordinated harassment campaigns. Such messages may be blocked and retained as evidence if legally required. Constructive disagreement is welcome; dehumanising language is not.

Newsroom security

Do not send executable attachments. Do not ask editors to click suspicious short links. If you are a security researcher reporting a vulnerability, include reproduction steps and impact, and allow reasonable time before public disclosure.