Anonymous by default
For nearly everyone, a CTXR site asks for nothing: a visitor opens a link and reads. No account, no sign-up, no tracking.
What a visitor leaves behind
Nothing that identifies them. The engine sets no tracking cookies, builds no visitor profiles and calls no third party. The web server keeps its ordinary access log — a line per request, as every web server does — and that is the whole trace.
There is exactly one cookie the engine can set, and a visitor never gets it. When someone opens a preview link for a draft, a cookie holds that preview for an hour so pages and images stay in draft while they click around. It is unreadable to scripts and expires on its own.
Installing the site as an app on a phone changes none of this. The install belongs to the device, not to a person; nothing is registered anywhere.
Do I need a cookie banner?
Not for anything the engine does. The question only arises for what you add on top — an analytics script, an embedded map or video, a chat widget. Each is your decision in your templates and brings its own obligations. The engine does not force one.
The one thing a visitor can send you
A form. What a visitor types is stored in an inbox the web server never serves, and sent to you by email. That inbox is the only place personal data from visitors lands — the one place to look for your privacy statement or for someone asking what you hold. How long it stays there is yours to decide. How the form works: Forms and what your site receives. Your duties: Privacy and GDPR.
Why this matters beyond privacy
Because the default is zero, most privacy questions do not arise: no visitor database to protect, no consent to collect and store, no profile to export or delete. What remains — the inbox, the editors with keys, the history of changes — is small and sits in known places.