Your camera roll stays put.
OTrip reads useful dates and locations from PhotoKit. The image files are not uploaded; the AI flow sends structured date and coordinate evidence to draft suggestions.
OTrip turns photo dates and locations into a travel record without uploading the photo files. Your atlas is personal, not another profile to maintain.
Many travel products begin with a map and end with a social graph. That changes the job: a journal becomes a performance, a memory becomes a post, and an old trip becomes something to publish.
OTrip starts somewhere else. It treats your travel history as a personal archive. Image files stay on the iPhone during detection. If you start the AI photo flow, structured timestamps, coordinates, counts, and travel clues are processed through OTrip's backend and OpenAI to suggest trips. You decide the final shape of the record.
Approved trips, stamps, and journal entries can sync privately to your account so they survive a new phone. OTrip does not need an advertising profile, follower count, or background location trail to build the atlas.
OTrip reads useful dates and locations from PhotoKit. The image files are not uploaded; the AI flow sends structured date and coordinate evidence to draft suggestions.
A weekend, a layover, or an ordinary afternoon does not become a trip until you approve and shape it.
Add notes and stamps for yourself. Sharing is deliberate, not the default state of the journal.
No image or video files are uploaded for trip detection. If you start the AI photo flow, structured timestamps, coordinates, counts, and travel clues are sent through OTrip's backend to OpenAI before you review the suggestions.
No background GPS trail is required to build your journal from the photos you already took.
Yes. The iPhone app uses native Firebase Analytics for product-usage events plus Crashlytics and Performance Monitoring for diagnostics. This website separately uses Google Analytics for page and conversion-button statistics. None of those services receives photo files for trip detection; see the privacy policy for exact event categories.
Request access by email and tell the maker what you want a private travel journal to remember.
Request privateBeta access