Privacy
Last updated 4 October 2026.
Northern Commander is a file manager that runs on your computer. It needs no network connection to work, and we don’t ask who you are.
This page says what the application sends, and when: what it asks for on its own, the reports it sends only if you agree, and what happens when you ask us for help. It covers the application and our website.
The short version
- No account. Nothing to sign up for, nothing to sign in to.
- No ads, and nothing we collect is sold, rented or shared for advertising.
- We don’t collect your files or what is in them.
- It needs no network to work. With one, it checks whether there is a newer version.
- Reports are off until you turn them on, and can be turned off again at any time.
What stays on your machine
The application keeps its own things in a folder in your home directory,
~/.northern-commander: your settings, where you have been and what you have run, the state of
your panes, a log of each run, and any report waiting for you to decide whether to send it. They
are ordinary files, and you can read or delete them.
When you use the built-in terminal, the commands you run are yours — where they connect, and what they send, is between them and you. The same goes for connections you set up yourself, to a server or to cloud storage: they go where you point them, and we are not in the middle of them.
Anything sent over the network
Whatever the application or the website sends carries your IP address, as every request on the internet does, and the servers that receive it log it, as servers do. A rough location — a country, a city — can be worked out from an address. Those logs are kept by whoever runs the server, for as long as they keep their own logs; we don’t copy them out or keep them ourselves, and we don’t use them to find out who you are or to connect one thing you sent with another. What you choose to give us, such as an email address, we have because you gave it.
Checking for updates
The application asks our download host whether a newer version exists. This is on by default and you can switch it off in Settings.
The request carries no identifier. What our host sees is what any web server sees: your IP address, the time, and a line naming the application and the version you are running. The files are served by Cloudflare, who keep those request records briefly for security and for counting downloads.
Reports you choose to send
The application asks on first launch, and nothing is sent until you say yes. Settings has the same choices. Depending on the choices the application offers, reports go automatically or after you have looked at them, and turning them off stops the sending straight away.
Each section below says what kind of thing a report holds, what it is for, what it never holds, and who receives it. Those are the promises. What the current version sends is set out in more detail in the documentation of the Privacy settings, and the release notes say when a version starts sending something more.
Like any server, the ones that receive a report see the network address it came from. The application tells both of them not to keep it and not to work out a location from it.
Crash reports
When something goes wrong in the application — it crashes, hits an error of its own, stops responding, or leaves you waiting for something that never finishes — it can send a report so we can fix it. A report holds three kinds of thing:
- What went wrong, and where in the program: the error’s message, the place in the code it came from, how long a freeze or a wait lasted.
- What the application was doing: the commands it was carrying out, by name and never what they were used on. Where it was waiting for something that never came, what that was is said only as a rough size and the kind of disk it is on, never its name or where it is.
- What it was running on: the application and macOS versions, your Mac’s processor type and memory, how the application’s own memory and threads stood at that moment.
It carries a random identifier, so that fifty crashes from one computer are not read as fifty broken computers.
A report never holds your files, what is in them, or what you typed. Before a report is sent, or kept for you to decide on, the application takes out your user name wherever a path carries it, and what would name your Mac. An error the application caught is reported in fixed wording, without the file or folder it was about. One thing we cannot rule out: the message of a crash is written by whatever failed, and it can still name the file it was about.
You can have these reports sent automatically, or be asked each time. Asked each time, a report is kept on your computer and nothing is sent; the next time the application starts it lists what was kept and asks whether to send it, and you can read each one first, exactly as it would go.
For a crash too deep for the application to report itself, macOS writes its own crash file, and on the next launch the application can report from that instead. It takes the same kind of thing from the file and nothing else: the identifier macOS keys to your machine is not part of it, and neither is anything else in there about you or your computer.
The same choice covers the counts that say whether a release is healthy: how many runs there were, on which versions, and how many of them ended badly. These carry a random identifier that Sentry’s library keeps on your Mac, separate from the one on a crash report, so that runs are counted by computer.
Crash reports go to Sentry (Functional Software, Inc.), in an organization hosted in the European Union, in Frankfurt. Sentry is an American company: its data is stored in the EU, and its staff can reach that data in order to run the service. It processes the reports only on our instructions, under its data processing addendum. Reports are kept for as long as Sentry keeps them on our plan, and then deleted.
Usage reports
Separately, you can let the application say how it is used. It is how we find out which parts are worth the work. A usage report holds four kinds of thing:
- What was done, and how it was reached: that a command was run from its shortcut or from a menu, that the editor was opened, that a setting was changed.
- What kind of file it was about: the kind, never the file. What our list of file types
calls it — an image, an archive — and its extension, such as
.json. - How it went, and how long it took: sizes, durations and the number of files in an operation are rounded before they are sent — about 40 MB, rather than the exact figure.
- What it was running on: the application and macOS versions, the processor type, the language your system is set to, the shell the terminal starts.
It carries its own random identifier, separate from the one on a crash report, so that a month of use from one computer is not read as a month of use from many.
Usage reports never carry what you type, the names of your files and folders, or anything inside them. What you searched for, where your panes are standing, and what you ran in the terminal stay on your machine.
As the application grows it will measure more things of these four kinds. The limits in the paragraph above are not ones we move.
Usage reports go to PostHog (PostHog, Inc.), on its European cloud, in Frankfurt. As with Sentry: an American company, data stored in the EU, staff able to reach it to run the service, and processing only on our instructions under a data processing agreement. Individual usage events are kept for as long as PostHog keeps them on our plan, and then deleted. Totals worked out from them — how many people used a feature in a month, say — carry no identifier, and we may keep those.
Asking us for help
When you report a problem from inside the application, it sends what you write and a few facts about the application and your Mac: which version and build, which macOS, which processor. You can choose to include the logs of your recent runs — plain text, with your user name already taken out of the paths in them. The screen shows everything that would go, and you can read it before you send.
Two things are offered there and sent only if you leave them in. If you send crash reports, the identifier they carry can go with your description, so that we can find the crashes it is about; without it, nothing connects the two. And you can give an email address, if you want us to have a way to reach you in case we need more information.
Send feedback sends what you write, the choices you make on that screen — which part of the application it is about, for one — the same facts about the application and your Mac, and an email address if you give one. It carries no logs and no identifier.
Both arrive through Cloudflare and are kept in a private repository on GitHub — the description as an issue, any log you included as a file beside it — for as long as they help us fix the problem and recognize it if it comes back. Nothing else about you is part of a report unless you write it in.
To stop anyone flooding it, the service that receives them counts how many arrive from each network address in a day. It counts a scrambled form of the address, made with a key it throws away at the end of each day, so what it keeps cannot be turned back into an address.
If a report cannot be sent — something on your network may be blocking it — the application can save exactly what it would have sent as a file in your Downloads folder, for you to attach to an email to us. Nothing leaves your computer until you send that email.
Email to support@northerncommander.com passes through Cloudflare and is kept in Google Workspace (Google LLC) for as long as the conversation needs it.
We may write up a problem and its answer, in our own words, in our public support repository so that other people can find it. We never publish what you sent as it stands.
The box is a text box, and we cannot tell what you paste into it — so don’t paste passwords or keys.
Your choices, and what you can ask us for
Every choice is in Settings, and you can turn any of them off at any time.
The identifiers a report carries are random and mean nothing outside the service that received it, and we cannot look anyone up by them — which is the other side of not asking who you are: there is no account to find you in. Crash reports and individual usage events are deleted when their service stops keeping them on our plan, whether or not anybody asks.
Depending on where you live you may have rights to see what we hold about you, to correct it, to have it deleted, or to complain to your data protection authority. Write to support@northerncommander.com and we will do what we can with what little we have.
Where European or United Kingdom law applies, our legal basis for the reports is your consent; for what you send us yourself — a problem, feedback or an email — it is answering you and acting on it; and for the update check and the website, it is our legitimate interest in keeping the application current and secure and the site working. You can object to the update check by switching it off.
We are in Canada, which European and United Kingdom law recognize as protecting personal data adequately. Sentry, PostHog, Cloudflare, GitHub and Google are American companies; what goes to them is covered by the EU–US Data Privacy Framework or by the standard contractual clauses in our agreements with them.
Northern Commander is not meant for children under 16, and we do not knowingly collect anything from them.
Who is responsible: Outonomy, in British Columbia, Canada, is the controller of the data described here. Sentry, PostHog, Cloudflare, GitHub and Google process it for us, as described above. The person responsible for privacy at Outonomy is reached at support@northerncommander.com.
The website
Our website uses the same PostHog account, in the EU, to count visits and to follow one from the page it began on to a download. It uses no persistent cookies: what it keeps for a visit is gone when the visit ends. Each page view says what any page view says — the page, the page you came from, your browser and the size of your screen — and roughly where it came from; your address itself is not kept. There is no advertising and nothing to sign up to. Cloudflare serves the site and keeps brief request records, as it does for downloads.
What we will never do
Sell, rent or share what we collect for advertising. Put ads in the application. Collect your files. Require an account to use the application.
If this changes
This page changes when a promise on it does: a kind of data it does not describe, a new purpose, a new company receiving it, or a limit above that would no longer hold. A new kind of data will be optional, off until you turn it on, and described here before it ships. If a change goes beyond what you have agreed to, we will ask you again.
More of a kind this page already describes — another detail in a crash report, another thing counted in a usage report — does not change it. The documentation of the Privacy settings describes it, and the release notes say so.
Paid services, if they ever exist, get their own terms and their own notice.
Questions: support@northerncommander.com.