Privacy
publicdata.au has no accounts and sets no cookies. Nobody is asked who they are, on the pages, in the query API or through the MCP server. The site is run by National Digital.
Page views
Cloudflare Web Analytics counts page views. It is served from this site's own provider, stores nothing in the browser and does not follow anyone across sites. There is no other tracking.
Cloudflare keeps every page view's beacon data for 7 days, then about one in ten of them, and the site can read those for six months.
Votes and dataset requests
A vote is stored under a salted hash of the date, the dataset, the address and the browser's user agent, so each browser counts once a day for each dataset. Because the date and the dataset are in the hash, the stored votes cannot show, without the salt, that two votes on different days or for different datasets came from the same browser. Only the total for each dataset is published.
A vote holds the dataset, the date and the hash, and the store records the time it was written. It does not hold the address or the user agent, and without the salt the hash cannot be turned back into them. Votes are kept indefinitely. The salt is a secret held in the site's hosting settings, outside the store that holds the votes, so someone with the store alone cannot test an address or a user agent against a vote. Someone with both the salt and the store could check whether a browser whose address and user agent they knew voted for a dataset on a given day. They could also find the address behind a vote by trying every IPv4 address with common user agents. Votes cast before the salt moved out of the store were hashed with an earlier salt kept in the store, and anyone with the store could test those votes in the same way while that earlier salt remains. The earlier salt is deleted when the site moves to the new one. If the salt is ever missing, the site records no votes and saves no dashboards. A vote withdrawn on the day it was cast is deleted. On the day the salt is set or changed, a vote cast earlier that day cannot be withdrawn, and the same browser can vote again that day.
A link pasted into the backlog is looked up in the catalogue and is not stored. When it names a dataset there, it counts as a vote for that dataset in the same way. When it does not, the page suggests sending it to National Digital, which is up to you.
Saved dashboards
Saving a dashboard in the explorer stores the dataset, the version and the dashboard's layout, including any titles or filter values typed into it, with the time it was saved. Anyone with its link can open it. A saved dashboard is kept indefinitely so that its link keeps working. To ask for one to be removed, send its link to National Digital through its contact page. A browser that opened it before it was removed may keep its own copy for up to a year.
To limit how many dashboards one browser can save in a day, each save also leaves a note that holds the date, the dashboard's id and a salted hash of the date, the address and the user agent, made like a vote's hash with no dataset, and the store records when it was written. The note therefore links that day's hash to the dashboards saved under it. Like a vote, it does not hold the address or the user agent, and without the salt the hash cannot be turned back into them. The salt is the same secret, held outside the store. Someone with both the salt and the store could check which dashboards a browser whose address and user agent they knew saved that day, or find the address behind a note by trying every IPv4 address with common user agents. Someone with the store alone could do neither, except for notes saved before the salt moved out of the store, which can be tested in the same way while the earlier salt remains. The notes are kept indefinitely.
Maps
A map panel in the explorer or in an embedded dashboard draws its background from OpenStreetMap's tile servers at tile.openstreetmap.org. While one is on screen, the browser asks those servers for tiles, so OpenStreetMap receives the browser's address and user agent and can tell the request came from publicdata.au. The OpenStreetMap Foundation privacy policy covers what it receives and states no period for keeping tile requests. Apart from these tiles and Cloudflare, no page loads anything from another party.
The query API and the MCP server
The query API answers from the data and records nothing about who asked. The MCP server logs the methods, tools and client software of each request, and leaves out the address and the arguments' values. To keep the rate limit, it counts row tool calls per address in Cloudflare's cache for 10 seconds.
The catalogue search, the dataset search and the backlog's link lookup share the MCP server's limit, and each counts requests per address in Cloudflare's cache for 10 seconds. The query API's own rate limit is a Cloudflare rule that also counts requests per address.
The MCP server writes one line for each request to the log of the site's functions, which Cloudflare shows live and does not store, so that a maintainer watching it can count how the server is used. The line holds the HTTP method and status, the MCP protocol version, whether a session id was sent and whether the request was a batch. It counts the calls by method, tool and prompt, gives the names of the arguments each tool or prompt was sent and counts the errors by kind. It names the client software and its version number when the client is on the server's list of known clients, and the product in the user agent when it is on a separate list of known agents. Any other name is written as "other". It also notes when a client came through the mcp-remote proxy. It marks the request as a client's or as a probe by a scanner. It never holds the address, the session id or the values of the arguments, so a question asked through the server is not kept. Of the request's headers, the line reads only the user agent, the protocol version and whether a session id was sent, and keeps only what is described here.
Hosting
Cloudflare hosts the site and handles every request, including the address it came from, to deliver it and to block abuse. Cloudflare also keeps data from that traffic for its own purposes, as the Cloudflare privacy policy describes. That policy says Cloudflare keeps personal information for as long as its business purposes need, or as long as the law requires, and then deletes it.
Cloudflare shows the site records of its traffic and of the requests its security rules acted on, and these can include a request's address. The site can see them for 31 days.
The site's functions write a log as they run, and Cloudflare Pages keeps no copy of it. A maintainer can watch it live, and the live view shows each request's headers, including the address it came from. The site sends Cloudflare's logs nowhere.
Contact
Questions about privacy go to National Digital through its contact page. Security reports go to the address in /.well-known/security.txt.