Document forensics

Document tampering signals, explained in plain language.

The moment a file arrives, Truvasse fingerprints it and runs its forensics engine across seven areas. Each finding comes with an attention level, a plain-language summary, the method used and where it was found.

Inside

The seven areas Truvasse examines

Every finding is labelled with its area, so a reviewer knows exactly what it is.

PART 0101 / 07

File integrity

Whether the file itself shows signs of tampering.

01 / 07
How it works

From request to a decision you can stand behind.

Four steps, in the order a careful reviewer would take them.

STEP 0101 / 04

Request

Send each person a secure, one-time link listing exactly what to provide. No account to create.

LEAST HARMFULFINAL
01 / 04
Workspace

Three attention levels, no verdicts

A reviewer's eye goes straight to what matters.

  • For information: context the reviewer may want.
  • Worth noting: something to consider.
  • Needs a closer look: review this before deciding.
  • Truvasse never decides; it hands the reviewer the evidence, method and location.
Built for trust

Evidence you can trust. Decisions you can defend.

A wrong flag can cost someone a job or a loan. Nothing here happens on a machine's word alone.

PRINCIPLE 0101 / 04

Evidence, not accusation

Truvasse shows what it found and why it might be innocent. It never declares a document genuine or fake. A person always makes the call.

NO MACHINE VERDICTS
01 / 04
Questions

Frequently asked questions

Can Truvasse detect AI-generated documents?

Truvasse reports forensic signals across structure, metadata, visual content and consistency, which can surface documents built from templates or edited after issue. It does not label any document fake or AI-generated; a reviewer decides.

Which file types are analysed?

Documents and images uploaded to a case, including PDFs and photos captured with the phone camera.

What happens when the engine improves?

A new engine version produces a new, separate run. Earlier findings are never rewritten, and you always see which version produced each finding.