Privacy Policy

MilesZone is the miles.zone website and service, operated by GEREZ TECH LABS. We decide what happens to the data described on this page. Questions about any of it: hello@miles.zone.

The shortest list first, because it is the one that matters.

• Your mileage program logins. We never ask for them and we never will. Everything we show comes from award seats that are publicly visible.
• Passwords. MilesZone has none. There is nothing here to reuse, leak, or steal.
• Card numbers. Card details are entered with our payment processor. We receive a reference to the payment method plus the brand and the last four digits. The number never crosses our boundary.
• Traveller details. No frequent-flyer numbers, no passport or identity documents, no date of birth, no postal address. Booking happens on the airline or program site, and what you give them there is between you and them.

• Your email address. That is the whole of your account: an address, when the account was created, and when you last signed in.
• Sign-in records. When you request a sign-in link we store a hashed version of the token, the address it was sent to, when it expires, whether it has been used, and the IP address that asked for it, which we use to stop abuse. If you sign in with Google we request the scopes openid email profile and nothing more, and we take your email address from the identity token Google signs. We never see your Google password.
• Your session. A hashed session token, when it was created, when it expires, when it was last used, and the browser user-agent string and IP address it started from.
• The alerts you create. The name you gave it, origin and destination, cabins, the programs and airlines you want, your date window, the minimum number of seats, your maximum miles and maximum fees, whether you want non-stop only, how often you want to hear from us, and whether the alert is running or paused.
• What your alerts find. Every match and near miss we record for you: the program, cabin, airline, flight number, miles, fees, seats left, stops, departure date and time, the booking link, when we saw it, when we re-checked it, and how long it stayed available.
• The emails we sent you. Subject, which of your finds the message carried, when it went out, whether the provider accepted it, its message identifier, and the error if it failed.
• The weekly email list. If you sign up we keep your address, when you asked and when you confirmed, the IP address, browser and page you did it from, and the wording of the form you saw, and an address that is never confirmed is deleted after 30 days. You can leave from the one-click link in any issue or from your account page, and we keep a note that you left so you are never added back by mistake.
• Your subscription. Plan, status, when a trial ends, when the current period ends, whether you have asked to cancel, any discount and how long it runs, and the payment-method reference, card brand, and last four digits described above.
• Why you cancelled. If you cancel we record the reason you pick and, if you write one, the free-text note you type in, stored as you wrote it. We also record which offer we showed you to keep you, whether you accepted it, and how long you had been subscribed.
• Feedback you send us. Survey answers, notes from the feedback box, what you tell us after a search that found nothing, and your replies to our emails. We keep them to improve the product, with the page or search they came from and, for a note from the box, a scrambled form of your IP address that we use only to stop abuse. Survey answers are linked to the account the survey link was emailed to, without you signing in; the link works for 60 days, and if it is opened in a browser signed in to a different account nothing is saved. Notes from the box and after a search are linked to your account when you are signed in. A reply to one of our emails is linked to your account when we can verify it came from your account's address; if we cannot, we keep it with the address it came from and do not link it to any account. Anything linked to an account carries a short summary of it such as your plan and how many searches and alerts you have. If you delete your account we keep your feedback without your identity: the link to the account and any email address are removed.
• Searches. Seeing search results needs a free account. Each search is kept with what you asked for: the route, dates, cabins, number of travellers and programs, and when you searched. If you are signed in, it is linked to your account through a hashed form of your account identifier, so we can show you the routes you searched, write to you about them, and count them in the summary kept with your feedback. If you are not signed in, it is linked only to a random identifier kept in a cookie in your browser, not to you. When you sign in from that browser, every search it made before you signed in is attached to your account, so your history starts where you did. Searches that are never attached to an account are deleted after 30 days, when the cookie that reaches them expires. Where product analytics are switched on they also record that a search happened and the route it was for; see cookies and analytics below.
• Your approximate location. When you sign in we look up your IP address in a database kept on our own server and find the airport nearest to it. We keep only the time zone of that airport, never the address or the place itself, and use it to send our emails at a sensible hour where you are. If the lookup finds nothing, we keep nothing.

MilesZone sets five cookies of its own. The measurement described below sets more, under its own names.

• mz_session keeps you signed in. It is strictly necessary: without it there is no account.
• mz_google_state protects the Google sign-in round trip against forgery. It lasts ten minutes, and carries your answer to “How did you hear about us?” if you gave one.
• mz_attr and mz_attr_first hold the ad click identifier and UTM tags a visit arrived with, so we can tell which advertising brings people who stay. When a first visit has neither and comes from a search engine or an AI assistant, mz_attr_first records which one instead: its address, read from the page your browser says sent you, marked as organic search or AI, and the page you landed on. They last 90 and 180 days. When you create an account, what they hold at that moment is saved with it, along with your answer to “How did you hear about us?”, and the UTM tags are copied to the payment provider if you subscribe.
• mz_consent remembers the answer you gave the cookie banner, for a year, so we do not ask again and so the site knows what it has to switch off.

Two things measure this visit. Counting how the site is used is PostHog, on its European hosting. Measuring which advertisement brought you here is Google Ads conversion tracking. Google Tag Manager and the OpenAI advertising pixel are wired into the code and switched off today; if we switch one on, this section is where we will say so. When a signup is recorded as a conversion, your email address is passed to the Google tag so that it can be matched to the advertisement that led to it. That is the one place where an identifier of yours reaches an advertising platform.

To tell people from automated visits, PostHog is also told one word about your connection: whether your IP address belongs to a cloud or hosting company. We look that up in a database kept on our own server; the address itself is not sent.

All of it runs from the moment you arrive, and the banner is how you stop it. It weighs accepting and refusing the same, it keeps showing until you answer it, and it offers the two purposes separately. Refuse, and we switch that measurement off and remember the refusal in mz_consent for a year, so it stays off on every page after it; Cookie choices in the footer reopens the banner if you change your mind.

• Sign you in and keep your session alive.
• Run your alerts: check the routes you asked for, re-check the seat before the email leaves, and send it to you.
• Rate-limit sign-in requests, and detect and investigate abuse, fraud, and scraping.
• Take payment, run the trial, and manage your subscription.
• Answer you when you write to us.
• Understand what people search for and where signups come from, so we know what to build and what to advertise.
• Meet our legal and accounting obligations.

We do not sell your personal information, and we do not use your alerts or your searches to target you with third-party advertising.

We share the minimum each provider needs to do its job:

• Email: Resend, which sends your sign-in links and your alert emails. It receives the address and the message.
• Sign-in: Google, if you choose to sign in with Google.
• Payments: Dodo Payments or Stripe, whichever took your subscription. Dodo Payments sells it as merchant of record, takes your card, and issues the receipt; Stripe takes the card for subscriptions started with Stripe. Either way we keep a reference, the brand, and the last four digits.
• Hosting and database: our infrastructure providers, who store the data described above on our behalf.
• Site assistant: Cerebras, and Microsoft Azure OpenAI when Cerebras is unavailable, which run the AI that answers the chat. They receive what you type there. See the site assistant.
• Analytics: PostHog, on its European hosting, and Google Ads conversion tracking. Google Tag Manager and the OpenAI advertising pixel are supported and not currently configured. See cookies and analytics.

These providers act as our processors: they handle your data to operate MilesZone, under their own business terms, and not for their own purposes. We do not sell your data.

Beyond the providers above, we disclose information only to comply with law, regulation, or valid legal process; to enforce our Terms of Service or protect the rights, safety, and security of our users, the public, or MilesZone; and in connection with a merger, acquisition, or sale of assets, in which case we will tell you. Airlines and programs never receive your data from us. When you follow a booking link you leave MilesZone and deal with them directly.

Some visitors see an “Ask MilesZone” button. It opens a chat with an AI, not a person, that answers from what this site knows: plans and prices, the programs we read, and seats we have found. It can be wrong, and it never books anything or promises that a seat will appear.

When you use it we receive what you type, the page you are on, and the route on screen if there is one, and we send them to Cerebras, which runs the model for us in the United States and does not keep what you type or what it answers. When Cerebras is unavailable they go to Microsoft Azure OpenAI instead, in its United States data zone. Microsoft does not use what you type to train its models. It may keep it for up to 30 days to watch for abuse, and then deletes it. Never type card details into the chat: we do not need them and do not ask for them. Before your first message a Cloudflare Turnstile check makes sure you are not a bot.

We keep each conversation for 60 days and then delete it. Email addresses, phone numbers and card numbers are blanked out before a message is stored. A conversation is linked to your account when you are signed in, and to a scrambled form of your IP address that we use only to stop abuse. If you ask the assistant to pass a question to us, the email address you type and the summary you approve are kept like any other feedback you send us.

Sign-in tokens expire after 15 minutes and are deleted 24 hours after that. Expired and revoked sessions are deleted on the same schedule.

A search made without an account is deleted 30 days after you made it, unless you signed in from the same browser before then and it became part of your account.

Your account, your alerts, and the finds and emails attached to them are kept while your account is open, because that history is what your alert pages show you. Delete an alert and the events and email records attached to it go with it. Close your account and we delete or de-identify your personal data within 30 days, except records we are required to keep for legal or accounting reasons.

Sign-in tokens and session tokens are hashed before they reach the database and compared in constant time, so we never hold a copy we could read or replay. Session cookies are HTTP-only, same-site, and secure in production. Sign-in requests are rate-limited per email address and per IP address. Traffic runs over HTTPS. No system is perfectly secure, so we cannot promise absolute safety, but we will notify you and the relevant regulator about an incident where we are required to.

Depending on where you live you may have the right to access, correct, export, or delete your personal data, to object to or restrict some processing, and to withdraw consent. Users in the EU and UK have these rights under the GDPR, California residents under the CCPA and CPRA, and users in the UAE under the Personal Data Protection Law. Write to hello@miles.zone and we will act on it.

You can also act directly, without asking us:

• Pause or delete any alert, from your account or from the links in any alert email.
• Unsubscribe from an alert in one click from the email itself.
• Change how often we email you.
• Cancel your subscription from your account settings.
• Close your account, which takes the data with it.

A search you start before signing in stays tied only to a random identifier in your browser, not to you, until you sign in from that browser.

We and our providers may process your data in countries other than your own, including in the United States and the European Union. Where the law requires it, we rely on approved safeguards such as Standard Contractual Clauses for those transfers.

MilesZone is for adults and is not directed at children. We do not knowingly collect data from anyone under 18. If you believe a child has given us data, write to us and we will delete it.

We may update this policy. When a change is material we will update the date at the top of this page and, where it matters, tell you. Continuing to use MilesZone after an update means you accept the revised policy.

Questions or requests about your data: hello@miles.zone.