In short
- OrgNav has no server, no account and no analytics. It never sends anything to OrgNav or to any third party.
- It talks only to the Salesforce org you are already logged into, using your existing login and your own permissions.
- The only things it keeps are your own settings, stored in your browser on your machine.
Who this policy covers
This policy covers the OrgNav browser extension ("OrgNav", "the extension") and the website at orgnav.app. OrgNav is built and published by Michael Aylesbury, an individual developer based in the United Kingdom ("I", "me"). It is not affiliated with, endorsed by, or sponsored by Salesforce, Inc.
If you have a question about this policy, email [email protected].
What the extension reads
OrgNav only has access to Salesforce sites. It reads the following, and only while you use it on a Salesforce page:
- The address (URL) of your Salesforce tabs, to work out which org, page and record you are on.
- Your Salesforce session cookie for that org, so it can call Salesforce on your behalf. It is held in memory only, used only for requests to that same org, and never stored or sent anywhere else.
- The org data you ask for. That includes metadata (objects, fields, flows, Apex, permission sets and so on) and also records: Easy Query runs the queries you write, Record Fields shows the fields of the record you are viewing, and search can find users by name, username or email.
Some of that data is personal information, such as a colleague's name or email address. OrgNav fetches it with your own Salesforce permissions, so you never see anything Salesforce would not already show you. It is displayed in the extension and then discarded.
Where your data goes
Every request the extension makes goes directly from your browser to your own Salesforce org. Nothing goes to OrgNav: there is no OrgNav server, no account, no analytics, no crash reporting, no advertising and no tracking. OrgNav does not sell, rent, share or transfer your data to anyone, and does not use it for any purpose other than showing it back to you.
OrgNav does not load or run code from anywhere other than the extension package itself.
What the extension stores
OrgNav saves your own settings in your browser's extension storage, on your machine only:
- Saved orgs: the org's address, and the name and colour you give it.
- Your quick-nav layout: tiles, folders, pinned apps and favourites.
- Bundles: the names of the components you add, each component's Salesforce ID so it can link back to it, the address of the org the bundle belongs to, and any notes and links you write.
- Display preferences, such as dark mode and where the edge tab sits on the page.
- A short note for each org you use OrgNav with, kept against that org's address: whether your user can use the Dev Console there (so its tab appears without a delay) and whether you dismissed the offer to save that org.
Some short-lived interface state is kept in session storage, which your browser clears when it closes. OrgNav does not store org records, query results or your session.
This data never leaves your browser and is not synced between devices. Removing the extension deletes it. The exports in Bundles and Easy Query (Markdown, package.xml, CSV and so on) are files you choose to save or copy yourself.
Changes the extension can make in your org
OrgNav is mostly read-only. A few features change your org, only when you use them, and only within your own Salesforce permissions:
- Editing a field value on a record saves that change to the record.
- Running anonymous Apex executes the code you write, which can change anything that code changes.
- Capturing a debug log for anonymous Apex creates a debug level named "OrgNav Dev Console" and a trace flag for your user, or extends one you already have.
- "Log in as" logs you in as another user, using Salesforce's own login-as feature. It is offered only if your user is allowed to do that.
These changes happen in your org and are recorded by Salesforce in the same way as if you had made them in Salesforce directly.
Chrome Web Store user data policy
OrgNav's use of information received from Salesforce adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Feedback and email
The extension's "Report a bug or request a feature" form opens an email in your own email app, addressed to [email protected], or copies the report for you to paste. Nothing is sent until you send it yourself. Any diagnostics attached are shown to you first and never include your org's address, session or data.
If you email [email protected], I receive your email address and whatever you write. I use it only to reply to you and to fix or improve OrgNav, and I delete it when it is no longer needed for that. Email is hosted by Zoho.
For email you send me, I am the controller of that information under UK data protection law. You can ask to see it, correct it or have it deleted by emailing the same address. You also have the right to complain to the Information Commissioner's Office (ico.org.uk).
The website
orgnav.app is a static website. It has no account, no forms, no analytics and no advertising, and it sets no cookies of its own.
It is hosted by Cloudflare, which processes standard technical information such as your IP address to deliver and protect the site. Cloudflare's own privacy policy covers that information. Everything else the site needs, including its fonts, is served from orgnav.app itself, so a visit sends nothing to any other company.
The Chrome Web Store is run by Google. Google's privacy policy covers what it collects when you browse or install from the store, and the store shows me only anonymous totals such as install counts.
Changes to this policy
If what OrgNav does with data changes, this page will change before or alongside it, and the date at the top will change with it. A change that means data leaving your browser would be announced in the changelog and would not apply to you until you update the extension.