Privacy policy
Policy version 2026-11-14 · updated 14 Nov 2026
What this site stores on your device
CruiseFare uses four cookies that the site needs to work: to remember the currency and the language you picked, to keep you signed in, and to hold an unfinished price-alert form for a few minutes. We do not use cookies for advertising or for tracking you across other websites.
The first two are currency, which remembers the currency you picked, and NEXT_LOCALE, which remembers the language you picked. The third is the session cookie, set once you have entered a valid sign-in code; it is what tells the next request that you are the holder of that account. The fourth is a short-lived signed cookie, set only while you are part-way through the price-alert form; it holds the address you typed and the cabin type you picked, so that neither has to travel in a web address.
The session cookie and the short-lived one cannot be read by any script on the page (httpOnly). The session cookie expires or is removed when you sign out, and the short-lived one expires in 5 minutes.
All four are strictly necessary to deliver the service you asked for, so they are not gated by consent and keep working whether analytics are on or off.
What we record when you go to a platform's site
When you use a go-to-site button we write one record, so that affiliate commission can be reconciled and so that we can show afterwards which price you were looking at. That record holds:
- the platform you went to;
- the sailing, the cabin type and the number of guests per cabin;
- the price shown on screen, its currency and its basis (cruise fare only, or including taxes and fees), plus the exchange rate used if anything was converted;
- the language you were using and the time you clicked;
- the page you clicked from, and your browser's user agent string;
- your IP address, stored only as a one-way salted hash rather than as a raw address.
The link that takes you to the platform may carry a reference number for this click, so the platform can credit the booking to us; it contains no name, email address or other detail about you. Once you are on the platform's site, that platform's own privacy and cookie policy applies, not this one.
Your IP address and how it is hashed
In go-to-site records and in consent records we never store your raw IP address. We store only a one-way salted hash (HMAC-SHA256) computed from your IP address together with a secret key that is kept outside the database. The hash cannot be turned back into the original address.
We use it only to tell whether several clicks came from the same visitor, which is what makes commission reconciliation and bot detection possible at all.
This hash is pseudonymised data. It is still personal data under Thailand's Personal Data Protection Act (PDPA), because we can reproduce it from an address, so we do not call it anonymous and we protect it like any other personal data.
There is one exception, which we state here so that the sentence above is not read more widely than it is true: a signed-in session row holds the raw IP address of that sign-in rather than a hash, and it is deleted with the session. See the User accounts section below.
How long we keep it
We keep the identifying fields of a go-to-site record for 24 months from the moment you clicked.
Once a record is older than 24 months we delete exactly three fields from it: the hashed IP address, the user agent string and the page you clicked from. The click counts, the platform, the price shown and the time are kept, because they are the evidence a commission dispute rests on.
This deletion runs automatically every day on Bangkok time, not only when someone asks for it.
Website analytics
We use Umami for website analytics. It records which pages are viewed, the page you came from, and general details such as browser, device type, language and country. It also counts clicks on go-to-site buttons, anonymously, with the platform, cabin type and number of guests. It sets no cookies, does not store your IP address and builds no profile of you across other websites.
Analytics are on by default. You can turn them off at any time on the Cookie & analytics settings page at /cookie-settings, linked at the bottom of every page. From the next page on, the analytics script is not loaded at all.
If your browser sends a Do Not Track or Global Privacy Control signal, we treat it as turning analytics off.
If you turn analytics off or on, we store that choice in two cookies on your device: cf_consent, which holds the choice, and cf_consent_id, a random id that is tied to no account, name or email address. They last one year. If you chose Reject on our earlier consent bar, that choice still counts as off.
Your consent record
We record two separate kinds of consent, as separate records: your analytics setting, and consent to receive price-alert email. Each record holds your choice, what the consent was for (its purpose), the time you made it, the version of this policy, the language you were using, and one id saying who made the choice.
That id is not the same thing in the two cases. A cookie-consent record carries a random browser id, which is purely random and is tied to no account, no name and no email address. An alert-email consent record carries your account id, which is tied to your email address for as long as the account exists. When you delete the account the email address goes with it; the consent record stays, but what is left is an id with nothing attached to it.
The policy version shown at the top of this page is the version your consent would be recorded against. If we change this policy the version changes with it. A choice to turn analytics off stays in force when the version changes.
You can change your cookie and analytics choice at any time on the Cookie settings page, linked at the bottom of every page. Changing your mind writes a new record. We do not edit or delete the earlier one, so it stays possible to show which version of this policy you agreed to, and when.
User accounts
Signing in to CruiseFare uses a 6-digit code emailed to the address you give. There is no password, so we hold no password of yours, and we do not ask for your name, your phone number or any payment details — booking and paying happen on the site of the platform you choose, not here.
An account consists of your email address, an account id we generate, a permission level (role), which is user for everyone who signs themselves up, and one session row per sign-in. A session row holds the time you signed in, its expiry, your browser's user agent string and the IP address of that sign-in, and it is deleted when the session expires or you sign out.
While a 6-digit code is outstanding we hold the address and that code in one short-lived row, which expires in 5 minutes.
The lawful basis we rely on is your consent, given when you set a price alert or when you ask for a sign-in code.
You can delete your account, and every alert with it, yourself at any time from your alerts page at /alerts. It happens immediately, without asking anyone, with no confirmation email to wait for, and it cannot be undone. What is deleted is the account, every session and every alert of yours.
What survives deletion is the consent records and the record of which messages we sent and when. We keep those two because they are the evidence of the lawful basis and of what we actually did, which is the only reason such records exist. Once the account is gone neither holds your email address: what is left is an account id that can no longer point back at anybody. Go-to-site records are not tied to a user account at all, so deleting an account does not touch them.
Price-alert email
If you have set a price alert, we email you when the lowest price for the sailing and cabin type you picked drops meaningfully. That is the only reason we store your email address.
The consent you gave covers that one thing. We send no newsletter, no promotional email and no partner offers, and we do not pass your address to anyone for marketing. If we ever wanted to email you about something else we would have to ask for a separate consent.
There are two ways to stop it: the cancel link in every email, and your alerts page at /alerts. Stopping really deletes that alert rather than pausing it — there is no paused state here — and your other alerts keep running.
We keep one record per message we send, so that it stays possible to show what we sent and when, and so that we do not send the same thing twice. That record holds your account id, and holds the address as a one-way salted hash rather than as the address itself — the same mechanism, in the same terms, as the IP address above. The hash is therefore pseudonymised data, and is still personal data under the PDPA in exactly the same way.
Transfers outside Thailand
Everything we store, including your email address, sits on Railway's servers in the Singapore region (asia-southeast1), because that is where our web application and its database run. Holding the data of people in Thailand in Singapore is a transfer out of the country.
Email addresses and message content are processed by Resend, an email provider in the United States, solely to deliver sign-in codes and price-alert email. They are used for nothing else.
The safeguard we rely on is each provider's own data processing agreement. Both act as processors for us only, and neither is permitted to use your data for its own purposes.
Website analytics are processed by Umami Cloud, whose servers may be outside Thailand.
Neither destination country has been assessed as having adequate personal-data protection under Thai law. We tell you this here, before you choose, because the lawful basis for price-alert email is your consent.
Contacting us about your data
To ask about, see or delete the data we hold about you, email us at the address on the About us page.
What we hold about you is the go-to-site records, the consent records, and — if you have an account — the account data and price alerts described in the User accounts and Price-alert email sections above.
You do not have to wait for a reply to delete your account data: you can delete the account, and every alert with it, yourself and immediately from your alerts page at /alerts.