Privacy Policy

Last updated: October 2026

Overview

Yumu ("we", "us", "the Service") is an AI-assisted travel itinerary planner operated by Yumu Technologies Private Limited, a company incorporated in Singapore. This Privacy Policy explains what information the Service handles when you use it and how it is used.

Information We Collect

When you use the trip form, we process the information you enter in order to generate your itinerary: destination(s), travel dates or trip length, nationality (if provided), preferred currency, travel party size and ages, travel style preferences, and preferred transportation.

If you join the launch waitlist on our landing page, we collect the email address you enter and the language of the page you were viewing. We use them only to send you a confirmation link and, once you confirm, to tell you when Yumu opens up or when your invitation is ready. Nothing is added to the list until you click the confirmation link (double opt-in), and you can leave the list at any time through the link in our emails.

You do not need an account to generate an itinerary as a guest. If you choose to sign in (via Google or Facebook, through Firebase Authentication), we also receive your name and email address from that provider. If you additionally opt in to "remember my preferences," we store your nationality, travel party size, travel style, and preferred currency in your profile so they can pre-fill future trips; you can update or clear these at any time from your Profile page.

If you hold an active paid membership and choose to save an itinerary, we store its destination, its full day-by-day content, the trip-form inputs used to generate it, and anything you add to its Bookings section — such as flight, hotel, or train confirmation numbers, visa/insurance entries, and notes — in our database, against your account, until you delete it, your account, or ask us to remove it. If you enable collaboration on a saved itinerary (see below), invited collaborators can view or edit this stored copy according to the role you assign them.

If you mark a saved itinerary as an "all-time favorite," you publish a copy of it — its destination, full day-by-day content, your travel style tags, your username, your rating, and any blurb you write — to the Community Explore feed, where it is visible to other registered users until you remove the favorite. Comments and votes you post on any itinerary in Community Explore, together with the username on your profile, are likewise visible to other registered users.

If you report an itinerary in Community Explore, we record your account and the time of the report against it, so we can apply an automated threshold that hides itineraries receiving multiple reports pending review. We do not currently collect a reason for the report or share your identity with the itinerary's owner.

If you sign in, we also track participation in the Service's points/rewards program against your profile: a points balance and history of the events that earned it (e.g. completing your first trip, favoriting itineraries, commenting, voting, referring a friend), a shareable referral code unique to your account, and — if you signed up using someone else's referral link — which account referred you.

We also record, against your signed-in profile, that you accepted these Terms & Conditions and the version you accepted. If you use the Service as a guest, we instead record your acceptance locally in your browser (not on our servers).

Like most online services, when you use the Service our servers and hosting providers automatically receive technical information such as your IP address, browser and device type, and the time and nature of each request. We use this to deliver the Service, apply rate limits, prevent abuse, and diagnose errors.

If you consent to optional analytics cookies, we use Google Analytics for Firebase (operated by Google) to collect usage and device information — such as the pages and features you use, in-app events, your browser and device type, approximate location derived from your IP address, and a randomly generated identifier — to understand how the Service is used and to fix problems. Nothing is collected by analytics unless you opt in, and you can withdraw consent at any time from the "Cookie Preferences" link in the footer.

If you use the itinerary collaboration feature, we process the email address(es) you enter to invite other people to view or edit one of your saved itineraries. We store each invited email address, whether the invitation is pending or accepted, and — once someone accepts — a record linking their account to that itinerary, for as long as collaboration remains enabled on it.

If you are signed in, we send you transactional emails about your own account or content — for example, a notification when someone comments on your favorited itinerary, a digest of new likes on it, a reminder about a saved itinerary you haven't marked done, a nudge if your account has been inactive for a while, a welcome email when you register, a notice about your membership status, or a confirmation if you delete your account — using our email delivery provider, Resend. These are sent regardless of any marketing preference, since they relate to your own account activity. If you separately opt in from your Profile page, we may also send you occasional marketing emails through the same provider; you can withdraw this consent at any time from your Profile page, and it defaults to off.

If you use the itinerary map's "Imported Pins" feature, we process the place names and (if available) coordinates you upload from a Google Maps export file (for example, a Google Takeout "Saved Places" CSV). That file is parsed entirely in your browser and is never itself uploaded to our servers — only the resulting list of place names and coordinates is sent to us, and it is stored as part of your itinerary if you save it.

If you purchase a paid membership, payment is handled directly by our payment processor, Stripe — we do not receive or store your card number or other payment card details. We store, against your account, the membership tier you purchased, the amount charged, the purchase and expiration dates, and identifiers Stripe provides for the transaction (such as a checkout session and payment reference), so we can grant, manage, and, if you request it, refund your membership.

How Your Information Is Used

Your trip details are sent to our backend, which forwards them to Google's Gemini API to generate itinerary content. Destination and venue names may also be used to query Wikipedia (for images), a geocoding service (Photon, via our backend, to resolve venue names into map coordinates), and to build Google Maps / Google Search links. Once coordinates are resolved, the itinerary's embedded maps load interactive map imagery, pins, and tiles directly from Google Maps Platform in your browser — unlike the Google Maps search links elsewhere in the Service, these loads happen automatically when you view an itinerary, not only when you click a link.

We use the Gemini API's paid (billed) tier. Under Google's terms for its paid Gemini API services, Google does not use the content you submit — including your trip details — to train or improve its products or models. Google may log submitted content for a limited period solely to detect abuse and to meet legal obligations. We do not control this processing; see Google's own Gemini API terms and privacy policy for the current details.

If a place you import doesn't already include coordinates, its name is sent to the same geocoding service (Photon, via our backend) described above to resolve it into map coordinates. If you use the "Plan Around Your Pins" feature, your imported place names and a condensed summary of your itinerary are sent to Google's Gemini API to suggest which places might fit into your day plan.

If your itinerary involves a foreign currency, we send your preferred currency code (e.g. "USD"), via our backend, to a currency exchange-rate lookup service (open.er-api.com) to fetch a current rate for display and budget calculations — no other information about you or your trip is included in this lookup.

If you save an itinerary, its content and your trip-form inputs are stored so you can retrieve them on a later visit and, if you enable collaboration, so invited collaborators can view or edit them. If you mark it an all-time favorite, its content, your username, rating, and blurb are additionally used to display it publicly in Community Explore, and your votes are used to rank listings there. If you report a listing, your report is used only to apply our automated flagging threshold.

Your points balance, points history, and referral data are used solely to operate the rewards program itself (tracking progress, crediting referrals, and fulfilling claimed rewards) — not for advertising or profiling.

An invited collaborator's email address is used only to grant them the access level you specify (view-only, or full editing if they already have an account) on that specific itinerary, and to send them an invitation email via Resend, our email delivery provider. It is not used for any other purpose, and revoking their access or disabling collaboration removes it from our systems.

If you are signed in, we use your email address, via Resend, to send you transactional emails about your own account activity (see "Information We Collect" above), and, if you opt in, occasional marketing emails. We do not use your email address for any other marketing purpose.

If you purchase a membership, your email address and an account identifier are shared with Stripe solely to process your payment and any refund you request. Any card details you enter go directly to Stripe and never reach our servers — Stripe's own privacy policy governs its handling of that information.

We do not sell your information, and we do not use it for advertising purposes.

AI Training & Data Reuse

We do not use your trip details, saved itineraries, or other personal data to train, fine-tune, or otherwise improve any AI model that we ourselves develop or operate — Yumu does not build or train its own AI models.

The Service generates itinerary content using Google's Gemini API. As described above under "How Your Information Is Used," we use the Gemini API's paid (billed) tier, under which Google's terms state that submitted content is not used to train or improve Google's models or products. We call this out as its own point, distinct from general "service improvement," because whether submitted data is used to train AI models is a specific matter that warrants separate disclosure.

Google processes this content on our behalf to provide the generation service, and may retain it for a limited period for abuse detection and legal compliance, as described in Google's terms. If you are located in Singapore and wish to ask about any such processing, you can contact us, and may also contact Google. We will update this policy if Google's terms for this tier change materially or we change AI provider or tier.

Legal Basis for Processing

If you are located in the European Economic Area (EEA), the United Kingdom, or another jurisdiction that requires a stated legal basis for processing personal data, the bases we rely on are:

• Performance of a contract / provision of a requested service — processing the trip details you enter in the form so we can generate the itinerary you asked for.
• Consent — signing in via Google or Facebook, storing your saved profile preferences, and setting optional analytics cookies (see "Cookies & Tracking" below). You can withdraw this consent at any time, as described in "Data Protection Rights" below.
• Legitimate interests — retaining short-lived, non-profiling request logs to prevent abuse of the Service (e.g. rate-limiting) and to diagnose technical issues, where these interests are not overridden by your own rights and interests.

Data Storage

By default, the Service does not persistently store your generated itinerary or the destination/date details of a specific trip. Your itinerary exists in your browser for the duration of your session and is discarded when you close the tab, refresh, or start a new trip.

The exception is if you hold an active paid membership and choose to save an itinerary: its content, your trip-form inputs, and any Bookings entries are then stored in our database (Google Cloud Firestore), against your account, until you delete it, delete your account, or ask us to remove it. If you additionally mark it an all-time favorite, a public copy is stored in Community Explore until you remove the favorite.

If you sign in, your account profile (email, display name, and any saved preferences described above) is stored in our database (Google Cloud Firestore) until you delete your account or ask us to remove it. Guests who do not sign in have no server-side profile — nothing persists on our servers beyond transient request logs.

Data Security

We use commercially reasonable technical and organizational measures — including encryption in transit, access controls, and reliance on the security infrastructure of Google Cloud and Firebase — to help protect the information described in this policy. However, no method of transmission over the internet or method of electronic storage is completely secure, and we cannot guarantee absolute security. You are responsible for keeping your sign-in credentials confidential.

Data Retention

We keep personal data only for as long as necessary for the purposes described in this policy:

• Generated itinerary content and trip-form inputs are not persisted on our servers by default — they are processed in real time to generate a response and are not stored afterward, unless you save the itinerary as described in "Data Storage" above.
• If you sign in, your account profile (email, display name, and any saved preferences) is retained until you delete your account or ask us to remove it.
• A saved itinerary (including its Bookings entries) is retained until you delete it, delete your account, or ask us to remove it. If it is also published to Community Explore, that public copy — along with any reports filed against it — is retained until you remove the favorite.
• Waitlist: an email address you have entered but not confirmed is deleted automatically after 7 days. A confirmed address is kept for up to 12 months, or until you unsubscribe or delete your account (which also removes any waitlist entry for your email address), whichever comes first.
• Rate-limiting and abuse-prevention records (e.g. request timestamps keyed to your IP address or account) are retained on a rolling basis, typically no more than 24 hours, and are not used to build user profiles.
• Operational logs (such as error and event records, which may include an account identifier but not the content of your itineraries) are kept in Google Cloud Logging for a limited period, typically up to 30 days, for security and troubleshooting.
• If you purchase a paid membership, your account and membership-related data remain fully intact and restorable for one year after your membership expires or is canceled without renewal. After that, an account that has not renewed becomes eligible for deletion.

Where we retain data longer for legal, security, or fraud-prevention reasons, we limit retention to what is necessary for that purpose.

International Data Transfers

The Service is hosted on Google Cloud infrastructure (Google Cloud Run and Firebase), currently operated from the United States. If you access the Service from the EEA, UK, Switzerland, Singapore, or elsewhere outside the United States, your information will be transferred to and processed in the United States.

Our infrastructure providers (Google Cloud Platform and Firebase, both operated by Google) maintain their own cross-border transfer safeguards, including Standard Contractual Clauses where applicable, for personal data transferred out of the EEA/UK. By using the Service, you understand that your information may be processed outside your country of residence, in a jurisdiction that may have different data protection laws than your own.

Data Protection Rights

Where we process your information based on your consent (e.g. saving preferences to your profile, or signing in), you may withdraw that consent at any time — see below for how.

Regardless of your location, you have the right to: access the personal data we hold about you; request correction of inaccurate data; request deletion of your account and associated data; object to or request restriction of certain processing; and request a copy of your data in a portable format, subject to applicable law.

You can update or clear your saved preferences at any time from your Profile page. To request access to or export of your account data, contact us at the address below — we aim to respond within a reasonable time.

You can delete your account yourself from your Profile page. If you have an active paid membership, you must cancel it first. Deleting your account removes your profile, your saved itineraries, your Community Explore favorites, and your points and referral records from our database, and removes your sign-in record from Firebase Authentication. We then send you a confirmation email.

Some information may remain after deletion: (a) payment and refund records, which we and Stripe keep for as long as accounting, tax, or other laws require; (b) records held by our email provider under its own retention schedule; (c) routine backups, which expire on a rolling basis; and (d) comments, votes, and reports you made on other users' Community Explore listings, which are not currently removed automatically when you delete your account — contact us if you would like them removed.

Your Rights Under GDPR (EEA, UK, and Switzerland)

If you are located in the European Economic Area, the United Kingdom, or Switzerland, the General Data Protection Regulation (GDPR) and equivalent UK/Swiss data protection laws give you the rights described above, specifically: the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20), and objection to processing (Art. 21).

The Service does not use your personal data for any form of automated decision-making that produces legal or similarly significant effects on you.

You have the right to lodge a complaint with your local data protection supervisory authority at any time, in particular in the EU/EEA member state, UK, or Switzerland where you live, work, or where an alleged infringement occurred.

Given the limited, occasional, and low-risk nature of our processing of EEA/UK personal data, we do not currently maintain a dedicated EU or UK representative under GDPR Article 27 / UK GDPR; you can reach us using the contact details below for any GDPR-related request.

Your Rights Under Singapore's PDPA

If you are located in Singapore, the Personal Data Protection Act 2012 (PDPA) gives you the right to access the personal data we hold about you and to request correction of any inaccuracy, as described above.

See "AI Training & Data Reuse" above for the specific purposes for which submitted trip data may be used by our AI provider, disclosed separately from our general description of how your information is used, consistent with PDPA guidance on AI-related processing.

Where our processing of your personal data relies on your consent, you may withdraw that consent at any time by contacting us or, where available, adjusting your settings from the Profile page. Withdrawing consent may mean we can no longer provide certain features that depend on that data (for example, pre-filling your saved trip preferences).

In the event of a data breach that is likely to result in significant harm to affected individuals, or that is of a significant scale, we will notify Singapore's Personal Data Protection Commission (PDPC) and affected individuals as required under the PDPA's mandatory data breach notification obligations.

Our designated data protection contact (the person responsible for compliance with the PDPA) can be reached using the details in "Contact" below, and you may use them for any PDPA-related request or complaint.

Third-Party Services

The Service relies on the following third-party services, each governed by their own privacy policies and terms:

• Google Gemini API — used to generate itinerary content from your trip details (operated by Google; processed in the United States). We use its paid (billed) tier, under which Google's terms state that submitted content is not used to train or improve its models; see "How Your Information Is Used" above.
• Firebase Authentication — used to sign you in with your Google or Facebook account, if you choose to sign in (operated by Google; processed in the United States).
• Facebook Login — if you choose to sign in with Facebook, Meta Platforms, Inc. authenticates you and shares your name and email address with us; Meta's own privacy policy governs its handling of that sign-in. We do not post to your Facebook account or access your friends list.
• Google Analytics for Firebase — used, only if you opt in to analytics cookies, to measure how the Service is used (operated by Google; processed in the United States).
• Google Cloud Firestore — used to store your account profile, saved preferences, and, if applicable, your saved itineraries and Community Explore activity (operated by Google Cloud; currently hosted in the United States).
• Firebase Hosting and Google Cloud Run — used to host the Service and run its backend (operated by Google Cloud; currently hosted in the United States).
• Wikipedia / Wikimedia Commons — used to fetch destination and venue images; your browser contacts this service directly to load them.
• Photon (OpenStreetMap, operated by komoot) — used, via our backend, to resolve destination and venue names into map coordinates for the itinerary's embedded maps; your device never contacts this service directly.
• Google Maps Platform and Google Search — used to build map and ticket-search links, and to load the itinerary's embedded interactive maps (imagery, pins, and tiles) directly in your browser once venue coordinates are resolved.
• ExchangeRate-API (open.er-api.com) — used, via our backend, to fetch a currency exchange rate for itineraries involving a foreign currency, using only your preferred currency code.
• Google Maps Platform Weather API — used, via our backend, to fetch a live weather forecast for your itinerary's destination(s), using only a city-level latitude/longitude; your device never contacts this service directly (operated by Google Cloud).
• Resend — used to send transactional emails about your account or content, and, if you opt in, marketing emails (operated by Resend; see Resend's own privacy policy for how it handles email data).
• Stripe — used to process paid-membership purchases and refunds, if you choose to purchase one. Card details you enter are sent directly to Stripe and never reach our servers (operated by Stripe, Inc.; see Stripe's own privacy policy for how it handles payment data).

We encourage you to review these providers' own privacy policies, as your interactions with links to their services (e.g. clicking a Google Maps link) are subject to their terms, not ours.

AI & Your Device

Itinerary content is generated by Google's Gemini API, called from our servers only — never from your device or browser. Each request is a one-way text exchange: we send the trip details you entered and receive text back. The AI is not run as an autonomous agent and is not given tools, function-calling, code execution, web browsing, or any ability to take actions. It cannot see, access, control, or run anything on your device, browser, accounts, files, or other apps, and it does not receive anything from your device beyond what you submit in the trip form.

What the AI returns is treated purely as data: it is displayed as text, and the links in the Service (maps, directions, tickets, further reading) are constructed by us from place names, never taken as executable code or as arbitrary web addresses from the AI's output. We validate inputs before they are sent to the AI and instruct it to treat your inputs as literal data, but, as noted in our Terms, AI output can still be inaccurate.

Cookies & Tracking

The Service uses a small number of essential cookies and local storage entries required for sign-in sessions and to remember your app preferences. These cannot be disabled, as the Service cannot function without them.

Optional analytics cookies are only set if you opt in via the cookie preferences banner shown on your first visit. You can change your choice at any time from the "Cookie Preferences" link in the footer.

If you are signed in and choose to buy a membership while the app opens payment in the same window (for example when it is installed on your home screen, or your browser blocks pop-ups), the trip details you had entered on the form (such as destination, dates, travel party and preferences) are kept briefly in your browser's local storage on your own device, so that your itinerary can be generated automatically when you return from payment. This copy is not transmitted anywhere by this feature, is used once and then deleted, and is also deleted when you sign out or after one hour at most.

Children's Privacy

The Service is for people aged 18 or older and is not directed at children. We do not knowingly collect information from anyone under 18. The trip form asks for the ages of the people traveling with you; that is information about your travel party entered by you, the adult user, and is used only to tailor the itinerary. If you believe someone under 18 has provided us with information, please contact us and we will delete it.

Changes to This Policy

We may update this Privacy Policy from time to time. If a change is material, we will update the date above and the version you are asked to accept, and may notify you in the Service or by email. Continued use of the Service after changes are posted constitutes acceptance of the updated policy.

Contact

Data Protection Officer, Yumu Technologies Private Limited (Singapore)

Questions about this Privacy Policy, and requests to access, correct, export, or delete your data, can be sent to: the contact address shown on this page