Privacy Policy

Polo — Org Compare for Salesforce · Effective date: August 2026 · Contact: [email protected]

Polo is a Google Chrome extension that helps Salesforce administrators and developers compare components (fields, flows, Apex classes, layouts, validation rules, Lightning pages, permission sets, and others) across the Salesforce orgs they are logged into, and see each component's change history.

Short version: Polo does not collect any personal data. Polo does not transmit your Salesforce orgs' metadata to any server operated by us, or to any third party. All queries run inside your browser, from your browser directly to your own Salesforce orgs' APIs. Polo only ever reads — it never writes to any org. All caches are stored locally on your device.

What Polo reads, and from where

Your Salesforce session cookies (sid) — Polo compares one component across every Salesforce org you are currently logged into, so it reads the sid cookie for each logged-in Salesforce origin to discover those orgs and to authenticate its API requests as you, against your orgs. This is the same session-reuse pattern used by tools like Salesforce Inspector. A cookie value is never transmitted anywhere except back to the same Salesforce org it belongs to.
Salesforce metadata — component names and definitions, page layouts, validation-rule formulas, flow definitions, Apex bodies, field and object permissions, and dependency relationships — read via the Salesforce Tooling API and REST API. Polo also reads the Setup Audit Trail and flow version history to build each component's change timeline. This metadata is displayed to you in the Polo side panel, Pipeline matrix, and Explore view, and cached locally for performance.

What Polo can change in your org

Nothing. Polo is read-only by construction. Its network layer issues only HTTP GET requests — there is no code path in the extension that writes, updates, or deletes anything in any org, sandbox or production. When you export a package.xml manifest or a release report, Polo hands you a file and the command to run; you perform any retrieve or deploy yourself, with your own tools.

What Polo stores, and where

IndexedDB (in your browser) — cached component metadata, per-org snapshots for change history, and verdict caches, so repeat comparisons are instant. Stored per Salesforce org ID. Nothing here is synced across devices.
chrome.storage.local (in your browser) — your settings and your watchlist, such as which components you are tracking, the compare target per org, the theme, and whether you've seen the first-run tour.
chrome.storage.session (in your browser) — the temporary payload handed to the Explore view when you open it; cleared when you close the browser.

Nothing Polo writes leaves your device.

What Polo does NOT do

Polo has no user accounts. You never create an account with us and never provide us with a username or password. Nothing is installed in your Salesforce org — no connected app, no OAuth, no package.
Polo has no analytics, telemetry, or tracking. We do not know when you install, open, or use the extension, or which orgs you point it at, and we do not want to.
Polo has no advertising. We do not sell or transfer data to third parties.
Polo does not fetch or execute remote code. All JavaScript ships with the extension and is reviewed by the Chrome Web Store.

Third-party services

Polo makes network requests to exactly one kind of destination: your own Salesforce orgs' domains (*.salesforce.com, *.force.com, *.salesforce-setup.com). It contacts no server operated by us, and no other third party.

Chrome permission usage

sidePanel — draws Polo's UI as a side panel.
storage — stores your settings and watchlist locally.
cookies — reads the Salesforce session cookies, as described above, to authenticate read-only API requests as you against your own orgs.
tabs — knows which tab you are looking at, so it uses the right org as the comparison source.
scripting — re-injects Polo's small detection script into a Salesforce tab that was already open before the extension loaded, so detection works without a page reload.
alarms — runs the optional daily re-check of your watchlist and updates the toolbar badge when something has drifted.
Host permissions — *.salesforce.com, *.force.com, *.salesforce-setup.com — the only domains Polo is allowed to talk to.

Changes

If this policy materially changes, we will update the effective date at the top and note the change in the Polo release notes.

Contact

Questions: [email protected]