ScreenGuard – Blur Sensitive Info 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: dggihakhjjleajeimnfipcgbadkbjdcn
Permissions (5)
- Store local data
- Schedule tasks
- Monitor navigation
Related extensions
Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShieldProductivity
ScreenBlur - Privacy Screen ShieldMake Chrome Yours
BlurScreen - Blur & Hide Sensitive Info on ScreenTools
BlurScreen — Screen Blur for Privacy & Screen SharingMake Chrome Yours
BlurGuardMake Chrome Yours
Blur Data: Hide Sensitive Info & Blur Your Screen When Screen SharingTools
Frequently asked questions
Is ScreenGuard – Blur Sensitive Info When Screen Sharing safe to use?
Our latest automated scan rates the Chrome listing of ScreenGuard – Blur Sensitive Info When Screen Sharing at 82/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 ScreenGuard – Blur Sensitive Info When Screen Sharing require?
ScreenGuard – Blur Sensitive Info When Screen Sharing requests 5 permissions. The most significant: Store local data, Schedule tasks, Monitor navigation. See the full breakdown in the security report.
Who develops ScreenGuard – Blur Sensitive Info When Screen Sharing?
ScreenGuard – Blur Sensitive Info When Screen Sharing is published by robatdas2018. 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
- 1.0.17
- Current listed version
- 1.0.17
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 2 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.