01
You start a scan
Journey asks for Photos permission the first time you explicitly scan. It never starts by silently asking for access.
Journey Photo Discovery
Photos found privately, on your iPhone
Journey can suggest photos for existing memories and discover possible trips from photos already on your iPhone. Scanning and matching happen on-device. Nothing is uploaded to Maveon until you review and confirm.
Atlas
•
Found on this iPhone
Private
Photos for your April chapter
Local suggestions appear in Atlas, ready for review before anything is added.
How it works
A local discovery flow, from permission to upload
Photo Discovery is designed around a simple boundary: Journey may help you find relevant photos, but you stay in control of what becomes part of your Diary.
02
Metadata is read locally
The scan uses lightweight PhotoKit metadata: date, GPS coordinate, favorite status, media type. It does not read image pixels for matching.
03
Journey suggests matches
Photos can appear in Atlas chapters, the For You sheet, or a review sheet for a newly discovered place.
04
You approve uploads
Only selected photos are fetched in full resolution and uploaded through Maveon's existing photo upload flow.
Privacy
What stays on your iPhone, and what can leave it
The feature is intentionally strict: scanning, matching, clustering, thumbnails, and library metadata stay on the device. The only upload to Maveon happens after you confirm selected photos.
No library upload during scanning
Your photo library, thumbnails, and scan metadata are not sent to Maveon while Journey looks for suggestions.
Matching runs on-device
Date matching, nearby-location matching, trip clustering, and routine-place filtering all happen locally.
Uploads require confirmation
A photo leaves your iPhone for Maveon only when you select it in the review sheet and tap to add it.
The two things that can leave the device
Photo Discovery keeps the discovery process local, with two clear exceptions that happen for specific reasons.
A coordinate to Apple's reverse-geocoder
Used only to suggest a place name for a possible new memory. This goes to Apple's system geocoding service, not to Maveon.
A photo you explicitly selected
Uploaded to Maveon only after you confirm. New memory name, date, and location then sync like normal Diary data.
Discovery logic
Built to suggest memories, not guess wildly
Journey uses stricter evidence for suggestions that already belong somewhere, and even stricter rules before creating a brand-new place suggestion.
Date-confirmed matches
A photo can match a memory when its date lines up with the memory, hotel range, or trip. Nearby location, favorite status, and whether the memory already has photos help rank the suggestion.
Location-only help
For old memories without reliable dates, Journey can use very close location evidence. These suggestions are labeled so you know the date was not confirmed.
Trip clusters
Unmatched photos are grouped by time and place. Routine locations photographed across many days, like home or work, are filtered out before a new trip is suggested.
Review
Nothing is added until you say yes
Suggestions are intentionally review-first. You can select all, deselect all, choose individual photos, name a new place, and pick the type of memory before creating anything.
Existing memories
Open the suggestion, review local thumbnails, select the photos you want, then add them to the memory.
New places
Journey suggests a place name when it can. If it cannot, you can name it yourself and choose Activity, Restaurant, Hotel, or Flight.
Retries stay tidy
If a partial upload fails, failed photos remain selected so you can retry without creating duplicate memories.
Journey
Your photos stay yours until you add them
Photo Discovery helps Journey feel complete without changing the privacy boundary: discovery is local, upload is explicit, and every photo is your decision.