Skip to content

Validate redaction across table and download views

Check that a minimized artifact does not leak withheld fields through secondary representations.

Guides

Validate redaction across table and download views — what should the operator record?

A hidden column is not a redaction, and a cropped screenshot may still accompany a revealing source file. Validate every representation included in the handoff. The check should protect withheld information while leaving enough nonidentifying context for recipients to understand missing or unavailable evidence honestly.

Practical operations check
Check that a minimized artifact does not leak withheld fields through secondary representations.
List field categories to omit from this recipient view, using schema names rather than copying the sensitive values into the redaction checklist. A checklist should name categories such as source_handle or private_note rather than list the exact withheld values, preventing the checklist itself from becoming a leak.
Record which representations passed and keep any unreviewed format outside the package; do not label the whole bundle safe based on one screenshot. If only CSV was checked, do not include a JSON export on the assumption that the renderer's redaction applied there too; validate each delivered format independently.
01 / Guides

Define prohibited exposures

List field categories to omit from this recipient view, using schema names rather than copying the sensitive values into the redaction checklist. A checklist should name categories such as source_handle or private_note rather than list the exact withheld values, preventing the checklist itself from becoming a leak.

02 / Guides

Create a derived artifact

Build the approved keep-list projection from permitted input instead of deleting cells in the only working copy and hoping hidden values are gone. A new artifact revision makes the projection auditable and avoids accidentally distributing an earlier unredacted file because it retained the familiar final filename.

03 / Guides

Inspect all outputs

Review CSV, JSON, notes and archive metadata actually being delivered, checking that withheld columns and identifying comments are absent. Check embedded hyperlinks, alternate text and document properties where those representations exist; information can remain outside ordinary table cells and still reach the recipient.

04 / Guides

Test unresolved rows

Ensure a withheld state remains meaningful without exposing the original identity through a URL, filename, alternate column or embedded note. A useful test asks whether the receiver can resolve the old identity using any included field, not merely whether a particular name column has been removed.

05 / Guides

Approve the checked revision

Record which representations passed and keep any unreviewed format outside the package; do not label the whole bundle safe based on one screenshot. If only CSV was checked, do not include a JSON export on the assumption that the renderer's redaction applied there too; validate each delivered format independently.

Keep the boundaries clear.

  • Check that a minimized artifact does not leak withheld fields through secondary representations.
  • Operational record: Define prohibited exposures. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage