How we handle your information

Who this product is for

YourNav is built for adults only. There is no child account, no child-facing interface, and no service directed at children. If a trip involves a young athlete, that athlete is a record the adult account holder manages — a display name and optional team and sport details — never a user, a login, or an account of their own. We do not knowingly collect information directly from a child, and we do not collect a child’s age, date of birth, health information, custody information, passport data, payment credential, or live location as part of that record.

Information we collect

Account and household information

When you sign in, we use Firebase Authentication. You can sign in with a secure link sent to your email, with your Google account, with an email address and password, or with a verified mobile number where that option is offered. If you use a password, that password is held by Firebase Authentication — it never reaches YourNav’s own servers, and we never store it. We store your display name, your verified email address and/or mobile number, and the household and event your account is connected to. Firebase verifies control of a mobile number with a one-time code. We do not separately verify age or identity beyond the identifier used to sign in.

Trip planning information

As you use the product, we store the trip-planning information you and your household create: the event and household you belong to, any athlete records on that household, readiness checklist status (registration, travelers, hotel preference, arrival plan, waiver, gear), draft hotel preferences, and the approve/decline decisions you make on anything the concierge drafts. Hotel results are labeled by source: some are illustrative planning examples, while others may be live Booking.com rates at the retrieval time shown and can change. Neither kind is booked, held, or reserved through YourNav — see our Terms & Conditions for details.

Voice conversations

If you use the spoken trip agent in YourNav or by telephone, your audio is streamed live through our voice providers to carry on the conversation. We do not record or store raw audio or voiceprints. A minimized text transcript may be kept temporarily and then deleted. Telephone access is US-only. You can ask for a call at the verified number on your signed-in account. A caller whose number uniquely matches a current verified account connects without a code. Other eligible callers use a short-lived, one-use account code created inside YourNav and must call from that verified number. We do not place a follow-up call on our own. Caller ID alone is not sufficient; current verified-account eligibility is required.

Text messages (SMS)

Your account’s mobile number is first a sign-in method. Adding a mobile number for sign-in does not enroll you in YourNav Trip Alerts. The YourNav Trip Alerts program is inbound-initiated. When text access is active, its number and action appear in Profile; while it awaits activation, there is no active text link. You start every trip question, and the application sends one direct response without following up on its own. We do not send scheduled, automatic, or proactive trip reminders. After you reply STOP, replying START or UNSTOP records only your re-consent to text replies.

A verified phone number may be stored on your account. When an inbound message can be matched to that account, its content is used to respond to you and kept with your household’s trip conversation. A durable opt-out record keeps STOP effective across service restarts. We do not use this information to build an advertising profile or share it with a third party for that party’s own marketing.

Email conversations

Bidirectional concierge email is available only to an adult account with a verified email address. You write from that verified address to assistant@reply.yournav.ai; YourNav sends trip email from trips@send.yournav.ai and directs replies back through the assistant address. We use the signed provider event and the unique verified account match before any household context is loaded. Unknown, ambiguous, and unverified senders receive no trip information.

How we use information

• To run the product: authenticate you, load your household and trip, and carry out the actions you or the concierge draft and you approve.
• To generate trip-planning replies: your trip context and messages are sent to our AI providers only to produce the concierge’s response to you, never to train a public model on your data beyond what each provider’s own service terms allow.
• To send one direct application reply to each text question you initiate, persist your STOP/START preference, and provide private assistance only after a verified-adult match when you use an application-owned support word.
• To answer email you send from your verified account and telephone conversations you initiate through Call me, a recognized inbound call from a current verified number, or an eligible one-use call-in code.
• To keep the product secure and working — diagnosing errors, honoring the session and rate limits described in our Terms & Conditions, and preventing abuse.

We do not use your trip-planning or SMS messaging data for advertising, and we do not run third-party analytics or advertising trackers on this product.

Who can see what

Your household’s trip details — including a labeled hotel price or rate and your readiness checklist status — are visible to your household only. An athlete record on your household holds a display name and may hold team and sport details you provide; consistent with what we said above, we do not collect or store a child’s age, date of birth, guardianship verification evidence, or a private note for an athlete anywhere in the product. When a trip is organized through a team (for example, a club or race series), the team staff view is deliberately narrower still: the information a coach or team travel admin can see about another household is limited to a requirement name, its status, and whether it is overdue. That view has no place to put a price, verification evidence, a private note, or a date of birth — those fields simply are not part of what team staff can be shown, by construction, not by a setting someone could change.

Who we share information with

We do not sell your information. We share information only with the service providers that make the product work, each acting on our instructions:

• OpenAI — powers the typed and spoken trip concierge (text generation, live voice, and speech transcription).
• Resend — sends transactional trip email and receives messages addressed to the verified-account concierge.
• Twilio — carries the customer-initiated SMS program and the US telephone connection to OpenAI; your phone number and the content of the text or live call pass through Twilio to make those channels work. Twilio is not instructed to record calls.
• Firebase and Google Cloud — hosting, sign-in, and the database that stores your account and trip records. Your browser never has a direct connection to that database; every read and write goes through our server.
• Exa — a web search provider we use to look up public hotel ratings and social signal; it returns public web text to us and does not receive your personal information.

We may also disclose information if required by law, to protect the rights and safety of our users or the public, or in connection with a merger, acquisition, or sale of assets — in which case this policy would continue to govern any personal information involved.

Data retention

• Voice transcripts are retained temporarily and then deleted on a fixed schedule; raw audio and voiceprints are never stored.
• Account, household, and trip records are retained while your account is active, so your trip planning stays available to you.
• SMS message history is retained with your household conversation record. We also retain whether a phone number has opted out so the product can continue to honor that choice. Adding a number for sign-in is not stored as consent to receive Trip Alerts.
• Verified-account email content and minimized telephone transcripts may be retained with the household conversation. Provider event claims and call access codes expire automatically; the codes are stored only as cryptographic hashes.

Security

Provider credentials (including our AI provider key) are kept server-side and are never sent to your browser. Your browser holds no direct database credential; it presents a session binding, and our server decides who you are and what you are allowed to see or change on every request. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.

Your choices

• You can review and update your household’s trip information inside the product.
• You can opt out of SMS at any time by replying STOP to any text — see the SMS section above for the full detail.
• You can review the email address or mobile number linked to your account.

Children’s privacy

This product is not directed to children, and we do not knowingly collect personal information directly from a child. An athlete on a trip is a record the adult account holder enters and manages, not a person we collect information from directly.

Changes to this policy

We may update this policy as the product changes. We will update the “Last updated” date above when we do. A future change that introduces proactive text messages would require a separate consent flow before those messages could be sent.