GUIDE · PRIVACY MODE
Useful evidence. Deliberate retention.
Privacy mode is the default operating posture for evidence: mask familiar sensitive values, keep enough context to debug and treat full traces as a separate decision.
- Redaction before storage
- Trace capture off
- No background artifact upload
PRE-RUN REVIEW
Know each artifact before keeping it.
-
01
Mask editable regions
-
02
Sanitize token-like values
-
03
Inspect debug signals
-
04
Approve traces separately
Privacy checklist
01 · PLAN
Choose the environment. Choose the evidence.
Start with dedicated test data and decide which artifact types the workflow genuinely needs.
Avoid unnecessary real data
A staging journey with generated values makes every later privacy decision easier.
Data minimizationName the permitted artifacts
Decide whether screenshot, DOM, network and console evidence are appropriate for this workflow.
Team-owned decision02 · CAPTURE
Mask before writing. Keep the run useful.
RERUN applies privacy-mode transformations as evidence is captured, so the local artifact set is already the redacted version.
Editable regions masked
Form controls and editable content are obscured in stored screenshots.
Image stays useful for layoutValues and familiar secrets removed
DOM fields, token-like URLs and common credential patterns are sanitized.
Structure and failure signal remain03 · DEBUG
Treat full traces as sensitive evidence.
A full trace can retain significantly more browser state. Enable it only for a specific approved debugging run, then handle the result under the team’s policy.
One deliberate debug run
Do not turn trace capture into an always-on background default.
Privacy mode otherwise keeps it offRecheck before sharing
Local storage does not make an artifact safe to forward. Review its contents before it leaves the machine.
Human review