Effective date: October 14, 2026
This policy explains what MFSoft LLC ("MFSoft," "we," "us") collects, why, and what we do with it — across the MFCommander application, the mfsoft.dev website, and our licensing service.
MFSoft LLC is the data controller for the processing described here. Contact: [email protected].
MFCommander never sends us your files. Not their contents, not their names, not their paths, not directory listings, not the contents of any remote server, bucket, container, or cluster you browse. Not your credentials. Not ever. There is no third-party analytics SDK. The application sends privacy-minimized usage statistics that are on by default and can be switched off in Settings.
The application does talk to us in three narrow, disclosable cases, all described in full below:
All three can be understood completely from Sections 3, 4, and 5. None carries files, file metadata, connection details, or credentials.
The services you connect to are a separate matter, and we are not in the middle of them. When you connect MFCommander to a server or a cloud account, your Mac talks to that service directly. Section 6 describes that in full.
These never leave your Mac and are never transmitted to us:
Operation history stays on your Mac for the period you choose — 30 days by default — and is excluded from Time Machine backups. You can clear it, or limit it to the current session, in Settings › General. It is never sent to MFSoft or counted in usage statistics.
Trials are registered per Mac. On first launch without a license, MFCommander starts a 14-day trial on your Mac and registers it with our licensing service, which records when that Mac's trial began. If you are offline, the trial starts on your Mac and is registered the next time you are online.
Activation checks your key on your Mac, then registers the Mac. Your license key is a signed token verified on your Mac against a public key built into the application. MFCommander then registers this Mac with our licensing service, because a license runs on at most five Macs at a time. If you are offline, the license activates on your Mac at once and is registered the next time you are online. Activating requires no account and no sign-up; we do not create an account for you. Deactivating a Mac in Settings › License frees its place.
Validation is periodic and online. Once a license is active, MFCommander checks in with our licensing service from time to time, so that licenses which were refunded, charged back, or revoked for fraud stop granting paid features.
| What is sent | For a trial: an identifier of your Mac and the application version. For activation, deactivation, and validation: your license ID, a one-way SHA-256 fingerprint of your license key, and the identifier of your Mac; activation and validation also send the name you gave your Mac. Your IP address is visible to our server, as it is to any server you connect to. |
| What is not sent | File names, contents, or paths · directory listings · connection, host, bucket, or cluster details · credentials · the hardware UUID itself, serial numbers, or MAC addresses · usage, feature, or telemetry data · your name or email address |
| How often | At first launch and while a trial runs; when you activate or deactivate; and periodically for validation, in the background. Never blocking, never a dialog |
| Purpose | Enforcing the license grant — one trial per Mac, at most five Macs per license, and detecting refunded, charged-back, or revoked entitlements (performance of contract, GDPR Art. 6(1)(b); legitimate interests in preventing trial abuse, Art. 6(1)(f)) |
| Response | A signed statement of your trial, activation, or license status, cached locally so the answer survives being offline |
The identifier of your Mac. Starting a trial, and activating, validating, or deactivating a license on a Mac, sends an identifier of that Mac: a one-way hash of the hardware UUID macOS reports for it, combined with a value unique to MFCommander so it cannot be matched with other apps. Our licensing service uses it to recognize the same Mac across trials and activations, so that a trial is granted once per Mac and a license runs on at most five Macs. Activation and validation also send the name you gave your Mac, so you and we can tell your Macs apart. These requests never contain your email, payment details, or any file data. We keep the identifier as long as we offer trials and licenses, and delete it on request, which also lets that Mac start a new trial once MFCommander's own trial markers are removed from it. The identifier is never included in usage statistics.
We do not use this to track installs or profile you. The key fingerprint is a one-way hash; we send it instead of the key itself so a check never puts your key back on the wire. Against your license record our server keeps the time of the most recent successful check, and for each of your Macs its identifier, name, and when it was activated, deactivated, and last seen.
It never interrupts your work. These checks run in the background, and MFCommander remains usable offline; a network or service failure never downgrades a Mac on which your license is active. How licensing itself behaves is governed by the EULA; this policy covers what the check transmits.
Turning it off: registration and validation are part of how a trial and a paid license work and cannot be disabled separately. The Community edition, after a trial, does not use them at all.
Usage statistics are described in Section 4. With a paid license they carry your license ID, so they can be associated with your license record. They never carry the identifier of your Mac, and nothing in that section changes what a licensing request sends.
These are on by default, and you can switch them off. MFCommander sends a small daily summary of how the application is used, so we can tell which features earn their place and whether people keep using the app after installing it. It is the only way we learn anything about the Community edition, which never contacts our licensing service.
Turning it off: Settings › Privacy › Send privacy-minimized usage statistics. Switching it off stops collection immediately and discards anything not yet sent. Switching it back on generates a new identifier, unconnected to the old one.
Seeing exactly what is sent: Settings › Privacy › Show exactly what is sent displays the literal contents of the next report before it leaves your Mac.
| What is sent | A random installation identifier · report-format and policy-version numbers · the week usage statistics were first initialized on your Mac · your application version, macOS major version, and processor architecture · your edition (Community, trial, Pro, or Infrastructure) and, during a trial, which day of it · with a Pro or Infrastructure license, your license ID · the number of days the app was active in the reporting period · how many times each counted feature was used. Your IP address is visible to our server, as it is to any server you connect to; we do not store it. |
| What is not sent | File names, contents, extensions, or paths · directory listings · anything you searched for · connection, host, bucket, cluster, container, or share names · credentials · your license key, name, or email · device identifiers, serial numbers, MAC addresses, or hardware fingerprints · window titles · free-form text of any kind · any timestamp more precise than the day |
| How often | At most once a day, as a single summary. Never per action |
| Purpose | Understanding which features are used and whether people keep using the application, so development effort goes where it helps (legitimate interests, GDPR Art. 6(1)(f)) |
The identifier is random. It is generated on your Mac and is not derived from your license, your hardware, or anything about you. For the Community edition and during a trial, nothing connects a report to a customer.
Your right to object. Because we rely on legitimate interests rather than consent, you have the right under GDPR Article 21 to object to this processing at any time. The switch in Settings is how you exercise it, and it takes effect immediately — you do not need to contact us first. You can also email us to have reports already collected deleted.
If update checks are enabled, MFCommander asks our update host whether a newer version exists. The request carries the application version and platform only.
It does not send your license key, license ID, entitlement status, email, device identifier, file names, connector metadata, or any application data. Disable it any time in Settings.
MFCommander is a file manager, so most of what it does is talk to somewhere your files already live — a local disk, an SMB or SFTP server, an FTP or NFS share, an S3 bucket, a Kubernetes cluster, a Docker host, OneDrive, or iCloud Drive.
Every one of those connections runs directly between your Mac and that service. MFSoft operates no proxy, relay, gateway, mirror, cache, or backup in any of these paths, and receives nothing from them. We could not read what you browse there even if we wanted to, because it never reaches us.
Two things you ask for put a copy of a remote file on your Mac's disk, and neither leaves it. Previewing a document writes a temporary copy to your Mac's temporary folder, readable only by your account, deleted when you close the preview and cleaned up at the next launch if the app was force-quit; copying a file to a local pane writes it exactly where you chose. Folder listings and viewed content are otherwise held in memory, and the large-file viewer fetches only the portion on screen.
Hosts, share names, bucket names, cluster and container names, paths, and the credentials for all of them stay on your Mac as described in Section 2. Application usage statistics (Section 4) never include any of them: they record that a connection type was used, never which server, account, or file.
Purchases are processed by Polar Software Inc., our Merchant of Record. Polar takes your payment details directly — MFSoft never sees or stores your card number. Polar acts as an independent controller for its own tax and payment compliance; see Polar's privacy policy.
Polar passes us what we need to issue and support your license, which we store in our licensing service:
| Data | Why |
|---|---|
| Name and email address | Issue the license, email you the key, handle support and recovery requests |
| Order ID and edition purchased | Match the order to the license, prevent duplicate issuance |
| License ID, issue date, updates-window end date | The entitlement itself |
| License status (active / refunded / charged back / revoked) and revocation date | Answer validation checks |
| Timestamp of the last validation check | Support and abuse investigation |
Your license key is emailed to you through our transactional email provider. We send mail about your license and purchase. We do not add you to a marketing list because you bought something.
There is no signup form. mfsoft.dev does not have a waitlist, a newsletter, or a mailing-list signup, and no page asks for your email address. The only place you give us an email address is license recovery, below.
License recovery. If you use the recovery form, your email address is sent to our licensing service to look up and re-send your keys. We do not store a separate record of the request on the website.
Server logs. Our web servers keep standard request logs, including IP addresses, for security and troubleshooting.
Website analytics. We measure page visits, download intent, checkout starts, and where visitors came from, using analytics software we run ourselves on our own servers. It records the page you viewed, the referrer and any campaign parameters, your browser, operating system, device type and screen size, a coarse location derived from your IP address, a pseudonymous visitor identifier that is re-salted daily, and the named actions you take. It sets no cookies. Session replay is off, and your raw IP address is not retained in the analytics record. These records are deleted after 90 days.
We do not run third-party analytics, advertising, or session-recording scripts, and we set no advertising or tracking cookies. Because we host our analytics ourselves, no analytics company receives your visit at all.
Our licensing service and usage-statistics endpoint run on cloud hosting infrastructure in the United States. Our website and its analytics run on servers we operate ourselves, and we keep a copy of usage statistics and license records on those servers for internal reporting. Payments run through Polar. Transactional email runs through an email provider in the United States. All of them are engaged under data processing agreements.
If you are in the European Economic Area, the United Kingdom, or Switzerland, your data is transferred to the United States. Those transfers rely on the European Commission's Standard Contractual Clauses and the equivalent UK and Swiss mechanisms, incorporated into our agreements with those providers.
We share personal data only with these service providers, under contracts that require them to protect it — or where we are legally compelled to, or must to establish or defend a legal claim. We do not sell personal data, and we do not share it for cross-context behavioral advertising, as those terms are defined under California law.
| Purchase and license records | For the life of the license, plus the period tax and accounting law requires us to keep transaction records (generally 7 years) |
| Mac identifiers and names for trials and license activations | Indefinitely, while we offer trials and licenses; deleted on request |
| Raw application usage reports | No fixed period at present; deleted on request |
| Monthly application-usage aggregates | Indefinitely; these contain no installation identifier |
| Raw mfsoft.dev website analytics records | 90 days |
| Web server logs | Up to 90 days |
| Support correspondence | Up to 3 years after the matter is closed |
Wherever you live, you can email [email protected] to access, correct, delete, or receive a copy of your personal data, or to object to or restrict how we use it.
If you are in the EEA, UK, or Switzerland, you have those rights under the GDPR or UK GDPR, plus the right to withdraw consent where a purpose relies on consent and the right to lodge a complaint with your national supervisory authority. For application usage statistics, which rely on legitimate interests rather than consent, you have the right to object under GDPR Article 21; switching off Send privacy-minimized usage statistics exercises that right immediately.
If you are in California, you have the rights to know, delete, correct, and opt out of sale or sharing under the CCPA/CPRA. We do not sell or share personal data, so there is nothing to opt out of. We will not discriminate against you for exercising any of these rights.
We respond within 30 days. We may need to verify your identity first — usually by confirming you control the email address on the account.
License keys are cryptographically signed and verified on your own Mac. Traffic between MFCommander and our services is encrypted in transit with TLS. Our signing keys are held in a managed secrets store, separate from the systems that serve requests. Credentials for the servers you connect to stay on your Mac in the macOS Keychain, and we could not retrieve them if we wanted to.
No system is perfectly secure. If we discover a breach affecting your personal data, we will notify you and the relevant authorities as the law requires.
MFCommander is developer tooling and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us data, contact us and we will delete it.
We may update this policy. Material changes will be announced by an updated effective date at the top. Where a change affects what the application transmits, the release notes for the version that introduces it are our primary disclosure channel, not an optional courtesy. We will not begin collecting a new category of data from the application without publishing the policy change and those release notes first.
MFSoft LLC — [email protected] — https://mfsoft.dev