Privacy Policy

Tripmojo and Airport Mojo (“we,” “us,” or “our”) are travel apps operated by Candle Studios LLC (Washington, USA). Tripmojo organises booked trips; Airport Mojo provides airport, lounge, live-flight, and airport-place information. This Privacy Policy covers both apps and the tripmojo.ai website. It explains what personal information we collect, why we collect it, how we use it, who we share it with, and the choices you have.

If you have questions, contact us at contact@tripmojo.ai.

• Account information. When you create an account we collect your email address. If you sign in with Google or Apple, we receive your email and name (Apple may give you a relay email via Hide My Email), and a profile picture where provided. During combined Google signup, if you grant the separate birthday permission, we also receive and store your date of birth when Google provides a complete date.
• Profile and preferences.Optional details you add - display name, home city, home currency, traveler type, budget preference, dietary preferences, interests, trip vibes, and places you’ve visited - used to personalise suggestions.
• Trip content. Destinations, dates, travelers, bookings (flights, hotels, activities, restaurants, transit), itinerary items, expenses and who owes whom, comments you add to plan items, and any photos or notes you add.
• Public contributions. Ratings, reviews, display names, and photos you choose to post about airport places. We show approved contributions to other users and process them for moderation, abuse prevention, and reports.
• Travel documents.Booking confirmations, boarding passes, and e-tickets - ones you upload, ones we find in a booking email you asked us to read, and ones our check-in assistant saves from an airline’s website (Section 5a) - plus anything you choose to store in your Wallet. Wallet documents can include sensitive information such as passports, visas, driver’s licenses, IDs, insurance, and vaccination or health certificates. We store what you choose to upload; please only add documents you’re comfortable storing with us.
• Booking emails. If you forward a booking email to your Tripmojo inbox address, or connect a Gmail account (see Section 4), we receive and process those emails - including their attachments - to build your trips. Forwarded emails are archived so we can re-read them if extraction needs to be re-run.
• Device location (optional).If you grant permission, the app uses your device’s approximate location to suggest nearby places. This happens on your device to fetch suggestions; we don’t store your device location on our servers. Coordinates we do store are for places you add to a trip (e.g. a hotel or activity).
• Notifications. If you enable push notifications, we store a device push token so we can send you trip updates.
• Usage, analytics, and diagnostics. We collect feature-usage events, screen views, app performance, and crash reports (see Section 7), plus standard log data such as IP address, device/browser type, and timestamps, to operate, secure, and improve the service.

We do not receive or store complete payment card or bank account numbers. If you buy an eSIM or another paid product in Airport Mojo, the payment provider collects and processes your payment details; we receive transaction status, order, amount, currency, and fulfilment records needed to complete and support the purchase.

• Provide and operate the service (accounts, trips, sharing, expenses).
• Read and parse booking emails and documents to build your itinerary.
• Personalise destination ideas and nearby suggestions.
• Send service communications (account confirmations, trip updates, security notices).
• Improve, troubleshoot, secure, and prevent abuse of the service.
• Comply with legal obligations.

We do not sell your personal information, and we do not use your data to train third-party AI models.

Google profile birthday. During first-run combined Google signup, we ask for the user.birthday.read scope. If you grant it, our server requests the birthday on your own Google profile through the Google People API and stores it as your Tripmojo date of birth. We use it to personalise birthday-relevant experiences. Google may provide no birthday or a month and day without a year; in either case we store nothing. We do not request this permission when you later connect a secondary Gmail account, and declining it does not prevent Google sign-in or Gmail booking import.

You can optionally connect a Gmail account so we can find your travel emails automatically. When you connect, Google asks you to grant the gmail.readonlyscope, which is read-only access to your Gmail. We use it for three things and nothing else, all to enrich how Tripmojo works for you: finding travel bookings (flights, hotels, car rentals, rail, activities) and extracting their details into your trips, finding reward points statements so we can keep your points and miles balances current in Tripmojo, and, during a trip, finding card transaction alerts and app receipts so we can log your trip spends. We don’t use it to read unrelated personal, financial, or medical email for any other purpose.

Which reward points statements. Reward points statements from airlines, hotel groups, other travel programmes and card issuers and banks are covered by connecting Gmail, and the connect screen lists them among the things we look for. You can turn reward points statements off at any time in Settings, under Consents, and we will stop. Turning them off does not disconnect Gmail or affect your booking confirmations.

From any reward points statement we read only the points balance it states. We do not read, extract, infer or store the purchases, transactions or account balances in money listed on a statement. Trip spends are a separate feature, described below.

What we access and store.Our servers query your mailbox for messages matching travel-booking searches and read those messages’ content, including HTML bodies and attachments (e.g. PDF confirmations), because that’s where booking details live. From them we store: the extracted booking details (dates, times, confirmation numbers, locations, prices), an archived copy of the source booking email and its attachments (so extraction can be re-run and so you can open the original), and scan bookkeeping (which message IDs we’ve already processed). Messages that don’t look like travel bookings are discarded after the automated check and are not stored.

Reward points statements.We search your mailbox for points statement emails (subject lines such as “points balance” or “miles summary”) and read the text of the messages that match. From a reward points statement we store: the programme, your balance and the unit it is counted in, the tier or status printed, the statement date, any expiry date the email states, and the membership number and member name as printed. We also keep a reference to the source message and a record of which messages we have already processed. We do not keep a copy of the statement email itself. For a card issuer programme we identify the account by the issuer and card name you confirm, never by a card number or its last four digits. Messages that turn out not to be reward points statements, including ordinary bank and credit card statements, are discarded after the automated check and are not stored.

Trip spends. Reading trip spends is on by default when you connect Gmail. From one day before a trip starts until three days after it ends, we search your mailbox for transaction alerts from your bank or card issuer and for receipts from ride, food delivery and shopping apps, and read the text of the messages that match. From each spend we store: the amount and currency, the merchant and its city, the date and time, the category, any order or transaction reference printed, and the last four digits of the card when the alert prints them. We also keep a reference to the source message and a record of which messages we have already processed. We do notkeep a copy of the email, and we never store a full card number, account number or account balance. Messages that turn out not to be a spend, or fall outside your trip dates, are discarded after the automated check and are not stored. On a trip only you are on, spends are added to that trip’s expenses; on a shared trip they wait as suggestions that only you can see until you add them. You can edit or remove any of them. You can turn trip spends off at any time in Settings, under Consents, and we will stop. Turning them off does not disconnect Gmail or affect your bookings or points.

Scanning runs on our servers, not on your device. We store the access we’re granted (an OAuth token) securely on our servers so we can perform the scans you ask for; we never place these tokens on your device. You can disconnect at any time in Settings → Connected accounts, or revoke access from your Google Account; deleting your Tripmojo account also revokes them and deletes the data described above.

Limited Use.Tripmojo’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we:

• only use Gmail data to provide the user-facing features described here - importing your bookings, keeping your loyalty balances current, and logging your trip spends - never for advertising, market research, or building profiles unrelated to those features;
• only transfer Gmail data to service providers acting as our processors for these features (the AI service providers in Section 5, which extract booking, loyalty and trip spend fields and help our check-in assistant, and our cloud hosting/storage - see Sections 5, 5a and 6), as necessary to provide them, or when required by law;
• do not sell Gmail data;
• do not allow humans to read it, except with your explicit consent (e.g. a support request you initiate), for security or abuse investigations, or to comply with law;
• do not use Gmail data to train generalised AI or machine-learning models.

Tripmojo uses AI service providers to read your travel content and help organise it. Specifically, we send them:

• the text and images of booking emails and documents you forward, upload, or that we find in a connected Gmail account, so it can extract booking details (dates, times, confirmation numbers, locations, and similar fields);
• the text of travel loyalty statement emails found in a connected Gmail account, so it can extract your programme, balance, tier, membership number and statement date;
• during a trip, the text of card transaction alerts and app receipts found in a connected Gmail account, with card numbers masked first, so it can extract the amount, merchant, date and category of each spend;
• trip context and your profile/preferences, so it can suggest destinations, plans, and nearby activities;
• during an airline check-in, screenshots of the airline’s website together with the booking reference, passenger names and, when the airline asks for them, travel-document details from your Wallet, so our check-in assistant can complete the airline’s steps (Section 5a).

These providers process this data only on our behalf and are not permitted to use it to train their models. AI output can be wrong or incomplete - always verify important details against the original source.

Where you switch on automatic check-in, we check you in on the airline’s website and save your boarding pass to your booking. For flights you are travelling on, we also fetch a boarding pass you have already obtained yourself and attach it to your booking. We use a hosted browser to do this, and an AI model (Section 5) reads each page of the airline’s website to decide the next step. We never use your airline login.

We don’t sell your data. We share it only with service providers (“subprocessors”) that help us run Tripmojo and Airport Mojo, each processing data on our behalf under their own terms:

• Cloud hosting providers - application hosting, databases, file storage, and web hosting and deployment.
• AI service providers - AI processing of emails, documents, trip context, and the airline web pages our check-in assistant reads (Sections 5 and 5a).
• Google APIs (People, Gmail, Maps/Places) - Google-profile birthday retrieval during combined signup, booking-email import (with your consent) and place/location lookups for suggestions.
• Hosted browser providers - the browser our check-in assistant drives on airline websites (Section 5a). It handles what that task needs: the booking reference, the passenger name, any travel-document details the airline requires, and the boarding pass the airline shows.
• Firebase (Google) - sign-in/authentication, push notifications (Cloud Messaging), analytics, and crash reporting (Section 7).
• Email routing providers - inbound email routing and short-term storage of raw forwarded emails so we can process them.
• Email delivery providers - sending transactional email (invites, confirmations, notices).
• Google & Apple - when you choose to sign in with those providers.
• Payment and fulfilment providers - payment processing and delivery when you choose to buy an eSIM or another paid product in Airport Mojo.

We disclose information to law enforcement only when required by a valid legal request.

We use Firebase (a Google service) for product analytics, performance monitoring, and crash reporting. Analytics records feature-usage events and screen views with an account identifier so we can understand and improve how the app is used. Crash reports include a one-way hashed account identifier plus diagnostic breadcrumbs (such as the screen you were on and connection state) - they do not include your emails, names, documents, or booking details.

When you add someone to a trip as a Viewer, Editor, or Organiser, that person can see the trip’s contents (itinerary, bookings, members, expenses, comments, and activity history). If you add someone by email, we email them an invite and they gain access when they sign up. Public trips you share via a link are visible to anyone with the link.

We’re not responsible for how other trip members handle information you share with them. Only invite people you trust, and only add documents you’re comfortable sharing with that trip’s members.

We keep your account and trip data for as long as your account is active. When you delete a trip, it and its attached files (bookings, itinerary, documents, comments, and expenses) are permanently deleted.

When you delete your account, we promptly delete your profile, preferences, connected-account tokens (and attempt to revoke them at the provider), notifications, push tokens, Wallet documents, and the trips you solely own; trips shared with other members continue under the remaining organiser. We also purge the raw copies of any emails you forwarded to us. Traveller reviews and their uploaded photos are deleted with the account; moderation and abuse records may be retained where necessary to protect the service and enforce our rules.

Deleted content may persist for a short time in our service providers’ encrypted backups before being overwritten on their normal backup cycles.

In Airport Mojo, deleting your account removes your profile, preferences, saved flight watches and alerts, notification tokens, reviews, uploaded review photos, and blocked- traveller list. Completed eSIM or other purchase records may be retained after being disconnected from your account where required for tax, accounting, fraud prevention, refunds, chargebacks, or legal compliance. See the dedicated Airport Mojo account and data deletion page for the exact steps.

Depending on where you live, you may have the right to:

• Access the personal data we hold about you.
• Correct inaccurate data.
• Delete your data (you can delete your account in either app at any time, or follow the Airport Mojo deletion steps).
• Export your data in a portable format.
• Object to or restrict certain processing.

To exercise these rights, email us at contact@tripmojo.ai from the email address associated with your account.

With your consent, the app may ask for access to your camera and photo library (to scan and attach booking documents), your microphone and speech recognition (to dictate trip ideas in the planner), your approximate location (for nearby suggestions), and to send notifications. You can change or revoke any of these in your device settings at any time; the related features simply won’t work without them.

Tripmojo and Airport Mojo are not directed to children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us and we will delete it.

We and the service providers listed in Section 6 may process your information in countries other than the one you live in.

We use industry-standard measures to protect your information, including encrypted transport (TLS), encrypted storage at rest, and server-side authorization checks on every data access (clients never talk to the database directly). Gmail OAuth tokens are stored only on our servers, never on your device. No system is perfectly secure, but we take our obligations seriously.

We may update this Privacy Policy from time to time. Material changes will be announced in-product or by email. The “Last updated” date at the top of this page reflects the most recent revision.

Privacy questions, data requests, or anything else: contact@tripmojo.ai.