How AI Reference Photos Work in Travel Apps

How AI Reference Photos Work in Travel Apps

Understanding how AI reference photos work starts with separating three actions: uploading a photo, allowing it to be shared for image creation, and requesting the finished image. In Unlocked, references are checked and normalized, stored privately, and sent to OpenAI when a traveler requests a Memory. Travelers can remove references later, but deletion has boundaries.

Unlocked is a native travel app, not a general-purpose image generator or a public social network. Its journey is physical presence → Landmark Unlock → curated Experience → Memory → My World. A reference photo helps personalize the Memory; it does not establish that you visited the Landmark. The visit is verified separately through a location submission.

The Unlocked product overview describes Experiences as editorial choices available after an Unlock. You can create a Memory later, including from home, while the service and your account remain active. That distinction matters: being at a Landmark and sending a photo for image creation are different steps.

Consent comes before processing and sharing

Reference image consent involves both permission to use the photograph and permission for the app’s handling of it. Neither should be assumed simply because a photo is available on your phone.

Under the Unlocked Terms and Conditions, you retain your rights in uploaded content and must own it or have the permissions required to use it. You must not upload someone’s image without their permission. The terms give Unlocked a limited licence to process content for the service, including a Memory you request.

Unlocked documents two distinct technical controls. Reference upload requires an explicit consent signal. Memory creation has a separate OpenAI-sharing consent record, with an ask-once “Photo permission” sheet in the native apps when consent enforcement is enabled. In that mode, creation without consent is rejected.

There is an important qualification: the documentation also describes an enforcement-disabled mode. In that mode, the sheet is bypassed and first creation records consent implicitly, without overwriting an explicit withdrawal. The supplied material does not establish which mode is currently active. An unconditional claim that every traveler always sees the sheet would therefore be too strong.

Users can withdraw sharing consent from the Privacy screen at any time. Withdrawal and deletion are separate controls.

Normalization prepares the uploaded file

Unlocked checks and re-encodes a reference photo before storing it as usable image content. This preparation is called normalization; it is not identity verification.

The documented upload requirements are one file, a permitted image type, a maximum size of 10 MB, and valid dimensions. Processing applies the image’s orientation, removes metadata through re-encoding, and constrains its size.

For a traveler, the useful distinction is between information carried alongside the picture and information visible within it. Metadata removal does not promise to remove a recognizable face, a readable sign, or other details in the image itself. Review the photograph, not just its file properties, before uploading.

Unlocked explicitly states that it does not perform facial recognition, compare identities, or create biometric embeddings. Those are specific limits on its handling of references—not a claim that personalization requires no processing of the picture.

Private storage controls access, not every later use

Unlocked stores references and Memories in private object storage rather than exposing permanent public image addresses. Its documented access controls tie requests to a verified signed-in account, rather than letting a request choose whose account it represents.

When the app returns an image link, that link is signed and short-lived. The technical distinction matters: access is time-limited rather than provided through a permanent public address. It is not a guarantee that no copy can ever exist elsewhere.

The Unlocked Privacy Policy also states that image bytes and signed image links are not logged. It says Unlocked does not sell face reference images or automatically publish a gallery.

Publication is a separate choice. Optional Public Passports are explicitly selected collections that can include individually selected Memories. Private reference storage should not be confused with that sharing feature.

For any AI travel photo app, ask what “private” describes: storage access, public visibility, external processing, or all three. Unlocked expressly warns that private storage does not mean data is never shared with external services.

A Memory request sends the reference to OpenAI

Memory creation is the documented point at which Unlocked sends reference images to OpenAI. The request also includes any current-look photo, the selected Landmark and Experience, visit date and time-of-day context, and optional aesthetic instructions.

That is the central data path for a traveler deciding whether to proceed. Uploading places a reference in Unlocked’s system; requesting a Memory uses reference imagery in an external image-creation service. The documentation ties that transfer to Memory creation, not simply to earning an Unlock.

The reference supplies visual information, while the selected Experience supplies the curated creative direction. The resulting Memory is not necessarily an exact reproduction of the traveler or the place. Unlocked’s terms warn that generated content can be imperfect, inaccurate, or visually inconsistent, and the product identifies generative content.

A verified visit therefore establishes the basis for the Landmark Unlock, not the truth of every detail in a Memory. The finished image is a creative output, not evidence that the depicted scene occurred.

The supplied sources do not establish an OpenAI retention period or a blanket no-training commitment. Neither should be inferred from Unlocked’s private-storage controls.

Travelers can delete references and Memories separately

Unlocked lets users remove one reference, all references, individual Memories, or the entire account. These options address different parts of the photo’s path, so choose the action that matches what you want removed.

Removing a reference and deleting a finished Memory are distinct options. The documentation does not say that removing a reference automatically deletes Memories already created with it.

For an individual Memory, deletion immediately hides the image from product reads and removes its feedback and creation provenance. Its private image object is permanently removed, with durable retries if storage is unavailable. A historical creation record remains for purposes including credit accounting and referral qualification; image deletion is not erasure of every associated record.

Local cached copies are evicted on the deleting device and reconciled on other devices when they reconnect. Copies already exported or shared remain outside Unlocked’s deletion scope. Previously issued links, backups, and OpenAI retention also have separate limits.

Deleting a Memory does not revoke its Landmark Unlock or refund spent credits. Deleting the last Memory empties the gallery while retaining earned travel history. Account deletion is the broader option for removing the account and its owned content.

Questions to settle before uploading

Evaluate AI reference photo privacy across the whole process, not through the word “private” alone. Unlocked’s documentation answers several practical questions, while leaving external retention details unresolved in the supplied material.

For any service, ask:

• Is upload consent separate from permission to send images elsewhere?
• Which service receives the photo, and what triggers that transfer?
• What context accompanies it?
• What are the retention and training-use rules?
• Can you remove references, finished images, and the account separately?
• What remains after deletion, and for how long?

These are evaluation questions, not claims that every app offers the same controls. Private AI photos still need clear explanations of access, transmission, and deletion.

Before choosing a reference, use the AI travel photo privacy checklist alongside the current policy and in-app permission screen. If external retention or sharing consent remains unclear, resolve that point before uploading.