A location check proves a particular arrival; background tracking checks location beyond that immediate interaction. For travelers weighing location check vs background tracking, the useful question is not just whether an app requests location permission, but what it does with location afterward.

Unlocked’s core flow does not need a continuous account of your route. It verifies presence for a Landmark unlock, which opens curated Experiences you can use later. An optional nearby-reminder pilot has a different purpose: helping you notice a Landmark, with proximity checks kept on your device rather than sent back as a route history.

Location Check vs Background Tracking in Travel Apps

A location check answers a bounded question, while background tracking operates beyond the moment when you actively request that check.

For an arrival-based feature, the question is straightforward: are you at the relevant place now? A GPS check-in app can use a location reading to support that decision. The result might be a recorded visit or access to something tied to that place. Establishing that arrival does not inherently require recording how you got there or where you go next.

Background location access supports checks outside that immediate interaction. Whether it produces a continuous travel history depends on the app’s implementation. Processing proximity on the device is different from sending successive coordinates to a remote service and retaining them.

That distinction matters when comparing travel app location tracking. A permission label alone does not explain the full collection pattern. Look separately at:

  • Purpose: What question does the location check answer?
  • Timing: Does it happen during a deliberate action or beyond it?
  • Transmission: Does location stay on the device or leave it?
  • Retention: What remains after the feature has done its job?

These are evaluation questions for any app, not a claim that every travel app behaves alike.

Unlocked verifies an arrival, not the journey around it

Unlocked’s core requirement is physical presence at a Landmark, not continuous access to a traveler’s route.

The product sequence is Physical presence → Landmark unlock → Curated Experience → Memory → My World. Arrival is the condition that opens the experience; the journey between arrivals is not the product’s central record.

When you request an Unlock, Unlocked checks the submitted location on its servers. Its documented checks consider whether the reading is timely, valid, sufficiently informative, and near the relevant Landmark. A phone simply declaring that you are there is not enough to authorize the Unlock.

Those checks support presence verification, but they should not be mistaken for a guarantee that location deception is impossible. Unlocked’s documentation does not make that claim. Nor does a successful verification establish a complete account of a traveler’s day.

The reward is access to the Landmark’s curated Experiences. Once unlocked, those Experiences remain available permanently, so you can create a Memory later from home. You do not need to stay at the Landmark to complete that later creative step.

For more context on that arrival-based relationship, read how location-based travel apps reward arrival.

Nearby reminders and an Unlock are different moments

Unlocked’s optional nearby reminders help with discovery; they do not themselves verify a visit or award an Unlock.

The documented Paris Nearby discoveries pilot uses opt-in operating-system geofences and local notifications. In plain language, the device checks proximity to prepared Landmark locations so it can offer a nearby reminder. Those proximity checks stay on the device. This feature does not send coordinates or route history to Unlocked’s servers.

The reminder system uses local consent associated with the account, prepared Landmark information, and a history used to avoid duplicate reminders. Signing out, opting out, and confirmed local unlocks cancel the relevant reminder requests.

Tapping a notification opens a browsing destination after an account check. Presence verification remains a separate, server-checked step. Being notified that something is nearby is therefore not equivalent to having earned its Unlock.

This is an important qualification for background location privacy: an optional location-aware feature can work beyond a deliberate check without sending a continuous route to the app’s servers. It is still worth understanding and choosing consciously.

The documentation describes this as a Paris pilot, not a universal promise that nearby reminders are available everywhere.

A successful Landmark unlock records earned travel history

A successful Landmark unlock establishes an earned visit associated with that Landmark and opens its Experiences permanently.

My World presents that history as a restrained digital passport, with a map, city progress, unlock dates, and Memories. The useful distinction is between a record that you earned a particular Unlock and a record of your movements between places. The former is part of Unlocked’s product; a continuous route is not needed for its core flow.

The Unlock is also separate from the Memory you may create afterward. An Experience is a curated creative choice, and a Memory is the resulting generative image. That image is not the mechanism used to verify a Landmark visit: the presence check comes first.

Deleting an individual Memory does not revoke the Landmark unlock. Even deleting the last Memory leaves earned travel history intact while emptying the gallery. If your goal is to remove the broader account rather than one image, those are different deletion decisions.

Unlocked is a native travel app, not a generic image generator or a public social network. My World deliberately avoids public feeds, points, and leaderboards. Optional Public Passports are explicitly selected collections, rather than an automatically published account of your travels.

Evaluate location privacy separately from photo privacy

A bounded location check does not answer every privacy question about the rest of an app.

For general app evaluation, separate the arrival feature from reminders, image creation, storage, and sharing. A service can minimize one category of collection while still needing other information for a different task. Ask what each action sends and what each deletion control removes.

For Unlocked specifically, Memory creation sends reference images and any current-look photo to OpenAI, together with the selected Landmark and Experience, visit date or time-of-day context, and optional aesthetic instructions. Private image storage therefore does not mean that images never leave Unlocked for processing.

Unlocked states that it does not perform facial recognition, compare identities, create biometric embeddings, or sell face reference images. References and Memories live in private storage, and the app does not automatically publish a gallery.

Deletion also has boundaries. Copies you have already saved or shared are outside Unlocked’s deletion scope, while backups and external retention have separate limits. These details deserve their own review rather than being folded into a broad promise of “no tracking.” The guide to travel photos and privacy addresses the image side of that decision.

Choose the access that matches the task

The most useful privacy test is whether the location activity matches the feature you want to use.

If you want to prove one arrival, look for a clearly defined check and an explanation of what the successful result preserves. If you also want nearby reminders, review that feature separately: where proximity is processed, whether coordinates are transmitted, and how to turn reminders off.

For Unlocked, the distinction is deliberate. The Unlock verifies presence and preserves earned access; the optional nearby pilot supports discovery without sending coordinates or route history to its servers. Creating a Memory later is another action, with separate photo-sharing considerations.

Before deciding which features to enable, read the Unlocked Privacy Policy alongside the permissions shown on your device. Choose an arrival check for the arrival you want to record, and assess optional reminders on their own terms.

Useful details

Frequently asked questions

How is a location check different from background tracking?

A location check answers a bounded question, such as whether you are at a Landmark when requesting an Unlock. Background tracking operates beyond that immediate interaction. It may support ongoing functions, but whether it creates a route history depends on what the app collects, sends, and retains.

Does Unlocked need continuous access to my route?

No. Unlocked’s core flow verifies presence for a Landmark unlock rather than requiring a continuous route. Its optional Paris nearby-reminder pilot uses on-device proximity checks and does not send coordinates or route history to Unlocked’s servers. Those reminders are separate from verification.

What does a successful Landmark unlock record?

A successful Landmark unlock establishes an earned visit associated with that Landmark, with the unlock date reflected in My World. It permanently opens the Landmark’s Experiences. That travel history remains if you delete a Memory; the created image and the earned Unlock are separate.

Source notes

Sources

This article was prepared with editorial automation using the source pack below.