This cookie policy explains the small data files this site stores in your browser. We use cookies sparingly — only what’s genuinely needed for the site to work or for honest first-party analytics.
What is a cookie
A cookie is a small text file a website asks your browser to remember between visits. Cookies can store things like “this visitor accepted the cookie banner” or “this visitor prefers dark mode”. They can’t access your filesystem, your other tabs, or anything outside the website that set them.
Cookies this site sets
Strictly necessary
- wordpress_logged_in_* — set when an editor logs in to the WordPress admin. Expires when the admin session ends. You’ll never see this as a visitor.
- cookie_consent — records that you dismissed the cookie banner. Expires after twelve months.
Analytics (first-party, anonymised)
- _ced_session — anonymous visit identifier so we can count unique sessions (not unique people). Reset every twenty-four hours. No cross-site tracking, no IP storage, no personally identifying data.
What we don’t use
- Google Analytics, Facebook Pixel, or any other third-party behavioural-advertising tracker.
- Session-replay tools (Hotjar, FullStory, LogRocket).
- Persistent fingerprinting.
- Ad-network cookies.
How to control cookies
You can block or delete cookies through your browser settings — every modern browser has clear controls for this. Blocking the strictly-necessary cookies will not break the site for visitors (only the admin login won’t work without them).
EU / UK / California residents: you have the right to opt out of non-essential cookies. Since the only non-essential cookie we set is anonymous first-party analytics, opting out simply means we don’t count your session in aggregates.
Changes
If we add or remove cookies, this policy is updated and the “last updated” date at the top changes. Material changes are also reflected in the cookie banner.
Contact
Questions about cookies: hello@cmsexpertdev.com. For the full data-handling picture, see the privacy policy.