On-device search
Describe it, even if you never tagged it.
Your own tags are the reliable way back. But some evening you'll want a photo you never got round to naming, and all you have is what it looked like. Type that instead.
Photo Flashlight carries an OpenCLIP model inside the app and runs it on the phone itself, through CoreML on iPhone and the equivalent on Android. Your phrase becomes a vector on your device, gets compared against your own photos on your device, and is ranked there.
Nothing is uploaded. No server sees the words you typed or the library you searched. Put the phone in airplane mode and it still works, which is the whole difference between a privacy policy and an architecture. A policy is a promise about what a company chooses not to look at. This is a description of where the work happens.
It's a foothold, not the system. The machine is good at a dog on a green lawn and useless at the trip where the tent leaked. The first gets you into the right neighbourhood on a night when you have nothing else. The second is only ever findable because you named it, which is why the tags still matter and always will.
Privacy by design
Your archive stays
yours to pass on.
Your photos never leave your phone. Photo Flashlight stores a perceptual fingerprint for each picture — a small hash that recognizes the image without containing it. That's how your tags follow you to a new device, and how the legacy you build stays yours to give.
- Originals never leave your phone.
- Tags and organization sync as compact diffs, not images.
- A photo on a new device? Its fingerprint maps it back automatically.
- We have no admin view of your library, because the library isn't on our servers.