What we store
- A random device token. Generated in your browser when you start a trip, 48 characters, meaningless on its own. It's how the app finds your trip again. It is not tied to a name, email, or account of any kind.
- Your trip corridor, in text. Origin, destination, and the working estimate of where you are, as you type it. That's the whole state the agent reasons about.
- The chat messages of the current trip. Both sides of the conversation, so the thread renders when you come back.
- A push subscription, if you turn one on. The subscription endpoint your browser gives us. The push payload itself never carries your location or trip content, only a generic line like "NightSaver has a question about tonight."
What we never store
We never ask for a name, an email, or a phone number, so there is no account to store. No GPS or precise location, ever, from any device sensor. No account, no password, no cross-trip history tied to you as a person. If you tell the agent a town name in conversation, that town text is stored with the trip (see section 05) and is the only location information that exists. It is scoped to that one trip and tied only to the random token.
Demo-data policy
Right now, hotel names and prices shown in the app come from a demo inventory set while live booking-partner access is being set up. Every one of those listings is labeled DEMO DATA directly in the product, in the same signage caps used elsewhere. It is never mixed in silently with real listings. When live inventory is on, this page and the product copy get updated together.
Price-timestamp policy
Every price you see carries the time it was generated, like "as of 6:02 PM." Hotel prices move. We're not claiming the number is still accurate by the time you tap it, we're telling you exactly when it was true so you can judge for yourself. Always verify price and vacancy before you arrive.
How long trip data lives
Your trip corridor and the chat messages are stored as long as the trip record exists, so the thread renders when you come back. Being straight with you: there is no automatic deletion running yet, so a finished trip's text stays in the database until a scheduled cleanup is added, which is on the near-term list. What is stored is only what section 01 describes, tied to a random token and never to you as a person. It is not sold, shared, or aggregated into any dataset tied to you individually.
If you would rather not have a town name or note sit in storage, keep the conversation to place names and skip anything personal. The agent only needs where you are and where you are headed.