# Privacy Is Not a Feature — It's Architecture. How Swipe Cleaner Processes Everything On-Device

> Source: <https://dev.to/ethanwalker89m/privacy-is-not-a-feature-its-architecture-how-swipe-cleaner-processes-everything-on-device-3e0m>
> Published: 2026-07-04 03:00:38+00:00

Disclosure: I work on Opennomos, the ecosystem behind Swipe Cleaner.

Last week, I watched someone install a photo cleaner app, grant it full photo library access, and hit "Clean" — all without realizing their entire camera roll was being uploaded to a server in a different jurisdiction.

This isn't an edge case. It's the default.

Most iOS photo cleaners follow the same pattern:

The problem? **Step 2.** The moment your photos leave the device, you've lost control. No privacy policy can undo that.

Swipe Cleaner is 4.7MB. Everything happens on your iPhone:

No API calls. No cloud processing. No analytics that include photo metadata.

Privacy-as-architecture means three things:

Swipe Cleaner doesn't make network requests related to photo processing. The only network calls are for optional things like checking for app updates — and those don't include any user data.

Core ML, Vision, and Metal run on the same chip that stores your photos. There's no latency from network round-trips, and no exposure from data in transit.

When privacy is a feature toggle, it can be accidentally disabled, changed in an update, or removed under pressure. When privacy is the architecture, there's nothing to toggle. The data path simply doesn't include an exit.

On-device processing means:

But here's what I've learned: users don't actually want cloud processing. They want their photos organized. If you can do that locally, the "trade-off" disappears.

Apple's privacy labels have made data collection visible, but they haven't changed the default architecture. Most apps with "No Data Collected" labels still process user content on remote servers — they just argue that "processed" data isn't "collected" data.

That distinction doesn't hold up. If your photos touch a server, that's collection. Period.

Swipe Cleaner takes the harder path: build everything on-device, accept the engineering constraints, and let the architecture speak for itself.

*Swipe Cleaner is part of the Opennomos ecosystem. If you're building privacy-first tools, check out opennomos.com.*
