• Your account: name, work email, and a password. The password is held by our sign-in provider (Supabase) and FieldTrek never sees it in plain text.
• Traveler details for booking: legal name, date of birth, gender and title as airlines require them, contact email and phone, frequent-flyer numbers, and a TSA PreCheck (Known Traveler) number if you add one. Frequent-flyer and PreCheck numbers are shown only as their last four digits once saved.
• Home address if you choose to save one, plus the matching map coordinates, so searches can start from your front door.
• Travel preferences: preferred departure times, seating, usual number of checked bags, and any notes you add.
• Bookings: flight and hotel reservations made through FieldTrek, including the booking reference, route, dates, passengers, and totals, plus a copy of the airline's itinerary so we can tell you if a flight time changes.
• Price watches you set up and the email they alert.
• Your chats: the messages you type and the assistant's replies, so a conversation survives a refresh. The behind-the-scenes search data is not kept with the chat.
• An activity log of invites, bookings, and account changes, recorded in plain English for admins.

• You see everything you saved and every booking you made.
• Admins see the whole company roster (so they can book for anyone by name), every booking, saved home addresses (read-only), the activity log, and travel-spend totals.
• Nobody else sees your chats. Conversations are personal. Admins cannot open them.

Card numbers never touch FieldTrek's servers. Flights are paid from the company's prepaid balance with our flight provider (Duffel). Hotel payments are entered on a secure form run by our hotel provider (LiteAPI, processed by Stripe), and FieldTrek only learns that the payment succeeded.

Each one receives only what it needs to do its job.

• Duffel (flights): passenger names, dates of birth, contact details, frequent-flyer and PreCheck numbers, passed on to the airline to issue the ticket.
• LiteAPI (hotels): the guest's name and contact details, passed on to the hotel.
• Anthropic (the chat assistant): the text of your conversation and the search results it needs to answer. Anthropic's API does not use this data to train its models.
• Resend (email): your address and the itinerary or alert being sent.
• US Census Bureau, Geocodio, and Google (addresses and drive times): a street address or coordinates, so we can map it and route to airports. Nothing identifying you is attached.
• Ticketmaster and the US Energy Information Administration (events and gas prices): a city or region only, nothing personal.

We do not sell data to anyone, and we do not use it for advertising.

• Traveler details, your home address, preferences, and price watches stay until you remove them on My FieldTrek or an admin removes them.
• Bookings and the activity log are kept as the company's travel record.
• Chats can be archived, which hides them from your list. Ask an admin if you need one deleted entirely.
• Address lookups are cached for up to 180 days (30 days for Google results) to avoid repeat lookups.

• Every page requires sign-in. Sessions expire after 30 days.
• All provider keys live on the server only. The browser never receives them.
• Repeated failed sign-ins lock the account for a short time.
• Sensitive numbers are masked everywhere they are displayed.

To correct or remove anything, use My FieldTrek or ask a FieldTrek admin. Admins can deactivate an account, which stops sign-in immediately while keeping the booking record intact.