Ext Ops Panel
Open dashboard
Permissions and history

Is ClientPoint safe to install?

ClientPoint asks for 1 browser permission 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.

ClientPoint

Chrome extension by cws-developers · Lifestyle · Social

Open in the Chrome Web Store
What the developer says, and 4 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.

Data collection
1 kind of data declared
Audience
76 users · 5.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

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

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.

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 Lifestyle · Social, 8% of extensions ask for access to every site. This one: Runs its code on every site.

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

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

76 users

Users
+3 since 01.09
70-86 · 34 readings
  1. 2026-09-0173
  2. 2026-09-0274
  3. 2026-09-0470
  4. 2026-09-0574
  5. 2026-09-0671
  6. 2026-09-0876
  7. 2026-09-1077
  8. 2026-09-1579
  9. 2026-09-1776
  10. 2026-09-2073
  11. 2026-09-2172
  12. 2026-09-2576
  13. 2026-09-2680
  14. 2026-09-2879
  15. 2026-10-0483
  16. 2026-10-0881
  17. 2026-10-0976
  18. 2026-10-1077
  19. 2026-10-1180
  20. 2026-10-1384
  21. 2026-10-1686
  22. 2026-10-1885
  23. 2026-10-1982
  24. 2026-10-2078
  25. 2026-10-2182
  26. 2026-10-2280
  27. 2026-10-2378
  28. 2026-10-2477
  29. 2026-10-2575
  30. 2026-10-2876
  31. 2026-10-2980
  32. 2026-11-0178
  33. 2026-11-0377
  34. 2026-11-0676

What the store shows

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

cws-developers. This listing has been in the store since 2023-04-06 and was last updated on 2025-09-04.

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 ClientPoint access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 1 browser permission.
What data does ClientPoint 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 ClientPoint asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does ClientPoint 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-06.

Back to ClientPoint · Alternatives to ClientPoint

Where the data comes from: how the catalog is built