Last updated: 2026-11-05. Effective: 2026-11-05.
Table of Contents
The short version
Cyphlore uses a small, boring set of cookies. No advertising cookies. No cross-site tracking. No third-party marketing pixels. The cookies that exist are either functional (so the Site works) or security (so bots don’t swamp us).
Full list below.
What a cookie is
A cookie is a small text file a website asks your browser to store. It lets the site remember something small — that you’re logged in, that you just submitted a form, that Cloudflare already verified you’re not a bot. Cookies can also be used for cross-site tracking; we don’t use any that do.
Cookies set by Cyphlore
WordPress functional (only when you interact)
wordpress_test_cookie— set once to check your browser accepts cookies. Session cookie, deleted when you close the browser.comment_author_*,comment_author_email_*,comment_author_url_*— set only if you post a comment, so your name and email are prefilled next time you comment from the same browser. Expires after ~1 year. Deleting these just means you’ll re-type your name on the next comment.wp-settings-*,wp-settings-time-*— set only if you log into the admin dashboard. Expires after 1 year. Normal readers never get these.wordpress_logged_in_*,wordpress_sec_*— session cookies set only for logged-in admins. Deleted on logout.
If you never comment and never log in, Cyphlore itself sets zero cookies.
Cookies set by Cloudflare (CDN + security)
Cloudflare sits in front of the Site to serve pages fast and block abusive bots. It sets these only when its bot protection checks your browser; a normal page view sets none.
__cf_bm— Cloudflare Bot Management. Short-lived (30 min). Classifies traffic as bot vs. human. Does not identify you across sites.cf_clearance— Issued after a bot challenge if one triggers (rare for normal reading). Expires in 30 days. Tied to your challenge pass.
Cloudflare’s own cookie policy: cloudflare.com/cookie-policy.
Analytics
The Site runs no analytics script. Cloudflare’s dashboard gives us aggregate totals built from its network logs, which sets no cookie and never identifies you. There’s nothing to opt out of.
Cookies we don’t use
- Google Analytics (not installed)
- Facebook Pixel (not installed)
- TikTok Pixel (not installed)
- DoubleClick / AdSense / any ad network (not installed)
- Any cross-site tracking cookie, retargeting cookie, or data-broker tag
If an ad network cookie ever appears on Cyphlore, treat it as a bug and tell us through the contact page.
Managing cookies
Every browser lets you block or clear cookies. The relevant settings:
- Chrome — Settings → Privacy and security → Cookies and other site data
- Firefox — Settings → Privacy & Security → Cookies and Site Data
- Safari — Preferences → Privacy
- Edge — Settings → Cookies and site permissions
Blocking all cookies will not stop you from reading Cyphlore. It will stop the comment form from remembering your name, and it will keep you from logging into the admin (which you probably didn’t want to do anyway).
Changes
If we add or remove a cookie, we’ll update this page and the “Last updated” date at the top. Material changes get called out for a month.
Contact
Cookie questions: use the contact page.
— Davood Tavakoli, Cyphlore