Legal
Cookie notice
Nothing gets left on your machine. Two requests still go out over the wire when you load a page, and both are named below, including the one we are not happy about.
Effective 14 August 2026Version 2.0Privacy Act 1988 (Cth)
1The short answer
- Loading a page here leaves nothing behind on your machine. No cookie, nothing in local storage, nothing in session storage.
- There is no visitor counting, no advertising, no embedded video, no chat bubble in the corner and no consent dialogue in your way.
- A one-line claim like that is worth very little on its own, so the rest of this page sets out what these pages actually do, what goes out over the wire because of it, the one outside request that gets made and why, and where the signed-in side of the product stands separately from all of that.
Rather check than take our word? Open the developer tools in your browser, load any page here, and watch the storage panel and the network panel. Storage stays empty. The network panel shows the page, one stylesheet, one script, the font files and, on some pages, a photograph or two. That is the lot.
2What a cookie is, in plain words
- A cookie is a scrap of text a site leaves with your browser, like a docket shoved in the glovebox, and picks up again next time you pull in.
- That is how a site remembers you are signed in, what is sitting in a basket, or that you already waved a message away.
- It is also how an advertising network recognises the same browser turning up on unrelated sites, which is the use that earned cookies their reputation.
- Local storage and session storage do much the same job by another route. A site that swears off cookies while writing an identifier into local storage has changed nothing that matters.
- Fingerprinting goes a step past both, assembling an identifier out of the quirks of your device without leaving anything behind at all.
- So the statement worth making is not "no cookies here". It is that no identifier is kept by any means and no fingerprint is attempted. That is the statement being made.
- Every page here is a plain file. Nothing runs behind them that could hold a session, because there is no application, no database and no account system.
| The mechanism | What it can be used for | What happens here |
|---|---|---|
| Our own cookies | Sessions, preferences, remembering a dismissed message | None written |
| Somebody else's cookies | Advertising and measurement across unrelated sites | None. Nobody else could write one, because no outside script runs on these pages |
| Local storage | Holding an identifier or a preference that outlives the tab | Never written to |
| Session storage | The same trick, for as long as the tab is open | Never written to |
| IndexedDB | Structured storage inside the browser | Unused |
| Service worker | Offline caching and background sync | None registered |
| Beacons and tracking pixels | Clocking that somebody opened a page or an email | None. There is also no bulk email in which to hide one |
| Device fingerprinting | Picking out a browser without keeping anything | Not attempted. The single script here opens the menu and fades sections in |
3What actually goes out over the wire
Keeping nothing on your machine is not the same as sending nothing anywhere. Two things genuinely travel when you load a page here, and glossing over them would be the same dodge this page exists to avoid.
Asking for the page
- Your browser asks our host for the file, and that request has to carry the address your connection is using, which page you asked for, your browser string, and the page you came from where your browser chose to pass it along.
- The host writes that into a log for a short window, as every web host on earth does, and uses it to keep the thing running and to deal with abuse.
- None of it is copied into any system of ours and none of it is analysed. We could not tell you how many people read this page last week, and that is a real cost of the design rather than an oversight.
Asking for the type
- The type these pages are set in is served by Google Fonts, so loading a page sends your browser off to fonts.googleapis.com for a short stylesheet, then to fonts.gstatic.com for the font files themselves.
- Those requests show Google the address your connection is using, your browser string, and the fact that somebody loaded a page on this domain.
- Google says the Fonts service writes no cookies and that the requests feed neither advertising nor profiling. We cannot check that from here, so treat it as their assurance and not as ours.
- What we can say for ourselves is that those requests fetch plain files, that no script of Google's runs on these pages, and that the content security policy sent with every page forbids one.
This is a genuine trade-off and it is the weakest board in an otherwise sound floor. Serving the type off our own host would kill the outside request outright, and it sits on the list of things to fix. The day that happens, this section changes with it.
Where nothing goes
- To a visitor-counting service, because there is not one.
- To an advertising network, because there is not one.
- To a social platform. No share buttons, no embedded posts, no like widgets.
- To any content delivery network beyond the host serving the site and the font service named above.
- Into a form, because there is no form. Every contact route here is a plain link that opens your own mail program, and what happens after that is between you and whoever runs your mail.
4Where the law lands, and the missing banner
- Australia has nothing that squarely matches the European requirement to get consent before putting something on a device. There is no local version of the ePrivacy Directive, and the banner on most Australian websites is either aimed at European visitors or was copied off a template.
- The law that does reach this site is the Privacy Act 1988 (Cth), and with it the Australian Privacy Principles.
- Where a cookie or an identifier amounts to personal information, meaning it is about somebody identified or somebody reasonably identifiable, then collecting it engages APP 3, telling them about it engages APP 5, and holding it engages APP 11.
- An address in a server log can be personal information in the right circumstances. That is exactly why the logs are described in section 3 instead of being brushed aside.
- Section 6D of the Privacy Act lets out most businesses turning over $3 million or less, and ANDY AI PTY LTD sits under that line. We do not lean on it, and the privacy policy works through that decision and applies the principles as though the Act binds us.
Why you were not asked to click anything
- There is nothing here for you to agree to.
- A consent dialogue on a site that keeps nothing is worse than pointless. It teaches people to click through a box that does nothing.
- It also drags an outside script onto a page that otherwise carries none, and it usually writes a cookie in order to remember you waved it away.
- A site that genuinely keeps nothing ought to look like one.
Global Privacy Control
- Some browsers send a Global Privacy Control signal, objecting to personal information being sold or traded on.
- Nothing is sold or traded from here and no advertising runs on these pages, so the signal has nothing to switch off.
- It is honoured without effort, because what it asks for is already how the site behaves.
5Doing it yourself, without our help
None of the following needs our cooperation, and all of it works whatever any website claims about itself.
- Clear cookies, or block the lot, from the privacy settings in your own browser. Nothing here breaks, because nothing here leans on one.
- Block outside font loading with a content blocker if you would rather Google's servers never saw the request. Pages fall back to Georgia and to whatever sans serif your system uses, and everything stays readable. The layout was checked that way on purpose.
- Use a private window. It changes nothing here, but it costs you nothing either.
- Switch JavaScript off. The one script here inserts the menu button and fades sections in as you scroll past them. With scripting off, the navigation list simply stays open and nothing fades. Nothing is kept out of sight on any page, in any state.
- Turn on reduced motion in your operating system, and the fade stops entirely. Content arrives at full opacity straight away.
Browser makers publish their own instructions for cookie and storage controls, and those are more current than anything we could copy across into this page. Look under privacy or content settings in your browser's preferences.
6The signed-in side of the product
A trades business running Andy signs in to manage its own account, and signing in changes the position on storage. The pages you are reading now are one thing; the fence around that sign-in is another, and it is drawn here in public rather than argued over later.
| What | What it is for | The fence |
|---|---|---|
| A session cookie | Keeping a signed-in tradesperson signed in from page to page | Strictly necessary, ours alone, marked secure and http only, and gone when the session ends unless somebody asked to stay signed in |
| A preference cookie | Holding on to a setting such as which time zone you are in | Ours alone, carrying no identifier, and written only once the choice has been made |
| Error reporting | Working out why something broke for a real customer | Rolled up where it can be. Never a session recording, and never a replay of what somebody typed |
| Product analytics | Knowing which parts of the software get used | If it happens at all: ours alone, following nobody off to another website, and listed here with the supplier named before it runs |
| Advertising or measurement tags | Nothing at all | Never. This is a subscription product, not an advertising one, and there is no business reason for a tag |
Two promises about that table
- Nothing in it gets added quietly. This page is updated before a change goes live rather than after, and the effective date at the head of it moves with it.
- No outside script goes onto these marketing pages, whatever runs behind a sign-in screen. The pages you are reading stay as they are.
7Questions and complaints
- Anything about this page goes to [email protected].
- If you reckon something here is inaccurate, that is worth telling us. It gets corrected and the effective date moves.
- This page sits alongside the privacy policy, which is the fuller document and covers personal information generally, and the terms of use.
- Where this page and the privacy policy appear to disagree, go with the privacy policy, and tell us about the gap, because it is a mistake we would want to hear about.
- Unhappy with an answer from us about privacy? Take it to the Office of the Australian Information Commissioner at GPO Box 5218, Sydney NSW 2001, on 1300 363 992, or at oaic.gov.au. It costs you nothing and you do not need us to agree to it.
- The company behind andyai.link is ANDY AI PTY LTD. Its details, and where to check them on the public registers, are on the contact page.