<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Pure Life Tribe</title>
    <description>The latest articles on Forem by Pure Life Tribe (@pure_lifetribe).</description>
    <link>https://forem.com/pure_lifetribe</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3922945%2F57eab487-3404-4016-9d5a-a6d0f39a4c1a.png</url>
      <title>Forem: Pure Life Tribe</title>
      <link>https://forem.com/pure_lifetribe</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/pure_lifetribe"/>
    <language>en</language>
    <item>
      <title>I Built a PII Redactor That Runs 100% in Your Browser</title>
      <dc:creator>Pure Life Tribe</dc:creator>
      <pubDate>Sun, 10 May 2026 07:26:06 +0000</pubDate>
      <link>https://forem.com/pure_lifetribe/i-built-a-pii-redactor-that-runs-100-in-your-browser-15hk</link>
      <guid>https://forem.com/pure_lifetribe/i-built-a-pii-redactor-that-runs-100-in-your-browser-15hk</guid>
      <description>&lt;p&gt;Because sending logs with customer data should never feel like playing Russian roulette.&lt;/p&gt;

&lt;p&gt;You know that exact moment. You’re staring at a production log, a support ticket, or a messy JSON response. It has everything you need to debug the issue… and a bunch of stuff you definitely shouldn’t share.&lt;/p&gt;

&lt;p&gt;An email address here. A phone number there. Maybe even a credit card test number someone left in by mistake.&lt;/p&gt;

&lt;p&gt;You could spend 20 minutes doing find-and-replace. Or you could just cross your fingers and hope for the best.&lt;/p&gt;

&lt;p&gt;Or, you could paste the whole thing into a tool that redacts everything sensitive in one click, locally, with zero data leaving your machine.&lt;/p&gt;

&lt;p&gt;That’s exactly what I built.&lt;/p&gt;

&lt;p&gt;It’s called the &lt;strong&gt;PII Redactor&lt;/strong&gt; on &lt;a href="https://utilora.app/tools/developer-tools/pii-redactor" rel="noopener noreferrer"&gt;Utilora&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  How It Actually Works
&lt;/h3&gt;

&lt;p&gt;The core idea is stupidly simple: a bunch of regex patterns run one after another on your text. Every match gets replaced with a placeholder (you can choose what it shows - &lt;code&gt;[REDACTED]&lt;/code&gt;, &lt;code&gt;[EMAIL]&lt;/code&gt;, etc.).&lt;/p&gt;

&lt;p&gt;What I like is the feedback it gives you. After redaction, it tells you exactly what it found: “3 emails, 2 IPv4 addresses, 1 phone number.” That little summary has saved me more than once when I thought I was safe but actually missed something.&lt;/p&gt;

&lt;h3&gt;
  
  
  Built-in Filters (The Ones You’ll Use Most)
&lt;/h3&gt;

&lt;p&gt;Out of the box it catches the usual suspects:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Email addresses&lt;/li&gt;
&lt;li&gt;IPv4 and IPv6 addresses&lt;/li&gt;
&lt;li&gt;US Social Security Numbers (with dashes)&lt;/li&gt;
&lt;li&gt;Credit card numbers (13–16 digits)&lt;/li&gt;
&lt;li&gt;Phone numbers (fairly flexible format)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These patterns aren’t perfect (more on that later), but they cover 80-90% of everyday cases.&lt;/p&gt;

&lt;h3&gt;
  
  
  Custom Patterns = Where It Gets Powerful
&lt;/h3&gt;

&lt;p&gt;This is my favorite part.&lt;/p&gt;

&lt;p&gt;Every team has their own internal sensitive formats — order IDs, API key patterns, internal hostnames, employee IDs, etc. You can add your own regex with a label, and it gets treated exactly like the built-ins.&lt;/p&gt;

&lt;p&gt;I’ve used it for things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;ORD-[A-Z0-9]{8}&lt;/code&gt; style order numbers&lt;/li&gt;
&lt;li&gt;Specific UUID prefixes used internally&lt;/li&gt;
&lt;li&gt;Secret patterns that follow a company convention&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  It Also Handles Files
&lt;/h3&gt;

&lt;p&gt;Drag in a &lt;code&gt;.log&lt;/code&gt;, &lt;code&gt;.txt&lt;/code&gt;, &lt;code&gt;.json&lt;/code&gt;, or &lt;code&gt;.jsonl&lt;/code&gt; file and it works the same way. Super handy when someone dumps a giant log in your DMs.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why Browser-Only Matters
&lt;/h3&gt;

&lt;p&gt;I deliberately made this (and every tool on Utilora) run completely locally. No uploads, no accounts, no tracking.&lt;/p&gt;

&lt;p&gt;When you’re dealing with real customer data or production logs, the last thing you want is to send it to yet another third-party service — even a “trusted” one. &lt;/p&gt;

&lt;p&gt;This way it’s instant, works offline, and I can use it on planes, in cafes, or behind strict corporate networks without thinking twice.&lt;/p&gt;

&lt;h3&gt;
  
  
  Honest Limitations
&lt;/h3&gt;

&lt;p&gt;The IPv6 detection is pretty basic right now - it only catches the long form. Compressed IPv6 addresses still slip through.&lt;/p&gt;

&lt;p&gt;The credit card detector is deliberately loose. It’ll catch obvious card numbers but can also flag random long numbers. Good enough for most quick redaction jobs, but not production-grade secret scanning.&lt;/p&gt;

&lt;p&gt;If you need something more bulletproof for serious compliance work, this isn’t a replacement for dedicated tools — but for day-to-day debugging and sharing, it’s been fantastic.&lt;/p&gt;

&lt;h3&gt;
  
  
  Try It Yourself
&lt;/h3&gt;

&lt;p&gt;→ &lt;a href="https://utilora.app/tools/developer-tools/pii-redactor" rel="noopener noreferrer"&gt;PII Redactor on Utilora&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It’s completely free, no sign-up, and nothing ever leaves your browser.&lt;/p&gt;

&lt;p&gt;If you work with logs, support tickets, or any kind of data that might contain PII, bookmark it. You’ll probably use it more often than you expect.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>programming</category>
      <category>security</category>
      <category>cybersecurity</category>
    </item>
  </channel>
</rss>
