Trust & Privacy
This page is maintained by the Traveler team to answer common questions about how the product handles your account, data, and privacy. It describes the controls currently enabled in the app - not an independent certification or audit.
Accounts & authentication
Sign-in is handled by our managed authentication provider. Passwords are never stored in our application database - only the provider holds password material. Google single sign-on is offered alongside email/password.
Each account is tied to a unique email. Admin-only areas require a separate role on the account, granted server-side; the client cannot self-promote.
Your data
Traveler stores the information you provide to use the product: profile details, trips you create, connection requests you send or receive, messages with accepted connections, and events you create or attend.
Access to your rows is enforced at the database with row-level security. By default, other travelers can only see the fields you choose to share when matching on a trip; your email address and account identifiers are not exposed to other users.
What others see before you connect
When your itinerary overlaps someone else's, each side sees a limited profile - much like a LinkedIn request: their first name, profile photo, a short profile (per their visibility settings), the type of overlap ("Same flight", "Same hotel", "Same route", "Same airport") and a match score. Flight numbers, hotel names, exact dates and last names are withheld.
Once both sides have sent and accepted a connection request, the full name and the exact shared segment are revealed and chat opens. This gating is enforced in the database itself, not in the app screens - the withheld fields are never sent to your device before both sides say yes.
Messaging & connections
Messages are only visible to the two participants of an accepted connection. A connection request can only be accepted by the recipient - the requester cannot self-accept.
You can block another user at any time. Reports you submit are visible to the Traveler safety team and are used to take action on accounts that violate the community rules.
Verification signals
Verification is tracked as independent signals, not a single level. Today Traveler can confirm two of them: your account email (confirmed when you create the account) and LinkedIn (you sign in with LinkedIn, which proves the profile is yours). A third signal, work email, is confirmed by sending a one-time link to a company address; the link expires after 24 hours and works once. Free providers such as gmail, yahoo and outlook are rejected as work emails.
Phone and government ID are not verified today. They are listed in the app as not yet available, and no profile can claim them.
A confirmed account email is required to appear in anyone's matches at all. Which signals a traveler has verified is shown as a small badge before you connect - it is a trust signal and identifies no one, the same as the compatibility score. Verifying a work email adds the company domain as a badge; it does not reveal your work email address to anyone.
Colleagues & blocked companies
Being discoverable by colleagues is off by default. Verifying a work email never adds you to a company directory. You must switch on the colleague directory for your verified company on your profile before anyone with a verified email at that same company can be shown you as a colleague - and the opt-in has to be mutual, so both sides must have turned it on.
You can also block specific company domains. A blocked company is removed from your matches in both directions: people with a verified email at that company do not appear to you, and you do not appear to them.
Both rules are applied inside the database queries that produce matches, so blocked and non-opted-in travelers are never returned to your device in the first place.
Trip invite links
Trip invite links contain a secret token. Only the trip owner can list the invites they created. Joining a trip via an invite link is processed by a server-side function that validates the token without exposing other invites.
Subprocessors
Traveler runs on managed cloud infrastructure for hosting, database, authentication, file storage, and email delivery. These providers process data on our behalf to make the product work and are bound by their own security and privacy commitments.
Data retention & deletion
You can edit or remove your profile, trips, messages, and events from inside the app. If you would like your account fully deleted, contact us using the address below and we will remove your account and associated personal data.
Security contact
To report a security issue or a privacy concern, email support@jointraveler.com. Please include steps to reproduce and any relevant accounts or URLs. We aim to acknowledge reports within a few business days.
This page reflects current product behaviour and is not a legal contract, certification, or audit report. It is updated as the product changes.