Is OrgForge — Power Suite for Salesforce Builders safe to install?

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

When you add it, Chrome asks you to allow it to:

• Read and change your data on a number of websites
• Read your browsing history
• Display notifications

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: 10 match patterns.

• https://*.salesforce.com/* salesforce.com and all its subdomains
• https://*.force.com/* force.com and all its subdomains
• https://*.lightning.force.com/* lightning.force.com and all its subdomains
• https://*.cloudforce.com/* cloudforce.com and all its subdomains
• https://*.salesforce-setup.com/* salesforce-setup.com and all its subdomains
• https://*.sfdc.net/* sfdc.net and all its subdomains
• https://*.visualforce.com/* visualforce.com and all its subdomains
• https://*.my.salesforce.com/* my.salesforce.com and all its subdomains
• https://*.sandbox.my.salesforce.com/* sandbox.my.salesforce.com and all its subdomains
• https://*.scratch.my.salesforce.com/* scratch.my.salesforce.com and all its subdomains

Reaches your browsing data or every site

• Read and change cookies on the sites it can access cookies
• See the address and title of every tab you have open tabs

Routine for an extension

• Schedule work to run later alarms
• Show you notifications notifications
• Store data in your browser storage

Pages it runs its code on

It runs its own code on specific pages only: 4 site patterns.

• https://*.salesforce.com/* salesforce.com and all its subdomains
• https://*.force.com/* force.com and all its subdomains
• https://*.lightning.force.com/* lightning.force.com and all its subdomains

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.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse.

• https://api.anthropic.com/* only api.anthropic.com
• https://api.openai.com/* only api.openai.com
• https://generativelanguage.googleapis.com/* only generativelanguage.googleapis.com

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.

• Read and change cookies on the sites it can access (cookies): 7% of extensions in this category ask for it.
• See the address and title of every tab you have open (tabs): 26% of extensions in this category ask for it.

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

13 users

• Last updated in the store 23 days ago, on 2026-10-20.
• We have seen 3 new versions in the last 90 days.

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.

1. 2026-10-20Changed where it works (changed: optional site access)

Versions we have seen

1. 2026-10-20Version 1.5.0 · Changed where it works (changed: optional site access)
2. 2026-09-28Version 1.4.0
3. 2026-09-07Version 1.3.2

Who publishes it

Vamsee K, who publishes 2 listings we track. This listing has been in the store since 2026-04-25 and was last updated on 2026-10-20.

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. Salesforce PlayGround Access to specific sites only · 1 permission, 4 site patterns 280 users ★ 5.0
2. OrgKit Access to specific sites only · 3 permissions, 5 site patterns 13 users ★ 5.0
3. OrgCraft – Developer Tools for Salesforce Access to specific sites only · 4 permissions, 4 site patterns 10 users

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 OrgForge — Power Suite for Salesforce Builders access?

Specific sites only: 10 match patterns. It declares 5 browser permissions.

What data does OrgForge — Power Suite for Salesforce Builders 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 OrgForge — Power Suite for Salesforce Builders asked for more permissions over time?

Its permissions changed once while we watched, on 2026-10-20.

Does OrgForge — Power Suite for Salesforce Builders publish a privacy policy?

Yes, the store listing links to a privacy policy.