Privacy Policy

This policy describes how we collect, use, and share information when you use the product. It is a starting point — replace it with counsel-reviewed language before you go live.

Information we collect

We collect information you provide directly, such as your name, email address, and account details, along with technical data like device type, browser, and approximate location.

• Account data: name, email, authentication identifiers
• Usage data: pages viewed, feature usage, diagnostics
• Billing data: handled by our payment provider; we store the minimum needed to manage your subscription

How we use information

We use this information to operate the product, keep it secure, communicate with you, and improve the experience. We do not sell personal information.

If you have questions about a specific processing activity, contact us and we will point you to the relevant section.

Destination finder

When you search with the destination finder ("Where can I go?"), we log the search so we can see what travelers look for and improve the results:

• What we log: the filters you chose (passports, months, departure airport, trip length, flight budget, kinds of place and the visas you accept), the places the results showed, and the time. If you typed a sentence, we also log the sentence and any interests we could not match to a filter. A search log holds no IP address and is not linked to an account.
• How long we keep it: the sentence and the unmatched interests are deleted after 90 days. The filters and results stay, without them, for counting.
• Daily search limit: to allow 20 searches a day per visitor, we count searches under a one-way hash of your IP address with a random value that changes every day. We never store the IP address itself, and the counts and the daily value are deleted after the day ends.
• AI provider: when the sentence box is on, your sentence is sent to OpenAI to turn it into filters. We ask OpenAI not to store the request. Under its API data policy, OpenAI may still keep API requests for up to 30 days to detect abuse.
• Flight links: when you open a flight link from a result, we record the click with the search it came from, so we can count which searches lead to bookings.

Server error reports

When a request fails on our servers, we send a report of the error to PostHog, our error-tracking provider, so we can find and fix the fault. We send these reports whether or not you allow analytics cookies. Keeping the service working and secure depends on them, which is our legitimate interest, so we build each report to leave out what identifies you:

• When a page fails: the report holds the kind of error, its message, where in our code it happened (file, function and line, without the code itself), the page's route as a pattern (such as /[locale]/dashboard, never the address you opened), the kind of request that failed (such as rendering the page), the request method, and our framework's code for the error.
• When an API request fails: the report holds the kind of error, its message, where in our code it happened, the endpoint's route as a pattern (such as /api/auth/*), the request method, the response status, and a random request id. The error response your browser receives shows the same id, so if you send it to us we can find the report. The id is new for each request and is not linked to you or your account.
• What we take out of messages: values a database query ran with or rejected, quoted values, email addresses, and long strings that look like ids or tokens. These rules cover the identifiers we know our errors can carry. A message could still, rarely, contain other text that reached the failing code.
• What we never send: your account id, email address or name, cookies or other request headers, query strings, tokens from links, or the PostHog identifier in your browser.
• Network address: PostHog receives each report from our server, so it sees our server's IP address, not yours. We ask PostHog not to look up a location for it.
• No profile: each report goes under a new random id, and PostHog builds no profile from it.

Sharing

We share information with vendors who help us run the product (hosting, analytics, email, payments) under contracts that limit how they can use it. We may also share information if required by law.

Your rights

Depending on where you live, you may have the right to access, correct, delete, or export your personal information, or to object to certain processing.

1. Open your account settings and update what you can directly.
2. Email us for requests we cannot fulfill in the product.
3. We will respond within the time required by applicable law.

Contact

If you have a privacy request, email the address listed on the contact page.