Straight answers about the record.

Authmarks keeps a sealed record of how a document was written, while you are recording it — in Google Docs, in Word, in the Authmarks editor, or from the Authmarks keyboard. A named person can attest to that record. Anyone the owner authorises can check it. Authmarks does not score a finished draft as “% AI”.

No. Detectors guess from finished text. Authmarks keeps a record of the writing while it is being written. That record is evidence for a person to read, not a “% AI” score.

No. It provides evidence. Teachers, publishers, clients, or legal teams decide under their own policies.

There is no public signup, and asking does not create an account. When you want to be considered, email sales@authmarks.com. There is no public signup and no published price.

The browser extension witnesses Google Docs and Word in the browser. There are native add-ins for Microsoft Word and Google Docs, Authmarks Write — our own editor, as a desktop app and a web writing room with its own document drive — and an Android keyboard that witnesses writing at the device level. Access is arranged through sales.

Browser editors such as Notion are planned. LMS connectors (for example Moodle) are scoped with partners. Those are not generally available yet.

No. You can keep writing in Google Docs or Word. Authmarks Write, our own editor, is there if you want the record built in from the first keystroke — it is optional.

It follows the writing while recording is on. Text written before recording started, while recording was off, or during a gap is left unmarked. Authmarks does not invent a history for writing it did not see.

They are plain labels on the record: written in the session, brought in from elsewhere, produced without a person at the keyboard, accepted from a suggestion, or not witnessed. The labels are for a reviewer. They are not a finding of misconduct, and this page does not describe how a label is decided.

No. Authmarks is a record of writing it witnessed while recording was on. It is not a guarantee about every way text can appear in a document, and it does not decide that someone cheated. A person reads the record.

Events are stored locally and sync when you’re back online. Lost or interrupted capture shows up as gaps (untracked / unknown) — never invented history.

The sealed record can be checked to see whether it still matches what was sealed, without relying on a private explanation from us. The fuller writing record is available only to people the owner authorises.

A named person attests before the record is sealed, and the seal can be checked afterwards. We do not describe additional checks on this website. Provisional patent protection applies.

The cryptographic check fails. That is the point of a seal: a verifier can see the file no longer matches what was sealed.

Recording stays off until you allow it for that document. You can pause it or turn it off. You also need to be signed in. What happens to material already recorded is covered in the Privacy Policy.

No. It keeps what is needed to hold and check the record. It is not a permanent archive of everything you write. Retention is described in the Privacy Policy.

You can stop recording and revoke future capture. Sealed records may be retained for verifiability, legal, contractual, or institutional reasons — see Privacy Policy. Enterprise customers can set retention by contract.

Before sealing, the author or an invited reviewer confirms the record and accepts responsibility. That attestation is bound into the sealed package.

Since 2 August 2026, AI-generated text published to inform the public must be disclosed, unless a person reviewed it and holds editorial responsibility (Art. 50(4)). Authmarks’ named attestation is a record of that kind of review — not a claim that Authmarks alone makes you compliant.

Email sales@authmarks.com — demos, pilots, pricing, privacy, and legal questions all go there for now.

Yes. Email sales@authmarks.com. A request is how you ask to be considered. It is not access.