Authorship Certificate

An Authorship Certificate is a signed record of the writing activity Diglot captured for one document. As you write, it records events such as revisions, typed and pasted text, and use of Diglot AI tools. You can turn that record into a shareable certificate; anyone with the link can verify that the signed certificate has not been changed, without 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. Issuing a certificate is free and unlimited on every plan, Free included.
• 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 captured text was typed or pasted, and the size of each paste.
• Typing rhythm — timing patterns in captured keyboard events.
• Time and sessions — the period and sessions represented in the event chain.
• Revision — captured editing and replacement activity.
• AI usage — the share of final text attributed to Diglot AI tools where that source is known.

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

The verdict

Verdict	What it means
Green	The captured process met Diglot’s highest process-fidelity tier. It is not a finding by a school or an independent determination of authorship.
Yellow	The captured process contains material limitations or assistance that the certificate discloses.
Red	The captured process does not meet Diglot’s threshold for a shareable certificate. You can see the reasons privately, but cannot issue it.

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

Issuing a certificate is free and unlimited on every plan, Free included, and verifying one is free for everyone with no account. Certificates are never part of the price.

Plan	Certificates	Extras
Free	Unlimited	—
Spark	Unlimited	—
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 only the activity Diglot captured; it cannot establish what happened outside Diglot or independently prove who authored every word.
• If you turn protection on after text already exists, that pre-existing text is disclosed as not covered by the recorded process.
• A school, instructor, scholarship provider, publisher or other recipient decides whether it accepts this record. Check its current policy before sharing it.
• 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 my school accept it? Acceptance is decided by the school, instructor or programme. The certificate can give a recipient a verifiable record of captured Diglot activity, but it does not replace an academic-integrity process or a recipient’s policy.
• 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? A changed signed payload will fail verification. Verification confirms the certificate was issued by Diglot and has not changed; it does not independently validate events that were never captured.
• 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? The certificate is a signed, shareable snapshot of Diglot-captured activity. It does not claim to replace another editor’s history or to prove activity outside Diglot.
• 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.