Is Bulk Slack User Deactivation safe to install?

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

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 your data on all slack.com sites and api.lemonsqueezy.com

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: 2 match patterns.

• *://*.slack.com/ slack.com and all its subdomains
• https://api.lemonsqueezy.com/v1/* only api.lemonsqueezy.com

Reaches your browsing data or every site

• Watch the network requests your browser makes webRequest

Routine for an extension

• Store data in your browser storage

Pages it runs its code on

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

• *://*.slack.com/admin slack.com and all its subdomains
• *://*.slack.com/manage/*/people slack.com and all its subdomains

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 · Workflow, 19% of extensions ask for access to every site. This one: Access to specific sites only.

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

• Watch the network requests your browser makes (webRequest): 3% 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

219 users

• Last updated in the store 312 days ago, on 2025-12-23.
• No new version in the last 90 days.

What the store shows

• Established publisher The store's badge for publishers with a good record and no history of violations.

The listing says it offers in-app purchases.

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

lihster.developer, who publishes 13 listings we track. This listing has been in the store since 2023-05-02 and was last updated on 2025-12-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 Bulk Slack User Deactivation access?

Specific sites only: 2 match patterns. It declares 2 browser permissions.

What data does Bulk Slack User Deactivation collect?

The developer declares that it collects these kinds of data: Personally identifiable information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

Has Bulk Slack User Deactivation asked for more permissions over time?

The permissions this extension requests have not changed since we started watching it.

Does Bulk Slack User Deactivation publish a privacy policy?

Yes, the store listing links to a privacy policy.