DATA SAFETY LAYER / DOCUMENTATION

Privacy-first Audit Log

The Audit Log records what the Data Safety Layer decided during a browser session. It is designed to give you a useful decision trail without keeping a copy of the information you checked.

In plain English: the log can tell you that a scan was blocked because it found one protected term. It does not keep the name, address, message, document text or protected term itself.

01. What the log records

when a scan, copy action or manual override happened;
the risk score, classification and Allow/Block decision;
the number and category of findings, such as 1 protected term;
whether Semantic Mode was enabled; and
which detection rules were enabled for the scan.

02. What the log never records

text pasted into the scanner, including snippets or previews;
the redacted output or anything copied to your clipboard;
names, addresses, email addresses, phone numbers, account numbers or other detected values;
your custom protected terms; or
content fingerprints or hashes that could be used to identify the checked material.

03. How long records last

In this version, records exist only for the current browser session. They are not automatically uploaded to Mutantwork or stored in an online account. You can clear them at any time with CLEAR LOG.

04. What each event means

Event	Meaning
`ALLOW` / `BLOCK`	The policy result after a scan. A block means the Safety Layer found content requiring review.
`COPIED`	You copied the redacted output. This does not prove it was pasted into, or sent to, an AI tool.
`OVERRIDE`	You chose Send Anyway after a blocked result. The decision is recorded, but the original material is not.

05. Exporting your audit log

EXPORT JSON downloads the same decision-only records to your device. Review and store that downloaded file according to your own organisation’s policies. It contains no pasted content, detected values or protected terms.

06. A clear boundary

This browser-session log is useful evidence of the Safety Layer’s local decision process. It is not a tamper-proof third-party record and it cannot prove that content was or was not sent elsewhere.

07. Need help?

For questions about the Data Safety Layer, contact rick@mutantwork.com.