Cookie policy
This site sets no cookies. That is the whole policy; the rest of the page explains what it means and how you can confirm it.
What a cookie is
A cookie is a small piece of text that a website asks your browser to store and then send back on later requests, which is how a site recognises a returning visitor or keeps you signed in. Cookies can also be set by third parties whose code is embedded in a page — advertising networks and analytics providers being the usual examples — which is how browsing gets tracked across different sites.
What this site does
threat-guard.site sets no cookies of its own, and allows no third party to set any through it. There are no analytics cookies, no advertising or retargeting cookies, no conversion or tracking pixels, no social media embeds, no session identifiers, and no preference cookies. Not one cookie is named in this policy because there is not one to name.
The reason there is no consent banner on this site is straightforward: there is nothing to consent to. A banner asking permission for cookies on a site that sets none would be a statement about this site that is not true, and we would rather the absence be genuine than performed.
Nothing is stored in your browser either
Cookies are not the only way a site can keep data on your device. For completeness: this site uses no localStorage, no sessionStorage, no IndexedDB, and no browser fingerprinting of any kind — no canvas, font or device enumeration to identify you without a stored identifier.
The site loads no third-party scripts at all, including no externally hosted fonts, no content delivery network libraries, and no embedded video or maps. Everything the page needs comes from this domain: one stylesheet, one small JavaScript file, and pages made of text. That script opens the mobile menu, marks the current page in the navigation and expands answer panels; it records nothing and sends nothing anywhere.
What is recorded instead
The hosting provider serving these pages keeps ordinary web server logs, as effectively every web server does. A log entry contains the IP address the request came from, the date and time, which page was requested, the status returned, and the browser's user agent string. These logs exist for security and diagnostics, are retained for a limited period, and are described in full in the privacy policy. They are not cookies: nothing is stored on your device and nothing follows you to other sites.
How to check for yourself
This claim is one you can verify rather than take on trust, which is rather the point of making it. In any current desktop browser, open the developer tools with F12, go to the storage or application section, and look at the cookies and storage entries for this domain. They will be empty. The network tab will show requests to this domain only.
Blocking or clearing cookies generally
Nothing here needs blocking, but you may want to manage cookies elsewhere. Every major browser lets you view and delete stored cookies, block third-party cookies, block cookies from specific sites, or clear everything when the browser closes; the controls sit in the privacy or site-data section of the browser's settings, and the browser's own help pages describe the current location. Blocking cookies broadly will sign you out of sites that rely on them, which is the trade-off to be aware of. Nothing on this site will stop working, because nothing here depends on them.
Following a link away from this site
Links from these pages to other websites — the Australian government services referenced throughout, and the one paid link described on the affiliate disclosure page — lead to sites operated by other organisations, which set their own cookies and publish their own policies. This policy covers only threat-guard.site. That affiliate link does carry a tracking identifier in its address, which is how the vendor attributes a sign-up to this site; that attribution happens on the vendor's systems under the vendor's policy, and no cookie is set by us at any point.
If this ever changes
We consider a no-cookie site worth keeping. If that position ever changes, the sequence will be: this page updated to describe precisely what is set and why, a working consent mechanism in place, and only then anything set at all. No cookie will be placed on a reader's device before both of those exist.
Questions about this policy can go to info@threat-guard.site.