DewWow Org Launcher Privacy Policy

Short version: Org Launcher runs on your Mac, and your Salesforce data never comes to us. If you subscribe to Data Backup, the subscription check is the only request that identifies you.

This policy covers Org Launcher for Mac and for Windows. Where it names the Mac, the section on the Windows version below says what is different there.

What we collect

One number: how many times the app was started.

When Org Launcher starts, it adds 1 to a public counter on this website. That is the entire mechanism. The request carries no identifier, no account, no subscription key and no device or system details, and our server records no IP address, cookie or session for it. What we end up with is “on this date the app was started N times”, which cannot be traced back to you or your machine, and cannot tell one person starting it often from many people starting it once.

The request does carry one small stamp, made of three parts: the app’s version number, the current time, and a check value worked out from those two. It is there because the address is public, so without it anything that merely follows a link — a search engine, a link preview, a browser loading pages ahead of you — counted as somebody starting the app. That stamp is identical for every copy of a given version, so it tells the app apart from a crawler and nothing else. It cannot tell one installation from another.

You can turn this off in Settings > Privacy, and the counts are published on the product page.

If you want the full detail, every request the app makes is listed on What Org Launcher Calls, including which API version each one asks for.

Beyond that count, the Org Launcher app has no analytics and no crash reporting, and nothing in the app to sign in to. We do not see which orgs you have, which ones you open, or anything you do in the app. Buying Data Backup is an ordinary purchase on this website, and it comes with a DewWow account. The app never signs in to that account. About your subscription, it sends only the subscription check, and a request to release a computer when you take one off your key. The next section explains both.

Data Backup subscriptions

Data Backup is the one part of Org Launcher you pay for, and it is the one place anything identifies you. Two things to be clear about, because they pull in opposite directions and both matter.

Your backups never come to us. The records and the files go from your Salesforce org straight to a folder on your own disk — or to whatever folder you point it at, including an external drive. Nothing is sent to us: there is no DewWow cloud storage and no DewWow server in the middle. If you choose a synced folder, its sync service copies the backup like anything else in it. We have no copy of anything you back up and no way to get one. Those folders hold real records from your org, so they are worth protecting the way you protect any other client data on that Mac.

The subscription check is the one request that identifies a customer, and it only happens once you have entered a subscription key. A copy of the app with no key never contacts our subscription service at all — not during the free trial, which needs no card and no account, and not if you never use backup. When it does run, the body of that request carries exactly three things. Like any request on the internet, it also arrives from an internet address, and our subscription service does not store that address. The three things are:

• your subscription key;
• a one-way code standing for the computer. It is worked out from the Mac’s hardware id and cannot be turned back into it, and one computer is never told another computer’s code;
• the app’s version number.

Nothing else. No org name, no username, no instance, and nothing read from Salesforce. Cookies are switched off for the request and nothing is cached. The answer is a short signed permit that is stored as a file on your Mac, which is what lets a scheduled backup go ahead offline. While the app is open it checks once a day, once more the first time a new version of the app is opened, and whenever you enter a key or press Check Now. A scheduled backup only checks when that permit is close to running out. Once a check has come back, Settings > Subscription lists the computers using your key and lets you take any of the others off it; the Mac you are on is taken off with “Remove Key from This Mac” on the same screen. Your DewWow account shows the same list.

The launch count stays separate and stays anonymous. It is a different request to a different address, it carries no key and no computer code, and subscribing changes nothing about it. Keeping the two apart is deliberate: it is what keeps "that count cannot tell one install from another" true for everybody, subscriber or not. You can switch the launch count off in Settings > Privacy either way.

Buying and cancelling happen on this website, through our own Odoo store and Stripe. That is an ordinary purchase: your name, email and billing details are held for the subscription and the invoice, and Stripe handles the card — we never see the card number. Your subscription record holds the email you bought it with, a one-way hash of the key and its last four characters, and, for each computer using it, its one-way code, the app version it last reported, and when it was first and last seen. It holds nothing about your Salesforce orgs, because nothing about them is ever sent.

This website

The app and this website are separate, and it would be misleading to describe one and let you assume the other. These web pages use Google Analytics, as most websites do, so we can see how many people visit and which pages get read. It runs in your browser while you are on dewwow.com, sets its own cookies, and Google receives your IP address and browser details in the usual way.

It has nothing to do with the app on your Mac. Google Analytics cannot see your Salesforce orgs, your usernames, or anything Org Launcher does, and the app itself never contacts Google. If you would rather not be counted, any ad blocker or browser tracking protection will stop it, and the app works exactly the same either way.

What stays on your computer

Org Launcher reads the Salesforce connections you have already authorized with the Salesforce CLI. All of the following is kept on your Mac, or in the folder you choose for backups. None of it is sent to us:

• Your org list (alias, username, domain, type, and connection status), saved so the app opens instantly.
• Your favorites, recent orgs, and preferences.
• Your query history and saved queries, and how often you query each object.
• Any metadata you extract or compare, saved in your Downloads folder under OrgLauncher Exports and OrgLauncher Compare.
• Before Data Import updates records, the values it is about to replace, and before it deletes records, a list of which ones, saved as CSV files in your Downloads folder under Org Launcher Backups. This is real record data.
• The records downloaded for a duplicate check. These are a copy of real records from your org, kept in one file per check under ~/Library/Application Support/Org Launcher/Dedupe/ — note the space in that folder name, which makes it a different folder from the one above. They can run to hundreds of megabytes and they stay until you delete them.
• Everything Data Backup copies down: the records, the files and the list pairing the two, as CSV files and real files under ~/Library/Application Support/Org Launcher/Backups/ or a folder you choose. This is real data from your org and it can be large. The app removes old backups under the rule you choose; by default it keeps the last three full backups and the changes since each. None of it is ever sent anywhere, except back into your own org when you restore. Before a restore changes records, their current values are saved in the same Downloads folder as Data Import’s.
• Your Data Backup subscription key and the signed permit that goes with it, as files readable by your user only.
• Before a restore from a backup changes any record, the values it is about to replace, saved as a CSV file in your Downloads folder under Org Launcher Backups.

Your Salesforce passwords and access tokens are never stored by Org Launcher. The local cache deliberately excludes them. Logging in happens in the Salesforce CLI and your browser, and those credentials are managed by the CLI, not by us.

Spotlight

So you can open an org from anywhere on your Mac, Org Launcher adds your orgs to Spotlight, macOS’s own search index. It publishes the same details the org card shows — alias, username, login domain and server instance — and nothing else: no passwords, no access tokens, and nothing from inside Salesforce. That index belongs to your Mac and is never sent to us or to anyone else. Turn it off in Settings > Privacy and the entries are removed.

The Windows version

Org Launcher for Windows collects and sends the same things as the Mac version, with these differences:

• It has no Data Backup, so it never sends a subscription key or a computer code.
• It adds nothing to a search index. There is no Spotlight on Windows.
• It keeps its settings, your list of orgs, saved queries, saved duplicate-check setups, the last org-health readings and the copies of records downloaded for a duplicate check in %LOCALAPPDATA%\OrgLauncher on your PC. The same folder holds a diagnostic log, startup.log, which records the app and Windows versions, the processor count and memory, where the app is installed and, in some lines, the names of your orgs. None of it is sent anywhere. Before Data Import changes records, what it is about to replace is saved under Org Launcher Backups in your Documents folder. Metadata you extract goes to your Downloads folder.
• Its update check asks our server for a different small file, /org-launcher/appcast-win.json. Like any web request it carries your IP address and standard request headers, and it names the app and its version. Nothing about you, your orgs or your usage.
• Its switches are in its own Settings window. Send an anonymous launch count, Check for new versions automatically and the outage and maintenance status from Salesforce Trust are on until you turn them off. Check DNS records as well as Salesforce and the once-a-day check of every org are off until you turn them on. DNS lookups go through the DNS resolver your PC uses.

Network connections

Org Launcher connects to the network only when:

• You use a feature on an org. Query, Data Import, Find Duplicates, Storage and Limits, Release Updates, Email Domains, the Setup Audit Trail and metadata changes talk only to that org, as your own login. So do the once-a-day checks of every org, which are off until you turn them on in Settings. Nothing from them comes to us.
• You turn on the DNS check for email domains. It is off until you turn it on. The app then looks up DKIM, SPF and DMARC records through the DNS resolver your Mac uses, and that resolver can see which domains are being checked.
• You open an org or copy a login link. The app asks the Salesforce CLI for a login URL, which goes to your Salesforce org, not to us.
• The app checks Salesforce Trust for outages and maintenance. It asks api.status.salesforce.com, Salesforce’s own status service, for the public status of each server instance your orgs are on, so it can flag an instance having an incident and show upcoming maintenance and release dates. Because it asks about specific instances, Salesforce can see which instances you look up. Nothing else is sent with those requests: no org names, no usernames, no account, no identifier. Results are cached on your Mac and refreshed about twice a day. You can turn this off in Settings > Privacy.
• The app checks for updates. It requests a small version file from our server. That request includes your IP address and standard request headers, as any web request does. It contains no information about you, your orgs, or your usage. You can turn it off in Settings > Updates.
• The app adds 1 to the launch counter when it starts, as described above. You can turn it off in Settings > Privacy.
• Data Backup reads your org, and checks your subscription. The records and files it copies come from your own Salesforce org and go to a folder you choose. They go back into the org only when you restore. The subscription check goes to this website, only once you have entered a subscription key, and so does a request to release a computer when you take one off your key — see the section above for exactly what the check sends.

Deleting your data

Quit Org Launcher and delete both of these folders and the preferences file. Their names differ only by a space, so it is easy to remove one and leave the other:

• ~/Library/Application Support/OrgLauncher/ — the org list, preferences, query history and saved duplicate setups.
• ~/Library/Application Support/Org Launcher/ — with a space. This one holds the records downloaded for duplicate checks, so it is the one that matters most if those records came from a customer's org.
• ~/Library/Preferences/com.dewwow.orglauncher.plist
• In your Downloads folder: Org Launcher Backups, OrgLauncher Exports and OrgLauncher Compare. Org Launcher Backups holds real record data.
• If you used Data Backup: the backups themselves, which are inside the second folder above unless you chose somewhere else — so check the folder you picked. If you had a schedule turned on, turn it off in the app before deleting it, or delete ~/Library/LaunchAgents/com.dewwow.orglauncher.backup.plist by hand; deleting the app alone leaves that file behind.

Removing an org inside the app logs that org out of the Salesforce CLI on your Mac. It does not change or delete anything in Salesforce.

Children

Org Launcher is a professional tool and is not directed at children under 13.

Changes

If this policy changes, we will update the date above and post the revision on this page.

Contact

Questions: ejbantz@dewwow.com

Org Launcher is published by DewWow LLC, a Wisconsin limited liability company.

Questions?

Email ejbantz@dewwow.com and include the version number from Org Launcher > About Org Launcher.

Overview  ·  Find duplicates  ·  Data Backup  ·  Release notes  ·  Privacy  ·  What it calls

DewWow LLC · Wisconsin’s Odoo Partner · dewwow.com

Salesforce and related marks are trademarks of Salesforce, Inc. Org Launcher is an independent product and is not affiliated with, endorsed by, or sponsored by Salesforce, Inc.