Authorship Certificate

If an AI detector ever flags your writing as machine-generated, the Authorship Certificate is your proof that you wrote it. As you write in Diglot, the editor quietly records how your document came together — your revisions over time, when you typed versus pasted, how much help you got from AI tools. When you need to, you turn that record into a shareable, verifiable certificate. Anyone you send it to can confirm it’s genuine, without needing a Diglot account.

This matters most for non-native English writers, who are flagged by AI detectors far more often than native speakers — even when every word is their own.

How to find it

• Open the Process Timeline panel in the editor (the shield icon in the right-hand tool rail, or press Cmd+Shift+P / Ctrl+Shift+P).
• Inside that panel, the Generate Certificate button creates the certificate. You’ll see a confirmation first, since each certificate counts toward your plan’s monthly limit.
• To verify a certificate someone sent you, open its link or scan its QR code — no account needed.

Turning it on

Authorship recording is off by default. Turn it on in Settings → Security → Authorship Protection. The first time you enable it, Diglot shows you exactly what it records and asks for your consent. From then on, your editing is captured as you work — with no slowdown in the editor.

What it records

While protection is on, Diglot tracks the kinds of signals that distinguish real human writing from text that was generated and pasted in:

• Pasting — whether text was typed or pasted, and how large each paste was. A huge block of text appearing in one instant looks very different from typing.
• Typing rhythm — natural human typing varies; perfectly even keystrokes look automated.
• Time and sessions — writing spread across several sittings is a strong human signal; everything appearing at once is not.
• Revision — how much you backspace, rewrite, and refine. Humans revise; pasted AI text usually doesn’t get edited.
• AI usage — how much of the final text came from AI tools versus your own writing.

These add up to a single “process score” and an overall verdict.

The verdict

Verdict	What it means
Green — composed primarily by hand	Your editing pattern looks consistently human: varied rhythm, realistic time spent, little AI text.
Yellow — composed with AI assistance	You used AI help and it’s honestly disclosed. The certificate still validates — it just reflects that you had assistance.
Red — AI-heavy or rapidly assembled	A large share of pasted or AI-generated text. You can see this in your own view, but a Red document can’t be issued as a certificate for others.

You can see your verdict and the reasons behind it any time in the Process Timeline panel — even before you generate a certificate.

How verification works

When you generate a certificate, Diglot seals your editing record and signs it. The certificate includes a public link and a QR code. Whoever receives it can open the link, see the writing timeline, and click Verify signature — their browser checks the signature against Diglot’s published verification key and confirms the certificate is authentic and unaltered. The certificate also carries a fingerprint of your document text, so anyone with your original file can confirm the certificate covers that exact document.

Only Diglot can issue a certificate. Anyone can verify one. Changing even a single detail breaks the verification, so a certificate can’t be forged or quietly edited.

Plans and limits

Plan	Certificates per month	Extras
Free	1	—
Spark	5	—
Pro	Unlimited	—
B2B (universities)	—	Verification API for institutions

The Process Timeline self-view (your verdict and signals) is available on any plan once Authorship Protection is enabled.

Limitations

• A certificate covers one document — generate a separate one for each.
• It documents how your writing came together; it’s user-facing proof, not a legal ruling. The certificate itself says so.
• If you turn protection off partway through a document, the certificate notes the gap — it can’t fill in what wasn’t recorded.
• Red-verdict documents can’t be issued as certificates for third parties (you can still see the verdict yourself).
• A certificate shows your writing process — it doesn’t claim to catch every possible kind of AI use.

Common questions

• Will this hold up as evidence in a school case? It’s strong, verifiable proof of how you wrote your document, designed for you to share with a professor or reviewer. It’s positioned as user-facing proof rather than formal legal evidence.
• What if I dictate or use voice-to-text? Voice input is recorded differently from a paste, so the record can distinguish dictation from pasted text.
• Can someone tamper with my certificate? No. It’s signed by Diglot, and any change to it breaks verification. Anyone can verify a certificate, but only Diglot can issue one.
• Does turning this on slow down the editor? No. Recording happens quietly in the background with no added lag.
• How is this different from Google Docs version history? Google Docs history can be deleted and edited, and only you can see it. The Authorship Certificate can’t be altered, can be verified by anyone, and includes the behavioral signals that show genuine human writing.
• How do I verify a certificate I received? Open its link or scan its QR code, then click Verify signature. Your browser confirms it’s genuine — no account required.
• What does the document fingerprint prove? It ties the certificate to one exact document. If someone has your original file, they can confirm the certificate covers precisely that text.