This product was not featured by Product Hunt yet. It will not yet shown by default on their landing page.
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Presidio JS — Client-Side PII Scanner
Anonymize prompts privately and securely
PresidioJS detects and anonymizes PII entirely in your browser. No servers, no API keys, no data ever leaves your machine. Supports regex-based detection (emails, phones, IBANs, credit cards, SSNs, crypto wallets, insurance numbers) plus browser-native NER for names, organizations, and locations using a local ML model. Built for privacy-first workflows like sanctions screening and compliance. One HTML file, zero dependencies, works offline. Open source and free.
I built PresidioJS because I needed PII detection for a compliance workflow, but every existing solution required sending sensitive data to a server or API or installing extra libraries. That felt wrong, especially when dealing with lists and personal data that shouldn't leave your network. So I asked: why can't this just run in the browser? PresidioJS runs entirely client-side. Regex-based recognizers handle structured PII (emails, IBANs, credit cards, insurance numbers, etc.), and for unstructured data like names and locations, it loads a ~67MB NER model directly into your browser via ONNX. No backend, no API keys, no data transmitted.
Would love feedback from anyone working in compliance, privacy, or security. What entity types are you missing? What would make this useful for your workflow?
About Presidio JS — Client-Side PII Scanner on Product Hunt
“Anonymize prompts privately and securely”
Presidio JS — Client-Side PII Scanner was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #79 on the daily leaderboard. PresidioJS detects and anonymizes PII entirely in your browser. No servers, no API keys, no data ever leaves your machine. Supports regex-based detection (emails, phones, IBANs, credit cards, SSNs, crypto wallets, insurance numbers) plus browser-native NER for names, organizations, and locations using a local ML model. Built for privacy-first workflows like sanctions screening and compliance. One HTML file, zero dependencies, works offline. Open source and free.
On the analytics side, Presidio JS — Client-Side PII Scanner competes within User Experience, Privacy, Artificial Intelligence and GitHub — topics that collectively have 883.1k followers on Product Hunt. The dashboard above tracks how Presidio JS — Client-Side PII Scanner performed against the three products that launched closest to it on the same day.
Who hunted Presidio JS — Client-Side PII Scanner?
Presidio JS — Client-Side PII Scanner was hunted by Erges Mema. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Presidio JS — Client-Side PII Scanner including community comment highlights and product details, visit the product overview.
Erges Mema
I built PresidioJS because I needed PII detection for a compliance workflow, but every existing solution required sending sensitive data to a server or API or installing extra libraries. That felt wrong, especially when dealing with lists and personal data that shouldn't leave your network. So I asked: why can't this just run in the browser? PresidioJS runs entirely client-side. Regex-based recognizers handle structured PII (emails, IBANs, credit cards, insurance numbers, etc.), and for unstructured data like names and locations, it loads a ~67MB NER model directly into your browser via ONNX. No backend, no API keys, no data transmitted.
Would love feedback from anyone working in compliance, privacy, or security. What entity types are you missing? What would make this useful for your workflow?