Ext Ops Panel
Open dashboard
Permissions and history

WhatsApp CRM Pro is no longer in the Chrome Web Store: what it can access

WhatsApp CRM Pro is no longer in the Chrome Web Store: the listing disappeared on 2026-11-12. When it left, it had 14 users. WhatsApp CRM Pro asks for 3 browser permissions and 6 site patterns. 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.

WhatsApp CRM Pro

Chrome extension by EBoat · Productivity · Tools · no longer in the store

What to use instead

Listings still in the store that are closest to it in what they say they do. Comparable, not endorsed.

  1. LeadPlus - Turn your WhatsApp into a powerful CRM Describes nearly the same job, smaller audience 37 users ★ 5.0
  2. Whatsapp CRM for Businesses, with AI Agents - The Chat Quotient Describes nearly the same job, smaller audience 854 users ★ 4.9
  3. ChatCRM - Tag, Notes & Follow-ups for WhatsApp Describes nearly the same job, smaller audience 12 users (last published figure) ★ 5.0
  4. SalesDo.ai CRM for WhatsApp Describes nearly the same job, smaller audience 55 users ★ 5.0
  5. WhatsX Business – CRM & Sales for WhatsApp Web Describes nearly the same job, smaller audience 20 users ★ 5.0

All alternatives, with why each one is close

If you still have it installed

A listing leaving the store does not by itself remove the extension from browsers that already have it. If you still have it, you can see what it can reach and remove it in a minute:

  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.

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
Access to specific sites only
Data collection
Declares it collects none
Upkeep
Updated 167 days ago
Publisher
No store badges
Audience
14 users

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

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 1 site pattern.

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 · Tools, 20% 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 3 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

14 users

Users
+4 since 01.09
9-17 · 26 readings
2026-11-12: removed from the store
  1. 2026-09-0110
  2. 2026-09-049
  3. 2026-09-069
  4. 2026-09-0911
  5. 2026-09-179
  6. 2026-09-2011
  7. 2026-09-2110
  8. 2026-09-2611
  9. 2026-09-2810
  10. 2026-10-0515
  11. 2026-10-0811
  12. 2026-10-0912
  13. 2026-10-1010
  14. 2026-10-1312
  15. 2026-10-1612
  16. 2026-10-1811
  17. 2026-10-1913
  18. 2026-10-2212
  19. 2026-10-2315
  20. 2026-10-2414
  21. 2026-10-2917
  22. 2026-11-0115
  23. 2026-11-0314
  24. 2026-11-0716
  25. 2026-11-0814
  26. 2026-11-1214removed from the store

What the store shows

The listing is no longer in the store, so none of the store's badges apply to it now.

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

EBoat, who publishes 6 listings we track. This listing has been in the store since 2026-06-03 and was last updated on 2026-06-03.

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. Pk Whatsapp Mini Crm No site access · 4 permissions 17 users
  2. Mukaami CRM Access to specific sites only · 1 permission, 4 site patterns audience not published

Questions people ask

What can WhatsApp CRM Pro access?
Specific sites only: 6 match patterns. It declares 3 browser permissions.
What data does WhatsApp CRM Pro 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 WhatsApp CRM Pro asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does WhatsApp CRM Pro 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-11-12.

Back to WhatsApp CRM Pro · Alternatives to WhatsApp CRM Pro

Where the data comes from: how the catalog is built