12 honest answers

Yes — every itinerary, destination guide, and specialist page (accessibility, dietary, visa) is free to read. No paywall.

We earn affiliate commissions when you book a hotel, tour or travel insurance through some of our links, at no extra cost to you — see our affiliate disclosure. We may add display ads later; none run today. An optional premium tier with unlimited personalised itineraries and PDF export is planned. The reference content stays free.

Honest answer: good for a first draft, not a substitute for checking primary sources close to your trip.

Itineraries are written by Google Gemini from the destination and your settings — trip length, style, budget, pace and interests — plus a short list of current-state facts we maintain for some destinations (for example, that Hagia Sophia now operates as a mosque). Attractions on a fixed list of known sell-outs — teamLab, the Louvre, the Colosseum and a few others — get a Book ahead badge wherever they appear.

What language models still get wrong: opening hours, small restaurant details, seasonal closures. Check them before you book.

Where a wrong answer causes real harm — a missed flight over a visa rule, a wheelchair user at a “step-free” door with four steps, a coeliac trusting a dish a chatbot called gluten-free — we keep the core data out of the model:

• Visa matrix: 81 fixed entries across 9 passports × 9 destinations, each linked to the destination country’s government or official portal (Japan MOFA, Thailand MFA, the UAE’s ICP, Singapore ICA and others), with the date it was last checked. Nothing on these pages is generated when you load them.
• Accessibility guides: venues tagged wheelchair=* in OpenStreetMap — a contributor’s record, not an inspection. The overview and neighbourhood ratings are written by Gemini from a Wikipedia extract, and labelled; their sentences about public transport are left out, and the transport section carries the operators’ own figures.
• Dietary guides: venues tagged diet:halal|kosher|vegan|gluten_free in OpenStreetMap, marked when a venue serves only that diet. A tag is not a certification or a cross-contamination guarantee. These pages carry no model-written text: when we checked it, too many of its claims could not be backed by a source, so each page shows the tags, what they do not guarantee, and what to check in person.

Where model-written sections proved unreliable — invented hospital addresses, taxi operators and phrases in the specialist guides — they were switched off rather than left up. The methodology page has the details.

Tripozi is a one-person project started in April 2026, run by Szymon Łysek as a registered Polish sole proprietorship (JDG) with VAT registration.

• Not venture-backed.
• Not anonymous: the legal entity is identified on our Privacy and Terms pages, and reader contact is via the contact page.
• Not a keyword farm: generated pages are bounded by destinations × tools, not by search keywords.

Use it like any reference: treat the venue data and the visa sources as strong leads, and check what matters to you at the source. The methodology page says which layer is which.

Every personalized itinerary you generate gets a unique URL under /trip/[id] that you can bookmark, share, or email directly. No account required — the trip is stored server-side but indexed by an unguessable ID, so only people with the link can see it.

Additionally, your browser keeps a “recently viewed” list in localStorage, accessible via Your saved. This list never leaves your device.

Account-based saving with PDF export, itinerary history across devices, and multi-trip management is planned for the upcoming Tripozi Pro tier.

We cover 170+ destinations spanning 70+ countries — every continent except Antarctica. New destinations are added slowly; we’d rather describe fewer places carefully than thousands shallowly.

Accessibility and dietary guides are limited to 10 European cities (Barcelona, Kraków, Amsterdam, Lisbon, Berlin, Prague, Valencia, Copenhagen, Tallinn, Porto) because that’s where OpenStreetMap has enough contributor-tagged venues to build on. We’ll expand as coverage grows elsewhere — not before.

Passport Index and Sherpa are useful aggregators — good for cross-checking.

Tripozi’s difference lives in the source layer: every entry in our 81-entry visa matrix links to the destination country’s own government page or official portal (Japan’s Ministry of Foreign Affairs, Thailand’s MFA, the UAE’s ICP, Singapore’s Immigration & Checkpoints Authority and others), with the date it was last checked. Aggregators rarely show their sources; we do, so you can check before booking flights.

Please do. Three channels:

• Accessibility / dietary venues: each accessibility and dietary city page has a check-in form that writes to a review queue. Nothing is published automatically. We don’t edit OpenStreetMap ourselves — if a tag is wrong, fixing it on OpenStreetMap helps everyone.
• Visa matrix corrections: email [email protected] with the URL of the official government page showing the correct rule. We read every message; a correction we can confirm there is applied and the entry’s check date updated.
• Itinerary / tool errors: same email — include the page URL and what’s wrong. Generated pages can be regenerated once the cause is fixed.

As little as we can — and we tell you what and why:

• Analytics: self-hosted Plausible on our own infrastructure — no cookies, and IP addresses are not stored. It records the page address, referrer, browser, operating system, device type and an approximate location derived from the IP address, plus a few anonymous events such as clicks on outbound booking links.
• Saved itineraries: stored as an unguessable ID on our servers but not linked to your identity unless you choose to sign up for the premium tier (not yet live).
• Recently viewed + passport preference: stored in your browser’s localStorage — never leaves your device.
• Ads (if we add them): Google AdSense with Consent Mode v2, set to “denied” until you accept the cookie banner.
• Newsletter: if you subscribe, your email stays on Resend (our email vendor). Unsubscribe links are on every email.

Full breakdown including all data subprocessors (OVH, Cloudflare, Gemini API, OpenStreetMap, Unsplash, Resend, Google AdSense) on the Privacy page.

Google’s guidance on AI-generated content is about whether a page helps the person reading it, not how it was produced — and it treats generating many pages without adding value as spam. That is the bar we try to meet:

• Language model: itineraries, destination overviews and tool pages (packing, budget, day trips, food, when to visit), cached per destination and settings so repeated requests give consistent answers.
• Open data and official sources: the accessibility and dietary venue lists (OpenStreetMap) and the visa matrix (government sources).
• Switched off: model-written sections of the specialist guides that proved unreliable.

Pages that exist only for navigation — month-by-month pages and itinerary variants — carry noindex, so they don’t compete in search.

Business entity: Polish Jednoosobowa Działalność Gospodarcza (sole proprietorship) with VAT registration. The legal operator is named in our Privacy policy and Terms.

Infrastructure: origin servers in OVH Gravelines, France (EU); Cloudflare handles global edge caching; self-hosted Plausible analytics on same infrastructure; Google Gemini API and Unsplash API as external services.

Applicable law: EU GDPR governs your privacy rights on this site. Polish consumer protection + tax law governs the business. If you’re located in the UK, US, or anywhere else, your local laws still give you consumer protections that we honor — when premium tier launches, Paddle (merchant of record) handles cross-border VAT / sales tax compliance so you pay the right rate for your jurisdiction.

Email [email protected] with the URL and a brief description of what’s wrong. We read every message and fix what we can verify.

For visa corrections specifically: please include a link to the official government source (MOFA, MFA, immigration authority, or embassy) showing the correct rule. That lets us confirm the rule at its source and update the entry and its check date.

For accessibility / dietary venue issues: if you can, also file the correction at OpenStreetMap so the whole ecosystem benefits — our copy refreshes from OpenStreetMap weekly.