Cookies — The Honest Version
I checked. Here's what WordPress sets. That's all there is.
Last updated: April 2026
The Entire Cookie Inventory
Cookie What it does Duration Who sees it
─────────────────────────────────────────────────────────────────────────────────────
wordpress_test_cookie Checks your browser accepts cookies Session Everyone
wordpress_sec_* Authentication token Session Admin only
wordpress_logged_in_* Login state Session Admin only
wp-settings-* Interface preferences 1 year Admin only
wp-settings-time-* Preferences timestamp 1 year Admin only
PHPSESSID PHP session Session Everyone
Six cookies. All technical. All necessary for WordPress to function. None require your consent under the Garante's Provvedimento 231/2021 — Linee guida cookie e altri strumenti di tracciamento (Art. 122.1 D.Lgs. 196/2003).
If you're not logged into the WordPress admin panel, you'll only encounter two of these — wordpress_test_cookie and PHPSESSID. Both expire when you close your browser.
What's NOT Here
No analytics cookies. No _ga, no _gid, no Google anything. No Facebook pixel. No marketing cookies. No profiling cookies. No third-party cookies of any kind.
We verified this programmatically — fetched the site via API and checked every external resource loaded. Zero third-party scripts. Zero tracking. The fonts are self-hosted. The only HTTP requests your browser makes are to our WordPress server.
There is no cookie consent banner on this site because there is nothing to consent to. Technical cookies are exempt under Provvedimento 231/2021 and Art. 5(3) of the ePrivacy Directive (2002/58/EC). That's not a loophole — it's the actual rule. Official text published in Gazzetta Ufficiale n. 163, 9 July 2021. Cited under D.Lgs. 633/1941 Art. 5 (official acts of public administrations are excluded from copyright).
Managing Cookies
You can delete or block cookies in your browser settings:
- Chrome: Settings > Privacy and security > Cookies
- Firefox: Settings > Privacy & Security > Cookies and Site Data
- Safari: Preferences > Privacy > Manage Website Data
- Edge: Settings > Cookies and site permissions > Cookies
Blocking technical cookies may break WordPress functionality — login, session handling, that sort of thing. For regular visitors who aren't logging in, blocking cookies will have no noticeable effect.
Contact
Questions: archie@macrocode.ai
For data protection rights, see the Privacy Policy.
For complaints: Garante per la Protezione dei Dati Personali, Piazza Venezia 11, 00187 Roma — www.garanteprivacy.it
Live Proof
See the actual HTTP request/response (click to expand)
REQUEST
───────────────────────────────────
GET / HTTP/2
Host: www.macrocode.ai
User-Agent: Mozilla/5.0
Accept: text/html
RESPONSE
───────────────────────────────────
HTTP/1.1 200
server: aruba-proxy
content-type: text/html; charset=UTF-8
cache-control: max-age=60
set-cookie: (none)
x-powered-by: (not set)
strict-transport-security: (not set)
content-security-policy: (not set)
referrer-policy: (not set)
COOKIES SET
───────────────────────────────────
Set-Cookie: (none)
Zero cookies. Verified programmatically 2026-04-08.
Most cookie policies are 3,000 words of legal hedging about cookies the site "may" use. This one is 200 words because there are six cookies and none of them track you. Brevity is a feature.