Show how your document was written.

It is a cryptographically signed record of the writing activity captured while a document was created in Diglot. It summarizes the recording period, word count, writing surface, and activity pattern, and gives you a public URL that anyone can verify without a Diglot account.

Not much on the score itself: the certificate does not change what a detector reports, and it does not guarantee that a reviewer will accept it. What it gives you is a record of how the document was written. Diglot logs edits, pastes, and accepted AI assistance as an append-only chain while you write in its editor, so the record exists before anyone asks a question. If a reviewer raises a flag, you can send the verification URL: they open it in any browser, with no login and no Diglot account, and see the writing period, the word count, the activity summary, and a cryptographic signature check, to read alongside the detector result and the work itself. The record covers only what happens inside the Diglot editor.

No. It does not control a detector or guarantee that a reviewer will accept it. It gives you process evidence recorded before a question arises, so the discussion can include how the document developed instead of relying only on a probability score.

No. Verification is fully public. You open the certificate URL, see the payload and the signature status, and read the verdict — all without logging in. This is the core design property of the certificate: third parties shouldn't have to trust Diglot to act as a notary; they verify cryptographically.

Green, Yellow, and Red summarize documented activity patterns such as paste size, AI-assist density, and edit cadence. A tier is not proof of identity, guilt, innocence, or academic integrity; reviewers should read it together with the detailed activity summary and the work itself.

The chain stores edit operations (insert / delete / paste / accept-AI-suggestion) with timestamps and approximate sizes. It does NOT store the full text of every keystroke. The certificate aggregates the chain into a summary — the underlying chain stays inside Diglot unless you choose to expose it. See our Privacy Policy for the full retention rules.

No. The ed25519 signature is over the entire certificate payload, signed with a private key that never leaves Diglot. The verification page fetches the public key from diglot.ai/.well-known/diglot-pubkey.json. A forged certificate would either fail the signature check (status: INVALID) or point at an attacker-controlled key URL (the verify page falls back to the canonical public-key location and would still mark it INVALID).

No. It is a signed record of events observed inside the Diglot editor: the document was edited there during a specific time window, with a specific pattern of typing, pasting, and AI assistance, on specific surfaces. It cannot see activity outside the editor (another tool, dictation, or help from another person), and it is not a warranty of authorship or originality or a guarantee that a school, journal, or employer will accept it. We say this in plain language on the certificate itself. Treat it as process evidence to read alongside the work.

Create a free Diglot account, write in Diglot, then request a certificate from the editor. Every plan includes unlimited ed25519-signed certificate generation at no extra charge whenever the document’s recorded history meets the certificate criteria; recording cannot be added retroactively to work completed elsewhere.