Provenance receipts for written work
Document the process.Defend the work.
DraftProof records how a document was actually produced and creates a signed, shareable receipt before questions about authorship begin.
Free authoring plugin planned for Google Docs, Word, and VS Code.
Receipt verified
Writing process receipt
Session
02h 41m
Revisions
147
Paste events
03
This receipt documents captured activity. It does not prove authorship or rule out all spoofing.
Built for the accused
Evidence without the false certainty of a detector score.
Visible by design
A receipt says what was captured, what it means, and what it cannot establish.
Readable by recipients
No black-box verdicts. Just a neutral record that travels with the submitted work.
The receipt model
One document trail. Three deliberate stages.
Capture only what supports a fair conversation, sign the record, then make its strengths and limits easy to understand.
- 01
Record the session
DraftProof observes revision cadence, paste events, editor context, and disclosed AI-assist calls while you write in supported editors.
- 02
Seal the receipt
A signed summary turns captured events into a readable process record without publishing the writing itself.
- 03
Share with context
Attach one verification link to an assignment, application, article, or client delivery. Recipients can open it free.
For the person submitting
Keep a process trail before your work is questioned.
Students, freelance writers, and applicants can share the same neutral record. Recipients view it free, with caveats and verification details always attached.
Clear answers
What a receipt can—and cannot—say.
Early access
Help test whether process receipts earn trust.
Join the waitlist to test DraftProof, challenge its assumptions, and help shape a receipt recipients can interpret responsibly.