Why our apps make no network requests

---

Quick File Organizer ships with no networking code of its own. No analytics SDK, no crash reporter, no update pinger, no license server call. You can run it behind a firewall that blocks everything and every feature works identically — which is exactly what "works completely offline" on our Store listing means.

This is unusual enough that people assume it is marketing language. It is not, so here is what it actually means, including the one exception.

What "no telemetry" usually means

When a desktop app says it respects your privacy, it typically means one of:

• Analytics are anonymised (but still sent).
• Telemetry is opt-out (but on by default).
• Only crash reports are collected (which routinely contain file paths, and therefore usernames and project names).
• Data is collected but not sold (today, under current ownership).

All of those are defensible positions. None of them is the same as not sending anything, and the distinction matters because every one of them is a promise about behaviour rather than a property of the software.

The one exception, stated plainly

Quick File Organizer has an optional one-time Pro upgrade. Purchases and licence checks are handled by the Microsoft Store — Microsoft's systems, not ours.

We are not going to pretend that mechanism is magic. Verifying that a machine holds a licence is something the Store does, and it does not do it by telepathy. What we can tell you precisely is where the line falls:

• We wrote no networking code. There is no endpoint we own, no server we run, and nothing that reports back to us.
• We receive no personal data from it. Not your Microsoft account, not your payment details, not your email. Only whether a licence is present.
• The free version needs none of it. If you never buy Pro, that path is never exercised.

If a competitor claims something stronger than this while selling in-app purchases, be a little suspicious.

What this costs us

Being honest about the trade-off, because there is a real one:

We have no idea which features get used. Every product decision is made from support email and intuition. We have certainly kept features nobody uses and cut things people relied on.

We do not know when the app crashes. If something breaks on a hardware configuration we do not own, we find out only if someone emails us. Most people do not email; they uninstall.

We cannot measure the funnel. How many people open the app once and never return? No idea. That is genuinely the metric we would most like to have.

Updates are manual. No in-app update prompt means people run old versions for a long time. The Microsoft Store mitigates this, which is a large part of why we distribute there.

That is not a small list. A single analytics integration would meaningfully improve the product.

Why we do it anyway

Two reasons.

The first is that these are utilities. Quick File Organizer sees the name of every file in every folder you ask it to watch. A clipboard manager would see everything you copy. The blast radius of "we collect a little diagnostic data" is much larger for this category of software than for a game or a note-taking app. The safest way to not leak that data is to never have it.

The second is that it is a constraint that keeps us honest. Once a pipe exists, there is always a good reason to send one more field down it. Not building the pipe means that conversation never starts.

What we ask instead

If something breaks, email us. A person reads it and replies, usually within two business days. That is a worse bug-reporting channel than automated crash reports by every measure except one: you know exactly what you sent.