There is a post on r/unpopularopinion with over six thousand upvotes that says "most people do not actually like traveling, they like having traveled." The comments are full of people agreeing. The planning is stressful, the airports are miserable, the jet lag is real. But the memories, the stories, the map of places you have been — those matter. For a lot of people, the documentation of travel is as meaningful as the trip itself.
This creates a real problem. If you want a record of your travels, most apps expect you to share your live location data with them. They run GPS tracking in the background while you move, logging your coordinates to a server. This is how Polarsteps works: you start a trip, the app follows you, and your route appears on a map in real time. It is effective. It is also a significant amount of location data to hand over to a third party.
But here is the thing most people do not realise: you probably already have a complete travel record sitting in your phone. Every photo you have ever taken with your camera contains the exact GPS coordinates of where it was shot. You do not need an app tracking you in the background to document your travels. You just need to read the data your camera already wrote.
Every time you take a photo with your phone, the camera does something quietly useful: it checks the GPS chip, determines your exact position, and writes those coordinates into the image file. This happens in the background, without any notification, every single time you press the shutter button.
The data is stored in a format called EXIF — Exchangeable Image File Format. EXIF is essentially a block of metadata embedded inside the image file itself. It records the camera model, shutter speed, aperture, ISO, the date and time down to the second, and — most importantly for travel — your latitude and longitude. The GPS accuracy is typically within five to ten metres outdoors, which is more than precise enough to identify a specific street, landmark, or neighbourhood.
A single EXIF GPS entry looks something like this: 41 degrees 53 minutes 30 seconds North, 12 degrees 29 minutes 39 seconds East. That is the Colosseum in Rome. Your phone wrote that coordinate into the photo file automatically, and it has been doing this for every outdoor photo you have taken since you enabled location services for your camera — likely years ago.
The cumulative result is a remarkably detailed travel record. If you took photos on a trip to Japan in 2022, your phone logged coordinates in Tokyo, Kyoto, Osaka, and every stop in between. If you drove through the Scottish Highlands last summer, every photo you took at a viewpoint or lunch stop recorded the exact location. The data is already there, embedded in files you already own, stored on a device you already control.
It is worth understanding exactly what your photos know about you, because the breadth of EXIF data is often surprising. A typical photo taken with an iPhone contains:
The GPS coordinates and timestamps together create something more powerful than either alone. With coordinates, you know where you were. With timestamps, you know when you were there. Combined, they reconstruct not just which places you visited, but the order and timing of your movements. A sequence of photos from a single day tells a story: breakfast at a cafe near the harbour at 8:47am, the cathedral at 10:15am, a park on the hillside at noon, a restaurant in the old quarter at 7:30pm. That is a travel journal, written automatically, with no input from you at all.
The travel app market has converged on two fundamentally different approaches to documenting your trips. Understanding the distinction matters because the privacy implications of each are very different.
This is the model used by Polarsteps and similar apps. You install the app, start a trip, and the app continuously tracks your location in the background using your phone's GPS. Your coordinates are logged at regular intervals — every few minutes or whenever you move a meaningful distance — and uploaded to the company's servers. The result is a detailed route line drawn on a map, showing exactly where you walked, drove, or sailed.
The data this generates is extensive. A two-week trip might produce thousands of location data points, recording your position throughout the day and night. This data is stored on the company's servers, which is what enables features like cross-device syncing, sharing with friends, and printed travel books.
Always-on GPS tracking also has practical costs. Background location access drains battery faster — a meaningful concern when you are travelling and your phone is already working hard on maps, translation, and communication. And you need to remember to start tracking before each trip. If you forget to open the app before boarding a flight, that segment is not recorded.
The alternative model does not track your location at all. Instead, it reads the GPS data that your camera has already embedded in your photos. There is no background process, no continuous location logging, and no data transmitted to a server. The app simply reads metadata from files that already exist on your device.
The result is less granular than real-time GPS tracking. You get the specific locations where you took photos, not a continuous route between them. But for most travellers, this is more than sufficient. If you took photos at the airport, the hotel, the museum, the restaurant, and the beach, those five data points tell you where you were that day. The gaps between them — the taxi ride, the walk back to the hotel — are not particularly interesting to document anyway.
The privacy difference between these two models is significant, and it is worth examining closely.
When you use an always-on GPS tracker, you are generating a continuous stream of location data and sending it to a company's servers. This data reveals more than just your holiday itinerary. It reveals your sleep patterns (when you stop moving at night), your daily routine (if you use the app at home), and your real-time whereabouts during sensitive moments. The company holding this data has a detailed map of your movements that goes beyond what most people intend to share.
This is not a theoretical concern. Location data has been involved in real-world privacy incidents repeatedly. In 2018, Strava's global heatmap inadvertently revealed the locations and patrol routes of military bases by showing where soldiers were running with GPS watches. In 2023, researchers demonstrated that anonymised location data sets could be de-anonymised with surprising ease — as few as four spatiotemporal data points were enough to uniquely identify 95% of individuals in a data set of 1.5 million people (de Montjoye et al., Nature Scientific Reports).
Photo-based travel tracking sidesteps this entirely. The GPS data in your photos never needs to leave your device. An app that reads EXIF data locally can build your complete travel map without making a single network request. Your travel history exists only on your phone, under your control, accessible to no one else unless you choose to share it.
There is also a subtler privacy advantage. Always-on GPS tracking creates data that did not previously exist — a detailed log of your movements that would not exist without the app. Photo-based tracking, by contrast, works with data that already exists in files you already have. It does not create new surveillance data. It reads what is already there.
Reading GPS coordinates from a photo is straightforward. The interesting part is what you can infer from thousands of photos taken over several years.
Consider a photo library spanning five years of travel. The raw data is a collection of GPS coordinates with timestamps. From this, an on-device algorithm can determine:
The flight detection is particularly clever in practice. If your photos show you in Manchester at 6am and Barcelona at 11am, the only reasonable explanation is that you flew. An algorithm can identify the departure and arrival cities, estimate the airline route, and log it as a flight — all without you entering a single booking reference or connecting an email account. Over years of photos, this builds a surprisingly complete flight history.
All of this analysis can happen entirely on-device. Modern phones have more than enough processing power to scan tens of thousands of photos and extract their EXIF data in minutes. There is no technical reason this data needs to leave your phone.
Fairness requires acknowledging what the retroactive approach cannot do. If you want a drawn route showing the exact road you drove through Tuscany, photo-based tracking will not give you that — it will show you pins at the places you stopped and took photos. The road between those pins is inferred, not recorded.
You also lose the travel diary component. Apps like Polarsteps let you write notes at each stop: what you ate, how the weather felt, the name of the bartender who recommended the coastal walk. Photo-based tracking gives you locations and times, not stories. If the narrative of a trip matters to you as much as the map, you need either a journaling app alongside your photo tracker or an active tracking app that includes diary features.
There are also coverage gaps. If you visited a city but never took a photo — perhaps you were there for a layover, or your phone was dead, or you simply did not feel like photographing — that visit will not appear in a photo-based travel map. In practice, most modern travellers photograph prolifically enough that this is rarely an issue, but it is a genuine limitation.
Finally, photo-based tracking is inherently retrospective. You cannot watch your trip unfold on a map in real time while you are travelling. For people who enjoy seeing their route build during a trip — or who want to share their live location with family for safety — real-time tracking serves a purpose that retrospective analysis cannot.
If you want to build a travel journal without handing your location data to a third party, here is a practical framework:
This approach gives you the benefits of a travel tracker — a map, statistics, a record of everywhere you have been — without creating any new location data, without running any background processes, and without sending anything to anyone.
The travel app market has largely assumed that tracking your location is a prerequisite for documenting your travels. It is not. Your camera has been quietly building your travel journal for years, embedding precise coordinates into every photo you take. The only thing missing was a way to read that data and present it as a map.
For people who care about privacy — and the growing adoption of tools like Signal, VPNs, and privacy-focused browsers suggests many people do — the distinction between "an app that tracks where I go" and "an app that reads where I have been from data I already have" is not pedantic. It is fundamental. One creates new surveillance data and transmits it to a server. The other reads existing metadata and keeps it on your device.
The next time you come back from a trip and want to see it on a map, check your camera roll first. The travel journal you have been looking for might already be written.