Questions, answered at the boundary.

No. It does not book, hold, pay for, cancel, or contact an airline, hotel, agency, or other provider. A planning choice is not a confirmation.

You can record a reservation you made yourself elsewhere. Doing so marks that chapter of your route as confirmed, but the product did not make the booking and cannot change it.

No AI runs inside Assist With Travel, and none ever will — the product keeps your records; your own AI does the thinking. What has changed is that you can now connect the AI you already use, at https://www.assistwithtravel.com/mcp, so it reads and writes your records directly instead of you copying text back and forth.

Signing in is the approval. When you connect from your AI client and click Allow, that is the whole approval — there is no second screen to hunt for afterwards. It arrives able to do everything this product offers a connection — reading your Trips, saving research, shaping the plan, recording a decision you made, and archiving. Nothing waits behind a second screen. At /settings/ai you can switch off anything you would rather it did not do, or revoke it entirely, and revoking takes effect on the very next request. You can also just tell your AI to switch one off; it can never switch one back on. If you would rather approve every new connection by hand, there is a switch for that too — it is off by default, because a site that waits for a second approval leaves you having granted nothing while you believe you finished.

One thing no tool here does: add to your Queue. That list is what you asked for. When your AI thinks of something you did not ask for, it goes to AI Suggestions, where it waits and counts toward nothing until you accept it. The manual copy method still works and is still supported.

Open a Trip, choose one question, and the workspace builds a bounded brief from what you saved. Before you copy it you can see exactly what it includes and what it deliberately leaves out — other Trips, unrelated chapters, anything you marked sensitive, and every reservation, document record, and uploaded file.

Paste it into the assistant you choose, review the reply yourself, then record the result with its source. Nothing leaves merely because you opened the page, and no reply is imported for you.

Each thing you want to settle becomes a question in the Queue, in one of four states: Needs You, Working, Waiting for your AI, and Done. A question carries only the part of the Trip you point it at — the whole Trip, or exactly one chapter, place, comparison, decision, research pass, finding, or option.

You can revise a question, ask it again, close it with a reason, or reopen it. Nothing runs because a question exists; moving one is a record of what you did.

Signing in opens a home that shows what needs you across every Trip, what each plan still has open, recent activity, and every file and place you hold. You can archive a Trip without deleting anything, and restore it later.

You can also export your real records with their provenance, and delete all your travel data with a typed confirmation. Deleting stops at your sign-in: this product cannot remove an account at your identity provider.

The workspace requires Clerk sign-in and every implemented read or write derives the account owner on the server. There is no public Trip page or sharing surface.

That is a bounded owner-separation claim, not a promise of collaboration controls, recovery, field-level encryption, or a complete account lifecycle.

A privacy question about your own record goes to Assist With Life support at https://assistwithlife.com/support. There is no email address for this site to write to instead.

A Trip holds a Brief; an ordered route of chapters, including candidates nested inside the chapter they would happen in; the places those chapters name; findings and options with the source, date, and limits behind each one; comparisons with your own criteria and a ranked shortlist; decisions with the history of how they changed; your recorded constraints, reservations, and documents; the files you uploaded and attached to any of those; the four-state Queue handoff; the day you are actually in, with its itinerary, local tasks, packing and amounts; and what you thought of it all afterwards.

Nothing is researched for you. Every source is entered by you or transcribed from an answer you brought back yourself.

That is the point of it. A saved finding keeps what the source said, when it was observed, how confident you were, anything that argued against it, and what that source could not tell you. Options keep the same, plus typed detail such as walking time or cancellation terms so they can be compared rather than just listed.

Anything observed more than thirty days ago, or that you marked as needing a refresh, is called out as out of date rather than presented as current fact. Refreshing an option supersedes the old one instead of erasing it.

Each question keeps its current state, the option you prefer, a fallback, your reason, your concern, and when to revisit it. Every change to that — opening it, choosing, deferring, reopening — is appended with the date and who recorded it.

Candidate, shortlisted, and chosen stay distinct, and chosen never becomes confirmed by implication. Reopening a decision releases the option it had chosen rather than quietly leaving it marked.

Yes. You can upload reservation PDFs, tickets, screenshots, scans, and plain-text or calendar files, and attach each one to the part of the Trip it belongs to — a chapter, a place, a saved option, a research pass, a decision, a reservation, or a document record. Every file records where it came from, so a later session knows what it is.

Files are stored privately in this project's own storage. Deleting a file deletes the stored copy with it, and deleting a Trip deletes its files too. Opening a file gives you a direct link to it, so treat that link like the file itself.

Yes. A Today view resolves which chapter you are in from the dates you gave it, and shows that day in order, what you recorded as confirmed, documents that are expiring, the local things you still have to sort out, your packing, and what the Trip is costing. A travel day that belongs to two chapters is shown as both rather than resolved into a guess, and a gap between chapters is treated as a real day.

Everything there is what you recorded. Nothing checks live departures, availability, closures, safety, or weather, and amounts are totalled per currency and never converted between them. This is a notebook that knows your plan, not a service watching the world for you.

You can write up what you actually did — first-hand, dated, and marked as something you would do again, would not repeat, or was worth it once. You can say whether each decision you settled turned out the way you expected, so the reasoning and what came of it sit in one record instead of the plan alone.

Anything you would want on every future trip becomes a standing preference in your own words. Nothing is inferred from what you clicked; you promote it deliberately and can retire it later. A standing preference travels into future briefs because it is about you, while the Trip that taught it stays behind.

You can search everything you have ever saved, across every Trip, and carry one finding or option into the Trip you are planning now. It arrives with the source and date it originally had, is never marked fresher than it was, and a carried option arrives as a candidate because its old shortlisting belonged to a different question.

Searching across Trips is deliberate and so is carrying something over. A brief for one question still contains only that Trip.

It does not store confirmation codes, booking references, or provider logins. For a reservation you record where you keep the confirmation, in your own words; a field that looks like a booking code is refused.

You can mark a constraint sensitive. Sensitive constraints, reservations, document records, and every uploaded file are never placed in a brief for an outside assistant.

Every Assist With site is supported in one place: Assist With Life support, at https://assistwithlife.com/support. Take a question, a defect, a privacy concern, or a request about your own data there, and say it is about Assist With Travel.

There is no email address for this site — no support mailbox, no contact address, and none is planned. Anything that looks like an Assist With Travel email address is not ours. Nothing you write inside a Trip or a brief reaches a person either; the workspace is a private record, not a message to us.

No. This is a private soft launch. The durable planning record is live, while a connected AI, a remote tool server, live research, providers, booking, payment, sharing, and broader account lifecycle work remain Partial, Later, or Unknown.