Cookie notice

Your browser asked our host for this page and got back a file of text. It then asked for the stylesheet, the small script that opens the navigation menu on a phone, the icon in your tab, and whichever photographs appear on the page you landed on. All of those come from this domain and are just files.

That is very nearly the whole story. The rest of this page is the detail underneath it, in the order the detail happens.

No cookie was set by this site. Not a first-party cookie, not an analytics cookie, not a preference cookie, and nothing set by anybody else through us. Local storage stayed empty, session storage stayed empty, and no service worker was installed. Your browser holds no identifier that lets us recognise you the next time you visit, so as far as we are concerned every visit is the first one.

The reason is that we do not measure you. There is no analytics product on this site, no tag manager, no heat mapping, no session recording, no advertising or retargeting pixel, no embedded video player, no comment widget and no social media button that reports back. Those are the things that normally require a cookie, and none of them are here.

We would like to be precise about what that promise covers, because a claim like this is easy to make and easy to quietly break. It covers every page on this website as published today. If it ever stops being true, this page changes first, and the change will say what appeared and why.

Here is the honest exception, and it is the reason this page is longer than a single sentence. The lettering you are reading is served by Google's font service rather than from our own domain. So your browser reaches off-site twice while this page loads. Once to fonts.googleapis.com, which hands back a short stylesheet, and once to fonts.gstatic.com, which hands back the lettering itself.

Google's servers see those requests. That means they see your IP address, the browser and operating system you are using, and the fact that a request originated from a page on this domain. Google says no cookies are set on those font endpoints, and that the requests feed no advertising profile. Watching the traffic ourselves, we see nothing inconsistent with that. The requests still happen, though, and you are entitled to know it. We cannot audit what Google does with its own server logs, and we are not going to imply otherwise.

This is a genuine trade-off rather than an oversight. Serving the fonts ourselves would cut the third party out completely, and that is the first thing we would change if this page were ever tightened further. We have not made it yet.

You do not have to accept it. A content blocker that blocks third-party requests will stop the font fetch, and so will a browser setting or extension that blocks remote fonts. Nothing on this site depends on those files: the pages are plain HTML and will render in whatever typeface your device falls back to, with the layout intact and every word still readable.

If you want the belt-and-braces version, disabling JavaScript works too. The only script here toggles the navigation menu open on a narrow screen and adds a small fade as sections come into view. With it switched off, the menu links are still there and every page still works.

Having fetched the stylesheet and the images, your browser stored them locally so it does not have to fetch them again next time. We ask it to hold the stylesheet and the script for a day and the images for a month, which is why a second visit feels quicker.

That cache is a copy of public files, sitting on your own device, under your own control. It contains nothing about you, it is not readable by us, and clearing your browsing data removes it. We mention it only because a careful reader looking at what is stored after visiting a website deserves to know what those entries are.

A page cannot be delivered without knowing where to deliver it, so our host keeps the log every web server keeps: originating IP address, timestamp, which page was asked for, what code came back, and the user agent string your browser announced. That happens at the infrastructure layer, it is how a web server works, and it is not something we have switched on for our own purposes.

Those logs feed no profile, get joined to nothing, and have no report run off them. They exist for security and for diagnosing faults, they are held for a short period by the provider under its own retention schedule, and they are then discarded. Under Australian law an IP address can count as personal information, which is why the rest of that story sits in the privacy policy.

You did not get a pop-up asking you to accept anything, and that is not an omission. A consent dialogue exists to obtain permission for storage and tracking that would otherwise be unlawful or unwelcome. With no cookies to store and no tracking to run, there is nothing for such a dialogue to ask you about, and putting one up anyway would be theatre.

It would also be worse than useless. The usual banner is a small piece of software that itself sets storage in order to remember your answer, so a site with nothing to consent to that displays a consent banner has created the very thing it is asking permission for.

There are only a few realistic reasons this would change. If the application ever gets a web version, signing in would need a session cookie, which is strictly necessary for the thing you asked to do. If we ever ran a checkout on our own domain rather than through a store, that would need one too.

If we ever wanted to know how many people read the signal table, we would look for something that counts pages without identifying readers, and we would rather run nothing than run a product that profiles you. Advertising and retargeting are not on the list at all, at any point, for the same reason there is no advertising in the application.

Whichever of those happened, the order of operations is fixed: this page is updated to name the cookie, its purpose and its lifetime, before it starts being set. Anything past the strictly necessary would be put to you as a question rather than assumed, and refusing would actually refuse it.

This page is about the website. A mobile application does not use cookies in the browser sense, but it does store things on your device, and it would be a dodge to answer the narrow question and leave the broader one hanging.

When it ships, the application will keep your recordings and their analysis in its own storage on your handset, along with your settings and, if you have created one, your sign-in token. It will not read an advertising identifier, will contain no advertising or attribution components, and will not track you across other companies' apps or websites. The privacy policy covers all of it, including what Apple and Google require us to declare on their store listings.

Australia has no standalone cookie statute. What governs the position is the Privacy Act 1988 (Cth) and the Australian Privacy Principles in Schedule 1 to it, which apply whenever something stored on your device amounts to personal information about you or is used to collect it. Europe reaches a similar destination by a different road, through a rule requiring consent for storing or reading information on your device except where it is strictly necessary.

Our position happens to satisfy both without needing to work out which applies to you, because we do not store anything on your device beyond an ordinary browser cache of public files. That is a simpler thing to maintain than a consent framework, and it is a large part of why we chose it.

Do not take any of this on trust. Open the developer tools, find the storage or application panel, and read off the cookie list for this domain. It should be bare, and so should local storage and session storage. Then open the network panel and reload the page. Every request should point at this domain apart from the two font hosts named above.

If you find something on this site that contradicts this page, we would genuinely like to hear about it, and we will either remove it or document it here. That is a real invitation rather than a rhetorical one, and the address is below.

Anything on this page you want to raise goes to [email protected]. Subject lines and turnaround times are laid out on the contact page. The company is AI GOLF COACH PTY LTD, ACN 698 412 467, ABN 57 698 412 467, registered in New South Wales.

The privacy policy is the longer document, and it is where server logs, IP addresses, your recordings and everything the application does are dealt with properly.