Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing 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: caggdomdndfkfoadolmeblhoghnnodgk
Permissions (5)
- Execute scripts in pages
Related extensions
DataBlur: Blur Screen & Hide Sensitive Data for Screen SharingMake Chrome Yours
Page Blur - Hide Sensitive Info for Screen SharingProductivity
BlurScreen - Blur & Hide Sensitive Info on ScreenTools
BlurScreen — Screen Blur for Privacy & Screen SharingMake Chrome Yours
Blur ScreenTools
BlurMask — Blur Screen Share & Hide Sensitive DataMake Chrome Yours
Frequently asked questions
Is Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing safe to use?
Our latest automated scan rates the Chrome listing of Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing at 78/100 (some 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 Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing require?
Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing requests 5 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing?
Blur Data: Hide Sensitive Info & Blur Your Screen When Screen Sharing is published by Invictus. 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.2.9
- Current listed version
- 0.2.9
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 1 critical and 0 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.