Skip to content
← All release notes
2026.11.1addedsecurity

Signed exports for audit and chain of custody

On Enterprise, a report or dashboard export can carry a signature that an auditor or a lawyer can check without an account: the exact file, who exported it, when, and how current the data was.

Some exports are evidence: the access list handed to an auditor, the figures attached to a dispute, the report a regulator asks for. Whoever receives one has to be able to rely on it without trusting everyone who forwarded it.

A signed export is the export itself, unchanged, together with signature.json: a manifest naming the file's SHA-256, what it is an export of, the period and filters, how current the data was, who exported it and when, signed with your organisation's key (ES256).

  • Ask for it when you export. "Sign exports" on the reports list, "Signed PDF" on a dashboard, or signed=true on the export API. CSV, Excel and PDF.
  • Your key, or one made for you. Upload your own P-256 key (you keep the public half and can check everything without us), or have one generated. The private half is stored encrypted and never shown again. A retired key stays published, so what it signed still verifies.
  • Anyone can check it. /verify on your SignalForge address checks a file in the browser, without an account and without uploading it; a short Node script does the same offline. Each signed export is also in your audit log with its hash, and in a custody list you can show.

What a valid signature shows: this exact file came from your SignalForge with the details in the manifest. It does not vouch for the underlying data, and the time is the server's own clock.

Signed exports are part of the Enterprise plan.