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?
No comment highlights available yet. Please check back later!
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 #78 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.
Presidio JS — Client-Side PII Scanner was featured in User Experience (364.7k followers), Privacy (11k followers), Artificial Intelligence (466.2k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 141.7k products, making this a competitive space to launch in.
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.
Want to see how Presidio JS — Client-Side PII Scanner stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
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?