Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: clkobbjoaegkgnmkibjghlboeoplpmok
Permissions (2)
- Store local data
- Write to clipboard
Related extensions
PII Masker for ChatGPT & Claude – MOM ShieldMake Chrome Yours
PasteSecure – PII Redaction for ChatGPT & AIMake Chrome Yours
Prompt Armour — Redact Secrets & PII from ChatGPT, Claude & GeminiMake Chrome Yours
RedactaMake Chrome Yours
RedactrTools
Tutela AI Redactor: Protect Private Data in AI ChatsMake Chrome Yours
Frequently asked questions
Is Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini safe to use?
Our latest automated scan rates the Chrome listing of Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini at 86/100 (low risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini require?
Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini requests 2 permissions. The most significant: Store local data, Write to clipboard. See the full breakdown in the security report.
Who develops Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini?
Redaxa – Redact PII & API Keys for ChatGPT, Claude, Gemini is published by canadesino91. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 0.4.16
- Current listed version
- 0.4.14
- Scan date (UTC)
- Assessment status
- Completed
The current store version differs from the checked package. These results describe version 0.4.16; they do not verify version 0.4.14.
Recorded findings: 0 critical and 1 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.