How PrivShot Blurs Photos Without Uploading Them Anywhere

TL;DR

PrivShot does everything on your iPhone: detection and blurring run locally, with no account, no analytics, and no uploads. The original un-blurred image is handled in memory and never written to disk — only the redacted copy is saved.

How it works

  1. You import or capture a photo. It’s held in memory, not uploaded.
  2. Detection runs on-device to find faces and personal data.
  3. Redaction blurs those regions — again, on-device.
  4. Only the already-blurred pixels are written to disk when you export.
  5. The raw, un-redacted frame is discarded. It never touches storage or a server.

Why it works this way

The whole premise of a privacy tool falls apart if the “private” photo takes a round trip through someone’s cloud first. PrivShot’s design closes that gap: there is no server in the loop to leak from, get breached, or quietly keep a copy. “On-device” isn’t a marketing line here — it’s the reason the un-redacted image has nowhere to go.

Tips & edge cases

FAQ

Does PrivShot upload my photos to blur them? No. All detection and redaction run on your device. Nothing is uploaded, and there’s no account or analytics.

Is the original un-blurred photo ever saved? No. The raw image is processed in memory, and only the redacted pixels are written to disk.

Does it work in airplane mode? Yes. Because everything runs locally, PrivShot works with no connection at all.