Frequently Asked Questions

We are not going to claim we beat a travel agent — an agent has judgment and can phone ahead. What we do is mechanical: a Gemini model drafts the plan, then every activity is looked up in Google Places. Where a place matches, the plan carries that venue's real place ID, address, coordinates, opening hours and rating. Where nothing matches, we delete the place ID and rating the model produced rather than show you a number we cannot stand behind.

We do not trust the model's output — we check it afterwards. Once a draft exists, around eight automatic checks run over it: daily pace, duplicate activities, spend against your budget, opening hours, nighttime safety, overlapping times and route order. The same checks can be re-run on a trip you edited by hand. Each one reports clean, issues found, skipped or error. A skipped check is never counted as clean, because we could not check this and we checked this and it is fine are different statements.

Treat it as a strong first draft, not a booking. Where a place verifies against Google Places you get its real hours and coordinates; where it does not, the rating and place ID come off rather than being guessed, and any match more than 70 km from that day's city center is thrown out as the wrong city. We reserve nothing on your behalf, and hours and closures do go stale, so confirm anything time-critical with the venue before you build a day around it.

Every activity is looked up in Google Places after generation. A confident match gets that venue's address, coordinates, opening hours and rating attached. When there is no match, we clear the place ID, rating and review count the model produced. The suggestion stays, but without a rating or review count, so an activity with no rating is one we could not confirm exists. Google's own data still goes stale; email contact@travaio.co and we will look at it.

The two are handled differently on purpose. Accessibility can be checked, so a venue Google reports as step-free is kept even when its name sounds strenuous, and one reported as inaccessible is removed even when no keyword flagged it — but an absent field means no signal, never accessible. Dietary needs are only ever flagged, never used to delete anything: you cannot infer halal certification or nut-free preparation from a venue's name, and removing on a guess would delete safe restaurants while still missing unsafe ones. Gluten-free, nut-free and dairy-free have no signal to check against at all, so we report them as unchecked rather than counting them clean. Call ahead — we tell you what we could not check precisely so you know where to.

Your trips are stored in a private database. Only your account, and people you invite, can read them. Traffic runs over HTTPS. Planning does mean sending your destination, dates and preferences to Google, for the Gemini model that drafts the plan and the Places lookups that check it. Our other processors are Supabase (database and storage), Cloudflare (cache, rate limiting and cookie-free page analytics), Mapbox (map tiles), Resend (email), and Stripe if you subscribe. The Privacy Policy lists each one and what it receives. We do not sell your data or pass it to advertisers.

Your quiz answers — pace, rhythm, budget, the twelve interest scores, cuisine, and any dietary, accessibility or mobility needs you enter — plus the trip inputs themselves: destination, dates, traveler count. Then the itineraries you save and the edits you make to them, the thumbs up and down you give individual activities, your account email and display name, and your subscription state as Stripe reports it. You can download all of it from your account settings.

Yes, under Account, Security. Add an authenticator app and signing in will ask for its six-digit code after your password. Create recovery codes on the same page and keep them safe: they get you back in if you lose your authenticator, although the most sensitive actions may still ask for the authenticator itself.

Yes, from your account settings. Deleting the account removes your user row, and everything keyed to it goes with it: saved itineraries, journal entries, activity comments and votes, collaborations, notification preferences, device tokens and any API keys you generated. Feedback you left is stripped of identifying details rather than deleted. Journal photos and trip documents are deleted from storage too. Export a copy first if you want one, because deletion is permanent and we cannot restore it afterwards. If you have an active App Store or Google Play subscription, deleting the account does not cancel it: you are asked to acknowledge that first, and you cancel it in the store.

Only from things you tell it deliberately. Thumbs up and down on activities are tallied by category and carried into your next generation twice over: as a line the model reads, and as counts a separate pass acts on — one thumbs-down is a bad afternoon, five is a verdict, and it treats those differently. Places you have already been bias the next trip toward ones you have not. There is no model training on your data, and nothing learns from what you merely looked at.

Our iOS and Android apps are in testing and not yet in the app stores. The website works on a phone browser in the meantime, and we post updates on X and Instagram. The app does not yet have Trip Check, collections, Locate my stops, Edit by typing, AI agent key management, or PDF, KML, CSV and Markdown export; those are on the website.

Saved itineraries stay readable and exportable — they are stored, not regenerated on demand. New generation depends on Google's model and Places APIs, and if either is unavailable the request fails with an error rather than handing you a degraded plan. A scheduled checker polls our dependencies every five minutes and publishes what it finds on the status page. We are a small team, so there is no staffed round-the-clock desk behind that.

It depends on the trip. A short single-city trip finishes sooner than a long or multi-city one, which can take several minutes (up to ten), because each city is drafted separately and every activity is then checked against Google Places. The progress bar follows real stages rather than a timer: drafting runs to 85%, Places verification to 94%, route optimization to 97%.

Yes. The traveler count feeds pacing, cost estimates and venue choice, and Pro adds collaboration, so people you invite can edit the same trip. Two honest limits: generation runs from one person's quiz answers, so it is not merging four sets of preferences into a compromise; and if two people save the same trip at once, small changes (ticking a stop done, logging spend, changing a time, locking a stop) are merged automatically. Anything else is kept for you behind a banner with a Use my version button, so you can re-apply it deliberately rather than one save silently overwriting the other.

Swap an activity for a nearby alternative, add or delete one, reorder days — travel times are recomputed when you do — or regenerate a single day. Swaps and adds are Places lookups rather than fresh AI calls, so free and Pro users are not metered per trip, only bounded by a daily rate limit. Guests get two swaps and no adds per trip, because a guest cannot save a trip in the first place.

When Google Places matches the venue, we show its rating and review count as Google reports them. When there is no confident match we remove the rating rather than estimate one, so a missing rating means unchecked, not bad. We do not filter on a rating threshold, we have no review corpus of our own, and popularity is not taste — read the rating as one signal beside the description, not as a verdict.

You can regenerate a day, swap or delete activities, and reorder what is left. Regeneration drafts a fresh plan for the scope you regenerate rather than patching it, so hand-edits inside that scope are replaced — saved version history is the way back, keeping the last three versions on free and all of them on Pro. All of it needs a connection; there is no offline replanning.

Yes. On a stop, use the What the group spent field. It is the whole group's total for that stop, not a per-person price: it replaces that stop's estimate and is never multiplied by your party size, while estimates are per person. Totals keep the two apart.

With notifications on, a saved trip within two days gets a reminder, and on trip days you get a day summary plus reservation and check-out reminders. They are only sent between 09:00 and 20:00 on your own clock (the time zone in your account settings). During a trip, reservation and check-out reminders follow the trip's local time; if the trip's time zone is not known they are skipped rather than sent on the wrong clock.

Replanning needs a connection, but small edits do not have to be lost. If a save cannot reach us, the website keeps the edit on that device and offers to send it later, and the phone app queues ticks, costs and times. If someone else changed the trip meanwhile, those small edits are merged onto their version; anything else is kept for you to re-apply.

Signed-in visitors can save their own copy of a shared trip. It carries the plan: days, stops, notes and the general shape of the trip. It does not carry the owner's bookings, dietary, accessibility or party details, done ticks, logged spend or personalization tags, and it counts toward your saved-trip limit.

Some stops, especially on hand-built or imported trips, have no pinned location yet. When a day has none and you can edit the trip, the map offers Locate my stops, which looks the stops up on the map. Stops that cannot be matched stay off the map.

We have not measured how much time this saves anyone, so we are not going to quote you a figure. What $12.99 buys is concrete: no daily plan cap (fair use), no cap on saved trips, up to five cities in one trip, collaborators, unlimited version history and share links, packing-list regeneration and the weather contingency tab. The free tier — ten plans a day, three saved trips, two cities — is meant to be enough to decide with. If you enjoy the researching part, this is not for you.

No number, because we have not measured one. What it does instead of you: ordering the cities and deciding how many days each gets, drafting every day, checking each place exists and is open when you would arrive, and sequencing stops so you are not crossing the city twice. You watch its progress while it runs. Reviewing the result is still your job, and you should.

On Pro there is no daily plan cap (fair use) and no cap on saved trips; free is ten plans a day and three active saved trips, where archiving one frees a slot. Every itinerary gets the same treatment — day-by-day plan, Places-checked detail wherever a venue matches, route ordering, map, and export to PDF, ICS and KML plus the Pro-only formats. Two ceilings sit behind the word unlimited: full-trip plans are capped at 50 in any 24 hours, and day regeneration at 200 a day per account, roughly fourteen two-week trips regenerated day by day. Both exist to stop scripted abuse rather than to meter you.

On Pro, yes. In the More tab, describe a change in plain words; Travaio shows a before and after of only the stops it would touch, and nothing changes until you apply it. Pro accounts can send up to 30 of these instructions in any 24 hours.

A little, through two narrow mechanisms rather than a model quietly learning you. Your thumbs up and down are tallied by category and shape the next generation, and places you have already visited bias it toward ones you have not. The larger lever is still the quiz: the more precisely you set pace, interests and no-gos, the less there is left to guess at.

Regenerate the day, swap the item out, or restore an earlier version from history — free keeps the last three, Pro keeps all of them. If the trip is wrong rather than just not to your taste — a place that does not exist, hours that are impossible, a day that cannot physically be walked — email contact@travaio.co with the trip and we will look at the generation itself, not just the symptom.

Contact us via email at contact@travaio.co anytime. We reply within 1-3 business days.

The app is, and saved trips are readable whenever you are. New generation depends on Google's APIs and on our own service, so an outage on either side stops new plans while the ones you already have stay intact — live dependency status is on the status page. Support is not around the clock: it is email, and we reply within 1-3 business days.