Ext Ops Panel
Open dashboard
Permissions and history

Is DevToolkit for Salesforce — SOQL & Metadata safe to install?

DevToolkit for Salesforce — SOQL & Metadata asks for 5 browser permissions and 3 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.

DevToolkit for Salesforce — SOQL & Metadata

Chrome extension by Srijan (@geekymeeky) · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 3 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 specific sites only
Data collection
2 kinds of data declared
Publisher
Featured
Audience
71 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

Specific sites only: 3 match patterns.

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 specific pages only: 3 site patterns.

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 · Developer, 30% 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 5 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

71 users

Users
+34 since 01.09
37-71 · 30 readings
  1. 2026-09-0137
  2. 2026-09-0238
  3. 2026-09-0540
  4. 2026-09-0643
  5. 2026-09-0842
  6. 2026-09-0944
  7. 2026-09-1045
  8. 2026-09-1350
  9. 2026-09-1548
  10. 2026-09-2047
  11. 2026-09-2146
  12. 2026-09-2547
  13. 2026-09-2649
  14. 2026-09-2850
  15. 2026-10-0451
  16. 2026-10-0853
  17. 2026-10-0954
  18. 2026-10-1156
  19. 2026-10-1360
  20. 2026-10-1668
  21. 2026-10-1867
  22. 2026-10-1965
  23. 2026-10-2167
  24. 2026-10-2268
  25. 2026-10-2362
  26. 2026-10-2564
  27. 2026-10-2766
  28. 2026-10-2970
  29. 2026-11-0171
  30. 2026-11-0271

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

Srijan (@geekymeeky). This listing has been in the store since 2026-06-22 and was last updated on 2026-08-16.

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. sftools No site access · 7 permissions 55 users ★ 5.0
  2. Salesforce Terminal Access to specific sites only · 3 permissions, 4 site patterns 28 users ★ 5.0
  3. Retrieve Metadata/Data from Salesforce Access to specific sites only · 3 permissions, 4 site patterns 460 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 DevToolkit for Salesforce — SOQL & Metadata access?
Specific sites only: 3 match patterns. It declares 5 browser permissions.
What data does DevToolkit for Salesforce — SOQL & Metadata collect?
The developer declares that it collects these kinds of data: Authentication information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has DevToolkit for Salesforce — SOQL & Metadata asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does DevToolkit for Salesforce — SOQL & Metadata 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-02.

Back to DevToolkit for Salesforce — SOQL & Metadata · Alternatives to DevToolkit for Salesforce — SOQL & Metadata

Where the data comes from: how the catalog is built