Ext Ops Panel
Open dashboard
Permissions and history

Is PDF Toolkit: Merge, Split, Compress & Edit PDFs safe to install?

PDF Toolkit: Merge, Split, Compress & Edit PDFs declares no browser permissions and no site access in its manifest, which is as narrow as an extension gets. 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.

PDF Toolkit: Merge, Split, Compress & Edit PDFs

Chrome extension by bytecode.creation · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 5 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
No permissions at all
Data collection
Declares it collects none
Publisher
Trader
Audience
53 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

From the permissions it declares, Chrome shows no permission warning when you add it.

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.

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: No permissions at all.

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

53 users

Users
+14 since 01.09
39-57 · 33 readings
  1. 2026-09-0139
  2. 2026-09-0342
  3. 2026-09-0440
  4. 2026-09-0541
  5. 2026-09-0842
  6. 2026-09-0945
  7. 2026-09-1044
  8. 2026-09-1346
  9. 2026-09-1547
  10. 2026-09-1745
  11. 2026-09-2147
  12. 2026-09-2246
  13. 2026-09-2550
  14. 2026-09-2653
  15. 2026-10-0548
  16. 2026-10-0849
  17. 2026-10-1048
  18. 2026-10-1150
  19. 2026-10-1348
  20. 2026-10-1652
  21. 2026-10-1851
  22. 2026-10-1950
  23. 2026-10-2052
  24. 2026-10-2153
  25. 2026-10-2254
  26. 2026-10-2356
  27. 2026-10-2457
  28. 2026-10-2553
  29. 2026-10-2851
  30. 2026-10-3052
  31. 2026-11-0150
  32. 2026-11-0453
  33. 2026-11-0553

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

bytecode.creation. This listing has been in the store since 2025-09-12 and was last updated on 2025-09-12.

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 PDF Toolkit: Merge, Split, Compress & Edit PDFs access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares no browser permissions.
What data does PDF Toolkit: Merge, Split, Compress & Edit PDFs 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 PDF Toolkit: Merge, Split, Compress & Edit PDFs asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does PDF Toolkit: Merge, Split, Compress & Edit PDFs 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-05.

Back to PDF Toolkit: Merge, Split, Compress & Edit PDFs · Alternatives to PDF Toolkit: Merge, Split, Compress & Edit PDFs

Where the data comes from: how the catalog is built