Legal
Cookies and storage
1. The short answer
StrifePeek sets no cookies of its own. It has no analytics account, no advertising network, no social widget and no third-party tag of any kind. The site writes exactly one value into the browser's local storage, and only after a reader has pressed a button in the storage notice at the foot of the page.
2. The one key this site writes
The storage notice explains what is stored and offers two buttons. Pressing either one writes a single key, sp5_consent, into local storage so that the notice does not reappear on the next page. Accept writes the value accept; Decline writes the value decline. Nothing else changes: no script is loaded, no request is sent, and the page behaves identically either way, because there is nothing on this site that consent would switch on. The notice exists so that the storage is disclosed before it happens, not to gate content.
3. Full list
| Name | Category | Purpose | Duration | Party |
|---|---|---|---|---|
| sp5_consent | Local storage, strictly necessary | Records that the storage notice has been answered so it is not shown again | Until cleared in the browser | First party, StrifePeek |
| __cf_bm | Cookie, security | Cloudflare bot management: tells automated traffic apart from a person opening a page | About 30 minutes | Third party, Cloudflare |
| cf_clearance | Cookie, security | Written after a Cloudflare challenge page is passed, so the challenge is not repeated | Up to one year | Third party, Cloudflare |
| _cfuvid | Cookie, security | Lets Cloudflare rate limiting group requests from the same browser | Until the browser is closed | Third party, Cloudflare |
The three Cloudflare entries are listed because Cloudflare is the content delivery network in front of the site and may place them for security purposes on any site it protects. They are not configured by the operator, carry no advertising identifier and are not readable by this site's own code. Cloudflare describes them in its own cookie documentation.
4. Performance measurement by the delivery network
Cloudflare may add its own small performance script to pages it serves. It reports aggregate page-timing measurements such as Core Web Vitals, sets no cookie and identifies no individual. The operator does not install it, does not configure it and does not draw reports from it; it is mentioned here so that the list on this page is complete rather than convenient.
5. Removing what has been stored
Clearing site data for strifepeek.com in your browser removes the local-storage key and any Cloudflare cookies at once. The storage notice will then appear again on your next visit, which is the expected behaviour and not a fault. In Chrome, Edge and Firefox this is under the padlock icon in the address bar; in Safari it is under Settings, Privacy, Manage Website Data. Blocking cookies and local storage for this site entirely does not break anything: every page remains fully readable, and only the notice will keep reappearing because its answer cannot be remembered.
6. Changes and questions
If a key is ever added or removed, this table is updated on the same day and the date at the top of the page changes with it. Questions about anything listed here go to Connor MacDonald, 2232 Bloor St W, Toronto, Ontario M6S 1N6, Canada, telephone +1 416-769-9909, e-mail editors@strifepeek.com. How personal information is handled more generally is set out on the Privacy and data page.