Is Saygo Browser safe to install?
Saygo Browser asks for 4 browser permissions and declares no blanket site access. 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.
Chrome extension by williamda.dwl · Productivity · Developer
What the developer says, and 2 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
- No site access
- Data collection
- 9 kinds of data declared
- Upkeep
- Updated 4 days ago
- Publisher
- No store badges
- Audience
- 1 user
What data it declares
The developer declares that it collects these kinds of data:
- Personally identifiable information such as name, address, email address or age
- Health information such as heart rate, medical history or symptoms
- Financial and payment information such as transactions, card numbers or credit history
- Authentication information such as passwords, credentials or PIN codes
- Personal communications such as emails, texts or chat messages
- Location such as region, IP address or GPS coordinates
- Web history the list of pages you visit
- User activity such as clicks, scrolling, keystrokes or network monitoring
- Website content such as text, images or links on the pages you open
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:
- Read and change all your data on all websites
- Read your browsing history
- Communicate with cooperating native applications
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
No site access is declared in the manifest, so it cannot read the pages you open on its own.
Reaches your browsing data or every site
-
Attach to pages the way developer tools do
debugger -
Talk to an application installed on your computer
nativeMessaging -
See the address and title of every tab you have open
tabs
Routine for an extension
-
Store data in your browser
storage
How usual this is for its category
In Productivity · Developer, 31% of extensions ask for access to every site. This one: No site access.
The typical extension there declares 3 browser permissions; this one declares 4 browser permissions.
- Attach to pages the way developer tools do (debugger): 4% of extensions in this category ask for it.
- Talk to an application installed on your computer (nativeMessaging): 2% of extensions in this category ask for it.
- See the address and title of every tab you have open (tabs): 27% of extensions in this category ask for it.
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
1 user
- 2026-10-041appeared in the store
- 2026-10-071
- Last updated in the store 4 days ago, on 2026-10-03.
- No new version in the last 90 days.
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.
The permissions this extension requests have not changed since we started watching it.
Who publishes it
williamda.dwl. This listing has been in the store since 2026-10-03 and was last updated on 2026-10-03.
How to check or remove it in Chrome
- Type chrome://extensions in the address bar and find the extension in the list.
- 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.
- To uninstall it, choose Remove on the same page.
Questions people ask
- What can Saygo Browser access?
- No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 4 browser permissions.
- What data does Saygo Browser collect?
- The developer declares that it collects these kinds of data: Personally identifiable information, Health information, Financial and payment information, Authentication information, Personal communications, Location, Web history, User activity, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
- Has Saygo Browser asked for more permissions over time?
- The permissions this extension requests have not changed since we started watching it.
- Does Saygo Browser publish a privacy policy?
- Yes, the store listing links to a privacy policy.
We read the public store listing once 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-07.