Flood-Net › Terms of use
Terms of use
Last updated 15 October 2026
These terms cover using Flood-Net at floodwarning.net: the web application, its sign-in, and its read-only agent API. By using the site you agree to them. They are written to be read, so they are short.
Flood-Net is not a flood warning service. It does not issue warnings, forecasts or public alerts, and nothing on it is an official statement about flooding, river conditions or public safety. Readings shown here can be late, wrong or missing. Never use Flood-Net to decide whether you or anybody else is safe.
For official warnings, go to the Bureau of Meteorology and your state's emergency service. In an emergency, call 000; for flood or storm help from the SES, call 132 500.
Who runs it
Flood-Net is an independent open-source project, run by the maintainer of cdomotor-g/MegaNet on GitHub (“we”, “us”). It is not a product of, and is not endorsed by, the Bureau of Meteorology or any other agency. Contact details are at the end of this page.
Using the site
Reading needs no account: the station list, the maps and the tools are open to anyone. An account adds what is described when you create one — your own left-bar views, and, once approved, the field photos. Editing station records is limited to people an administrator has approved as editors.
The source code is MIT licensed, and you may run your own copy on those terms. These terms cover the hosted service at floodwarning.net, not your use of the code.
Your account
- Give an email address you control, and keep your password to yourself. An account is for one person.
- You can sign in with an email and password, a one-time code by email, or Google. Signing in with Google is also covered by Google's own terms.
- Approving an account, and deciding who may edit, is at the administrators' discretion. We may decline, suspend or delete an account that breaks these terms or puts the service or its data at risk.
- You can stop using Flood-Net at any time, and ask us to delete your account (see the privacy policy).
Acceptable use
Please don't:
- try to get past the sign-in, the approval step or the database's access rules, or use somebody else's account;
- interfere with the service — flooding it with requests, working around the agent API's rate limits, or probing for vulnerabilities without permission (report security problems privately, using the contact below);
- upload anything unlawful, anything you do not have the right to share, or malware;
- enter false information into station records, inspections or surveys;
- use the site to harass anyone, or collect other people's personal information from it.
What you add
You keep ownership of what you upload or type — photographs, inspection records, survey bookings, notes. You give us permission to store it, process it (for example, reading a photo's date and position, or making a thumbnail), and show it to the people the site's access rules allow, for as long as it is part of the service. You confirm that you are entitled to share it.
Site photographs show access routes, locks and sometimes people. Treat them as confidential, add only what the work needs, and avoid photographing people who have not agreed to it.
Flood-Net does not hold landholders' contact details. Who owns the land at a site, and how to reach them, stays with the Bureau of Meteorology and the councils and contractors who maintain the site. Do not put a landholder's name, phone number or email address in a form, remark, note or photo.
Changes to records are attributed to the account that made them, and kept in the record's history. See the privacy policy for who can see that.
Data from other sources
Flood-Net shows data it does not own: radio licence records from the ACMA, elevation and mapping from government and commercial providers, map tiles from OpenStreetMap and others, and telemetry from the networks themselves. That data stays subject to its owners' licences and attribution requirements, which the site credits where it is shown. It is provided as received, and may be incomplete, out of date or wrong.
The agent API
The read-only API at /api/v1 and /api/mcp is open for
scripts and AI assistants to read public station data, under the rate limits
described in its documentation.
Identify your client as that page asks, keep within the limits, and don't
present what it returns as an official warning or forecast. We may block a
client or address that misuses it.
Ask Claude
Station Health's Ask Claude briefing uses an AI model from Anthropic. Its answers are generated, can be wrong, and are a starting point for an engineer's judgement rather than a substitute for it. Use on Flood-Net's key is for approved editors and is limited per person and per day. If you use your own Anthropic key instead, that use is between you and Anthropic, under their terms and at your cost.
No guarantees
Flood-Net is provided free, as it is and as available. We work to keep it accurate and running, but we do not promise that it will be uninterrupted, error-free or suitable for any particular purpose, and we may change, suspend or stop any part of it at any time. Check anything that matters — a frequency, a position, a level — against its source before relying on it.
To the extent the law allows, we are not liable for any loss or damage arising from using the site or relying on anything shown on it, including indirect or consequential loss and loss of data. Nothing in these terms excludes, restricts or modifies any right or remedy you have under the Australian Consumer Law, or any other law, that cannot lawfully be excluded.
Changes to these terms
We may update these terms. The date at the top says when they last changed, and the history of every change is public in the repository. If a change is significant, we will say so in the app. Using the site after a change means you accept the new terms.
Governing law
These terms are governed by the laws of Queensland, Australia, and the courts of Queensland have jurisdiction over any dispute about them.
Contact
Email privacy@floodwarning.net about these terms, your account, or a security problem. For bugs and suggestions, use the app's Report a Bug button or GitHub issues — but don't put personal information in a public issue.