HAR Sanitization Before Support

Use this checklist before attaching a HAR file to a support ticket or sending it to a third party.

When to use this

  • Before attaching a HAR to a support ticket.
  • Before sending a HAR to a vendor.
  • Before opening a HAR in a shared review session.

How this checklist works

Some items run a quick local check (e.g. scanning sample responses for secrets or PII). Others are manual confirmations or open another tool. When you finish, copy the report as Markdown to paste into your PR description, ticket, or Slack.

Privacy

This page is a static HTML file. The checklist component runs locally in your browser. The raw text you paste into the Run boxes stays in memory and is never saved. Your progress — checked items, notes, owner/reviewer, and each check's verdict and trimmed output — is saved to localStorage in this browser so you can resume, and you can remove it any time with Reset or the footer's "Clear local data" action.

Related tools

Other release checklists

What to capture during this HAR sanitization

Use the checklist as a release note template, not just a pass/fail list. Capture which cookies, auth headers, query tokens, and request bodies were removed or masked before the file was shared. This gives reviewers enough context to understand what changed and what still needs follow-up.

Common blockers

  • Evidence is copied from staging but the production path, host, or namespace is different.
  • A secret, token, cookie, or personal field appears in an example that will be shared outside the team.
  • The release owner signs off without a clear rollback note or known-risk comment.

Helpful next checks