Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield 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: lnnmacapfomfnfnmejcofohhimoebafk
Permissions (5)
- Execute scripts in pages
Related extensions
ScreenBlur - Privacy Screen ShieldMake Chrome Yours
BlurShield - 민감정보 블러 도구Tools
BlurScreen - Blur & Hide Sensitive Info on ScreenTools
BlurShield - Blur Sensitive InfoMake Chrome Yours
ScreenGuard – Blur Sensitive Info When Screen SharingMake Chrome Yours
BlurPilot - Auto-Blur Sensitive Data for Screen SharingTools
Frequently asked questions
Is Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield safe to use?
Our latest automated scan rates the Chrome listing of Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield 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 Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield require?
Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield requests 5 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield?
Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield is published by Sky Dream Workshop. 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
- 3.0.1
- Current listed version
- 3.0.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 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.