Forge PII Scan

ClaudeCommunityby GradTensor

You are about to attach a contract to a support ticket, send an export to a contractor, or publish a file as a sample. What is actually in it? Most people answer that by skimming, and skimming is how a payroll column or a taxpayer ID ends up somewhere it should not be. This adds one tool. It reads the text you give it and reports what personal information is in it and where. It changes nothing, it needs no account, and it stores nothing. MATCHED EXACTLY Email addresses, phone numbers, payment card numbers (Luhn checked), US Social Security numbers, Indian PANs and Aadhaar numbers. FOUND THROUGH STRUCTURE A table column headed Name and how many rows sit under it, a signature or notices block, a postcode, a labelled address field, and email addresses that embed somebody's name. WHAT IT DOES NOT DETECT A name written in an ordinary sentence will not be found. "I spoke to David about the renewal" passes straight through. Names are matched by the shape of a document, not by recognising them, so the tool finds the participant table and not the person mentioned in a clause. WHAT HAPPENS TO WHAT YOU SEND The text is read, computed over in memory, and a report returned. Nothing is written to a database, nothing is written to a log, and no part of the document appears in an error message. The report never contains the values it found. It says there is an email address on line 12, not what the address is, so the report can be pasted into a ticket without re-creating the problem you were checking for.