Privacy Policy

Introduction

SoGoJet ("we", "us", "our") shows you flight fares we have checked and hands you to a booking partner when you want to book. This policy explains what we collect when you use the app or the website, why, and who else sees it.

SoGoJet does not take bookings or payments, in the app or on the website. When you book, you do it on our partner’s site, and they collect the traveller and payment details they need under their own privacy policy.

Information We Collect

Account information, if you sign in: your email address, your name if your sign-in provider shares it or you enter it in Settings, and the account identifier our authentication provider issues for you. If you sign in with Apple, Google or TikTok, we receive the identifier and email that provider releases to us, including Apple’s private relay address if you chose to hide your email. We never receive your password for any of those accounts.

Saves and swipes: the destinations you save, and which cards you viewed, skipped or saved. If you are signed in they are stored with your account id, so your saved trips follow you to other devices and your feed is ordered by what you liked. As a guest they stay on your phone.

App events: things like saving a destination or tapping through to our booking partner, with the destination, the route and the screen you were on. These are stored without your account id.

Searches: the text you type into search or the trip planner is used to answer it. It is not stored against your account, but it can appear in our server logs, which we keep for up to 14 days. Text you type into the trip planner or the AI search is sent to Anthropic to write the answer (see below).

Departure airport: the airport you choose, or, if you allow location, the nearest one, worked out on your phone. Your location itself does not leave your phone; the airport code does. It is sent with your requests so we can show fares from it, and it is stored in handoff records.

Device and connection information: app version, operating system version, device model, and your IP address. Your IP address is used to rate-limit abuse and, when you open the booking pass and again when you tap through to our booking partner, to estimate roughly where you are connecting from, so we can check whether we may send you to a partner from your state. Our web server logs record IP addresses and the addresses requested, and are kept for up to 14 days.

Identifiers: a random diagnostics ID created when you install the app (shown in Settings), sent with sign-in diagnostics so we can investigate sign-in problems; a second random install ID, kept in your phone’s keychain and sent only with Swipe Together and Fare Watch requests, so we can tell your phone apart from another person’s when you use them as a guest; and, if you allow notifications, your device’s push notification token, stored with your account id when you are signed in, with that install ID, and with your phone’s time zone (such as America/New_York) so we do not send Fare Watch notifications at night.

Swipe Together: when you start or join a session we store a random session code, the first name you choose to give (optional), your home airport, which cards in the shared deck you swiped right or left, and the cities you and the other person both picked, each with the fare we had checked from each home airport at that moment and the day it was checked. We store these with your account id if you are signed in, or with the install ID above if you are a guest.

Fare Watch: for each trip you save or match while Fare Watch is on, we store your departure airport, the destination, the fare we had checked when you saved it and the day it was checked, and whether Fare Watch is on for you. When we send a Fare Watch notification we record the new fare, when we sent it and, if you open it, when you opened it.

Crash and performance data: if the app crashes or hangs, Apple’s MetricKit gives us a diagnostic report with your app version, iOS version and device model. It does not include your account id.

Handoff records: when you tap through to our booking partner we record the route, the dates, the number of travellers, the price the card showed you and when that fare was checked, which screen you tapped from, your departure airport and a random click id. These records are never linked to your account, even when you are signed in. We also store a keyed, daily-rotating hash of your IP address, which tells us “same network twice today” and cannot be turned back into the address without our key. We keep these to know what we are being paid for and to answer a complaint that the app showed one price and the seller charged another.

On the website: when you open a fare on sogojet.com we check your rough location from your IP address, the same state check as in the app, and when you tap its Book button we keep the same handoff record, marked as coming from the website. To show fares from near you, the homepage sends your IP address to Travelpayouts to estimate the nearest airport. The airport you type into the departure board is sent to our server only to fetch that airport’s fares. Neither is stored, apart from our server logs (kept up to 14 days).

Website visitor counts: sogojet.com counts its visits with Umami, an analytics tool that runs on our own server. No other company receives any of it. It sets no cookies and stores nothing in your browser. For each page you open it records the page’s address (without anything after a “?”), the site that linked you to us, your browser, operating system, device type, screen size and language, and the country, region and city your IP address suggests. Your IP address itself is not stored. To count one visitor once, it makes a scrambled code from your IP address, your browser type and a key that changes every month. The code cannot be turned back into your IP address without our key, and a visitor is not recognised from one month to the next. It also counts taps on three kinds of link (App Store buttons, “See this trip in the app” and Book buttons), with the page the tap came from. This is the website only: the app does not use it. These counts carry no name, email or account. We delete them after 24 months.

Bookings, from our partner: our booking partner later tells us, for a click id, whether it led to a booking, and the booking’s value and status, so we can be paid. Because handoff records carry no account id, we cannot connect a booking to your account.

What We Do Not Collect

We do not collect your precise location. If you allow location, the app uses it on your phone to pick the nearest departure airport, and only that airport code leaves your phone.

We do not use advertising identifiers, we do not track you across other companies’ apps or websites for advertising, and we do not sell your personal information or share it for targeted advertising. There is no advertising SDK in the app.

We do not collect traveller details, card details or billing addresses. Your booking partner does, on their own site.

How We Use Your Information

To order the destinations in your feed from what you have saved and swiped.

To show fares from your departure airport.

To keep your saved trips on every device you sign in on.

To send notifications you allowed: a Swipe Together match, and a Fare Watch notification when a fare we check is at least 10% under the one you saw, at most one a week per trip and three a week in all, and never between 9 pm and 8 am in your time zone.

To run Swipe Together: to show you and the other person the same cards in the same order, and to show each of you the cities you both picked.

To detect and limit abuse of our search capacity, and to apply the state check described above before sending you to a partner.

To account for what our partner pays us, and to answer complaints about a price.

To improve the service. We do not send anything to a third-party analytics company. In the app we learn from our own records and logs; on the website we also count visits with a tool on our own server (see “Website visitor counts” above).

We do not use your information to make automated decisions with legal effects, other than not sending you to a booking partner from a state where we cannot do that yet.

Who Else Sees Your Information

The other person in a Swipe Together session: they see the first name you gave (if any), your home airport, how many cards you have swiped, and, for each city you both picked, the fare we checked from your home airport and the day it was checked. They do not see your other swipes, your email or your account.

Hostinger: hosts our servers. Our database runs on our own server there, and everything we store about you is stored there.

Clerk: authentication and account management (Sign in with Apple, Google or TikTok). Clerk holds your name, email and sign-in identifiers; we do not hold your sign-in credentials.

Apple, Google and TikTok: if you sign in with one of them, they know you signed in to SoGoJet. Apple also delivers push notifications, including Swipe Together and Fare Watch notifications, which contain the city, the fares and their dates.

Travelpayouts, and Kiwi.com or Aviasales: our booking partners. When you tap through, we open the partner’s site inside the app with the route, the dates, the number of travellers, our partner id and a random click id. Your name, email, account id and phone number are not sent and are not available to them from us. Because their site loads on your phone, they receive what any website receives, such as your IP address and device type. They later tell us whether a click led to a booking, and its value and status, so we can be paid. When you open the booking pass, and again when you tap through, we send your IP address to Travelpayouts to estimate your location for the state check. Once you are on Kiwi.com, Aviasales or a seller’s site you are on their service, under their privacy policy, and what you do there is between you and them.

Duffel: we use it to check fares. It receives routes and dates only, never anything about you.

Anthropic: writes trip plans and answers the AI search. It receives the destination, the trip length and style, and any text you type into those features, and never your account details.

Unsplash: destination photos. Your phone loads them from Unsplash, so Unsplash receives your IP address and device information, as any image host does.

Resend: delivers the email we send, such as a reply to you. It receives the recipient address and the message, and tells us whether each email was delivered. We keep that delivery record, with the recipient address and subject.

We do not currently run any error-reporting service. Our server error monitoring (Sentry) is present in the code but is switched off and receives nothing; if we turn it on, we will update this policy in the same change.

We share information with law enforcement only where we are legally required to, and we will tell you unless we are forbidden from doing so.

Cookies & Local Storage

On the website we use browser localStorage to keep your preferences (departure airport, currency, haptic settings) and session state on your own device. In the app the same preferences, and a guest’s saves, are kept on your phone. We do not use third-party tracking cookies, and there is no advertising tag on the site. The website’s visitor counter runs on our own server and sets no cookies (see “Website visitor counts” above).

Your Rights

Access: you can request a copy of the personal data we hold about you.

Deletion: you can delete your account from Settings, or ask us to delete it. Either removes your saved trips, swipes, preferences, push tokens, Fare Watch records and every Swipe Together session you were in within 30 days. A copy of a match the other person already saw stays on their phone. Handoff records never carried your account id, so there is nothing in them to remove.

Correction: you can ask us to correct anything we hold that is wrong.

Data export: you can request an export of the data we hold about your account, including saved trips and swipes. Handoff records are not linked to accounts, so they cannot be part of it.

Opt-out: you can use the app as a guest without an account. Your saves stay on your phone, but the app still sends the usage, diagnostic and handoff information described above, without an account id.

If you live in California, Colorado, Connecticut, Virginia, Texas, Oregon or another state with a consumer privacy law, or in the EU or the UK, you have these rights under your own law as well. We do not charge for exercising them or treat you differently for doing so. We do not sell your personal information, and we do not share it for cross-context behavioral (targeted) advertising, so there is nothing to opt out of. If your browser sends a Global Privacy Control signal, we treat it as an opt-out request anyway.

Data Retention

We keep your account data for as long as your account is active. If you delete your account, we remove your personal data within 30 days.

Handoff records, and what our partner reports about them, are kept for as long as we need them to account for commission and tax, which we expect to be up to seven years. They do not contain your account id, so they do not point to you, and deleting your account leaves them as they are.

Server logs are kept for up to 14 days.

A Swipe Together session lasts 7 days. It is deleted, with its swipes and matches, 30 days after it ends. Matches you saw also stay on your phone until you delete the app.

Fare Watch records are kept until you delete your account. Removing a saved trip switches its Fare Watch off, and turning Fare Watch off in Settings stops all of its notifications.

Aggregate figures that no longer identify anyone (how many people searched a route, how many cards were swiped) may be kept indefinitely.

Contact Us

Questions about this policy, or to exercise any of the rights above: privacy@sogojet.com. We aim to respond within one business day and in any case within the time your law allows.

To make a request, email privacy@sogojet.com from the address on your account. If you use the app as a guest, tell us roughly when you used it. We confirm your request within 10 business days and answer it within 45 days. We may extend that once, by another 45 days, if we tell you why. If we turn a request down, reply to our answer to appeal, and we decide appeals within 60 days. An authorized agent may ask for you with your signed permission.

SoGoJet is currently operated by an individual developer rather than an incorporated company. When an operating entity is formed, its legal name and registered address will be published here.

Questionssupport@sogojet.com