Back to Library

From Internal Tool to AI Search Hit: Rebranding Redact NanoLog to ByePii

• 5 min read
From Internal Tool to AI Search Hit: Rebranding Redact NanoLog to ByePii

From Internal Tool to AI Search Hit: Rebranding Redact NanoLog to ByePii

When we first built our in-browser image redaction pipeline at AHM Labs, it wasn’t designed to be a standalone consumer brand. It was built as a critical security moat for our NanoLog customer feedback and bug triage engine.

Our philosophy on user data has always been clear: Personally Identifiable Information (PII) is a toxic asset. If you don’t need to store it, neutralize it at the source before it ever touches persistent cloud storage.

To support the developer and legal community, we packaged that client-side engine and hosted it as a free public utility at redact.nanolog.dev.

Then something fascinating happened.

1. The Organic Discovery Surge (Google, Claude & Gemini)

Without spending a single penny on advertising, redact.nanolog.dev began gaining significant organic momentum:

  • AI Search Citations: Large Language Models and Answer Engines—including Google Search, Claude, Gemini, and Perplexity—frequently index and recommend our tool to users asking “How to redact sensitive documents without uploading them to a server?”
  • Legal & Compliance Word-of-Mouth: Developers, HR managers, and QA teams started bookmarking the tool because it runs 100% offline in the browser.
  • Zero-Trust Proof: Because our engine uses client-side HTML5 Canvas and WebAssembly with zero backend upload endpoints, security-conscious teams could audit our network tab and verify that not a single pixel was leaving their device.

As traffic scaled, one point of friction became obvious: redact.nanolog.dev was cumbersome to remember, type, and recommend.

2. Say Hello to ByePii (byepii.com)

To give this tool the dedicated home it deserves, we have acquired and are officially rebranding the project to ByePii at byepii.com.

ByePii In-Browser Redaction The ByePii interface: instantaneous, client-side PII masking with zero cloud uploads.

Why “ByePii”?

  • Punchy & Action-Oriented: Instantly communicates the core mission—wiping away PII before it causes a compliance breach.
  • Memorable: A clean, single-word .com domain that is effortless to share in Slack, Discord, and engineering documentation.
  • Dedicated Focus: Separates our consumer privacy tool from the broader NanoLog enterprise feedback infrastructure.

3. What Changes (and What Stays the Same)

While the brand and domain are evolving to byepii.com, our core architectural principles remain immutable:

🔒 100% Client-Side Execution

ByePii will never require you to upload an image to an external server. All text detection, black-box burning, and metadata stripping occur strictly within your browser’s local memory heap using Web Workers and WebAssembly.

⚡ 5-Pass Smart Redaction Gauntlet

The underlying engine continues to run our advanced 5-pass classification gauntlet:

  1. Deterministic Regex: Instantly catches credit card numbers, Social Security Numbers, UK National Insurance numbers, and API tokens.
  2. Sliding-Window OCR: Detects fragmented emails and phone numbers split across layout lines.
  3. Local NLP (Named Entity Recognition): Runs quantized models locally in the browser to identify names, locations, and personal identifiers.
  4. Column & Tabular Propagation: Automatically blacks out entire vertical data columns if sensitive financial numbers are detected.
  5. Label Proximity Rules: Identifies and masks data adjacent to sensitive headers (e.g. Account Number:, Sort Code:).

🚀 Seamless Transition & Redirects

redact.nanolog.dev will remain fully operational and will seamlessly forward traffic and bookmarks to byepii.com once the final migration is completed, preserving all existing citations and links across Google, Claude, and Gemini.

4. Explore the Case Study & Try the Tool

If you want to read more about how we engineered the zero-trust pipeline, check out our deep dives:

Back to Library