Quick question for fullstack and backend engineers:
When an uncaught exception hits your application, how does your team ensure sensitive JWT tokens, passwords, and user PII don't end up sitting in third-party APM log databases?
Most traditional trackers rely on server-side scrubbing, meaning sensitive customer data still crosses the wire unmasked.
I built a sub-5KB listener for Next.js and modern stacks that runs an on-device regex AST to scrub tokens directly in the client browser before the network payload ever dispatches:
👉 https://snaptrace-dashboard.vercel.app/test
Do you handle data sanitization on the client before dispatch, or rely on third-party cloud scrubbing rules?
Top comments (0)