Privacy and GDPR
Privacy is partly a property of the software and partly a set of duties on whoever runs a site. This page draws the line: what a CTXR site does by construction, and what remains yours to decide.
Who is responsible for what
Under the GDPR your organisation is the controller: you decide what data is collected and why. Whoever hosts and maintains the site for you — CTXR — is a processor, acting on your instructions.
Being the controller means a few things should be in place regardless of the software:
| Yours as controller | Why |
|---|---|
| A processing agreement with CTXR | Documents the processor relationship |
| A privacy statement on the site | Covers visits and anything a visitor sends you |
| Retention periods | How long you keep form submissions and the history of changes |
| A process for data subject requests | How you answer someone who asks what you hold on them, or asks to be removed |
| A breach procedure | Who acts, and how fast, if something leaks |
CTXR keeps the data side small: there is little to hold, so there is little to lose or hand over.
What the site holds
| About | What is held |
|---|---|
| Visitors | Nothing. No tracking cookies, no profiles, nothing shared with third parties. The only cookie is a short-lived one for someone previewing a draft; see Anonymous by default. A cookie banner is a question about what you add on top, not about the engine. |
| Form submissions | Personal data, stored in an inbox the web server never serves and forwarded to you by email. Not part of the site’s history. See Forms. |
| People with a key | No accounts. The site stores who the key belongs to (a name or address you choose) and a hash of the key — never the key itself. Remove the key and nothing is left. |
| The journal | Who changed what, in plain language, plus the full file history. This is your audit trail — and personal data about the people who work on the site. Keep that in mind when someone leaves. |
Where the data lives
A CTXR site is one folder on one server. Nothing is synced to a platform, and no central service sees all sites. You can ask in writing where the server stands and who the sub-processors are (the hosting provider and the CDN in front of it); the answer is short.
What is fully your decision is what you connect. The agent that manages your site — Claude, or another — reads your content while it works, under that provider’s terms. Any external service built into your templates sends data outward by your choice. Both fall in your column, not the engine’s.
Two more things in your column: uploaded files are public the moment they go live (Images and files), and a key acts with the rights of whoever holds it (Who can do what).
Privacy by shape
Three traits of the engine do the heavy lifting. A visitor is never identified, so for most people there is no personal data to protect. Editors are keys, not accounts, so there is no user database to breach. And the site is a folder, so “what do you hold on me” or “delete my data” means looking in two places — the inbox and the journal — rather than querying a platform.
The engine cannot decide how long you keep either. That decision, written down, is what makes you compliant.