OrgHopOrgHop Privacy Policy
OrgHop helps you search and open Salesforce Setup pages, apps, objects and records. It works entirely inside your browser. OrgHop has no servers, no accounts, no analytics and no advertising, and the developer never receives any of your data.
The short version
- OrgHop only talks to the Salesforce org you are already signed in to, using your existing browser session.
- Nothing is sent to the developer or to any other third party.
- Your Salesforce session cookie is read only when needed. It is never saved and never leaves your browser except in requests to your own org.
- The only thing OrgHop keeps after you close the browser is your list of pinned Setup pages.
Information OrgHop uses
| What | Why | Where it is kept |
|---|---|---|
Your Salesforce session cookie (sid) for the org in the current tab |
To call your org's Salesforce REST API as you, so OrgHop can show your apps, objects and matching records. | Read from the browser when a request is made and held only in memory for that request. It is never written to storage or to logs. A short one-way fingerprint of it (part of a SHA-256 hash, from which the session id cannot be recovered) is kept with the cached lists below, so that after a new sign-in, or "Log in as" another user, OrgHop never shows the previous user's lists. |
| Org details: org name, org id, whether it is a sandbox, and your Salesforce username | To show which org and user you are working in. | Shown in the extension. Cached in chrome.storage.session. |
| Lists of the apps and objects you can access, and object metadata | To let you search and open them. | Cached in chrome.storage.session, which Chrome clears when the browser closes. |
| Your search text and the matching record names | To find records in your org as you type. | Sent only to your org's search API. Results are shown and then discarded. Search text is not stored. |
| Pinned Setup pages | To keep your favorite pages at the top. | chrome.storage.sync: only the ids of the pinned pages, such as "Users" or "Flows". If Chrome sync is on, Google syncs them between your browsers. |
| A diagnostics log of recent errors and events (last 100 entries) | To help you report a bug. | chrome.storage.session, cleared when the browser closes. Before saving, OrgHop removes session ids, access tokens, email addresses and usernames, record and org ids, query values, org-specific parts of hostnames, and the addresses of non-Salesforce pages. |
Who receives your data
Only Salesforce, at the org you are already signed in to, through requests to that org's own REST API (/services/data/…) on Salesforce domains. OrgHop does not sell, rent, share or transfer your data to anyone. It does not use your data for advertising, credit decisions or any purpose other than navigation.
The diagnostics report is shown to you in the extension. It leaves your browser only if you click "Copy" and paste it somewhere yourself, for example in a bug report. The "Report a bug" link opens a public GitHub form at github.com/bizstow/orghop and sends no data with it.
Permissions
- cookies: to read your Salesforce session cookie so OrgHop can call your org's API as you.
- scripting: to add OrgHop's own bundled content script to a Salesforce tab that was already open before OrgHop was installed or updated, so the search overlay still opens there. No remote code is ever run.
- storage: to keep your pins and the session caches described above.
- Host access to Salesforce domains (
salesforce.com,lightning.force.com,salesforce-setup.com): to see which org the active tab is on, run the search overlay on your org's pages, and call your org's API. OrgHop runs only on Salesforce org pages, not on other Salesforce sites such as Help or Trailhead, and not on any other website.
Your choices
Unpinning a page removes it from storage. Closing the browser clears all session data. Uninstalling OrgHop removes everything it stored. Signing out of Salesforce ends the session OrgHop uses.
Children
OrgHop is a tool for Salesforce users and is not directed at children.
Changes
If this policy changes, the new version will be posted at this address with a new effective date.
Contact
Questions about this policy: anas.dev01@gmail.com.