"Swipe Cleaner: A Technical Deep Dive into On-Device Photo Privacy"
Disclosure: I write about projects in the OpenNomos ecosystem, including Swipe Cleaner. Most photo cleaning apps have a dirty secret: your photos leave your device. They get uploaded to some server for "AI processing," "cloud analysis," or just because the developer didn't think about it. Swipe Cleaner takes the opposite approach. Everything happens on your iPhone. Not a single pixel leaves your device. Let me break down why that matters, and how it actually works under the hood. Swipe Cleaner i
Disclosure: I write about projects in the OpenNomos ecosystem, including Swipe Cleaner.
The Problem With Photo Cleaners
Most photo cleaning apps have a dirty secret: your photos leave your device. They get uploaded to some server for "AI processing," "cloud analysis," or just because the developer didn't think about it.
Swipe Cleaner takes the opposite approach. Everything happens on your iPhone. Not a single pixel leaves your device.
Let me break down why that matters, and how it actually works under the hood.
The Architecture
Swipe Cleaner is built on three principles:
1. On-device processing, always. Image analysis, duplicate detection, and similarity matching all run locally using Apple's Core ML and Vision frameworks. No cloud roundtrips, no server costs, no privacy policy loopholes.
2. Tinder-style UX for decisions. You don't manage a grid of thumbnails and checkboxes. You swipe. Right to keep, left to delete. This isn't just a UI gimmick — it's a deliberate choice to reduce decision fatigue. When you have 3,000 photos to clean, you need flow, not friction.
3. Sandboxed storage access. The app requests permission for exactly what it needs. It doesn't ask for your entire photo library if you only want to clean screenshots. This is iOS privacy-by-design done right.
Why On-Device Matters Now
We're in a weird moment. AI capabilities are exploding, which means the temptation to "send it to the cloud for better results" is stronger than ever. But at the same time, Apple is pushing hard in the opposite direction — Private Cloud Compute, on-device ML, differential privacy.
Swipe Cleaner aligns with where the platform is going, not where the industry has been.
The Technical Trade-offs
Local-first isn't free. Here's what you give up:
- Model size constraints. You can't run a 70B parameter vision model on an iPhone. The models need to be small, optimized, and ruthlessly efficient.
- No cross-device sync. Your cleaning decisions stay on one device. No cloud means no sync. For a photo cleaner, this is arguably a feature, not a bug.
- Battery & thermal limits. Heavy image processing on-device generates heat. You need to batch operations, throttle when needed, and respect the device's thermal state.
What's Next
The team is exploring on-device ML for smarter grouping — detecting burst photos, identifying "best shot" candidates, and flagging near-duplicates with subtle differences. All without a server in sight.
If you care about privacy and you have an iPhone with thousands of photos you've been meaning to clean, Swipe Cleaner is worth a look. It's free, it's fast, and your photos never leave your phone.
Built on OpenNomos. Contribute tools or improvements and earn ecosystem rewards.