Privacy Policy

Magellan is a Google Chrome extension that helps Salesforce administrators and developers review Apex classes, Apex triggers, Flows, and Lightning Web Components against best-practice rules (SOQL in loops, missing sharing declarations, hardcoded Ids, missing fault paths, and others), scan a whole org for the same findings, and see which components are currently failing at runtime.

What Magellan reads, and from where

• Your Salesforce session cookies (sid) — Magellan reads the sid cookie for the Salesforce org open in your tab (and, for the org switcher, for other Salesforce orgs you are currently logged into) to authenticate its API requests as you, against your org. 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 code and metadata — Apex class and trigger bodies, Flow definitions, Lightning Web Component source files, component names and Ids, dependency relationships (MetadataComponentDependency), and installed managed-package class names — read via the Salesforce Tooling API. This is what the rules engine analyzes. It is analyzed in your browser and displayed to you in the Magellan side panel, Atlas, and Universe views.
• Runtime failure records — recent failed or aborted asynchronous Apex jobs (AsyncApexJob) and errored Flow interviews (FlowInterview), read via the Salesforce REST API, to show you which components are currently failing ("What's on fire"). Magellan reads stored results only; it never runs, retries, or aborts a job.
• Org identity — your org's Id, name, and whether it is a sandbox or production, so the UI can label which org you are looking at.

Where the analysis happens

In your browser, and only there. The rules engine is pure client-side code bundled with the extension. It has no network access of its own — it cannot upload your code even if it wanted to. The org-wide scan (Atlas / Universe) is the moment other tools upload an entire codebase to a cloud service; Magellan does not.

What Magellan can change in your org

Nothing. Magellan is read-only by construction. Its network layer issues only HTTP GET requests — there is no code path in the extension that writes, updates, deletes, executes, or deploys anything in any org, sandbox or production. Findings are shown to you with a "Fix" hint and a documentation link; you make any change yourself, with your own tools.

What Magellan stores, and where

• IndexedDB (in your browser) — a per-org cache of fetched component source/metadata (24 hours) so repeat analyses and org scans are fast. Stored per Salesforce org Id. Nothing here is synced across devices.
• chrome.storage.local (in your browser) — your settings, such as the theme and whether you have seen the first-run tour.
• chrome.storage.session (in your browser) — which component is currently open in each Salesforce tab, so the side panel follows you; cleared when you close the browser.

Nothing Magellan writes leaves your device. Exports (CSV / JSON of scan findings) are files handed to you, saved wherever you choose.

What Magellan does NOT do

• Magellan 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.
• Magellan has no analytics, telemetry, or tracking. We do not know when you install, open, or use the extension, which orgs you point it at, or what it finds, and we do not want to. (The license server sees a PRO activation or trial start, as described below. It never learns which org you use or what Magellan found.)
• Magellan has no advertising. We do not sell or transfer data to third parties.
• Magellan does not fetch or execute remote code. All JavaScript, including the 3D globe library, ships with the extension and is reviewed by the Chrome Web Store.

Third-party services

Magellan makes network requests to two destinations, and no others:

1. Your own Salesforce org's domains (*.salesforce.com, *.force.com, *.salesforce-setup.com), for the read-only metadata reads described above.
2. Our license server (license.creedysolutions.com), only when you start the free PRO trial, activate a PRO license key, or when an activated key renews (about once a day while you're online). The request carries the license key you typed (or nothing, for a trial), a random install identifier that Magellan generated locally (it is not derived from your machine, browser profile, or any Salesforce org), and the product name. Magellan also asks the same server whether checkout is open, which sends nothing about you. No Salesforce data, cookies, org IDs, or metadata are ever sent to the license server. If you only use the free side panel, Magellan never contacts it.

Payment itself is handled entirely by our merchant of record (Lemon Squeezy) on their own pages. Magellan never sees your payment details. Documentation links in findings (to PMD, Salesforce Help, and similar public sites) open only if you click them.

Chrome permission usage

• sidePanel — draws Magellan's findings UI as a side panel.
• storage — stores your settings locally, and, if you use PRO, the license key, install identifier and signed license token on this browser.
• cookies — reads the Salesforce session cookies, as described above, to authenticate read-only API requests as you against your own org.
• tabs — knows which Salesforce tab you are looking at, so the panel analyzes the component you have open and the scan targets the right org.
• Host permissions — *.salesforce.com, *.force.com, *.salesforce-setup.com — the only domains Magellan 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 Magellan release notes.

Contact

Questions: [email protected]