Ext Ops Panel
Open dashboard
Permissions and history

Is WebPT Extension safe to install?

WebPT Extension asks for 4 browser permissions and 1 site pattern. 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.

WebPT Extension

Chrome extension by lokesh.nttf · Make Chrome Yours · Functionality

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
Runs its code on every site
Data collection
2 kinds of data declared
Publisher
No store badges
Audience
27 users

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

Specific sites only: 1 match pattern.

Worth knowing

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.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 1 site pattern.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Make Chrome Yours · Functionality, 12% 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 4 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

27 users

Users
+1 since 01.09
25-30 · 23 readings
  1. 2026-09-0126
  2. 2026-09-0327
  3. 2026-09-0928
  4. 2026-09-1529
  5. 2026-09-1727
  6. 2026-09-2126
  7. 2026-09-2529
  8. 2026-09-2630
  9. 2026-09-2829
  10. 2026-10-0930
  11. 2026-10-1029
  12. 2026-10-1127
  13. 2026-10-1626
  14. 2026-10-1925
  15. 2026-10-2127
  16. 2026-10-2226
  17. 2026-10-2427
  18. 2026-10-2526
  19. 2026-10-2825
  20. 2026-10-2926
  21. 2026-10-3027
  22. 2026-11-0127
  23. 2026-11-0327

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

lokesh.nttf, who publishes 2 listings we track. This listing has been in the store since 2023-09-12 and was last updated on 2024-08-17.

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. intake.ninja No site access · 3 permissions 2 users
  2. MDTimeline Form Filler Runs its code on every site · 3 permissions 12 users
  3. FirstVisitMD Chrome Extension No site access · 3 permissions 3 users (last published figure)

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 WebPT Extension access?
Specific sites only: 1 match pattern. It declares 4 browser permissions.
What data does WebPT Extension collect?
The developer declares that it collects these kinds of data: Personal communications, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has WebPT Extension asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does WebPT Extension 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-03.

Back to WebPT Extension · Alternatives to WebPT Extension

Where the data comes from: how the catalog is built