Skip to content
TripStory
How it worksExamplesPricingAbout
  • English
  • עברית
Sign inStart free
Privacy policy

Your photos, your trips, your call.

Last updated November 14, 2026

On this page
  1. What we collect
  2. How we use it
  3. AI and your photos
  4. Journey pages and sharing
  5. Who helps us run TripStory
  6. Statistics and cookies
  7. How long we keep things
  8. Your choices and rights
  9. Security
  10. Children
  11. Changes and contact

The short version

  • We use your photos and the time and place stored in them for one thing: making your trip’s story, map and film.
  • Your photos are never used to train AI models - ours or anyone else’s.
  • Living photos on your free trip and with a Trip Pass are made on our own servers. Only Explorer trips use outside engines (Google Gemini Omni, Google Veo, Kling).
  • Journey pages never show your photos’ GPS data or exact times; places are rounded to about 100 m.
  • No ads, and we never sell or share your data. Our own statistics, and remembering which link brought you, run only with your OK.
  • Delete a trip and its photos, film, comments and reactions are removed right away.

What we collect

Your account

When you sign up we receive your email address and, if you use Google, your name and profile picture. Sign-in is handled by Firebase Authentication, so your password is never stored by TripStory.

Your photos and what’s inside them

When you create a trip you add photos. Photo files contain metadata - usually the date and time they were taken, the location (GPS), and the camera’s orientation. We read that metadata to work out your days and places. Before you upload, the landing page’s instant preview reads it in your browser only; nothing is sent until you ask for a story.

Photos you import

If you import from Google Photos, you choose the photos in Google’s own picker and we receive only the ones you picked, with their date and camera details. Google doesn’t share their locations with us. The access Google gives us is short-lived and used only to fetch the photos you picked: we never store it, and we close the picking session afterwards. Our use of information received from Google APIs adheres to the Google API Services User Data Policy (opens in a new tab), including its Limited Use requirements.

If you paste a link to an iCloud shared album (a beta feature), our servers read the photos in that album the way anyone with the link could. We never sign in to your iCloud account.

What we make for you

For each trip we create smaller copies of your photos, short captions, the place each photo was taken (from its location, or recognised from what it shows), the story in the voice and language you choose, your route, a film with an original soundtrack and living photos, and a preview image for sharing. Edits you make (titles, sentences, places, cover choices) are saved too.

What visitors leave

People viewing a journey page can react and leave a postcard with a name they choose. When they do, their browser keeps a random identifier (not an account), so they can undo a reaction and we can deal with abuse.

Gifts you give

If you buy a Trip Pass as a gift, you can give us the email address of the person it’s for, how the gift is signed and a message. We use them only to deliver that gift: an email to that address, in the language you chose, with your name and message, which also show to whoever opens the gift code. We send that address nothing else. If you received a gift email and want your address removed, write to hello@tripstory.fun.

Usage and diagnostics

We record product events as described in Statistics and cookies below. Our servers also keep standard logs (request times, errors and performance data) to keep the service running. The requests that carry your privacy choices, our daily totals and our statistics are left out of those logs, so no IP address is kept with them.

How we use it

  • To make and show your trips, and to let the people you choose see them.
  • To run, secure and improve TripStory - for example, finding where uploads fail or how long films take to render.
  • To reply when you contact us, and to send essential account messages (never marketing without your consent).

We don’t sell your personal information, share it for advertising, or use it to build profiles about you.

AI and your photos

To caption your photos, recognise places and write your story, we send downscaled copies of your photos, together with the places and dates we found and any notes you wrote about the trip, to Google’s Gemini models through Google Cloud. The results come back to us and are stored with your trip. Your notes are never shown on your journey page.

When a photo has no location - phones and Google Photos often remove it - the same model suggests where it was taken from what it shows: a landmark, a sign, the landscape. We check each suggestion against your other photos, mark the places found this way, and you can move any of them.

To make living photos - a few seconds of motion in some of your film’s best shots:

  • On every plan: our own film studio adds the motion, on TripStory’s servers in Google Cloud (it may use an open image-to-video model, Wan 2.2, running there). Those photos never leave TripStory.
  • On Explorer, AI motion: an image-to-video model, Google Gemini Omni or Google Veo (Vertex AI, part of Google Cloud) or, when they can’t take a photo, Kling (Kling AI, by Kuaishou Technology). Downscaled copies of the photos chosen for motion are sent to them, and the clips come back to us.

Faces are matched only on your own device, never on our servers. When you add the people on a trip while making it, your browser looks for faces and pets in the photos you picked and shows each person or pet once, as a small picture, so you can name them in one go. This runs entirely in your browser: no face, face measurement or picture of one is sent to us or to anyone else, and nothing of it is kept once you leave the page. What reaches us is only what you choose: the names you type (a first name, and a relation or an age if you like) and which photos they are in. Nothing is matched across trips. If you dictate your notes with the microphone, your browser turns your speech into text with its own speech service (Google’s in Chrome, Apple’s in Safari); we receive only the text. Those names stay yours: journey pages show them as initials unless you turn on “Show first names on the journey page”, and then only first names, never surnames, relations or ages.

We keep AI motion away from close-up faces and from children. A photo with children only comes alive with AI if you tick “These photos are mine to share, including photos of children in my care” for that trip, and then only with an engine named above; you can untick it at any time. Every AI-animated scene in a film is labelled.

Your photos are never used to train AI models. We only use AI services under terms that prohibit the provider from training on our customers’ content, and we don’t train models of our own on it.

AI can get things wrong - a place, a detail, a mood. Everything it writes is editable, and nothing is shared until you share it.

Journey pages and sharing

Each trip has a visibility setting that you can change at any time: Public (anyone can view it, and it may be featured on TripStory), Anyone with the link, or Only you.

When a trip is shared, visitors see its title, story, photos, film, route and the places you visited. To protect you, journey pages never include your photos’ GPS data or exact timestamps, place coordinates are rounded to roughly 100 metres, and your name is shortened (for example, “Dana K.”).

Anyone who can see a journey page can also copy its route or download what’s shown on it, so share with people you trust.

You can also turn on a public profile (off unless you do): a page at your own address with your public journeys, the name you choose, an optional line about you, and your account photo or an initial. Link-only and private journeys never appear on it, and turning it off removes the page immediately.

Who helps us run TripStory

We use a small number of service providers, each only for the job listed:

  • Google Cloud and Firebase - sign-in, database, photo and film storage, servers and job queues; the Gemini models for captions, place recognition and stories; Gemini Omni and Veo for Explorer’s living photos; and the servers our open living-photo model runs on. Google’s sign-in code loads only when you choose to sign in, or are signed in.
  • Kling AI (Kuaishou Technology) - makes living photos for Explorer trips. It receives downscaled copies of the photos chosen for motion, processed through its API in Singapore.
  • OpenStreetMap Nominatim - turns the approximate coordinates of your places into names like “Sintra”. Our servers send coordinates only; no photos or account details.
  • OpenFreeMap - serves the map tiles your browser shows. Like any website, it sees your IP address and which part of the map is being viewed.
  • Stripe - processes payments for paid plans. TripStory never sees or stores your card number.
  • Paddle - where we use it, sells paid plans as merchant of record and handles checkout data under its own policy. Its checkout loads only on our payment pages.
  • Resend - sends our emails: account and trip emails, purchase confirmations, and a gift’s email to the person it’s for. It receives the address, the subject and the message. Open and click tracking are off, so our emails carry no tracking pixels or rewritten links.

Google Photos and iCloud are places you choose to bring photos from, not providers we send your data to: we only fetch the photos you pick or share with us.

Fonts are served by TripStory itself, and we don’t embed social-media widgets or advertising scripts.

Statistics and cookies

TripStory asks before it keeps anything optional in your browser. You decide in Privacy choices, at the bottom of every page; one choice covers every TripStory site in this browser for 6 months. The full list of cookies and similar technologies, with how long each lasts, is in our Cookie policy.

Our own statistics (only if you allow them): a random identifier in the ts_mid cookie (12 months, never extended) and a visit identifier let us see how TripStory is used: pages, features, loading times and errors. While you are signed in, these events are linked to your account. They stay with TripStory, are kept for 400 days and are never used for ads.

Counting without an identifier: until you choose, we count visits, loading speed, errors, and how often this question is shown in daily totals only. The count carries no identifier and nothing is stored in your browser for it; it stops once you refuse our statistics or your browser sends Global Privacy Control or Do Not Track.

Which link brought you (only if you allow it): the link you arrived through (a TripStory partner’s link, campaign tags and the first page you saw, or a journey page someone shared with you) is kept for 30 to 90 days, so the right person is credited if you sign up. When you sign up, it is recorded with your account, together with the consent ID of your choice, to show the credit was allowed. If you later turn it off, that record is removed from your account. A friend’s invite works differently: see the next paragraph.

A friend’s invite: when you press Start on a friend’s invite page, the ts_rcode cookie keeps the invite for 30 days so your gift applies when you sign up. It is part of the invite you asked for, so it needs no separate OK.

Partner links

  • Some creators and travel sites share TripStory through partner links.
  • If you open one and allow "Which link brought you", the ts_aff cookie keeps, for 30 days, the partner’s code, which of their links you used, a tag they chose and the time of the click. It replaces a friend’s invite if there was one: the link you opened last counts.
  • Your click is also counted in that partner’s click totals (with that link and tag and the kind of page it led to), never who you are.
  • If you then create an account, the partner learns that an account joined through them and what it bought (plan and amount), never who you are: no name, no email, no photos.
  • The partner does see which of their own links and tags the account came through. A partner who gives each person a link of their own could therefore tell that person’s purchases apart.
  • If you later turn "Which link brought you" off in the same browser, or anywhere while signed in, your later purchases stop counting for the partner.
  • Partners who are paid give us their payout email, which PayPal, Wise or Payoneer receive when we pay them.

Global Privacy Control and Do Not Track: if your browser sends either signal, we treat it as "Reject all" without asking, show "Opt-Out Request Honored" in Privacy choices, and credit no partner for your visit. If you are signed in, we also note the opt-out on your account. We do not sell or share personal information.

A record of your choice: each time you choose, we keep what you chose, when, on which TripStory site and which kind of page, in which language and on which kind of device (phone, tablet or computer), with a random consent ID that Privacy choices shows you. The record itself has no name, email, IP address or account; if you allow "Which link brought you" and sign up, the consent ID is noted with your account. We keep records because the law asks us to show what you agreed to and that we respected what you refused, use them for nothing else except daily totals of how people answer, and delete them 5 years after the choice ends. The Cookie policy has the details.

Signing in uses Google Firebase, which keeps you signed in with your browser’s storage and records its own software versions. Firebase and Google’s sign-in code load only when you sign in or are signed in.

Allowing "Our own statistics" or "Which link brought you" is voluntary, and refusing changes nothing you can do in TripStory.

How long we keep things

  • Trips and your account: until you delete them. Deleting a trip removes its photos, film, story, comments and reactions from our database and storage immediately.
  • Uploads that never became a trip: removed with the trip draft they belong to.
  • Google Photos access: used only while we fetch the photos you picked, never stored; the picking session is deleted afterwards.
  • Living-photo records (which engine animated which photo, and how it went): 30 days.
  • What our AI said about your photos (captions, the place a photo was recognised at, a numeric fingerprint), kept with your account so the same photo is never sent to an AI model twice, even in another trip. Removed when you delete the last trip with that photo, and with your account.
  • Gifts: the recipient’s email address until the gift is redeemed; the name and message with the gift code. Your order keeps the gift’s details with your purchase records, and loses them if you delete your account.
  • Email delivery records (which email went out, when, and whether it arrived; the address only as a one-way hash and its domain, never the message): 180 days.
  • Statistics events (as described above): 400 days, then deleted. Daily totals without identifiers: 25 months.
  • Totals made from statistics (how many visits, sign-ups and purchases each week and month) and anonymous summaries of the trips people plan (where, how long, which month, the budget and the places; never an account or anything you typed): kept without a time limit. They describe how TripStory is used, not who uses it; once a plan is deleted or expires, nothing links its summary to anyone.
  • Records of your privacy choices: while the choice lasts, plus 5 years.
  • Server logs: kept for about 30 days.

Your choices and rights

  • Change who can see any trip, edit anything we wrote, or delete a trip, from the app.
  • Delete your account and every trip in it yourself, from your Account page. It takes effect immediately.
  • Download your films as MP4 files at any time.
  • Ask us for a copy of your data, or to correct it, by emailing hello@tripstory.fun. We reply within 30 days.
  • Change or withdraw your privacy choices at any time in Privacy choices, at the bottom of every page, as easily as you gave them.

Depending on where you live (for example the EU, UK, Israel or California), you have legal rights to access, correct, delete, port and object to the processing of your personal data, and to complain to your local data-protection authority. We honour these rights for everyone, wherever you are.

Security

Everything travels over encrypted connections. Photos are stored in private storage buckets and served through unguessable links; only your account can change your trips. No system is perfectly secure, so we keep what we store to what the product needs.

Children

TripStory isn’t meant for children under 13 (or under 16 where local law requires it), and we don’t knowingly collect their data. If you think a child has created an account, contact us and we’ll delete it. Everything optional is off for everyone by default, whatever their age.

Changes and contact

If we change this policy we’ll update the date at the top, and tell you by email or in the app before any change that affects how your photos are used.

Questions or requests: hello@tripstory.fun. See also our Terms.

About TripStory

TripStory

Stories, maps and films made from the trips you’ve already taken.

hello@tripstory.fun
Englishעברית

Display

Theme

Product

How it worksTry it on your photosExamplesRoad tripsPricing

Company

AboutOur privacy promiseQuestionsContact

Legal

PrivacyTermsCookiesCreditsAccessibility

Follow

Instagram soonTikTok soonYouTube soon
© 2026 TripStorySample trip photos from Wikimedia Commons contributors (photo and font credits) · Maps © OpenStreetMap contributors · Coastlines: Natural Earth