Generate a signed, tamper-evident audit report
Record what was done to a file — anonymized, scrubbed, encrypted, erased, whatever applies — alongside a classification scan FileX runs locally, then get a report with an integrity hash any tampering breaks. Optionally sign it with your FileX ID so it can be traced back to you years later.
Open in FileX (Pro) →How it works
- Open the Audit Report tool (a FileX Pro feature) and drop in the file the report is about.
- Add a row for each action you took, and any notes — FileX also scans supported text files locally and attaches a suggested classification.
- Generate the report, optionally sign it with your FileX ID, and download it as a .json record, a .txt summary, or a formatted .html/.pdf report.
An attestation, not a certification
FileX does not independently verify that the actions you list actually happened — it records what you enter, plus whatever its own classification scan finds when it can read the file as text. The report's value is in its integrity hash and optional signature: once generated, any change to its contents breaks the hash, so it is tamper-evident even though it is not an independent audit.
Why sign it
Signing is optional and uses your FileX ID's ML-DSA-65 key (the same post-quantum signature scheme used to authenticate FXQ1 files and erasure certificates), with its own domain-separated context so a report signature can never be mistaken for either of those. A signed report can be traced back to a specific FileX ID indefinitely — useful when a report needs to hold up well after the fact.
Frequently asked questions
Does FileX verify the actions I record actually happened?
No, other than the classification scan it runs itself on supported text files. Everything else — what you did, when, and why — is entered by you. The report is only as accurate as what you record.
Is my file uploaded to generate the report?
No. The file is hashed and, if it is a supported text type, scanned for the classification section entirely in your browser. Nothing is uploaded.
What does signing require?
A FileX ID created on this device (see the New ID tool) and its keystore passphrase. Signing is optional — an unsigned report still has a verifiable integrity hash.