Authmarks for Business

Show how the work was written.

Verifiable authorship, and records for compliance that an auditor can check. Authmarks records how a document was written, with the writer's consent, and seals that record so a client, an auditor or a regulator can check it for themselves. Pro is for one person; Team and Enterprise are priced per person.

The writer owns the record

Recording is off until the writer allows it for a document. They see their whole record, attest to it, and choose who receives it. What they share is a sealed record the recipient checks without an Authmarks account.

01

Verifiable authorship

A record of how each document was written: typed, pasted, dictated, accepted from a suggestion, produced by automation, or not observed. A named person attests before it is sealed.

02

Self-provenance

The writer sees their own full record, decides when recording is on, and decides who it is shared with. The record is theirs to show, not a file kept about them.

03

Records an auditor can check

A sealed record a client, an auditor or a regulator can check for themselves, with the time it was signed and the trail of where its evidence came from.

How it works

From the first keystroke to a record a client can check

  1. 1

    Record with consent

    The writer turns recording on for a document in Google Docs, Word, the desktop app or the Authmarks editor. Nothing is recorded before that, and it can be paused.

  2. 2

    See the whole record

    The writer and their team see the labelled history: what was typed, pasted, dictated, suggested, automated or not observed.

  3. 3

    Attest and seal

    The writer, or a reviewer they invite, accepts responsibility for the record. Only then does the seal unlock.

  4. 4

    Share and check

    Share the sealed record with a client, an auditor or a regulator. They check it themselves at authmarks.com/verify, with no account.

Source lineage

Where did this paragraph really come from?

A pasted paragraph rarely starts where it lands. It may have been copied from an article into a notes file on Monday and pasted into an essay on another computer on Thursday. Source lineage shows that path, one step at a time, back to the earliest place the copy was witnessed.

Source lineage
Follows copied text back to its original source, across apps, devices and days, and shows each step, marking which steps Authmarks verified itself and which a device reported.
Character-level lifecycle
Every character in the sealed text carries a labelled source (typed, pasted, dictated, inserted by a tool, or unknown), followed while recording was on from the moment it arrived, through every edit and move, to the seal.
Source lineage3 witnessed steps · earliest first
  1. Journal article on a library databaseReported by the device
    Browser, laptop · Copied · Monday 09:14
  2. Research notesReported by the device
    Word desktop app, laptop · Pasted 09:15, copied again · Wednesday 16:40
  3. Changed between these steps while recording did not see it: 38 characters, shown as a gap
  4. History essay, the assignmentVerified by Authmarks
    Google Docs, library computer · Pasted · Thursday 19:02

Illustration only, not real data.

The limits, stated

  • A step that a device reported and Authmarks could not check itself is labelled as reported, never presented as verified.
  • When text was changed between two steps and recording did not see the change, the timeline shows a gap. Those characters are not credited to the source, and not to the writer either.
  • A source that was never witnessed is never named. Pasted text with no witnessed copy is shown as pasted, source unknown.
  • Copy sources are recorded only when the organisation turns them on and the writer agrees. Copied text stays on the device unless it matches what is pasted or typed into a recorded document.
  • Lineage is an observation for a reviewer to weigh. It never decides anything by itself.

Patent-pending methods: the methods behind source lineage and the character-level lifecycle are covered by provisional patent applications, so we describe what they show, not how they work.

Where it is used

Anywhere authorship has to survive scrutiny

Compliance & regulated content

A record of human review

Since 2 August 2026, AI-generated text published to inform the public must be disclosed unless a person reviewed it and holds editorial responsibility. Authmarks' named attestation is a record of that review.

Legal & professional services

Custody for client work

Contracts, filings and client deliverables with a record of how they were written and who stood behind them, sealed with a custody trail.

Media & publishing

Editorial transparency

Show how a piece was produced and reviewed before publication, without handing over the drafting tools themselves.

Consulting & agencies

Verified deliverables

Hand clients work with a record of how it was produced. They check the seal themselves, with no Authmarks account.

What you get today

Capabilities, with their status

Every line says whether it is available now, set up with you on request, or still in development. Which plan includes what is on the business pricing page.

  • Recording in Google Docs, Word, the desktop app and the Authmarks editorAvailable
  • Source lineage: copied text traced back across apps, devices and daysAvailable
  • Character-level lifecycle of every characterAvailable
  • Named attestation before every sealAvailable
  • Public seal check with no accountAvailable
  • Shared review: several reviewers on the same recordsAvailable
  • Audit-log export of plan, role and policy changesAvailable
  • Retention set to match your records policyAvailable
  • Single sign-onOn request
  • Choice of where data is hostedOn request
  • Signed data processing agreement and SLAOn request
  • Bulk export and case filesAvailable
  • Legal holdAvailable
  • Chain-of-custody case files and evidence packs, with a SHA-256 of every fileAvailable
  • Chain-of-custody export for legal review tools (load files)Available
  • SCIM provisioning and audit-log streaming to your SIEMAvailable

How it's verified

Designed with the published standards for authenticating electronic records in mind

When an electronic record is questioned, the same four things are asked of it. The Authmarks seal is designed so anyone reviewing the evidence can check each of them independently, and the record states its own limits. That is a statement about how the evidence is built, not a promise about how any matter ends.

Integrity

Has anything changed since it was recorded?

Writing events are hash-chained as they arrive, and the finished record is sealed with a C2PA signature over its contents. Any change after sealing shows up as a failed check.

Authenticity

Who stands behind it, and when?

The seal names the signed-in author who signed the AI-use declaration; later reviews are chained to the seal. Its signature carries an RFC 3161 time-stamp, asked first of independent authorities (DigiCert, then Sectigo, then GlobalSign); only when none answers does Authmarks' own time-stamp authority countersign, and the seal records which one did. Independent time-stamping is pending its first production proof.

Chain of custody

Where did the evidence come from?

Each seal includes a custody fact: which connections submitted the evidence, in how many batches, over what period, and whether any device reported a different account than the one signed in. Server reads of dictation audio are logged.

Independent verification

Can someone check it without asking us?

Anyone can check a seal at authmarks.com/verify with no account, or with standard C2PA tools against our published root certificate. Our root is not on the C2PA trust list, so those tools report a seal as valid rather than trusted.

For a sense of the kind of standard involved: in US federal courts, Federal Rule of Evidence 901 asks for evidence that an item is what it is claimed to be, including evidence about the process or system that produced it, and Rule 902(14) covers data copied from an electronic device or file and identified by a process of digital identification, such as a hash, certified by a qualified person. We describe these rules so you can see what the record is built for. Authmarks does not claim compliance with any rule of evidence, and whether a record is admitted is always for the tribunal or court to decide.

Legal hold is live: an organisation can place a hold that suspends deletion of a record on every deletion path, and export a chain-of-custody case file, a zip whose manifest lists the SHA-256 of every file in it. Read what checking a seal actually shows and what a writing record cannot prove.

Get started

Start a 14-day trial, or talk to sales.

Try Pro or Team free for 14 days, no card. Regulated organisations and Enterprise write to sales@authmarks.com.