What does Telebugs look for?
Anything named like a password, token, secret, authorization header, cookie, API key, or card field. Telebugs checks the whole report and replaces the sensitive value with [Filtered].
Scrub secrets before they settle
Passwords, tokens, API keys, and card details can sneak into error reports. Telebugs replaces them before they reach your database, while leaving the useful context around them intact.
When does the scrubbing happen?
While the report is coming in, before Telebugs stores it. By the time the error reaches your database, the matching secrets have already been replaced.
Does it wipe out the useful bits too?
No. Telebugs replaces the sensitive values and keeps the surrounding report intact, so you still have the backtrace, request details, breadcrumbs, and other clues you came for.
Should I still filter data in the SDK?
Yes. If your app does not need to send something, stop it at the source. Server-side scrubbing is the safety net for anything that slips through.