Why Camronic Keeps Your Photos On Your Device
Our photo library is the most personal thing on the phone. Here is how Camronic handles that, what leaves the device and what does not, and the trade-offs we accept to keep it that way.
Most photo apps want your photos in their cloud. There is a reason for that. The cloud is where they store, search, and learn from your data. It is also where the storage bill shows up on your card every month.
We took the other path. Camronic stores your photos on your device only. Nothing is uploaded. Nothing is kept on our servers. The library lives in the app's private storage and goes away when you uninstall. This post explains how that actually works, what does leave the device, and the trade-offs that come with the choice.
What "on device" actually means
When you import a photo into Camronic, it is copied into a private folder belonging to the app. That folder lives on your phone, encrypted by the operating system. It is invisible to other apps, and to us. We do not have a server with a copy of your library on it.
- Originals: stay on your device. Always.
- Edited copies: rendered locally where possible, kept on your device.
- Library metadata (categories, scores, notes): stored locally on your device.
- Account profile: a tiny record on our server with your name, email, and sign-in provider. No photos.
What does leave the device, and why
Being honest about this is the only way the privacy promise means anything. Two things leave the device, briefly, when you ask for them.
1. A tiny preview for analysis
When you tap Analyze, we send a small, downscaled JPEG preview (about the size of a thumbnail) to our analysis service. The service runs a vision model on it, returns a score and a structured quality readout, and the preview is discarded. We do not store it.
2. A working copy for the export render
When you tap Save on an AI edit, we send a working-resolution JPEG to our render service so the final file has every adjustment correctly applied. Same rule: processed in memory, returned to you, discarded.
Why on-device is also better, performance-wise
Privacy is the headline, but the speed is the surprise. Anything on-device runs at the speed of your phone. Anything in the cloud runs at the speed of your worst signal that day.
- The realtime editor previews every slider change at 60 frames per second, with no network at all
- Scrolling the library is instant because the photos are local
- Sharing a photo takes a fraction of a second because the file is already on your phone
The trade-offs we accept
On-device first is a choice, not a free lunch. There are things we cannot do as well as a cloud-only app.
- Cross-device library sync. We do not have it yet because it would require a copy of your library somewhere central.
- Backup recovery. If you uninstall the app, the in-app library goes with it. Your original photos in the phone's photo gallery are untouched.
- Server-side history. We do not keep a log of what you edited last week because there is no place to keep it.
For most people, the trade-off is worth it. The phone's gallery is the source of truth, and Camronic is the workspace on top of it. If you uninstall, your photos go nowhere.
Closing
The library is the most personal data most people own. We did not want to be one more company asking you to trust us with all of it. On-device first means there is less for us to handle, less for us to leak, and less for you to worry about. The privacy is real because the architecture insists on it.