Ext Ops Panel
Open dashboard
Permissions and history

Is Codr Website Cloner safe to install?

Codr Website Cloner asks for 7 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.

Codr Website Cloner

Chrome extension by Nifemi Alpine · Productivity · Workflow

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

Site access
Access to every site
Data collection
1 kind of data declared
Audience
75 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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Reaches your browsing data or every site

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.

How usual this is for its category

In Productivity · Workflow, 19% of extensions ask for access to every site. This one: Access to every site.

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

75 users

Users
+3 since 31.08
70-82 · 36 readings
  1. 2026-08-3172
  2. 2026-09-0275
  3. 2026-09-0474
  4. 2026-09-0573
  5. 2026-09-0770
  6. 2026-09-0872
  7. 2026-09-0971
  8. 2026-09-1376
  9. 2026-09-1582
  10. 2026-09-1780
  11. 2026-09-2180
  12. 2026-09-2579
  13. 2026-09-2778
  14. 2026-09-2880
  15. 2026-10-0478
  16. 2026-10-0882
  17. 2026-10-0980
  18. 2026-10-1676
  19. 2026-10-1878
  20. 2026-10-1977
  21. 2026-10-2078
  22. 2026-10-2177
  23. 2026-10-2375
  24. 2026-10-2477
  25. 2026-10-2576
  26. 2026-10-2672
  27. 2026-10-2875
  28. 2026-10-2972
  29. 2026-10-3073
  30. 2026-11-0170
  31. 2026-11-0273
  32. 2026-11-0474
  33. 2026-11-0676
  34. 2026-11-0777
  35. 2026-11-0973
  36. 2026-11-1075

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

Nifemi Alpine, who publishes 5 listings we track. This listing has been in the store since 2025-03-28 and was last updated on 2025-03-28.

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. NestSynth Runs its code on every site · 3 permissions, 1 site pattern 3 users
  2. DivGenius Access to specific sites only · 4 permissions, 4 site patterns 2 users (last published figure) ★ 5.0
  3. SnapCode — Site to Prompt Access to every site · 3 permissions, 2 site patterns 98 users ★ 5.0

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 Codr Website Cloner access?
Every site you visit. This extension can read and change the content of any page you open. It declares 7 browser permissions.
What data does Codr Website Cloner collect?
The developer declares that it collects these kinds of data: Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Codr Website Cloner asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Codr Website Cloner 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-10.

Back to Codr Website Cloner · Alternatives to Codr Website Cloner

Where the data comes from: how the catalog is built