Frequently asked questions
Clear answers before you plan.
Generation, booking actions, saved trips and the limits of the prototype are explained here.
MichiWise FAQ
Questions, answered.
Can I generate a trip now?
The planner checks the backend before enabling generation. It requires the configured AI planning service, durable quota storage and human verification. If configuration or a request fails, MichiWise shows a clear error and does not substitute the fixed sample.
What does MichiWise check before showing an itinerary?
The server validates the dates, day count, route skeleton, regional coverage, daily geography, walking limits, chronological stops, recovery windows, stop priorities and booking structure. These checks improve feasibility but do not make a plan a live service report.
Are opening hours, event dates, fares and prices live?
No. The Japan prototype does not aggregate nationwide live weather, rail, bus, ferry, airport or event information. The itinerary identifies what still needs official verification and does not treat a missing warning as an all-clear.
Why are regional coverage levels visible?
Japan-wide does not mean equal planning depth everywhere. Tokyo and Kanto and Kansai have deep coverage; other packs are guided or limited. The labels describe prototype maturity rather than whether a destination is worth visiting.
Does MichiWise make bookings?
No. After a traveller chooses an enabled booking action, the configured third-party provider controls prices, availability, payment, booking terms, changes, cancellations and refunds. MichiWise may earn a commission from eligible links.
What happens when a provider is not configured or a tracked link fails?
The affected action remains visibly unavailable. MichiWise does not open a direct provider URL, generic search link or another substitute. A successful action is opened only after the approved tracking service returns a validated tracked link.
How does the Japan eSIM action handle trip details?
It is separate from the generated itinerary booking schema and uses only a neutral Japan eSIM query. It does not receive your origin, gateways, dates or traveller count. Confirm that your phone is unlocked and supports eSIM before choosing a plan.
Where is a generated trip stored?
A newly generated itinerary first stays in session storage for the current browser tab. If you explicitly save it, the validated itinerary is stored in account data under a one-way identifier derived from your verified Google email. Missing, invalid or unavailable saved data is never silently replaced.
Who can see a shared trip?
Anyone with the exact private-by-link URL can read it. The page contains no owner identity, AI credential or booking actions. Signed-in viewers can shortlist stops anonymously or save an independent account copy; the owner sees only combined totals.
Who can see my trip feedback?
Only your signed-in account can reopen the reflection attached to its saved trip. It is not included in share links or recipient copies, and it is not sent to the AI planning service or booking providers. You can update or delete it at any time.
What information goes to third parties?
Planner answers and optional notes go to the third-party AI planning service only when you request generation or a rewrite. Cloudflare processes human verification. A selected affiliate action sends only the approved values required by that provider link. Do not enter passport, payment, medical, contact or other sensitive details.
Does the fixed sample use my answers?
No. The sample itinerary is explicitly labelled demonstration content. It is not generated from your preferences and never represents live travel data.
What does a subscription change?
The public pricing page describes the available account limits and features. Reading a shared trip, revoking your own share link, recipient voting and other protected free paths remain available according to their documented rules, including when a subscription feature is dormant.
Next step