What Colophon actually records
Every session becomes a TWFF file: a timestamped log of a few categories of events, not a recording of keystrokes. This is the same disclosure Colophon's Chrome Web Store listing points to for what its single purpose, logging your writing process, actually collects.
Writing activity
Edits are grouped into blocks (not individual keystrokes) with a position and a short before/after snapshot; enough to reconstruct what changed, never a keystroke-by-keystroke timeline.
Pasted & external content
Pastes, cited links, and inserted images: where they landed and a short preview, not the full source.
AI interactions
Which model, what was suggested (a short preview, not the full prompt), and how much of it survived into the kept text: a similarity score, not a verdict.
Session shape
Start/end times and periodic word-count checkpoints; enough to see how a document came together over time.
What's never recorded
Individual keystrokes, full prompts or full AI outputs, screen recordings, mouse movements, biometric data, or any browsing activity outside the document you're writing.
Full field-level detail: the format is open; see the TWFF specification. For the fuller privacy picture, see our privacy architecture page.