Cookie Policy
Effective date: 9 October 2026
A cookie is a small piece of text a website asks your browser to store and send back on later visits, which is how a site recognises a returning visitor. Related technologies do similar jobs by other means: browser storage areas that keep data on your computer, invisible images used to register that a page was opened, and scripts loaded from someone else's server that can observe what you do.
This page says, item by item, which of those macrofacet.online uses. The short version is that the only one is the server access log, and everything else is unused.
What we checked
- Cookies set by this site
- Not used. This site sets no cookies of its own, for any purpose, including preferences and session handling.
- Cookies set by others through this site
- Not used. No third party is given a route to set a cookie here, because no third-party content is loaded on any page.
- localStorage
- Not used. Nothing is written to your browser's persistent storage area.
- sessionStorage
- Not used. Nothing is written to your browser's per-tab storage area either.
- IndexedDB
- Not used. No database is created in your browser.
- Tracking pixels
- Not used. There are no invisible images, beacons or counters on any page.
- Browser fingerprinting
- Not used. Nothing here examines your fonts, screen, hardware or configuration to build an identifier.
- Web fonts and third-party scripts
- Not used. The site uses the fonts already on your computer and one short script of our own, so your browser makes no request to any other server while reading it.
- Server access logs
- Used. Our hosting provider records each request to the site, as described below.
Why there is no banner
Consent banners exist so that you can agree, or decline, before a site stores something on your device. There is nothing here to agree to. Showing you a banner asking permission for cookies we do not set would be a false statement dressed as a courtesy, so we do not show one.
What does happen
Our hosting provider keeps an ordinary server access log. Each entry records an IP address, the date and time, the page requested, the referring page if your browser sends one, and the browser's user-agent string. Those logs are kept for 30 days and are used for site security, preventing and investigating abuse, and diagnosing faults. The Privacy Policy sets out who holds them and for how long, and that is the entire picture: logs, and nothing else.
The checklists do not remember your ticks
The boxes beside each checklist item are drawn with the stylesheet. They are not form controls and they hold no state. If you reload a step page or come back tomorrow, nothing will be marked, because remembering would mean writing to localStorage, sessionStorage or IndexedDB, and none of those are used. This is why the All checklists page offers printing instead.
After you follow an affiliate link
The course contains paid affiliate links to one game vendor. Following one takes you to a site we do not operate. That vendor, and the affiliate network that operates the link, may set cookies or use similar technology on their own domains — commonly to record which site a visitor arrived from. We do not control those cookies, cannot read them and do not receive them. Their own cookie and privacy notices are the place to find out what they set and why, and they are worth reading before you register anywhere.
Blocking or clearing cookies in general
Nothing here needs blocking, but the controls are worth knowing. Every current browser keeps them under a privacy or site-data heading in its settings, and all of them offer the same three things: a list of stored site data you can clear, a setting for refusing third-party cookies, and a private or incognito window that discards everything when you close it. Browsers rearrange these menus often, so the publisher's own help pages for your browser are a better guide than a set of steps written down here. Blocking cookies broadly can stop sites that rely on them from working; it will not affect this one.
If this ever changes
If we ever introduce a cookie or any similar storage, this page will be rewritten to describe it before the first one is set, with an updated effective date, and a working consent mechanism will be in place at the same time. We will not start storing something and document it afterwards.
Contact
Questions about this page go to info@macrofacet.online.