Contact
This site is built and maintained by one person. Every email is read by a human — there is no support queue and no ticket system.
What to write about
- Something is broken. Tell me which browser you were using and what you clicked. Bugs that only appear on certain devices are the hardest to find, so a device name genuinely helps — a button that silently did nothing on a phone was found exactly this way.
- A feature you'd use. One line is enough. What gets built next is decided by what people actually ask for, not by a roadmap written in advance.
- Something in the sample itinerary is wrong. Opening hours, fares and transit times go out of date. The built-in Tokyo example is illustrative, and corrections are welcome.
- A question about your data. Short version: your itinerary never leaves your browser. The privacy policy has the full detail.
Why there's no contact form
A form means a server, a database, and somewhere your message sits. This site deliberately has none of those — the planner itself works without a backend, and the contact page follows the same rule. A plain email address collects nothing, stores nothing, and goes straight to an inbox.
Response time
This is a side project, so replies usually take a few days rather than a few hours. Bug reports get looked at first; feature requests are collected and weighed against each other rather than answered one by one.
Want to see the code, or open an issue instead? The project is on GitHub. If you'd rather have the message drafted for you, the feedback page does that.