Privacy policy

• • Account: email, an optional display name, a hashed password, whether the address has been confirmed, and which versions of these documents you accepted when you signed up.
• • Sign-in with Google: the provider, your provider account ID and the email it reports. Triplet does not store provider access tokens.
• • Travel profile: your departure airports, base location, trip length, budget and comfort preferences — used to personalize search, ranking and watch behavior.
• • My World: the countries you mark as visited, lived in or on your wishlist, any dates you add, and your private notes. This is visible only to you.
• • Saved watches: the search criteria, the address to notify, the conditions that trigger an email, how often it runs, when it last ran and what was sent.
• • Trip suggestions: trips generated for you are stored so a link keeps working, and expire on their own.
• • Usage and plan: AI search counts, your plan, and trial status — to apply the limits your plan describes.
• • Sessions and security logs: sign-in events, session records with the browser you used, and a one-way keyed hash of your IP address rather than the address itself.
• • Billing: when paid plans are enabled, Stripe customer and subscription identifiers. Card numbers never reach Triplet.

We process your account and profile data to perform the service you signed up for (Art. 6(1)(b)), and keep minimal security logs under our legitimate interest in protecting the service (Art. 6(1)(f)). We do not sell your data or use it for third-party advertising.

Triplet's primary account database is a PostgreSQL instance hosted in the EU/EEA (Amsterdam), on infrastructure that encrypts data at rest. Access requires credentials held only by our backend services, and passwords and tokens are stored only as one-way hashes. Some service providers we rely on — flight data, email delivery, and payments when paid plans are enabled — may process limited information outside the EU/EEA under their own contractual and legal safeguards, so we do not claim that every piece of data stays inside the EU at all times.

Triplet shows fares it has observed rather than live prices. To learn how far those drift, it may ask whether a price still held after you followed a live-price link. Following the link sends nothing — the check is noted only in your browser. If you answer, what is stored describes the fare: the route, how old the observation was, what Triplet showed, and which of the four answers you chose. Nothing describes you — no account link, no address, and no identifier beyond a random value whose only purpose is to stop one check being answered twice. Triplet asks at most once a day, never twice about the same fare, and “Don’t ask again” stops it entirely.

Flight prices come from Travelpayouts / Aviasales. When you open a deal we add an affiliate marker to the link itself, so Triplet may earn a commission if you book; Triplet adds no fee to the fare, and the booking provider sets the price you pay. Once you follow that link their site applies its own policy and cookies. Commission does not affect how Triplet ranks results. When paid plans are enabled, subscription payments are handled by Stripe — card details never touch our servers. Triplet loads no third-party scripts at all: no advertising, no analytics, and no affiliate tracking script. Attribution travels in the booking link, not in code running on your browser.

• • Account, profile and My World data: until you delete your account.
• • Email confirmation and password reset links: short-lived and single-use.
• • Sessions: until they expire or you log out, which revokes them.
• • Watches you never confirmed: removed automatically after a set period, so an address that never said yes does not sit in the database indefinitely.
• • Trip suggestions and cached fares: short-lived and expire automatically.
• • Security audit logs: pruned on a rolling window and anonymised when you erase your account.
• • Fare observations: kept long-term as market data. See below.

Triplet records the fares it observes — the route, the dates, the price, which source reported it and when. That history is what lets Triplet say whether €120 to Lisbon is genuinely good or merely normal, and it is the reason the product exists.

These observations describe a market, not a person. They are not linked to your account, and deleting your account does not remove them, because there is nothing in them that is yours. Your searches, watches, profile and trips are a different matter and are erased with your account.

When you search in plain language, Triplet sends your request and the minimum constraints needed to search it — dates, budget, airports — to the AI provider configured for the service. It is never sent your password, your session, payment details, or your private My World notes.

Prices do not come from the AI. The model can interpret a request, help shape search criteria and draft an itinerary. Every fare is produced by Triplet's own deterministic search against provider data, and the model cannot invent one or book anything.

Triplet supports more than one AI provider and uses the one configured for the service at the time. Ask at the support address if you need to know which is currently in use.

You can download all your data or permanently delete your account at any time from your Account page — deletion removes your personal data across our systems. You also have the right to correct your data and to lodge a complaint with your local data-protection authority.