Names every line where your Node/TypeScript service writes personal data into logs, crash reports and analytics: console.log(req.body), pino without redact, sendDefaultPii: true. 22 rules. Runs entirely in your browser — nothing is uploaded.
Same engine as the VS Code extension, byte for byte.
This page is the working piece. The full pack has everything below.
22 rules that name the lines where a Node or TypeScript service writes personal data into logs, crash reports and analytics — with the article it touches and the one-line fix.
GitHub Advanced Security lists at $49 per active committer per month ($30 Code Security + $19 Secret Protection) and looks for secrets, not for a customer's name travelling in a log line.
Buy the full version — $29It reads a JavaScript or TypeScript file and marks each line that sends personal data to a log sink: console.log(req.body), a whole user record, a password or token argument, sendDefaultPii: true, morgan('combined') writing the client IP, pino with no redact option, or a stack trace returned to the caller. Each finding names the rule and the fix.
Node and TypeScript backend engineers whose service handles EU personal data, and the platform engineer who has to say which services log what. It is written for the person who inherited a repo where logging was added by a coding assistant and nobody has read every console call since.
ESLint's no-console rule treats every console call the same way, so teams switch it off; it cannot tell req.body.orderId from req.body. Secret scanners hunt keys and tokens, which are not personal data. Neither one knows that an IP address is personal data in the EU under CJEU C-582/14.
The file you have open is free, with all 22 rules, no key and no limit — you can clean a file with it and never buy anything. The paid tier, $29 once, runs the same rules across every .js and .ts file in the workspace and writes the findings to a report file you keep. Scope and ownership, not crippled rules.
GitHub Advanced Security lists at $49 per active committer per month, split as $30 Code Security and $19 Secret Protection, and it looks for secrets rather than for personal data in log lines. A privacy engineer reading one service's logging calls by hand is a day of work per service, repeated each release.
One question, answered by the person who built it. Your email only if you want the answer sent.