Privacy policy

Updated September 25, 2026. For privacy questions or requests, email pamihood@gmail.com.

What we collect and why

We use your Apple or Google account identifier (or existing email sign-in), email address, and the name or photo you provide to sign you in and maintain your account. Your profile includes your name, optional photo, and how you travel: your own words, if you add them, and the tags you choose.

When you choose trip photos, we upload resized copies and available capture dates, embedded location coordinates, and photo metadata. We use these to organize your itinerary and identify places. We do not request continuous device location or access your entire photo library. You choose the photos.

When you add videos, the app converts each one on your phone before uploading it: at most 1080p and only its first 5 minutes, with its sound but without its location or other embedded details. We store the converted video, a poster image and three still frames from it. Its capture date and location are kept separately to place it on the right stop and are not shown to readers. The app keeps its own copy of a video only until the upload finishes.

We store your guides, edits, tips, audience settings, friendships, requests, and saves to provide the service. Technical logs, errors, device/app details, and performance diagnostics help us fix failures and keep the service secure. Support and safety reports include the information you submit.

We also keep our own log of how the service is used: events such as starting an upload, a trip becoming ready, editing, reviewing, publishing, opening, saving or sharing a trip, and searching, with your account, the trip involved, whether it happened in the app or on the website, a random id for that visit, and the search text you typed. We use it only to understand how the product is used and to improve it. The log is never shown to other members or used for advertising; guide view counts, below, are kept separately and hold no information about who opened a guide. Our hosting providers process it to operate the service; we do not sell it or share it for others’ marketing. We retain it for up to 400 days (about 13 months), or until you delete your account, whichever comes first.

AI and service providers

Before creating or extending a guide, we ask permission to send selected photos (and, for videos we need help placing, three still frames), capture dates and trip information to OpenAI for analysis of places and activities, and location coordinates and place clues to Google Maps Platform to identify places. We use the analysis to build your guide. All uploaded photos can be analyzed, including photos you later hide from the guide. Leave out any photo you do not want analyzed. AI never receives your videos or their sound. When a video’s capture time and place are not enough to put it on a stop, we send three still frames from it to OpenAI to find where it belongs; videos without a location are never sent. Leave out any video whose frames you do not want analyzed. When you reach Your take or request an updated suggestion, we also send itinerary details and review feedback to OpenAI to prepare an optional introduction. It does not replace your writing unless you choose to use it. AI can make mistakes: review the draft before publishing. You can decline and continue browsing.

Supabase hosts accounts, database records and uploaded images and videos; Vercel hosts our website and backend; Inngest coordinates guide creation. OpenAI processes AI requests. Google provides place lookup and maps; Apple provides native maps and sign-in. Google also provides sign-in and web fonts. Route maps on the website load map tiles from OpenStreetMap servers, which receive your IP address and the map areas you view. Sentry receives diagnostic events when enabled. Resend sends account-related notifications when configured. These providers process data for the functions described here and under their own applicable terms and retention rules.

We do not sell personal data or use it for cross-app advertising. We do not train our own AI models on your photos. Under OpenAI’s API data policy, API data is not used for training by default. Safety logs may contain submitted content and are normally kept for up to 30 days. Legal or safety exceptions can require longer retention, including some images flagged for review. This is separate from the photos we store to build and display your guide; it is not a promise that all copies are deleted within 30 days. Processing may take place outside your country.

What other people can see

There is no searchable member directory. People can connect through a friend invitation or the author of a guide they can read. Profile access depends on sign-in, friendships and shared guides. When you save a guide, its owner can see that you saved it and when, and everyone who can open the guide sees how many people saved it. A guide’s owner can also see how many people have seen it: the first time a browser or the app on a device opens it, one is added to a daily count, and nothing else is recorded with it, not your account, IP address or the time. Owners never see who opened their guide, and nobody else sees that number. Your guide audience controls access: Only you, Anyone with the link, Friends and link, Friends only, or Public. Anyone with a shared link can forward it. Public guides are readable by anyone. Photos, videos with their sound, and location details you publish may reveal where you traveled or stayed. A video appears in a guide only after it has finished uploading and we have checked that it carries no location data. Only upload and share images and videos you have permission to use.

Blocking removes your friendship and prevents interactions and guide/profile access between the signed-in accounts. Public and link-shared content may still be viewed while signed out. Previously downloaded copies cannot be recalled; existing signed image and video links may work briefly until they expire.

Your controls and deletion

Edit your profile, hide a photo or video from a guide, change a guide’s audience, unpublish a guide, regenerate its link, remove a friend, or delete a guide in the app. You can decline AI processing and keep browsing without uploading photos.

Use Profile → Delete account in the iPhone app, or Delete account on the web. This removes your account and associated guides, uploaded images and videos, profile, saves, and friendships from our live service. Failed deletion can be retried. A minimal safety-report record may be retained to investigate abuse, with deleted account references removed.

Operational backups, transient processing caches, and service-provider security logs may retain copies after live deletion until their retention periods end. They are not used to restore your deleted profile or guides to the live service. Email us to request access, a copy, correction, or deletion of personal data, including questions about provider retention.

Cookies and local storage

We use session cookies and app storage to keep you signed in, remember preferences, and resume interrupted uploads. Your browser and the app remember which guides they have already counted, so opening a guide again doesn’t count it twice. The app caches images and temporary files for performance, and keeps videos waiting to upload until they finish. Signing out removes your session and those files; deleting the app clears its local data.

Children and changes

This beta is intended for adults and is not directed to children. Do not create an account if you are under 18. Contact us if a child’s information was submitted without appropriate permission.

We will update this page when our practices change and request new permission when required for a materially different use of your data.