Most AI-privacy tools redact on their servers — your data still leaves your machine. ONYRI Sanitize doesn't: detection, masking and restoration run 100% in your browser, and the token↔value mapping never touches a server. 0 bytes of sensitive data ever leave. What stands out: • Reversible tokens, not black boxes — the AI keeps context; you restore values in place • 38 detectors, 6 families: names to API keys, salaries to cloud secrets • Text, CSV/Excel + built-in Chat for GPT, Claude & Mistram
No reviews yetBe the first to leave a review for ONYRI Sanitize
Maker
📌
Hey Product Hunt 👋
I'm Alex, maker of ONYRI Sanitize.
This started with a small, scary realization: a single copy-paste can leak your company's most sensitive data — for good. You drop a customer export, a support ticket or an HR spreadsheet into an AI to "just rewrite this," and names, IBANs, salaries, even API keys leave your perimeter with no way back.
The usual fix is a server-side gateway that redacts your text — but that means your data still travels to someone else's machine first. That felt backwards.
So ONYRI Sanitize does the opposite: the whole engine runs in your browser. It detects 38 types of sensitive data across 6 families (from a name to an AWS key), swaps each one for a reversible token, and you send only the clean text to the AI. When the answer comes back, the tokens turn back into your real values — locally, in place. The token↔value mapping never touches our servers. 0 bytes of sensitive data leave your device.
A few things I'm proud of:
• Reversible, not just redacted — the AI keeps context, so the answer is actually useful.
• Works on text AND tables (CSV/Excel), column by column.
• A built-in Chat to talk to GPT, Claude, Gemini or Mistral with anonymization applied automatically.
One honest caveat: no detector catches 100% of everything. So every detection is visible and editable before you send, and you can add your own rules for the patterns specific to your work. You stay in control.
There's a Free tier to try it on real text right now, and Pro/Team plans for daily use.
I'd love your help: what kinds of sensitive data should we detect next? Reply with the gnarliest thing you've ever almost pasted into an AI 😅
Thanks for taking a look 🙏
— Alex
Report
Maker
We asked Reddit "what does AI do with our data?" — here's what ~50,000 views taught us
A few days ago we posted one simple question across r/OpenAI, r/ClaudeAI and r/artificial:
"A healthcare professional asked me: if I paste my patients' personal info into ChatGPT, is that a problem?"
It hit a nerve. ~50,000 views, dozens of candid replies. We read every one. The same three things came back, again and again:
1. Fear, not facts.
"No one except OpenAI truly knows what they do with the data — and that's what's so scary about it."
2. It's worse than people assume.
"Once you put that data in, it never leaves the system." — and on free tiers, "you can turn off training… it's just on by default."
3. The "fake name" trick doesn't hold. Someone suggested just using a fictitious name. The honest reply: "to save time, they stop doing it." Manual anonymization always loses to a deadline. And for health data, one comment was blunt: "it is 100% a HIPAA violation to enter patient information into ChatGPT."
But here's the part that made us build ONYRI Sanitize: across hundreds of comments, everyone said "don't paste sensitive data into AI" — and not one person could say how to use AI safely anyway.
That gap is the entire product.
ONYRI detects the private bits in your text (names, emails, card numbers, patient data, API keys), swaps them for reversible tokens before anything is sent, and restores the real values right inside the AI's answer. It all runs in your browser — the token↔value mapping never touches a server. The AI helps; your data stays home.
To the healthcare pro who started the thread: yes, it's a problem — and now there's a fix. 🙂
We asked Reddit "what does AI do with our data?" — here's what ~50,000 views taught us
A few days ago we posted one simple question across r/OpenAI, r/ClaudeAI and r/artificial:
It hit a nerve. ~50,000 views, dozens of candid replies. We read every one. The same three things came back, again and again:
1. Fear, not facts.
2. It's worse than people assume.
3. The "fake name" trick doesn't hold. Someone suggested just using a fictitious name. The honest reply: "to save time, they stop doing it." Manual anonymization always loses to a deadline. And for health data, one comment was blunt: "it is 100% a HIPAA violation to enter patient information into ChatGPT."
But here's the part that made us build ONYRI Sanitize: across hundreds of comments, everyone said "don't paste sensitive data into AI" — and not one person could say how to use AI safely anyway.
That gap is the entire product.
ONYRI detects the private bits in your text (names, emails, card numbers, patient data, API keys), swaps them for reversible tokens before anything is sent, and restores the real values right inside the AI's answer. It all runs in your browser — the token↔value mapping never touches a server. The AI helps; your data stays home.
To the healthcare pro who started the thread: yes, it's a problem — and now there's a fix. 🙂
👉 Try it on your own text: Link
What's the riskiest thing you've ever almost pasted into an AI? 👇