Cookie notice

No code belonging to this website writes anything to your device. Two cookies may nonetheless be placed by the provider that delivers these pages, both of them there to keep the service reachable, and both are named in the table below. That is the complete list.

There is no measurement product on these pages, no advertising, no tracking pixel, no session recorder, no heat map, no tag manager and no mechanism that would recognise you on a later visit. Because none of that is present, no permission is being sought from you and no banner appears.

One thing does reach past the page without storing anything at all. The two typefaces used here are fetched from Google's font infrastructure, which discloses your network address to a company that is not us. Nothing is written to your device by that request, but omitting it from a document with this title would be a technicality standing in for candour, so clause 6 deals with it in full.

Every item that can be written to your machine by this website appears in this one table. There is no companion table elsewhere and no category deferred to another document.

Neither cookie is legible to this company as an identifier of a person. Neither is put to any purpose beyond keeping the service available, neither is combined with anything, and neither is read by a human being.

An inventory that can only be believed is worth less than one that can be checked, and this one takes about a minute to check from where you are sitting.

• Open the storage or application panel of your browser's developer tools, look at what is listed for this origin, and compare it line by line against the table above.
• Open the network panel and reload a page. Every request the page makes is listed there, and the only destinations should be this domain and the two font hosts named in clause 6.
• Read the script itself. This site loads one file of its own, it is served from this domain, it is short, and its only job is opening and closing the navigation menu on a narrow screen.

Where what you find differs from what is written here, that is a defect worth reporting, and clause 12 says where to send it. A discrepancy would be treated as a fault in the site or in this document, not as a detail that had been quietly left out.

Australia has no dedicated cookie consent regime. There is no domestic counterpart to the European ePrivacy Directive, no statutory obligation to obtain agreement before placing a cookie, and no requirement anywhere in Australian law to display a consent banner. A banner on an Australian site is therefore a design choice, or a convention borrowed from another jurisdiction, and not compliance with anything local.

What does govern this ground is the Privacy Act 1988 (Cth). Where a cookie or a comparable technology gathers information about a person who is reasonably identifiable, that information is personal information and the Australian Privacy Principles attach to it in the ordinary way. APP 3 governs whether it may be gathered at all, APP 5 governs telling you that it was, APP 6 confines what may then be done with it, and APP 11 requires it to be kept secure and destroyed once it is spent.

So the questions that decide whether a site is behaving are whether you were told, whether the thing is genuinely needed, and whether it is used only for the stated purpose. This document answers all three in sequence. Readers in the European Economic Area or the United Kingdom are covered by a stricter regime than the one binding this company, which makes no practical difference here, since storage limited to what is strictly necessary would be exempt from a consent requirement under those regimes too.

Leaving the banner out was a decision rather than an omission, so the reasoning belongs in the open where it can be argued with.

A consent dialogue exists to obtain agreement to storage that goes beyond what a service strictly requires. Nothing of that kind runs here, which means a dialogue on these pages would be asking you to agree to an empty set. That is worse than leaving it out, for two reasons. It trains a reader to dismiss a control that genuinely matters elsewhere, one reflex click at a time. And it advertises an activity this site does not engage in, which is an odd thing to imply about yourself.

Where measurement or advertising is ever introduced here, three things happen in order. This document is amended first. Agreement is sought before the technology loads rather than while it is already running. Declining is made exactly as easy as accepting, and declining degrades nothing about the site.

The typefaces on this site are fetched from infrastructure operated by Google. The stylesheet describing them comes from fonts.googleapis.com, and the font files themselves come from fonts.gstatic.com. Those two destinations are the only hosts outside our control that any page here contacts, and being exact about what the request discloses is the point of this clause.

Making it tells Google's servers your network address, the browser string your software declares, and which page asked. Google's published position is that the font service places no cookies and that requests to it are not used for advertising or to assemble a profile. That position is theirs rather than something this company has independently established, which is why the sentence names who is making the claim.

Serving the two font files from this domain would remove the request altogether, and it is on the list of work to be done. Until then this paragraph is the accurate description rather than a gap. Blocking both hosts in your browser or in a content blocker leaves every page working normally in whatever faces your system provides, because the stylesheet names fallbacks for each of them.

Any server that answers a request writes down that it did. A document describing what reading this site involves would be answering an easier question than the one you asked if it stopped at the boundary of your own machine.

The provider delivering these pages records the network address the request came from, the moment it arrived, the path asked for, the browser string declared, any referring page, the status code returned and the number of bytes sent. None of that is written to your device, so none of it is a cookie. It is still personal information under Australian law and it belongs in an honest account.

Those logs stay with the provider on the provider's own cycle, presently under thirty days. They exist for delivering pages and for absorbing automated abuse, and for nothing beyond that. They are not exported to us, not joined to anything, and not searchable by person. Clause 4 of the privacy policy sets out the same class of item alongside its authority and its disposal date.

Every current browser can block cookies, delete whatever has already been stored, and show you exactly what a site has written. Blocking the two items in clause 2 may mean the delivery provider challenges you more often, and it will not stop these pages working.

• Chrome: open Settings and go to Privacy and security. Third party cookies governs what may be placed; Site data lists whatever already was.
• Safari: under Settings, open Privacy and choose Manage Website Data.
• Firefox: under Settings, open Privacy and Security and scroll down to the Cookies and Site Data panel.
• Edge: open Settings and go to Cookies and site permissions.

A private or incognito window discards everything when it closes, which changes very little here, given that nothing on this site persists between one visit and the next in the first place. A content blocker that also blocks the two font hosts behaves as intended and is not worked around.

Global Privacy Control, and the older Do Not Track header that preceded it, are both honoured on this site. That is an inexpensive commitment to make, because neither signal has anything here to switch off: when one arrives, no additional storage occurs and no additional processing happens, which is precisely what happens when neither does.

It is stated anyway. A site that ignores those headers while saying nothing about it has made a decision it would prefer not to be examined, and saying so plainly is worth more than an outcome that happens to be identical.

Cookies are a browser mechanism. The measurement tooling described elsewhere on this site has no browser, no session and no page, so there is nothing in its design capable of placing one.

What the tooling carries and what it refuses is set out in clause 22 of the privacy policy. Briefly, a result list is joined to judgements using identifiers rather than text, and document contents, question text, embedding vectors and credentials all sit outside the boundary by construction.

The clause appears here because a document about what this company stores would be answering a narrower question than the one a reader has in mind if it quietly confined itself to the website.

Anything that would store information on your device beyond the table in clause 2 is added to that table, with a new version and effective date, before it goes live rather than after. Where the law applying to you requires agreement first, agreement is sought first, and declining will not degrade anything on this site.

Superseded versions of this document are kept and supplied on request. If you need to know what this page said on a particular date, ask for that date rather than relying on a summary or on an archive that may have missed a revision.

Write to [email protected]. A question about this document is answered within five working days. A request under the Privacy Act 1988 (Cth) to inspect or correct personal information is answered within thirty days, and clauses 19 and 20 of the privacy policy set out how each of those runs.

Where our answer does not satisfy you, the Office of the Australian Information Commissioner takes complaints from individuals directly: GPO Box 5218, Sydney NSW 2001, telephone 1300 363 992, oaic.gov.au. Complaining costs nothing, the process is built to be used without professional help, and it does not depend on our agreement.