Security and data

What Mnestiq records, and where it goes

Last updated 27 October 2026

Short version: the recorder writes evidence to files you control and sends nothing to us. The Workbench sends data only where you point it. The hosted Evidence Vault receives fingerprints of your evidence, never its content.

What the recorder captures

  • What the agent's model was given (system prompt, user messages, tool results, documents, web pages), each piece labelled with where it came from.
  • What the model answered and which tools it asked for.
  • Each tool call the agent ran, with its arguments and result.
  • Approvals, and who or what gave them.
  • Network connections the agent opened: addresses and ports, and the URL and status for web requests. Not the content of those connections.
  • The run, step, agent, operator and container each event belongs to.

That can include personal data or secrets that passed through the agent. API keys sent to model providers are never written down.

Where it stays

In the file you choose, on the machine the agent runs on. The recorder makes no network calls of its own, with two exceptions you switch on yourself: a signing service or Azure Key Vault, which receives only the checkpoint to sign (hashes, never content), and RFC 3161 timestamp authorities, which receive only a hash of a signature. The proxy forwards model calls only to the providers you configure. The dashboard listens on this machine only.

Encryption and integrity

The recorder protects evidence against changes: every record is hash-chained and regularly signed, so an edit, deletion or reordering is detected. It does not encrypt evidence at rest. Keep it on an encrypted disk (BitLocker, FileVault or LUKS) in a folder only the agent's account can read. On Linux and macOS new evidence files are readable by their owner only.

mnestiq redact makes a copy without prompts, documents or tool output that still verifies. Since version 1.0 every redacted value has its own random salt, so it can't be found again by guessing.

Deleting evidence

Evidence files are yours: keep them as long as you need them and delete them when you don't. We hold no copy.

The Workbench

The Workbench runs on the machine it is installed on. It sends data only to destinations you configure, such as your Microsoft Sentinel workspace. Nothing goes to us by default.

During a pilot, we run the Workbench on our own machine with evidence you choose to send, under a signed pilot agreement. It travels encrypted to our key or through your own secure share, is kept on an encrypted drive outside any cloud sync, and is never put into online services or AI assistants without your written consent. At the end of the pilot we delete everything and confirm it in writing, with the files and their hashes.

The Evidence Vault

If you use the hosted Vault, it receives your signed checkpoint records exactly as written: the chain's id, sequence numbers, a time, the hash of the record before, which records the checkpoint covers, a Merkle root over their hashes, a public key, a signature and, if you use them, a timestamp token. No prompts, documents or customer data. It runs in the EU (Germany), with nightly encrypted backups, also kept in the EU. Using the hosted Vault requires a separate agreement.

Reporting a vulnerability

Please report security problems privately through GitHub, or by email to alexander@mnestiq.com. You'll get an acknowledgement within a few days, and we agree on a disclosure date once a fix is ready. What is in scope is in SECURITY.md.

Support

The open-source recorder is supported on a best-effort basis through GitHub issues, with security fixes for the latest release. Pilot partners and customers reach us directly by email.