Why we build privacy-first downloader apps (and what that actually means)

"Privacy-first" shows up in a lot of app store listings without much behind it. We'd rather explain exactly what it means in our own apps than just claim the label.

Downloads happen on your device

Our downloader apps fetch the media you ask for directly from the source to your device. We don't route your downloads through our own servers to "process" them — there's nothing to log on our end because the file never passes through infrastructure we control.

We don't need your account to make the app work

Wherever technically possible, our apps work without requiring you to create an account or sign in. No account means no profile of your activity sitting in a database somewhere waiting to be a liability later.

Permissions match function, not ambition

A downloader app needs storage access to save files. It doesn't need your contacts, your microphone or your precise location. We treat every permission request as something we have to justify, not something to collect "just in case" a future feature needs it.

Ads, when present, are not personalized off your downloads

Monetization has to exist for a free app to keep working, but the content you download with our apps isn't used to build an ad profile of you. Ad networks we use operate at the platform level, not based on what you've personally saved.

We publish what data we actually collect

Every app links to a real, specific privacy policy — not a generic template copy-pasted across every listing in our portfolio. If a policy doesn't mention something, it's because that app genuinely doesn't do it.

None of this makes us special — it's closer to what privacy should mean as a baseline. We just think it's worth saying plainly instead of leaving it as a vague badge on the store listing.