Your content, readable and safe

Your content lives as small structured files: Schema.org JSON, the public vocabulary search engines and AI assistants already understand. A team page is a file that says it is an Organization with these employees; a news item is an Article with a headline, a date and a body. Anyone who can read JSON can read it — there is no proprietary format and nothing to convert out of.

No hidden copy

What you see is what is stored. There is no database holding a second, “real” version of your content behind the scenes, and no platform account that holds it instead. The files are the site.

History is kept for you

Every change is written to the journal — what was done, who did it, what was touched — and the whole site is kept in version history. That gives undo (any earlier state of any file), an audit trail (who changed what, from day one) and a safe copy. CTXR keeps this for you; see History and undo.

Who owns what

CTXR runs and keeps your site: the hosting, the engine and the backups are CTXR’s to maintain. Your content is yours: structured, readable, and exportable at any time through the MCP (a pack of your files). The engine that renders it stays with CTXR — that is the one real line between what you can take and what you cannot. The agent you connect works under its own provider’s terms, and what you tell it lives there too. A complete history cuts both ways: the journal names your editors, so that record is part of what is kept. See Privacy and GDPR.