Ext Ops Panel
Open dashboard
Permissions and history

Is Un-Safelink Outlook safe to install?

Un-Safelink Outlook declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

Un-Safelink Outlook

Chrome extension by Dunky13 · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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 permissions at all
Data collection
Declares it collects none
Publisher
No store badges
Audience
696 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your 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 does not link 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

No site access is declared in the manifest, so it cannot read the pages you open on its own.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

Pages it runs its code on

It runs its own code on specific pages only: 7 site patterns.

Show the remaining 4
  • https://outlook.office.com/mail/* only outlook.office.com
  • https://outlook.office365.com/mail/* only outlook.office365.com
  • https://outlook.cloud.microsoft/mail/* only outlook.cloud.microsoft
  • https://mail.google.com/mail/* only mail.google.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 Productivity · Developer, 30% of extensions ask for access to every site. This one: No permissions at all.

The typical extension there declares 3 browser permissions; this one declares no 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

696 users

Users
+39 since 01.09
657-702 · 31 readings
2026-10-20: released 0.2.92026-10-24: released 0.2.11
  1. 2026-09-01657
  2. 2026-09-04671
  3. 2026-09-06673
  4. 2026-09-08667
  5. 2026-09-10664
  6. 2026-09-13669
  7. 2026-09-15681
  8. 2026-09-16693
  9. 2026-09-20682
  10. 2026-09-21688
  11. 2026-09-25690
  12. 2026-09-26683
  13. 2026-09-28677
  14. 2026-10-04702
  15. 2026-10-08695
  16. 2026-10-09683
  17. 2026-10-10682
  18. 2026-10-11681
  19. 2026-10-13680
  20. 2026-10-16684
  21. 2026-10-17680
  22. 2026-10-18675
  23. 2026-10-19679
  24. 2026-10-21678
  25. 2026-10-22675
  26. 2026-10-23673
  27. 2026-10-24671released 0.2.11
  28. 2026-10-27678
  29. 2026-10-29679
  30. 2026-10-31693
  31. 2026-11-01696

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.

Versions we have seen

  1. Version 0.2.11
  2. Version 0.2.9

Who publishes it

Dunky13, who publishes 3 listings we track. This listing has been in the store since 2018-05-03 and was last updated on 2026-10-23.

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 Un-Safelink Outlook access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
What data does Un-Safelink Outlook collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Un-Safelink Outlook asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Un-Safelink Outlook publish a privacy policy?
No, the store listing does not link 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-11-01.

Back to Un-Safelink Outlook · Alternatives to Un-Safelink Outlook

Where the data comes from: how the catalog is built