TRIBA private beta
Privacy notice
Effective 27 September 2026
TRIBA is an experience intelligence app in private beta. This notice explains the information the beta uses, including optional Oura, Gmail and Outlook connections. You can use the app without connecting any of them.
Information you give us
We collect your account details and the Tribe profiles, preferences, dietary needs, trip plans, itinerary entries and feedback you choose to enter. Please only add information about another person when you have their permission to share it with TRIBA.
Oura, if you connect it
Connecting Oura requires a separate permission step and Oura authorisation. The current connection requests Oura’s Daily scope. On a manual sync, TRIBA retrieves daily activity and sleep data for approximately the previous three days and stores step counts and sleep duration in minutes, associated with your account. We store encrypted access and refresh tokens on the server to maintain the connection. TRIBA does not request your Oura credentials. These summaries are for your personal context; they are not shown to your Tribe or published as community options.
Booking email connections, if you choose them
With separate trip import permission and provider authorisation, TRIBA can read recent Gmail or Outlook messages to identify possible travel bookings. The current scan examines up to 50 recent messages per check and stores only candidate facts such as title, date, place, type and a one-way hash of the provider message ID. Email bodies, attachments, payment details and identity documents are not stored. Candidates stay private to your account until you approve one for an itinerary. Reviewed booking changes can update the linked itinerary entry while preserving fields you edited yourself. TRIBA reads mail for this connection and does not change your mailbox or calendar. We do not send email, invite attendees or treat a candidate as a verified reservation. You can disconnect the mailbox; stored tokens are removed, while already accepted trip entries remain until you delete them. Google and Microsoft process account authorisation and API requests under their own notices.
Shared moments and learning
Adults you accept into your Tribe can see trip summaries and only photos you explicitly share with them. People with access to a shared photo can react and comment on it. Those interactions are visible to the photo owner and other adults with access to that photo. Each adult may separately allow structured reaction and comment activity to inform their Tribe’s suggestions. With that permission, TRIBA records the photo reference, account references, reaction type or comment activity and time in a private intelligence ledger; it does not copy comment text or image contents into that ledger. Turning this permission off deletes associated ledger events. A separate optional permission allows reaction counts to contribute to broad community patterns. Those patterns expose only country and emoji totals once at least ten opted-in Tribes and thirty reactions contribute; they do not include photos, comments or account identities. Sharing still works without either learning permission.
How we use information
We use the information to run your account, manage your Tribe and trips, make contextual experience suggestions, resolve problems and improve the beta using feedback. Suggestions are automated and may be incomplete or wrong. We do not use connected Oura readings as a basis for medical advice.
Who handles information
Our application infrastructure and authentication providers process information to operate TRIBA. If you choose Google sign-in, Oura, Gmail or Outlook, those providers handle information under their own notices too. We do not sell personal information. A connection to one provider does not authorise access to your other apps. Service providers and storage may operate outside your country.
Control, security and retention
Your account controls access to your Tribe and trip information. Provider tokens are encrypted in server storage. Oura summaries and imported booking candidates are account restricted. Disconnecting Oura attempts to revoke its token and removes TRIBA’s stored Oura tokens and synced readings. We keep other account information while needed to provide the beta, handle requests and meet applicable obligations. To ask to access, correct or delete your information, or to raise a privacy concern, use the TRIBA contact page. We will review your request and respond through that channel.
Changes
We may update this notice as the beta changes. We will update the effective date here and give additional notice when a material change calls for it. Other proposed travel, social or wearable connections are not active merely because they are discussed in the product roadmap; each needs its own integration and your choice to connect it.