Ext Ops Panel
Open dashboard
Permissions and history

Is Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield safe to install?

Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield asks for 5 browser permissions and 1 site pattern. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield

Chrome extension by Sky Dream Workshop · Make Chrome Yours · Privacy

Open in the Chrome Web Store
What the developer says, and 5 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Runs its code on every site
Data collection
5 kinds of data declared
Publisher
No store badges
Audience
58 users · 1.0/5

What data it declares

The developer declares that it collects these kinds of data:

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Specific sites only: 1 match pattern.

Worth knowing

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

Show the remaining 20
  • https://*.goto.com/* goto.com and all its subdomains
  • https://*.loom.com/* loom.com and all its subdomains
  • https://*.webex.com/* webex.com and all its subdomains
  • https://*.zoom.com/* zoom.com and all its subdomains
  • https://*.zoom.us/* zoom.us and all its subdomains
  • https://app.gather.town/* only app.gather.town
  • https://app.livestorm.co/* only app.livestorm.co
  • https://app.slack.com/* only app.slack.com
  • https://discord.com/* only discord.com
  • https://meet.google.com/* only meet.google.com
  • https://meet.jit.si/* only meet.jit.si
  • https://meeting.zoho.com/* only meeting.zoho.com
  • https://riverside.fm/* only riverside.fm
  • https://streamyard.com/* only streamyard.com
  • https://studio.restream.io/* only studio.restream.io
  • https://teams.cloud.microsoft/* only teams.cloud.microsoft
  • https://teams.live.com/* only teams.live.com
  • https://teams.microsoft.com/* only teams.microsoft.com
  • https://video.ringcentral.com/* only video.ringcentral.com
  • https://whereby.com/* only whereby.com

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Make Chrome Yours · Privacy, 42% of extensions ask for access to every site. This one: Runs its code on every site.

The typical extension there declares 3 browser permissions; this one declares 5 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

58 users

Users
+18 since 01.09
39-58 · 22 readings
2026-10-22: released 3.0.0
  1. 2026-09-0140
  2. 2026-09-0239
  3. 2026-09-0841
  4. 2026-09-0942
  5. 2026-09-1346
  6. 2026-09-1647
  7. 2026-09-2147
  8. 2026-09-2556
  9. 2026-09-2758
  10. 2026-09-2857
  11. 2026-10-0456
  12. 2026-10-0854
  13. 2026-10-0955
  14. 2026-10-1053
  15. 2026-10-1651
  16. 2026-10-1850
  17. 2026-10-2151
  18. 2026-10-2452
  19. 2026-10-2554
  20. 2026-10-2756
  21. 2026-10-2958
  22. 2026-10-3158

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

  1. Asked for more permissions (6, was 3) (changed: pages it runs its code on, browser permissions)
  2. Privacy policy link added to the listing

Versions we have seen

  1. Version 3.0.0 · Asked for more permissions (6, was 3) (changed: pages it runs its code on, browser permissions)

Who publishes it

Sky Dream Workshop. This listing has been in the store since 2026-03-04 and was last updated on 2026-10-22.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. BlurGuard Runs its code on every site · 2 permissions 8 users
  2. DataBlur: Blur Screen & Hide Sensitive Data for Screen Sharing Runs its code on every site · 3 permissions 3k users ★ 4.9
  3. BlurShare: Click-to-Blur for Screen Sharing No site access · 3 permissions 15 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield access?
Specific sites only: 1 match pattern. It declares 5 browser permissions.
What data does Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Financial and payment information, Authentication information, Web history, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-10-22.
Does Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-10-31.

Back to Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield · Alternatives to Auto Blur Sensitive Info for Screen Sharing & Demos | ScreenShield

Where the data comes from: how the catalog is built