Privacy Policy

Marco is a Google Chrome extension that helps Salesforce administrators and developers see where components (fields, flows, Apex classes, layouts, validation rules, LWCs, and others) are used across their org's metadata.

What Marco reads, and from where

• Your Salesforce session cookie (sid) — for the Salesforce origin of the tab you are currently on. Marco uses this cookie value to authenticate its API requests as you, against your Salesforce org. This is the same session-reuse pattern used by tools like Salesforce Inspector. The cookie value is never transmitted anywhere except back to that same Salesforce org.
• Salesforce metadata — component names, dependencies, page layouts, validation-rule formulas, flow definitions, field permissions, object permissions, and object/relationship (schema) definitions used to draw the 3D schema map — read via the Salesforce Tooling API and REST API. This metadata is displayed to you in the Marco side panel and Universe view and cached locally for performance.

What Marco can change in your org (at your explicit request only)

Marco can update the description text of custom fields, flows, and validation rules in your org — and nothing else — when you type a description and click “Save & deploy” in the panel. These writes:

• go directly from your browser to your own Salesforce org's API, using your own session and permissions — never through any other server;
• are only possible in sandbox, scratch, and Developer Edition orgs (production orgs are always read-only in Marco), and only if your user has the “Customize Application” permission;
• change only the description attribute; Marco verifies after each save that nothing else was modified.

Marco never changes anything in your org on its own.

What Marco stores, and where

• IndexedDB (in your browser) — cached dependency results and per-org flow indexes, so repeat queries are instant. One database per Salesforce org ID. Nothing here is synced across devices.
• chrome.storage.local (in your browser) — user settings, such as the per-org overlay toggle and whether you've seen the first-run tour; plus, if you buy PRO, your license key and its signed activation token.
• Page-local storage (localStorage, in your browser) — view preferences for the Universe page, such as which galaxies you've hidden.

Nothing Marco writes leaves your device.

What Marco does NOT do

• Marco has no user accounts. You never create an account with us and never provide us with a username or password.
• Marco has no analytics, telemetry, or tracking. We do not know when you install, open, or use the extension, and we do not want to.
• Marco has no advertising. We do not sell or transfer data to third parties.
• Marco does not fetch or execute remote code. All JavaScript ships with the extension and is reviewed by the Chrome Web Store.

Third-party services

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

1. Your own Salesforce org's domain (*.salesforce.com, *.force.com, *.salesforce-setup.com) — all metadata reads and the optional description edits described above.
2. Marco's license server (license.creedysolutions.com) — only when you activate or renew a PRO license key. This request carries exactly two values: the license key you typed and a random install identifier that Marco generated locally (it is not derived from your machine, browser profile, or any Salesforce org). No Salesforce data, cookies, org IDs, or metadata are ever sent to the license server. If you never buy PRO, Marco never contacts it at all.

Payment itself is handled entirely by our merchant of record (Lemon Squeezy) on their own pages — Marco never sees your payment details.

Future opt-in AI features (not in the current beta)

Future paid versions of Marco may offer an opt-in “Ask Marco” feature that uses Anthropic's Claude API. If you choose to enable it, you provide your own Anthropic API key. Your questions and the minimal context Marco packs around them are sent from your browser directly to Anthropic (api.anthropic.com) using your key. This feature is off by default and does not exist in the current beta.

Chrome permission usage

• sidePanel — draws Marco's UI as a side panel.
• storage — stores user settings locally.
• cookies — reads the Salesforce session cookie, as described above (used for reads and, in developer/sandbox orgs at your request, description updates).
• contextMenus — adds a “Marco: inspect this component” right-click item on Salesforce Setup pages.
• tabs — knows which tab you are looking at, so it queries the right org.
• Host permissions — *.salesforce.com, *.force.com, *.salesforce-setup.com — the only domains Marco 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 Marco release notes.

Contact

Questions: [email protected]