Last updated: 28 October 2026
Information you enter
Travel search forms do not currently store the information you enter, and Rutaiva does not currently offer newsletter signup or collect newsletter addresses. Contact-form submissions are sent through Cloudflare Email Service to Rutaiva’s private inbox so the team can respond; Rutaiva does not store a separate copy in an application database. Explore Anywhere and Route Planner selections are handled in your browser. Explore filters may appear in the page address for navigation or sharing; opening a reviewed route or airport guide uses that guide’s public address.
My Trips as a guest
When you save without signing in, the itinerary and its saved places, reservation records, preparation checklist, packing and budget details are stored in this browser on this device. Rutaiva does not receive that guest copy merely because it is stored locally. Clearing browser data may remove it. Do not store payment-card details, passport numbers, government IDs, passwords or other unnecessary sensitive personal information in a trip.
Signed-in My Trips
Rutaiva uses Supabase to provide password-free email authentication and cloud storage. A signed-in account stores the email needed for authentication and the trip data you choose to sync: itinerary, destination, dates, traveler count, interests, pace, saved places, reservation details, checklist status, packing list and user-entered budget planning values. Reservation details may include a booking reference, note or confirmation link that you enter manually. Cloud copies are associated with an internal account identifier and protected by row-level access policies. Rutaiva does not claim end-to-end encryption. A validated local trip is uploaded only after you accept the migration prompt, while later signed-in saves sync automatically and retain a local cache.
Private trip sharing
A trip owner can create an expiring, single-use invitation and choose whether a signed-in collaborator may edit or only view that trip. Authorized collaborators can access the trip information permitted by that role until they leave or the owner removes them. Invitation tokens are stored as one-way hashes, are not included in analytics, and do not reveal trip contents before sign-in and explicit acceptance. Booking references are kept separately from shared reservation planning data and are visible only to the person who added the reference and the trip owner. Rutaiva does not claim end-to-end or zero-knowledge encryption.
Booking confirmation import
Signed-in users can paste booking confirmation text or upload a TXT or EML confirmation for structured extraction. Rutaiva processes the submitted content transiently on its server, filters recognizable payment-card, passport, password and token patterns, and does not intentionally store the raw message or uploaded file. The V4A importer uses deterministic text parsing, not OpenAI. Nothing is added to a trip until the user reviews, corrects and confirms the extracted fields. Only the structured reservation fields the user approves are then stored under the existing My Trips access and booking-reference privacy rules.
Maps and coordinates
The My Trips map uses only coordinates you save with a place and renders locally in the page without a third-party tile or geocoding service. Rutaiva does not infer or request your current location. Places without known coordinates stay in the accessible place list.
Trip planning
Trip Planner requests use only the starting point, destination, dates or duration, traveler count, approximate budget, interests and pace you provide. They are not published as public pages. Signing in does not add your account identity or email to an AI planning request.
AI itinerary generation
Rutaiva uses OpenAI for optional AI trip planning. When you request or regenerate an itinerary, Rutaiva sends OpenAI only the trip-planning inputs needed to generate it: your starting point if supplied, destination, dates or duration, traveler count, approximate budget, selected interests and pace. Booking confirmation imports, saved places, reservation details, checklists, packing lists, budget amounts, Rutaiva account identifiers and email addresses are not intentionally sent for AI generation. Do not enter unnecessary sensitive personal information in planner fields. OpenAI processes the request to generate the itinerary under its API data controls.
Analytics and affiliate measurement
Rutaiva uses Cloudflare Web Analytics to measure page views and website performance. Cloudflare states that its beacon does not store or access cookies, local storage or other browser storage, and does not track people across websites. Google Analytics is currently disabled by a fail-closed production feature flag: its script, configuration and event adapter do not load. Travelpayouts Drive remains off by default and may measure content and affiliate-link interactions only if you allow optional measurement through “Analytics preferences” in the footer. Rutaiva does not intentionally send itinerary text, packing items, budget amounts, names, email addresses, contact messages, planner form content or Schengen travel-history dates to either service. Booking-confirmation text and filenames, saved-place names or addresses, reservation references or notes, checklist text, invite tokens and collaborator identities are also excluded. Cloudflare, Google when enabled, and Travelpayouts process permitted data under their respective privacy policies.
Affiliate handoffs and third-party websites
Official operator, tourism and sponsored provider links open third-party websites whose privacy and cookie terms apply. Current sponsored handoffs may lead to Aviasales, Klook, EconomyBookings.com or Kiwitaxi through official Travelpayouts tracking, or to Trip.com through a direct official affiliate link for Stays. Rutaiva does not send your Rutaiva account identity, email or saved itinerary to these providers. It also does not send saved places, reservation records, checklist details or collaborator information. Search details must be entered and confirmed on the provider website.
Your choices
No analytics prompt is shown automatically. You can allow, decline or change optional analytics and affiliate measurement at any time using “Analytics preferences” in the footer. You can leave a shared trip, delete individual trips you own, export your trips as JSON, clear device copies using browser controls, or request deletion of your Rutaiva account and associated cloud trips through the contact form.