Log sharing / privacy handoff
Choose what to keep or hide before sharing logs
Keep only the minimum diagnostic context and hide emails, tokens and cookies before sharing. Stop on a secret-bearing example and hand off only reviewed text.
Use three sensitivity classes
Classify each synthetic fixture field as shareable, redact-before-sharing or never-share. Record both the reason to keep and the reason to hide.
| Field | Class | Decision | Reason |
|---|---|---|---|
| timestamp | Shareable | Share | Correlates the incident |
| request_id | Shareable | Share | Finds the matching event |
| error_code | Shareable | Share | Identifies the failure family |
| user_email | Redact before sharing | Redact | Personal data is not needed |
| authorization / cookie | Never share | Stop | May be a credential |
Build a safe handoff
sample.log contains synthetic secret examples. The shareable version keeps only the timestamp, request ID and error code, and names removed and unknown fields.
timestamp=2026-09-20T01:00:00Z
request_id=req-synthetic-001
error_code=E_SYNTHETIC
removed=user_email,authorization,session_cookie
Redaction is not a guarantee that every secret was found. Hold unknown fields until the owner reviews them.
Review before sharing
- Keep the smallest time window and identifiers needed to diagnose.
- Redact email, token, cookie, credential and unnecessary user content.
- Never share authorization headers or session cookies.
- Record removed fields and the reviewer in the handoff.
- Stop until the data owner reviews any field with unknown sensitivity.
This guide is static browser-local material. Real data, input and fixtures are not sent to or stored by an external service.
Do not share secret-bearing logs
TOKEN_EXAMPLE_ONLY and COOKIE_EXAMPLE_ONLY are synthetic examples, but they must not remain in shared text. Never paste a real token or cookie; stop, revoke if needed and ask the owner to review.