Privacy Policy

This Privacy Policy explains how Rumo collects, uses, stores, and shares information when you use our website, account features, AI-powered trip-planning tools, saved itineraries, subscriptions, and related services.

Rumo is currently operated by an individual founder. References to “Rumo,” “we,” “us,” and “our” refer to the Rumo service and its operator.

Account information. When you create an account, we process information such as your email address and authentication information through our authentication provider.

Trip prompts and travel details. We process the free-text prompts and trip information you provide, which may include destinations, departure locations, dates or timing, trip duration, budgets, party size, companion information, accommodation preferences, interests, travel style, things you want to avoid, and other details you choose to include.

Passport nationality and entry-related information. Where you provide it, where it is reasonably inferred from your request, or where it is needed to generate relevant travel-planning guidance, Rumo may process passport nationality or related travel-context information.

Clarification answers and preferences. We process answers to follow-up questions and changes you make to your preferences or Traveler Profile.

Revision requests. If you ask Rumo to update a trip, we process the revision request together with relevant itinerary and trip context.

Support and privacy communications. If you contact us, we process the information you include in your message so we can respond and handle your request.

Rumo uses AI to turn trip prompts and answers into structured travel information. This can include inferred destinations, timing, budget context, party size, travel preferences, and other planning fields.

Rumo may also generate or infer a Traveler Profile or Traveler DNA, including attributes such as pace, companion dynamic, splurge priorities, experience level, interests, avoid-list preferences, travel style, trip intent, novelty tolerance, social energy, energy rhythm, and decision style.

We also generate and may save itineraries, budget estimates, flight guidance, stay recommendations, activity recommendations, food suggestions, route information, practical guidance, and revisions to those materials.

Rumo uses first-party analytics to understand how the service is used and where the planning flow succeeds or fails. Analytics information may include event names, a persistent visitor identifier, a session identifier, trip identifiers, destination, budget, duration, party size, Traveler Profile information, generation timing, completion or failure status, error information, and related event properties.

Our hosting, database, authentication, payment, and other service providers may also receive ordinary technical information necessary to deliver their services, such as network request metadata, IP address, browser or device information, timestamps, and security-related information, according to their own systems and policies.

Rumo uses authentication cookies and related storage needed to keep users signed in and maintain secure account sessions.

Rumo also uses browser storage, including localStorage and sessionStorage, to support functionality such as a persistent first-party analytics visitor identifier, an analytics session identifier, pending or resumable trip state, account or trip handoff state, and upgrade or checkout-return state.

Pending trip state stored in the browser may include portions of your prompt, extracted trip information, clarification state, or Traveler Profile so that the planning flow can resume without starting over.

We use information to provide and personalize trip planning; create and maintain accounts; generate and revise itineraries; save and resume trips; enforce plan limits and usage allowances; process subscriptions; troubleshoot failures; secure the service; understand product usage; improve reliability and user experience; respond to support, privacy, billing, and legal requests; and comply with applicable law.

We use service providers and third-party services to operate Rumo. Depending on the feature you use, relevant information may be processed by:

• Supabase for authentication, database storage, saved trips, analytics records, billing metadata, usage records, and related backend functionality.
• Anthropic / Claude for AI-powered prompt interpretation, clarification, Traveler Profile inference, itinerary generation, budget and travel-planning analysis, revision requests, and related AI features. The travel context sent for these tasks may include prompts, destinations, timing, budgets, preferences, party size, passport nationality where relevant, Traveler Profile information, itinerary context, and revision requests.
• Stripe for subscription checkout, billing, subscription management, and the Customer Portal. Stripe-hosted Checkout handles payment-card entry. Under Rumo’s current implementation, Rumo does not directly store your full payment-card number.
• Vercel for website hosting and application infrastructure.
• Travelpayouts / Aviasales when you use certain explicit affiliate flight links. Those links may include Rumo affiliate identifiers and flight-search context such as route or dates contained in the destination URL.
• Viator and GetYourGuide when you use certain affiliate activity links.
• Google Search or Google Maps when you choose outbound search links for stays, food, or other travel information. Search terms can include destination, accommodation name, dining area, cuisine, or similar trip context.
• Unsplash, when configured, to retrieve destination or travel imagery and display required attribution. Search terms may include destination or experience context.

Some Rumo links are affiliate links. Rumo may receive compensation when you book or purchase through certain links, generally without an additional charge to you. Current affiliate relationships may include Travelpayouts / Aviasales, Viator, and GetYourGuide. Not every external link is necessarily an affiliate link.

When you click an external link, you leave Rumo and the third party may collect information under its own privacy policy. See our Affiliate Disclosure for more information.

Rumo may store billing and subscription metadata such as your Rumo user ID, current plan, Stripe customer ID, Stripe subscription ID, Stripe price ID, subscription status, current billing-period dates, whether cancellation is scheduled for period end, and AI-usage records tied to generation or revision activity.

Payment-card details entered in Stripe-hosted Checkout are handled by Stripe, not entered into a Rumo-hosted card form.

We retain information for as long as reasonably necessary for the purposes described in this Policy, including providing saved-trip and account functionality, maintaining subscription and usage records, operating analytics, resolving disputes, meeting legal obligations, and protecting the service.

Different categories of information may be retained for different periods. We do not state a fixed universal retention period because the appropriate period depends on the type of data, why it is used, account status, legal requirements, and operational needs.

Rumo does not currently provide a self-service account-deletion control in the product. You may request privacy assistance or request deletion of your account and associated data by emailing support@travelwithrumo.com.

We may need to verify your request before acting on it. Some information may need to be retained where required or permitted by law, for fraud or security prevention, billing records, dispute resolution, or other legitimate obligations. We will evaluate deletion requests in light of the systems that hold the relevant information, including saved-trip, billing, and analytics records.

We use reasonable administrative and technical measures designed to protect information and rely on established service providers for core authentication, hosting, database, and payment functions. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Rumo is not directed to children under 13, and we do not knowingly seek to collect personal information from children under 13. Rumo does not currently operate an age-verification system. If you believe a child under 13 has provided personal information to Rumo, contact us at support@travelwithrumo.com so we can review the situation.

Depending on where you live, applicable law may give you rights relating to access, correction, deletion, restriction, objection, portability, or other handling of personal information. You may contact us at support@travelwithrumo.com to make a privacy request. We will respond as required by applicable law.

We may update this Privacy Policy as Rumo changes, our service providers change, or legal requirements evolve. We will post the updated Policy with a revised effective date and may provide additional notice for material changes where appropriate.

For privacy, deletion, support, billing-error, or legal questions, contact support@travelwithrumo.com.