Cookie Policy
Effective date: 7 October 2026
A cookie is a small file that a website asks your browser to keep and hand back on your next visit, which is how sites remember a sign-in or a preference. Similar technologies do the same job by other means: browser storage areas that hold data locally, tiny images loaded to record that a page was opened, and scripts fetched from other companies that can observe your visit.
This page lists each of those and says plainly whether it is in use on plainmethod.online. Only one entry says it is.
What we checked
- Cookies set by this site
- Not used. The site sets no cookies of its own, for any purpose, including preferences and session identifiers.
- Cookies set by others through this site
- Not used. No third party has any code on these pages, so nobody else is in a position to set a cookie through them.
- localStorage
- Not used. Nothing is written to your browser's local storage area, which is why the checklists do not remember what you tick.
- sessionStorage
- Not used. Nothing is written for the duration of your visit either.
- IndexedDB
- Not used. The site opens no browser database.
- Tracking pixels
- Not used. There are no invisible images, beacons or counters on any page.
- Browser fingerprinting
- Not used. We do not read fonts, canvas output, device details or any similar signal to recognise a browser.
- Web fonts and third-party scripts
- Not used. The site uses the fonts already installed on your computer, and the only script it loads is our own file for the menu and the print button. No content is fetched from any other server, so a visit makes no external request at all.
- Server access logs
- Used. Our hosting provider records each request to the site, as described below. This is the only entry on this list that is in use.
Why there is no cookie banner
You have not been asked to accept anything, because there is nothing to accept. A consent banner exists to obtain permission before a cookie is set; where no cookie is set, a banner would be asking you to agree to something that is not happening. We would rather publish this page than show you an untrue dialog.
What does happen when you open a page
Your browser asks our hosting provider's server for the page, and the server writes a line in its access log. That line can include your IP address, the time, the address you asked for, the page you came from if your browser sent it, and the identifying string your browser supplies. Those logs are kept for 30 days and then deleted. They are used to keep the site running, to look into faults and to deal with abuse.
That is the entire extent of it. The Privacy Policy describes the same handling in more detail, including who the logs are visible to and how to ask about them.
The checklists do not remember your ticks
The boxes printed beside each checklist line are drawn by the stylesheet. Nothing is recorded when you mark one on paper, and nothing is stored if you reload the page. There is no localStorage, no sessionStorage, no IndexedDB, no fingerprinting and no pixel behind them. Your answers belong on your own notepad, which is also why the checklists page is built to print.
What happens after you follow an affiliate link
This course contains paid affiliate links, set out on the Affiliate Disclosure. Following one takes you to another company's website, and at that point this policy stops applying. The affiliate network that operates the link, and the vendor of the product, may set cookies or use similar technology on their own domains to record that the referral came from here. We neither control nor can inspect what they set. If that matters to you, read their own cookie notices before continuing.
Blocking or clearing cookies in general
Nothing here needs blocking, but the controls are worth knowing for the rest of the web. Every current browser has a privacy or site-data section in its settings where you can delete stored cookies, block them outright, or block only those set by sites other than the one you are on. Most also offer a private window that discards everything when it closes, and a per-site panel beside the address bar that clears what one site has stored.
If this ever changes
We do not plan to introduce cookies. If that changed, this page would be rewritten to describe each cookie, its purpose and its lifetime, and a working consent mechanism would be in place before any cookie was set — not afterwards, and not as a notice that assumes agreement. The effective date at the top would change on the same day.
Questions
Write to info@plainmethod.online. If you have inspected this site with your browser's developer tools and believe anything above is wrong, we would like to hear it.