Privacy

This page describes what a node keeps. It applies to the documentation site you are reading as well as to the caching nodes themselves.

This site

The documentation pages are static files. They set no cookies, load nothing from a third-party domain and run no analytics or tracking script. Nothing about your visit is written to a request log.

Caching nodes

A node keeps aggregate counters only: request count, hit ratio and bytes served, per zone and per hour. These counters contain no addresses, no URLs and no headers.

Per-request logging is off by default. An operator may enable it on one zone while investigating a specific fault; when enabled it records the timestamp, the request path, the status code and the X-Cache value, and it is switched off and deleted once the investigation ends.

What is never stored

• Request or response bodies beyond the cached object itself.
• Authorization headers and cookies — responses that depend on them are not stored at all.
• Anything derived from a visitor across two different zones.

Retention

Aggregate counters are kept for 30 days and then dropped. Cached objects live no longer than their TTL, at most 31 days, and are removed immediately on purge.

Requests

Because no per-visitor record is normally created, there is usually nothing to export or erase on request. Correspondence sent to the operator is kept until the matter is closed.