What we collect, and what we do not

MyTripLogix is owned and operated by Kairos Software AI, Inc., doing business as MyTripLogix, registered at 721 Old Dairy Drive, Wake Forest, NC 27587. “We,” “us” and “our” in this page mean that entity.

• ·Trips are private until you share them. Collaboration is invite-only, and every share surface states in plain language who can see what.
• ·Your original photo files are kept exactly as uploaded, with their metadata — including location — stored privately. Every copy shown on screen, shared, printed or sent to a model has the location metadata removed.
• ·We ask your date of birth and country once, to check you are old enough for where you live, then discard both. Neither is ever stored.
• ·Location data is never published without you turning it on for that specific trip.
• ·You can delete everything from your account settings without asking us first. Deleted content is hidden at once and destroyed 30 days later. The self-serve export is temporarily unavailable; email us and we send a copy within 30 days.

• ·Your account. Email address, display name, and a password you set. Sign in with Google or Apple instead and we receive your email and name from them rather than holding a password at all. New accounts also get a short series of emails on how to use the product, about one a week; every one has an unsubscribe link and the series can be turned off under Account, then Email.
• ·Your trips. Everything you enter — days, stops, times, routes, budgets, expenses, notes and captions — plus who you have invited and what role you gave them.
• ·Your photos. The files you upload and the information already inside them, which for most cameras and phones includes the time the photo was taken and often the place. That is what lets a photo file itself against the right day and stop. The original keeps that metadata and is stored privately; the copies made for display, sharing, print and TripLogix AI have the location metadata removed.
• ·Payments. Subscription status and book orders. Card details go to Stripe on the web and to Apple in the iOS app, and never reach our servers.
• ·Operational records. Ordinary server and security logs, and a per-trip audit of significant actions such as invites, ownership transfers and share links, which the trip owner can see.

To run the product you asked for: to build your itinerary, to file your photos against it, to write and lay out a book from the result, to bill you if you are on a paid plan, and to keep accounts secure.

We do not sell your data, and we do not use your trips or photos to advertise to you.

For readers who need the formal basis: running the product, filing your photos and billing you rest on the contract we have with you. Security logs and fraud prevention rest on our legitimate interest in keeping the service and its accounts safe. For visitors in the EU, the UK and Switzerland, the analytics and advertising cookies described under Cookies below rest on your consent; everywhere else they rest on our legitimate interest in knowing whether the site and our ads work, and you can opt out of them.

Several features send your content to a model run by Anthropic (Claude). Photo captions send a reduced-size preview of the photograph itself, with the trip title, place, date and the stop it was filed under — a model shown only your text writes a caption you would not recognise. No location metadata goes with it. Day descriptions, the trip narrative, the trip summary, plan suggestions and the enrichment of plan items send text only — your itinerary, captions and notes, not the images. Pasting a flight ticket to fill in a flight sends the pasted text, and importing a plan sends the PDF or the text you give it. All of these are proposals you can edit or discard, and nothing TripLogix AI writes is published without you approving it.

Trip cover art, the illustrated banner you can generate for a trip, is made from text alone. Anthropic's model condenses your itinerary into a short description of the trip, and that description goes to Google (Gemini) with the trip title, dates, destination and any cover art notes you wrote; Gemini paints the image. None of your photos are sent, and it runs only when you ask for it.

Book cover art differs from everything above in two ways. It is generated by Google (Gemini) from a banner image that is itself AI-generated — never from one of your photos — and it runs automatically in the background when a book is created or its size or paper changes, so that the book is ready to look at. Everything else on this list runs only when you ask for it, and a caption you wrote or edited yourself is never overwritten by a bulk run.

Suggested activities are generated from your destination and dates, and are marked as estimates. Verify hours and prices yourself.

We use a small number of service providers, each for one job, and each bound to handle your data only on our instructions.

• ·Supabase — database, authentication and file storage.
• ·Amazon Web Services — application hosting and content delivery.
• ·Anthropic — the model behind captions, day descriptions, trip narrative and summary, plan suggestions and enrichment, flight-ticket parsing, trip import, and the description trip cover art is painted from, as described under Artificial intelligence above.
• ·Google (Gemini) — generates trip cover art from a written description of the trip, and book cover art from an AI-generated banner image. It never receives your photos.
• ·Mapbox, Visual Crossing, AeroDataBox and the U.S. Energy Information Administration — place, weather, flight and fuel-price lookups. Each receives only the place, date or flight number being looked up: no photos and no personal data.
• ·Stripe — subscription and book payments on the web.
• ·Apple — subscription payments made through the iOS app.
• ·RPI, our print partner — receives the finished book PDF and the shipping address, and nothing else.
• ·Resend — delivers our email, such as invites, confirmations and order updates.
• ·Google Analytics — counts visits to the site and the app, as described under Cookies below. Events from the iOS app are relayed through our server with an internal account identifier, never your name or email.
• ·Google Ads and Meta — receive a conversion event when you create an account or complete an order, as described under Cookies below.
• ·Stay22, our booking-link partner — when you follow a Find a hotel link it receives the search you asked for (the place, dates and number of guests) and that you came from this site, and sends you on to a booking site. The hotel map on the booking page is loaded from stay22.com with the same details. Its script on our pages is covered by the cookie choice below. It never receives your account, trips or photos.
• ·Kairos Software, our support desk — its widget loads on the marketing pages and, when you are signed in, receives your name and email so that support can reply to you. It is not covered by the cookie choice below.

Which rows you can read is enforced by the database itself rather than by application code that could forget to check. Photos are served through short-lived signed links, never public URLs, and your original camera files are never sent to a browser at all — a shared trip page gets derivatives generated for display, with the location metadata removed.

No system is perfect. If you think someone else has reached your account, change your password and write to support@mytriplogix.com straight away.

We set cookies to keep you signed in, and to remember that you have unlocked a password-protected share link — both are necessary for the product to work and are set regardless of the choice below. Google Analytics, Google Ads and Meta Pixel each set one more, a random identifier that lets them tell a returning browser from a new one, and the Stay22 script sets one so that a hotel booked after you followed one of our links can be credited to us. That is the entire list, and all four are optional analytics, advertising and partner cookies covered by the same choice. This page, the Terms and the Support page set none of them and show no cookie prompt, so opening them from the MyTripLogix iOS app involves no tracking of any kind.

Google Analytics tells us how many people visit each page, which pages, from which countries and on what kind of device, and whether a visit ended in an account being created or a plan or book being bought. Google Ads and Meta Pixel are told only that an account was created or an order completed, so we can tell whether an ad led to one — no page-by-page browsing history, and neither receives your trips or photos. None of the three receive your name or email address, the Google Signals advertising features are switched off, and none of them are loaded on the operator console.

A banner on your first visit offers Accept or Decline, and everything else on the site works exactly the same either way. What happens before you choose depends on where you are. In the EU, the UK and Switzerland, no analytics or advertising cookie is set until you press Accept: Google Analytics and Google Ads load in Google's consent mode, which lets them record that a page was viewed without setting a cookie or storing any identifier on your device. The Meta Pixel has no such mode, so there it loads with its consent revoked and sends nothing until you press Accept; it reads where you are from your browser's time zone. The Stay22 script has no such mode either, so in those regions it does not load at all until you press Accept. Everywhere else, all four cookies are set from your first page, and Decline turns them off.

Declining deletes the cookies already set, stops the scripts sending anything more, and means none of the four load on later visits. If your browser sends a Global Privacy Control signal, we treat it as Decline without asking. Neither Google service is used to personalise ads to you, whatever you choose.

MyTripLogix is operated from the United States, and the providers above process data there and in some cases elsewhere. Where personal data of people in the UK or the European Economic Area moves out of those regions, it moves under the EU–US Data Privacy Framework where the receiving provider is certified under it, and under Standard Contractual Clauses where it is not.

We have not yet designated a representative in the EU or UK under Article 27 GDPR / UK GDPR. Until we do, a person in the EU or UK exercising a right under this page should write to privacy@mytriplogix.com, and we will handle the request directly under the same statutory deadlines.

• ·Export. The self-serve export is temporarily unavailable while we rebuild the tool that assembles it. A request queued from your account is saved and runs when exports resume. For a copy now, email privacy@mytriplogix.com and we prepare it by hand — everything you own or wrote, as structured data plus your original media files — within 30 days.
• ·Delete. From your account. Deleting asks you to type to confirm, states exactly what will be destroyed, and locks the account immediately. Content then enters a purge queue and is destroyed 30 days after the request, during which you can contact us to reverse it. Deleting a single photo or trip works the same way: it is hidden at once and destroyed 30 days later, and until then a photo can be brought back with Restore and a trip by asking support. Records we are required to keep for tax and accounting are kept, and nothing else is.
• ·Correction or objection. Ask us to correct something or object to how we use your data through Support in the app, or by emailing support@mytriplogix.com. We work to the statutory deadline that applies to you.

MyTripLogix is not built for children and we do not knowingly hold data about them. You need to be at least 13, or 16 where local law requires it. We check at signup and do not keep the date you give.

If this page changes in a way that affects what we do with data you have already given us, we will tell you before it takes effect rather than quietly revising the date at the top.