DocSupra

DocSupra › Enterprise Compliance Studio › Hash-chained document audit log

DocSupra

DocSupra · Enterprise Compliance Studio

An audit log, chained by hash

Who audited what, and when, chained by hash. Names, hashes and verdicts. Never the images.

A document audit log chained by hash, that you can verify at any time.

The short answer. Every batch a desk records goes into the organisation log: the files by name or pseudonym, their SHA-256 hashes, sizes and verdicts, the department, the destination, who did it and when. Each record is sealed with a SHA-256 that includes the seal of the record before it. Verification recomputes every seal and reports any stored record that no longer matches, and any gap in the sequence. The log never holds a document.

An auditor asks two questions: what did you do with these documents, and how do I know this record was not written afterwards? A spreadsheet answers the first. The second needs a record whose order can be checked. This one is kept by the software as the work happens; the service recomputes every seal when you ask, and the seals your own systems received by webhook are your independent copy.

What the log holds, and how it is protected

Batches

Each audit and each delivery: date, type, department, destination, who, how many files were ready, fixable or to retake, a sequence number and a seal.

Rows

Per file: the name or a pseudonym, the SHA-256 of the source, the SHA-256 of the delivered file on deliveries, the verdict, the reasons, the integrity risk and what was done on export.

The chain

Every record carries the seal of the one before it. Verification recomputes every seal of a month, names the first record that no longer matches its seal and counts the gaps: a batch that was audited again, purged or has expired leaves one.

Administration, in the same log

Policy changes, purges, key and webhook changes are recorded as entries in the same chain, so the trail of administration is part of the evidence.

Compliance mode

Under HIPAA, GLBA or GDPR mode the desk requires the record before it releases a batch, names become pseudonyms and records are kept for the retention window you set, from 30 to 400 days.

Out to your systems

An API key reads the log and verifies the chain; signed webhooks and SIEM export (Splunk, Datadog, Sumo Logic) push each batch as it happens; an AI assistant can read and verify the log through the connector.

How it works on a desk

  1. Audit a batch

    Open the Enterprise Compliance Studio, choose the department and the destination and drop the files. Every file is measured on your own machine.

  2. Record it

    Record the batch to the organisation log. Under compliance mode this is required before the ZIP is released.

  3. Verify

    In the team console, verify the chain for the month: how many records were verified, whether any no longer matches its seal and how many gaps there are.

  4. Hand it to the auditor

    The evidence PDF summarises the policy in force and the state of the log. A read-only auditor role reads the log, the usage report and the member list, and cannot record, export or change anything.

What it is not

The log records metadata: names or pseudonyms, hashes, sizes and verdicts. It never contains an image or a page, so it cannot be used to recover a document. A verified chain shows that the stored records still match their seals. A batch that is audited again replaces its earlier record and shows as a gap, so keep the seals your systems received if you need to show what was there before. It does not certify that the organisation is compliant with any law, and we do not sell a certification.

What it costs a team

Both plans include the same software. Corporate Studio adds people, a named support contact and invoice billing.

Professional Team
$149 /mo
Up to 3 people. Batch queue and the Enterprise Compliance Studio, combined multi-page PDF per matter, archival TIFF masters, commercial use on client documents.
Corporate Studio
$349 /mo
Everything in Team. 10 people included and $29 per extra seat, up to 500 people. Named support contact within one business day. Invoice billing on request.

Prices are in USD and exclude any tax that applies in your country; Stripe calculates it and shows it before you pay. Only the monthly plans renew, and they cancel in one click from the Stripe receipt.

Open the Enterprise Studio →

Questions

How is the log protected against changes?

Each record carries a seal computed from its own content and the seal of the previous record. Verification recomputes every seal: a stored record that was altered no longer matches and is named, and a record that was replaced by a new audit, purged or expired leaves a gap that is counted. For an independent copy, keep the seals your webhook or SIEM received.

Does the log contain our documents?

No. It holds file names or pseudonyms, SHA-256 hashes, sizes, verdicts, the department, who did it and when. The images never leave the machine that opened them.

Can our systems read the log?

Yes. An organisation API key reads the log and verifies the chain, signed webhooks and SIEM export push each batch to Splunk, Datadog or Sumo Logic, and an AI assistant can read and verify it through the MCP connector. A key cannot download files, administer the organisation or change the policy.

How long are records kept?

For the retention window in your compliance policy, between 30 and 400 days. A purge is possible only by an administrator and is itself recorded in the chain.

Which plans include it?

It is part of both team plans: Professional Team ($149 per month, up to 3 people) and Corporate Studio ($349 per month, 10 people included and $29 per extra seat, up to 500 people).

More on DocSupra

Client document capture linksA link per client: their phone makes the exact file your office needs. AI connector (MCP)Connect Claude and other AI assistants to DocSupra. No document ever travels. Enterprise Compliance StudioThe studio this page opens, explained. Studio 3 of 3. What is DocSupra?The definition, the facts and how the three studios fit together. Trust centerSecurity, DPA, SLA, sub-processors, accessibility, status.

Made and copyrighted © 2026 by Soelys Muñoz. DocSupra™ is her trademark. All rights reserved. How to recognise the real site.