Flood-Net › Privacy policy

Privacy policy

Last updated 18 October 2026

What Flood-Net at floodwarning.net keeps about the people who use it, why, who else handles it, how long it stays, and how to have it removed.

Who we are

Flood-Net is an independent open-source project, run by the maintainer of cdomotor-g/MegaNet on GitHub (“we”, “us”). It is not run by the Bureau of Meteorology or any other agency. Write to privacy@floodwarning.net about anything on this page.

If you only read

A visit count

The app makes up a random number for your browser, keeps it in the browser's storage, and records against it, once a day: that it visited, which tabs it opened, and whether the screen is phone, tablet or desktop sized. Nothing in it names you unless you are signed in, when the row is linked to your account so administrators can see when it was last active; otherwise they see only totals. Rows older than 400 days are deleted. Clearing the site's data in your browser starts a new number.

Server and network logs

Like any website, the services that carry the site — Cloudflare, which serves it, and Supabase, which hosts its database — see your IP address and browser details with each request, and keep short-lived logs for security and to keep the service running. We do not combine these with anything else.

Base stations

A base station — a receiver computer that sends its readings to Flood-Net — checks in about once a minute. For each one we keep when its check-ins stopped and started again, and the network it called from shortened to its provider's block (for example 168.140.x.x), with a fingerprint that shows when the address changed. The full address is not stored. Administrators see this for the last year.

The agent API

To rate-limit the read-only API, the server hashes your IP address (with the client name you send, if any) and counts requests against the hash for a minute. The address itself is not stored.

If you make an account

Your account

Your email address; the name you give, if you give one; when the account was created, last signed in, and approved or declined, and by which administrator; and your role. Your password is never seen by Flood-Net: it goes straight to our sign-in provider, Supabase, which keeps only a salted bcrypt hash of it. For each signed-in session, Supabase also records the browser it came from and its IP address; administrators can see the browser and when the account was last active.

Your settings

The left-bar views you make, so they follow you to other devices.

What you change

When an editor saves a change to a station, inspection, survey, photo or site feature, the record notes the email address of the account that made it, and the change is kept in the record's history. Station records are public, so the address of whoever last changed a station can be read alongside it, through the app's open database. Inspections, maintenance forms and photos are visible to approved members — the people who maintain the sites, since the inspection records hold their access notes and lock codes — and surveys, site features and the station history to editors only.

Notifications, if you are an administrator

If you turn notifications on for a device, we keep that device's push address (a link at Apple's, Google's, Mozilla's or Microsoft's push service, whichever your browser uses), the two keys messages to it are encrypted with, what the device is called (such as iPhone · Home Screen), and whether the last message reached the push service. Each message is encrypted so that the push service carries it without being able to read it, and says only how many things are waiting and a base station's own name and code — never a person's name or email address. Turning notifications off, or removing the device from the list, deletes it; deleting your account deletes them all.

Emails we send

Confirmation codes, sign-in links, password resets, and notes that your account was approved. They are sent through Resend, our email provider, from noreply@floodwarning.net. We do not send newsletters or marketing.

Signing in with Google

If you choose Continue with Google, Google asks your permission to share your name, email address and profile picture with Flood-Net (the openid, email and profile scopes) — nothing else: no contacts, no files, no calendar, no Gmail. Our sign-in provider, Supabase, receives them and keeps them with your account.

• How we use it. Your email address is your identity in Flood-Net: it is what an administrator approves, what decides whether you may edit, and what is recorded against changes you make. Your name is shown to you and to administrators. The profile picture is stored by Supabase with the rest of what Google sends, but Flood-Net does not display or use it.
• Who it is shared with. Only the providers named below that run the service for us, and other users only as this page describes: your address on public station records you edit, and the part before the @ in the digital twin. We never sell it, never use it for advertising, and never use it to train AI models.
• How long. As long as you have an account. Deleting the account deletes it (see deleting your data).
• You can revoke Flood-Net's access at any time from your Google account's third-party connections page. That stops new sign-ins with Google; it does not delete the account, which you can ask us to do.

Flood-Net's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Field photos, surveys and your location

Some tools record where you are, because where a photo or a reading was taken is the point of it:

• The Field Camera writes your position, heading, height and the time into the photo, both in its file data (EXIF) and as a visible stamp. Photos you upload from elsewhere keep whatever position data the file already carries.
• Level surveys, site features and reception logs save the position you were at, or chose, with the record.
• The map's where am I dot and the AR view use your position on your device only; they do not send it anywhere.

Your browser asks before any page can use your location or camera, and you can refuse. The microphone is never used. Photos and their positions, and surveys, site features and reception logs, are visible only to approved members or editors, and each records which account added it. Photo files are stored in Cloudflare R2, or Supabase Storage, and served only through links that check you are approved.

Landholders

Flood-Net does not keep landholders' names or contact details. Who owns the land under a station, and how to reach them, is held by the Bureau of Meteorology and the councils and contractors who maintain the site. The maintenance form has no box for them, and the historical inspection records brought into Flood-Net had them removed first.

Exploring the digital twin together

While Explore together is on (it is a setting in the digital twin, on by default), other people looking at the same station's digital twin can see you there: your name, which is the part of your email address before the @ if you are signed in or a Visitor number if you are not; your avatar's colours; and where you are standing in the model, relative to the station. Nothing else is shared, and nothing is kept on our side: it passes between open pages through Supabase's realtime service and is gone when you leave. Turn the setting off to explore alone.

Ask Claude

Station Health's Ask Claude sends what the tab has worked out about the stations — readings, findings, station details such as the owning organisation and the last visit — and the questions you type, to Anthropic, whose model writes the briefing. Your name and email address are not sent with it.

• On Flood-Net's key (editors), the request passes through our server, which checks you are allowed and counts your calls against a per-minute and a daily limit. The counts are kept by email address for a minute; only the day's totals are kept longer. The request itself is not stored.
• On your own key, your browser talks to Anthropic directly, and the key never reaches our server. It is kept in your browser only if you tick the box saying the device is your own.

Anthropic's commercial terms say that what is sent through its API is not used to train its models.

Bug reports

Report a Bug fills in a new GitHub issue for you — the tab you were on, the app's version, your browser, screen size and language, and any recent errors — and opens it on GitHub, or copies it for you. Nothing is sent until you submit it yourself, and you can edit it first. GitHub issues are public, so leave out anything personal.

On your device

Flood-Net sets no tracking or advertising cookies. The only cookie is Cloudflare Access's sign-in cookie, where that gate is in use. The app does keep things in your browser's own storage, which stays on your device:

• your sign-in session, so you stay signed in until you sign out;
• the random visitor number described above, and your settings, views and preferences;
• drafts of inspection and maintenance forms you have not saved yet — which can include a council contact's name, email and phone;
• Field Camera photos and level surveys until they upload, and receptions logged by the serial monitor;
• a copy of the app, the station list and map data, so it opens with no signal.

Signing out ends the session. Clearing this site's data in your browser removes the rest — so upload or save anything you are working on first, especially on a shared computer.

Services that handle data for us

These providers run parts of Flood-Net. Each handles only what its part needs, under its own privacy policy.

Cloudflare

Serves the site and the server code, stores field photos (R2), and, where it is switched on, runs the Access sign-in gate.

Supabase

The database, sign-in and file storage. The database is in Sydney, Australia.

Google

Sign-in, if you choose Continue with Google.

Resend

Sends the account emails.

Apple, Google, Mozilla and Microsoft

Deliver an administrator's notifications, if they turn them on — whichever runs the push service of the browser they use. The messages are encrypted to the device, so the push service cannot read them.

Anthropic

Ask Claude, as described above.

GitHub

Hosts the source code and the issue tracker where bug reports go.

The maps and the tools fetch map tiles, elevation and public datasets directly from their publishers as you use them, so those services see your IP address and the area or point being looked up. They include OpenTopoMap, OpenStreetMap (map tiles, Overpass and the Nominatim place search, which also names the place where a Field Camera photo was taken), Esri, NSW Spatial Services, the Queensland Government's spatial services, the Department of Transport and Main Roads' QLDTraffic road lookup (asked who manages the road at a station or a point you pick), Geoscience Australia's elevation services, and the public terrain tiles on Amazon Web Services. Code libraries load from the unpkg and jsDelivr content networks.

Some of these providers are outside Australia, mostly in the United States, so information can be handled overseas.

Deleting your data, and your other rights

Email privacy@floodwarning.net from the address on your account to:

• get a copy of what we hold about you;
• correct it; or
• delete your account. Deleting it removes your account, your name, your settings, your notification devices and what Supabase holds about your sign-ins, within 30 days. Records you changed stay, because other people rely on them; your email address stays in their history unless you ask us to remove it, which we will do wherever it does not leave a record unaccountable.

We answer within 30 days. You can also complain to the Office of the Australian Information Commissioner, or to the data protection authority where you live.

Security

Everything travels over HTTPS. Who may read and change what is enforced inside the database, not just by the page, and the code that does it is public for anyone to check. No system is perfectly secure; if we learn of a breach that is likely to harm you, we will tell you.

Children

Flood-Net is a tool for people who work on telemetry networks. It is not meant for children, and we do not knowingly hold information about anyone under 16.

Changes to this policy

The date at the top says when this page last changed, and every change is public in the repository. If we start keeping something new about you, or using it in a new way, we will say so in the app first.