CleanHAR Join the waitlist

For SaaS support teams

Get a clean HAR with a single link.

Cookies, tokens and passwords are removed on your customer's computer before it's sent. No back-and-forth, nothing to install.

Join the free pilot No card needed. Takes 30 seconds.
POST /api/v2/orders 500 1.21 s
Request headers
cookie: session_id=; _ga=
authorization: Bearer
x-csrf-token:
content-type: application/json
referer: https://app.example.com/checkout?step=2
Request body
{ "cartId": "c_8812", "coupon": "SPRING10",
  "email": "j***@acme.com",
  "card_number": "" }
Console
TypeError: Cannot read properties of undefined (reading 'id')
  at checkout.js:118
Removed: 14 cookie values · 3 auth headers · 2 URL tokens Example capture

The problem

You know this ticket.

A customer reports something broken. You need the network log, so you send them your "How to generate a HAR file" article.

Then they get lost in DevTools, forget "Preserve log", record the wrong page, or send a perfect file with their live session cookies still in it. Now your help desk holds credentials it shouldn't.

  1. CustomerMon 09:12

    Checkout keeps spinning and never finishes. Tried twice.

  2. AgentMon 10:40

    Sorry about that! Could you send us a HAR file so we can see what's failing? Here's our guide: How to generate a HAR file (9 steps).

  3. CustomerTue 16:05

    I opened the console thing but I can't find a save button. Screenshot attached.

  4. AgentTue 17:20

    Thanks! Could you open the Network tab instead, tick "Preserve log", and try checkout again?

  5. CustomerThu 11:48

    Here you go.

    checkout.har · 4.2 MB Contains 3 live session cookies and a bearer token

3 days, 5 messagesNobody has looked at the bug yet.

How it works

One link out. Clean diagnostics back.

  1. Send a link from the ticket.

    Create a CleanHAR link and paste it into your reply. A Zendesk app that does this from the ticket sidebar is on the way; the link works with any help desk today.

  2. Your customer records the problem.

    The link walks them through it in their own browser: Chrome, Edge, Firefox or Safari. Nothing to install. With the CleanHAR extension for Chrome and Edge (on the way), it's one click.

  3. The results come back to your team.

    Failed requests, console errors and the customer's browser details, plus the full HAR file. You get an email when they arrive.

What comes back

Everything your engineers ask for, in the first reply.

  • Network log (HAR)Every request while they reproduced the problem, with status codes, timings, and response bodies for API calls.
  • Console errors and warningsIncluding uncaught exceptions with stack traces.
  • EnvironmentBrowser and version, operating system, screen size, language and time zone.
  • A summary of what failedReady to paste into the ticket as an internal note.
Internal note on the ticketExample
CleanHAR capture: app.example.com · 2026-10-27 14:03 UTC · 42s
Browser: Chrome 130.0.6723.92 · macOS 15.1 · 1512×982 @2x
Locale:  en-GB · Europe/London

Failed requests (3)
  POST /api/v2/orders            → 500  1.2 s
  GET  /api/v2/user/settings     → 403
  GET  cdn.example.com/widget.js → blocked (CORS)

Console errors (5, first 3)
  TypeError: Cannot read properties of undefined
    (reading 'id')  at checkout.js:118
  Uncaught (in promise) Error: Request failed with
    status code 500
  Refused to load script: violates Content Security Policy

Cleaned: 14 cookie values, 3 auth headers,
2 URL tokens removed. Full HAR on the results page.

Privacy

Cleaned before it leaves the customer's browser.

CleanHAR removes the sensitive parts on the customer's own computer, before anything is uploaded. What your team needs to debug stays in.

Removed

  • Cookie values, including session cookies
  • Authorization headers, API keys, and CSRF and session tokens
  • Tokens in URLs, such as access_token, id_token, OAuth codes and signed-URL signatures
  • Passwords and secret fields in form and JSON bodies
  • Common secret formats wherever they appear, including JWTs, bearer tokens and cloud API keys
  • Card numbers, and email addresses masked down to the domain

Kept, so you can still debug

  • Cookie names, flags and blocked reasons, so you can see which cookies were sent
  • Every request's URL, method, status code and timing
  • Ordinary URL parameters such as ?page=2
  • API response bodies, with secret fields masked
  • Console errors, warnings and stack traces
  • Browser, operating system and screen details

The customer reviews it before sending.

Removed 14 cookie values, 3 auth headers, 2 tokens in URLs.

Stored briefly, then deleted.

Nothing is uploaded until the customer clicks Send, and only the cleaned file is uploaded. Only the team that asked can see it, and it's deleted after 30 days, or sooner if you delete it.

Automatic cleaning catches the common secrets, not every possible one. That's why customers review a summary before sending, and why you can add your own rules for your product.

Who it's for

Built for support teams who already have a HAR guide.

If your help centre has an article called "How to capture a HAR file" or "How to send us console logs", CleanHAR replaces it with one link.

No code on your product

Other bug-capture tools often need their script installed in your app before they can record console and network data. CleanHAR works on any site your customer is using.

Customers don't need to know DevTools

The link gives step-by-step instructions for their browser, and cleans the file before anything is sent.

Works with your help desk

Paste the link from Zendesk, Intercom, Freshdesk, Help Scout or plain email. The Zendesk app is on the way.

FAQ

Questions support teams ask

Does my customer need to install anything?

No. The link walks them through saving the network log from their browser's developer tools, step by step. Customers on Chrome or Edge will soon be able to install the CleanHAR extension and record in one click instead.

Can we debug issues we can't reproduce on our side?

Yes, that's what it's for. Some problems only happen for the customer: in their logged-in account, behind their company's firewall or VPN, with their browser extensions, or only now and then. The customer records it when it happens, and you see what their browser sent and got back, including the failing requests and the server's error messages.

For logged-in problems, you don't need their password. Their session cookies and login tokens are removed, so nobody can use the recording to sign in as them. It shows what happened behind the page, so for a purely visual problem you may still want a screenshot.

Which browsers does it work in?

The link works in Chrome, Edge, Firefox and Safari. The one-click extension is for Chrome and Edge.

Do we need to install anything on our app or website?

No. Your product stays as it is. When the Zendesk app is ready, you can add it to your help desk to create links from the ticket.

Where is the data stored?

Only the cleaned file is uploaded, stored encrypted in the US, and visible only to your team. It's deleted after 30 days, or sooner if you delete it.

Can customers check what's being sent?

Yes. They see a summary of what was captured and what was removed, and nothing is sent until they click Send.

Can the results go into our help desk automatically?

That's what the Zendesk app is for. It's on the way, and Intercom and Freshdesk will follow. Until then, you get an email and a results page, and one click copies the summary to paste into the ticket. Tell us which help desk you use in the form below.

Why will the extension say it's debugging the browser?

To record the network log in one click, Chrome requires an extension to use its debugging permission, the same access DevTools has. Chrome shows a banner while it records, and the extension only records the tab the customer chooses, only while they're recording.

Waitlist

Join the free pilot

You'll get the early version and a two-minute setup guide within a day. We'll only use your email to contact you about CleanHAR. Read the privacy note.

Required

How often do you ask customers for HAR files or console logs? 
What would your team pay per month for this? (optional)