Privacy Policy

1. Information we collect

• No-show records: whether the place recorded your booking as a no-show, and, if you told the place you could not come, when you did.
• Booking details: name, phone number, email, country, the place, the item you book (service, menu item, or rental item) and the time you choose, the number of people, and the names of anyone you add to the booking.
• Companions' email addresses and phone numbers, if you add them (optional): when you book for more than one person, you can add the people coming with you. Their names are part of the booking; you can also add an email address and a phone number for each companion, and both are optional. Companions don't sign up for anything: you enter their details for them, and the booking screen asks you to add details only for people who have agreed to share them. To add an email address or a phone number you also need to give that companion's name (an entry with no name is not kept). An email address or phone number that doesn't look right is left blank, and the rest of your booking goes ahead. We keep details for up to 9 companions per booking. If you leave the email and phone fields empty, we collect nothing under this item, and you can book without them. We don't email, text or message your companions: confirmations, payment requests and updates go to you only. Section 2 says what we use them for, section 3 who sees them, section 4 where they go, section 5 how long we keep them and section 6 what a companion can ask of us.
• Account information if you sign up (email, or your social login profile such as Google or LINE).
• Booking requests sent without an account (before 2026-10-21): until 2026-10-21 you could send a booking request without signing in or creating an account; from that date you need to be signed in, and what follows applies to requests already sent that way. We collect the same booking details as above, and an email address is required. After you send the request, we email you a link to manage that booking; the link carries a signed code that points to the booking, and it does not contain your email address. When you open the link, we record against the booking the time your email address was confirmed — we record the same if you sign in to pay with that email address. Until then, the place and millio's operators see the request marked “email not confirmed”. Opening the link in that first email does not sign you in. Once the place accepts, you sign in or create an account to pay: with Google, with a one-time code we email to the booking's email address (there is no password), or with one tap on “Continue as” followed by your partly hidden email address, on the page you open from the link in our payment email. That link works only for that booking, only until shortly after the payment deadline, and only once for this. A link we send you on WhatsApp or LINE never signs you in: it lets you pay that one booking without an account, and you can link the booking to an account later from our emails. If there is no account for that email address yet, one is created at that moment with that email address (account information, above), and the booking is linked to your account. If you sign in with a Google account that uses a different email address, the booking is linked only if you opened the link from our email in the same browser tab before signing in. If the email address you enter already belongs to an account, sending the request does not sign you in or link the booking to that account: that happens only when the account's owner signs in at the payment step. To keep out automated and repeated requests, our server counts these requests, and the steps that follow such as asking for a sign-in code, by IP address and by email address over periods of up to a day; each count is kept with that IP address or email address and is deleted automatically about a day after it starts. A request that repeats one sent with the same email address for the same place, item and times within 10 minutes is not made a second time, and the request form has a field people can't see — a request that fills it in is not accepted. We don't use a third-party CAPTCHA. None of this applies if you are signed in when you book. Section 2 says what we use this for, section 3 who sees whether your email address is confirmed, section 4 how the emails are sent, section 5 how long it is kept and section 7 what is put in your browser.
• Messenger records for a booking (only if you connect WhatsApp or LINE to a booking or to your account, or write a WhatsApp number in the booking form): each time we send you a booking update on WhatsApp or LINE, we record against that booking which messenger it went to, when, and whether it was sent — and if not, the reason (for example, WhatsApp no longer allowed an ordinary message and the update went by email only). We never record your number, your LINE ID or the text of the message here. An update about a payment or a proposed time carries a short link (millio.co/b/ and a random code), which we keep with the booking for 30 days together with the kind of update and the time until which it lets you pay without an account; it opens that booking in your language. If you connected WhatsApp or LINE on a booking page without an account and then reply there, our operators see your reply next to that booking, so they know which booking you mean. If you tap “Continue as” on the page opened from a payment email, we keep a one-way code made from that link for 2 days, only so that the link can't be used for this twice. Only millio's operators see these records; the place doesn't. The records of messenger updates sent are kept in our operations log, which we don't delete automatically; you can ask us to delete them (section 6). Section 2 says what we use them for.
• Your sign-in steps during a booking: when you sign in or sign up partway through a booking — on a place's booking screen, from the sign-up sheet in our support chat, or at the payment step of a booking you requested without an account — we record each step of that sign-in as one line. Each line holds: the time; a visit ID, a random value kept in the cookie that remembers the link or ad that brought you to millio (section 7), which lets us connect the steps you took before signing in to the account you then signed in to; your account, once you have signed in (when a sign-in works, the steps from the 2 hours before that were recorded with the same visit ID or the same email address are connected to that account too — we match the email address as well, because opening a confirmation link in a different browser gives you a different visit ID); an email address, only if you tried to sign up or sign in with email (never when you use Google, LINE, WeChat or WhatsApp) — the address you typed or, for a code sent to your email or the one-tap link in a payment email, the booking's email address (once the sign-in works, your account's email address), which may not yet be confirmed as yours; the step — the sign-in screen was shown, you chose a way to sign in, the sign-in worked, it failed, or you came back to your booking and carried on; the way you chose — Google, LINE, WeChat, WhatsApp, email sign-up, email sign-in, a code sent to your email or the one-tap link in a payment email; whether you were on the booking screen, in the chat's sign-up sheet or at the payment step; which place's booking you were making; if a sign-in fails, the kind of failure — the email or password didn't match, the email was not yet confirmed, the confirmation or sign-in link was opened in a different browser from the one you started in, you declined or closed the Google, LINE or WeChat window, your return to millio after signing in had expired or happened in a different browser, the sign-in provider (Google, LINE or WeChat) reported an error, we couldn't send the confirmation email or the code, there were too many attempts, the confirmation link had expired or had already been opened (for a code sent to your email or on WhatsApp: the code was wrong or had expired), you tried to sign up with an email address that already has a confirmed account, the sign-up form rejected the password as too weak or as one exposed in a data breach, or some other error — a category only, never the error message itself; whether this sign-in created a new account; the kind of device — phone, tablet, computer or unknown — worked out from what your browser tells us, which we don't keep; and the language you were viewing millio in. We do not record your password, sign-in tokens or codes, your IP address, the full text your browser sends to identify itself, the profile Google, LINE or WeChat gives us, anything you wrote in the support chat, or the item and time you chose for the booking (those are part of the booking details above). Signing in at other times, for example from the home page, is not recorded this way. The ordinary access records made when you visit millio (see “How you use millio, recorded automatically as you browse” above) are separate from this record. Section 2 says what we use this for, section 3 who can see it, section 4 where it is stored, section 5 how long we keep it, section 6 what you can ask of us and section 7 what is put in your browser.
• Messages you exchange with the place about your booking, and anything you type into our support chat.
• Payment status. Full card numbers are handled by PayPal — millio never receives or stores them.
• A card hold, if you choose Confirm faster (where millio offers it — see the Terms of Service): when you start a card hold, we record it against your booking — its status (for example placed, charged or released), the amount held in won and in US dollars with the exchange rate used, when it was placed, charged or released, the date and time of the booking that was confirmed and who confirmed it (the identifier of a millio operator's account, or you), why it was released if it was, a short error code if something failed, and the order, authorization and payment numbers PayPal gives us for it. We never receive or store your card number or payment-method details — you enter them with PayPal. If you don't choose Confirm faster, there is nothing here to collect. Section 2 says what we use it for, section 3 who can see it, section 4 what is sent to PayPal and to our usage-statistics provider, and section 5 how long it is kept.
• A trip plan you unlock in “Build my trip”, if you do (you have to be signed in): for each plan you unlock we record, against your account, a key that identifies the plan — a one-way code made from your answers, not the answers themselves — whether it was your free first plan, a paid one or one opened during a membership, when you unlocked it, and which version of the no-refund notice you agreed to and when. For a paid plan we also record the payment: the amount and currency, its status (for example paid or refunded), the dates, and the order and payment numbers PayPal gives it. Your card or PayPal account details are entered with PayPal directly and we don’t receive them. If we unlock a plan for you or give you one free plan to fix a problem — for example a payment that went through but didn’t open your plan — we also record that, who on our team did it and why. This record is separate from the “Build my trip” counts described below, which still have no column for an account. If you don’t unlock a plan, nothing is recorded under this item. Section 2 says what we use it for, section 3 who sees it, section 4 what PayPal receives, and section 5 how long it is kept.
• A membership code, if you use one: when you enter a code you got from a millio partner (for example, the company you rent your home in Korea from), or use a partner's link, to start a 30-day membership, we record against your account the code or link, the partner it belongs to, when the membership started and when it ends, the discount on millio's booking fee it gives (if the partner offers one), and the language of the screen you started it from. Each booking you request during the membership records the discount applied to its booking fee. We don't receive anything about you from the partner.
• Bookings and payments that come through a millio partner (only if you used a partner's code, or opened a partner's link as described in section 7): when you pay for a booking within that partner's counting period (usually 30 days), we record against the payment the partner, whether it came through the code or the link, the booking, when you paid and when you visited, millio's booking fee for that booking (never the deposit), the part of that fee owed to the partner, any part of the fee refunded, and its status (waiting, confirmed, paid out or cancelled), with copies of the kind of place you booked and the country you gave on the booking. If you book after opening a partner link while its cookie is still in your browser, we also note against that booking which partner link it was and when you opened it. Before you pay, we ask whether that partner may see the payment's date and amount, and we record your answer and when you gave it.
• Problems you run into while signed in: if an error screen appears, or a payment or a trip plan unlock fails, while you're signed in, we record it against your account — what kind of problem it was (an error screen, a failed payment or a plan that didn't unlock), the page address (without anything after “?”) or the payment or booking number, the error code and a short description with email addresses and long numbers hidden, and when it happened. If our team deals with it, we also record when, who and a short note. If you're not signed in, nothing is linked to an account. Section 2 says what we use it for, section 3 who sees it, and section 5 how long it is kept.
• Where your booking asks it: what you tell us will be on your nails when you come in (bare, polish, gel, extensions, or not sure). We ask once per person on the booking.
• Reference photos, if you add them to a booking that takes them: up to 3 pictures, 4MB each — the look you want, or how things look right now, so a picture may show part of you (your hands, your hair, your face). Adding them is optional and only possible while you are signed in; add none and there is nothing here to collect. Your browser re-saves each picture before sending it and our server processes it again, which strips out where and when it was taken and what device took it — we never receive the location of your photos.
• Links, if you paste them into a booking that takes them: up to 3 addresses of posts on the social apps we accept. We never visit the address ourselves — no fetching, no preview — and we strip the tracking parameters out before saving it.
• A note, if you write one on a booking that asks for it: up to 500 characters in your own words, plus the Korean translation we make of it. This is where you tell the place something they should know before your appointment, so it may include something about your health — a procedure you had, a pregnancy, an allergy, how your skin or scalp has been. We only collect it if you tick the separate box next to it (see below). Write nothing and there is nothing here to collect.
• Review photos, if you add them to a review: up to 4 pictures. These are different from reference photos — they are meant to be public. They can appear on the place's page, and the image file itself has a permanent public address, so anyone who has that address can open it even while the review is hidden. We strip out where and when the picture was taken.
• Trip plans, if you add them on your Trip page: the name you give a plan, what kind of plan it is (a stay, sightseeing, food, getting around, or something else), its dates (the day it starts and, if it has one, the day it ends) and — if you know them — its start and end times in Korea time, a place (its name — and, if you pick it from a place search, its address, its position on the map and its name in your language with the Korean pronunciation shown beside it; for a plan that comes from a regional trip guide, see below), and a note of up to 500 characters. Adding plans to your account is optional and only possible while you are signed in; add none and there is nothing here to collect. You can also try up to 3 plans on the Trip page before you sign in: those stay in your browser only, and we don't receive them unless you sign in and save them to your account. When you type a place into a plan in your account, what you type is sent as a search as you go (section 3). If you pick a result, we keep that place's name, address and position on the map — and its name in your language with the Korean pronunciation shown beside it; if you save without picking one, we keep what you typed as the place's name. Anything else you type while searching is used only for that search — we don't keep it. When you add a regional trip guide's itinerary to your trip, each plan from the guide that has a place is saved with that place's Korean name, its address in Korean (the street address, or the lot-number address where the official source gives only that) and its position on the map. You don't type these and you don't pick them from a place search: they are the public details of that place that millio already holds in the guide, taken from official tourism sources and other public sources — information about the place, not about you. Add nothing from a guide and none of this is saved. Each plan that comes from a regional trip guide holds a small label saying which guide, and which part of it, the plan came from. Our server makes the label from the guide when you add the itinerary: you don't type it. It is shown to no one — not on your Trip page and not to people you invite to see your trip plans (section 3) — and it is not sent anywhere. Plans you add yourself have no label. Plans added from a guide are kept, shown and deleted like any other plan of yours (sections 3 and 5).
• Inviting someone to see your trip plans (optional): if you invite someone to see your trip plans, we keep a record of the invitation — your account and theirs, the access you choose (view only, or view and edit), when it was made and accepted, and when it expires, and a scrambled (hashed) form of the invitation link; we don't store the link itself, and you see it once, when you make it. You and the person you invite can see each other's display name (the name on the account) — never each other's email address or phone number. To join, the person you invite has to sign up or sign in. If you give someone edit access, what they add to your plans is saved as part of your plans and we don't record who changed what; what they type into a Place field is handled just as if you had typed it (section 3). Invite no one and there is nothing here to collect.
• How “Build my trip” is used, counted as totals only: each time anyone, signed in or not, uses “Build my trip” (the planner that the “Plan my trip” button opens), our server adds 1 to a count. This is not information about you as a person: the counts sit in a table with no column for a name, an account, a device or an address, and each count is only a number that goes up by one. We count how many times the questions were opened; how many times a result was opened; how many times a result was saved to your trip (the whole suggestion, or only the places you picked); the answers behind each result that was opened — the number of days, who is travelling, where you will stay, how local you want the trip to be (the famous sights, a mix, or the places Koreans go day to day), your interests, the pace, how much walking, your daily rhythm, your food preferences, the beauty services you picked, when you would like them, your beauty budget, your travel style (value, balanced or luxury), any place outside Seoul you will go on to, the month you start (year and month) and how far ahead that is (within 7 days, 8 to 30 days, 31 to 90 days or 91 days or more, or not set), each one a choice from a list we set — the start month comes from the date you pick — and never something you typed; and which places to visit and which places to book a result showed, and which of them were saved. Each count belongs to a cell made of the day (Korea time), the country the visit came from and the language of the screen. The country is the two-letter code that arrives with each request — our hosting provider works it out from the connection and attaches it — and we read only that code; we never read or store your IP address for this. We do not count — and the table has no column for — your IP address, cookies or device identifiers, your account or email address, whether you are signed in, anything you wrote yourself (a request note included) or your exact start date. Requests from search and preview bots and from command-line tools are not counted; to tell them apart we read your browser's identifying text from the request, and we do not keep it. The ordinary access records made when you visit millio (see “How you use millio, recorded automatically as you browse” above) are separate from this record. This is also not the same as trying plans on your Trip page before you sign in: those stay in your browser only, and we don't receive them unless you sign in and save them. Section 2 says what we use the counts for, section 3 who can see them, section 4 what is not sent anywhere, section 5 how long they are kept, and section 7 what is put in your browser.
• Interests, if you pick them: the kinds of places you'd like to book in Korea — hair salons, nail salons, lash and brow studios and so on — chosen from our list of place categories (a category can be on the list before it has any places). You can pick them right after you create an account, on a card on your Trip page (it stays until you answer it), at any time in your account, or in a short “What interests you?” question that may pop up once after you send a booking request or after your booking is confirmed. Picking them is optional, and they are saved to your account only while you are signed in. If you don't answer, there is nothing here to collect; if you tap Skip for now, we keep only the time you tapped it, so the card doesn't come back, and count that answer in the statistics described in section 2. If you answer the short question while signed in, what you pick is added to the interests already in your account — nothing you picked before is removed. If you aren't signed in, your answer stays in this browser only and we don't receive it (section 7).
• The free “Korean phrases for your trip” PDF: when you download it while you are signed in, we record that you did — your account, the language edition you downloaded, the time, the kind of device you used (phone, tablet, computer or other — estimated from what your browser tells us, which we don't keep) and the country and city we estimate from your connection (this record does not include your IP address) — and attach that record to your account. Downloading the phrasebook is optional and only possible while you are signed in; download nothing and there is nothing here to collect.
• Web push notifications, if you turn them on: when you tap “Turn on notifications”, we keep the push address your browser's push service gives us for that device, the encryption keys that let only your device read a notification, the language you use millio in, your browser type (a label of up to 160 characters), your account if you are signed in or, if you are not, the number of the booking you turned them on from, and when we last sent you a notification successfully and when sending to your device first failed. Turning them on is optional and happens only when you tap; leave them off and there is nothing here to collect.
• LINE, if you sign in with LINE: whenever you sign in with LINE we keep your LINE user ID — the one LINE gives us when you sign in — and whether you are a friend of our official account, together with the time that status last changed, and whether you want booking updates on LINE (on unless you switch it off). We keep these whether or not you add the official account; we send LINE messages only to people who have added it as a friend. If you don't sign in with LINE, there is nothing here to collect.
• Messages you send to our LINE official account, if you write to it: the text and photos you send there, when you sent them, and the number LINE gives each message. They reach only millio's operators — never a booking or the places you book. If your LINE is linked to your millio account, they are added to your support chat (see “Your millio support chat” below); if not, they are kept as a separate enquiry with your LINE user ID so that we can answer you on LINE, and are moved into your support chat — with no copy kept — once your LINE is linked to your account. If you tap “Chat on LINE” on your booking page, we link your LINE user ID to the millio account you are signed in to, so that your LINE messages join your support chat and our operators can see which account — and which of its bookings — the chat is about. We don't keep stickers, videos, voice messages, files or locations you send. If you never write to our official account, there is nothing here to collect.
• Messages you send to our WhatsApp number, if you write to it: the text and photos you send there (with any photo captions), when you sent them, your WhatsApp phone number and the number WhatsApp gives each message. They reach only millio's operators — never a booking or the places you book. If your WhatsApp number is linked to your millio account, they are added to your support chat (see “Your millio support chat” below); if not, they are kept as a separate enquiry with your WhatsApp number so that we can answer you on WhatsApp, and are moved into your support chat — with no copy kept — once your number is linked. If you tap “Chat on WhatsApp” while signed in, we make a one-time reference code, valid for 30 minutes, and put it in the message WhatsApp fills in for you; when that first message arrives, we link your WhatsApp number to the millio account you are signed in to (and note the booking you started from). An operator may also link your number to your account after checking it — for example, that it matches the phone number in your millio account. We never link it automatically. For the link we keep your account, your WhatsApp number, how it was linked and the booking you chose. With the chat we also keep when you last sent us anything on WhatsApp, and mark any reply still waiting to be delivered there. We don't keep your WhatsApp profile name, or any contacts, locations, voice messages, videos or files you send — we just reply that we can read only text and photos — and we ignore stickers and reactions. If you never write to our WhatsApp number, there is nothing here to collect.
• WhatsApp booking updates and signing in with WhatsApp, if you use them: if your WhatsApp number is linked to your millio account — because you signed in with WhatsApp or confirmed your number with a WhatsApp code while signed in, tapped “Chat on WhatsApp” while signed in, or our operators linked it after checking with you — we keep that link (your account, your WhatsApp number, and how and when it was linked) and whether you want booking updates on WhatsApp, which is on unless you switch it off in your account. To sign in with WhatsApp, you enter your WhatsApp number and we send a 6-digit one-time code to it on WhatsApp. The code works once, for 10 minutes, and stops working after 5 wrong tries. For each code we send, we keep only scrambled forms (keyed hashes) of your number and of the code — never the number or the code themselves — with how many tries were made, when it expires and when it was used. If no millio account is linked to that number yet, signing in creates one (a number our operators linked for you can't be used to sign in), with a random sign-in address that does not contain your number. To keep out automated and repeated requests, we count sign-in requests by a scrambled form of your phone number and by IP address. To avoid sending you the same booking update twice, we keep a one-way code made from the booking, the kind of update and when it happened — not your number or the message.
• Booking updates on WhatsApp or LINE for a booking, if you connect them on your booking page: when you tap WhatsApp or LINE on your booking page, we make a one-time code, valid for 30 minutes and tied to that booking, and your app opens with a short message containing it. When you send that message, we link the WhatsApp number or LINE user ID it came from to that booking — you never type a number this way, so these updates can't go to someone else by mistake. If you are signed in, it is linked to your account as well — unless that WhatsApp number or LINE account is already linked to another millio account; then we link it to that booking only. For LINE we also note whether you have added our official account as a friend (we only check this; we don't keep your LINE profile). For WhatsApp we note when the number last wrote to us, so we know whether we may send an ordinary message. If you choose “Not now” instead, we note that choice for the booking so that we don't ask again. It doesn't limit payment and proposed-time updates to email: those still go to the WhatsApp or LINE linked to your account, or to a WhatsApp number you wrote in the booking form (see below). The booking's other updates go by email only. The message with the code, and a “STOP” message, are not kept as an enquiry.
• A WhatsApp number you write in the booking form, if you choose WhatsApp as your contact method: it is kept with your booking details. Even if you never connect WhatsApp, we may send that number the updates for that booking that could cost you if you missed them — payment is needed, the payment deadline is close, the place has proposed other times or the time to reply is running out, or you can still pay after the payment deadline has passed. We send them from millio's WhatsApp business account, through WhatsApp (section 4), and they contain only the place's name, the date and time or a deadline, and a link to your booking — nothing else about you. If the number is wrong, they could reach someone else, so please check it when you book. If WhatsApp or LINE is connected to the booking or to your account, we send to that instead, never to both. To stop them, send STOP from that number, or turn off messenger updates for the booking or in your account. Choosing “Not now” on the booking page doesn't stop them. Section 2 says what we use the number for.
• Your millio support chat, if you are signed in: the support chat with Jun · millio support that you use while signed in is kept with your millio account as one conversation, so that you can see its whole history on any device once you sign in. If you chatted while signed out and then sign in and open the chat, that conversation is joined to your account's conversation. Messages you send to our LINE official account or WhatsApp number from a LINE or WhatsApp linked to your account are added to this same conversation, and each message records whether it came through the website, LINE or WhatsApp — our operators see this, and you see it as a small mark in the chat window. If you never use the support chat while signed in, nothing is linked to your account.
• Departure reminders, if you turn them on: when you tick “Remind me before I go” while adding a regional trip guide's itinerary to your trip, we keep a reminder record — your account, the region of the guide (for example Busan), the trip's start date you chose, the language you use millio in, and when each reminder was sent. The record does not contain your plan's names, places, notes or prices, and your email address is not copied into it — we read it from your account when a reminder is sent. The box is off until you tick it; leave it off and there is nothing here to collect.
• Trip news and new-feature emails, if you agree: you can choose to get an email now and then about new millio guides and features. It is optional and it is off until you turn it on — no box is ticked for you. You can agree in three places: a box on the email sign-up screen (“Email me trip news and new features”); a card on your My bookings or Trip page, shown to people who already have an account, which stays there until you answer it (“Get trip news by email?”); and a switch in your account (“Trip news by email”). If you agree, we keep a record for your account: the time you agreed; where you agreed (the sign-up box, the card or the switch); the language of the screen at the time; the version of the wording you were shown (2026-10-04.1); and when you withdrew, if you did. If you tap “Not now” on the card instead of agreeing, we keep only the time you tapped it, so the card doesn't come back. We don't copy your email address into this record — we read it from your account when we send. For each such email we also keep a send record: your account, which email it was, whether it was sent, failed or skipped (with a short reason code), when, and the message number our email provider gave it — but not your email address or the text of the email. Agree to nothing and there is nothing here to collect, apart from the time you tapped “Not now”. We don't ask people who are not signed in, or people whose account has no usable email address (for example, an account created with LINE or WeChat sign-in).
• Records of the emails we send you: whenever we email you — a booking email, a sign-up confirmation, a trip-news email or any other — we keep a record of that email: your email address, its subject, what kind of email it is, the booking it concerns, if any, and when it was sent. Our email provider also tells us what became of it — delivered, delayed, bounced or marked as spam, and whether it was opened or a link in it was clicked — and we add that to the record. A report that an email was opened or a link was clicked also carries the IP address and browser details of the device or service that opened it or clicked the link and, for a click, the address of that link; a report that an email bounced carries the reason the receiving mail server gave. If an address bounces or is marked as spam, we also keep it on a list of addresses we no longer send to, with the reason, when we were told and how many times. Section 2 says what we use them for, section 3 who can see them and section 5 how long we keep them.
• A partnership enquiry, if you send one through the form on our About page: your name, your email address, your phone number if you give one, your company or brand, your country or region, your message, and the language of the screen you sent it from. Sending one is optional; send none and there is nothing here to collect. Section 2 says what we use it for, section 3 who can see it, section 4 how it is delivered and translated, and section 5 how long it is kept.
• How you use millio, recorded automatically as you browse: the pages you open, the links and buttons you tap, the site or ad that brought you here, and your browser and device details — and, when you create an account, the country and city we estimate from your connection. Section 7 explains how, and section 4 who receives it.
• Ad measurement, if it is on for you (section 7): the Google tag on millio.co sends Google these things straight from your browser and not through our servers: device and network details, the ad click identifier if you came from a Google ad and, once a booking request goes through, a scrambled reference to that booking (section 4). Your browser also keeps your choice about ad measurement; we don't receive that choice.
• A personal-recommendation request (the optional place-recommendation service), if you make one: you have to be signed in with a confirmed email address, and we collect the name you give, your city, the number of people, your budget per person, up to two must-haves, the kind of service you want and what you write about it, any reference links or extra conditions, your dates and time of day, the language you use, the time you accepted the fee, and the site or ad that brought you here; then the messages you and our team exchange about the request (with their translations), the recommendations we prepare for you — including a draft written with the help of AI — and the record of the fee you pay, which PayPal handles (section 4). Make no request and there is nothing here to collect. Section 5 says how long we keep it and what happens when you delete your account.
• A request to book a place that isn't on millio (free), if you send one: you have to be signed in, and we collect your name and phone number (with its country code), your account's email address, the place's name or the link you give, what you'd like done there, your preferred date and up to 3 times, the number of people, the language you use and the site or ad that brought you here; then the booking link our team sends you and the messages you and our team exchange about the request (with their translations). Make no request and there is nothing here to collect. Section 5 says how long we keep it and what happens when you delete your account.
• Contact details you share back from one of our digital business cards, if you choose to: when you scan the QR code that the card's owner shows on their phone (the card opens at an address starting “millio.co/card/”; at present the only card is our CEO's), “Save contact” saves the owner's details to your phone without asking for your name or contact details. If you then choose “Share yours back” and tap “Agree & send”, we collect what you type in — or what your phone fills in for you: your name, a phone number or an email address (at least one of the two) and, if you like, your company. We keep them with the language of the screen, the time we received them, the QR code they came through and the version of the notice you agreed to. Before you send anything, the screen tells you why we keep them, what we keep, for how long, and that sending is optional. To keep out automated and repeated sending, our server counts these sends by IP address; each count is kept with that IP address and is deleted automatically about a day after it starts. Send nothing and there is nothing here to collect. Section 5 says how long we keep them.

About that note. Under Korean law, information about your health is handled separately from everything else, and we may only collect it if you agree to that on its own — not bundled into the agreement you give for the rest. So the note has its own box, right underneath it, and the box only appears once you have written something. Here is what you are agreeing to: the note (and its Korean translation) is read by the place you booked — the owner and the person assigned to you — and by millio's operators, and by no one else; it goes through Anthropic in the United States to be translated into Korean, because the person doing your treatment reads Korean; it is never put in an email or a text message; and it is kept with your booking and deleted when your booking is. You can say no. Leave the note empty and book exactly as usual — nothing about your booking changes, and we ask for nothing.

2. How we use it

• To show a place you book with how many of your bookings a place recorded as a no-show when you had not told it you could not come — only that number — so it can prepare for your booking; and to let millio's operators see the same number.
• To create and manage your booking and pass it to the place you booked — or, where millio books on your behalf, to request that booking there for you.
• To place, charge and release a card hold for a Confirm faster you chose; to make sure the same booking never gets a second card hold or a second charge; and to respond to payment disputes.
• To give you access to the trip plans you have unlocked in “Build my trip”, to make sure each account gets its free first plan once, to make sure the same plan is never charged twice, to refund a duplicate or mistaken charge, and to keep the payment records the law requires.
• To give you a membership's benefits while it is on — new plans in “Build my trip” without payment, a lower booking fee if the partner offers a discount, and your booking requests and support chats handled first — and, for the partner whose code or link you used, to count the bookings, payments and visits that came through it and to pay that partner the share of millio's booking fee we agreed. A payment counts as confirmed 7 days after your visit if the fee has not been refunded by then. We give the partner how many times each of its links was opened each day, and totals: how many memberships, booking requests, payments and visits there were, how they split by country and by kind of place, how much was paid, and the amount we pay it. Any of these counts under 3 is shown as “fewer than 3”. Only if you agree before paying (section 3) does the partner also see that payment by day: its date, which of the partner's links or codes it came through, the amount paid and the partner's share. We never give the partner your name, email address or contact details.
• To find people who ran into an error or a failed payment, fix the problem and contact them if needed (the record of problems in section 1).
• To pass your reference photos, links and note — and, where your booking asks it, what will be on your nails — to the place you booked, so the right preparation can be made before you arrive. We use reference photos and your note for nothing else — not advertising, not reviews, not training AI, not analytics.
• To pass the details of the companions you added — their names and, if you gave them, their email addresses and phone numbers — to the place you booked, along with your booking, so the place knows who is coming and can have a seat ready for each of you. It is not a way for us to reach your companions, and we don't use it for that. We use companions' email addresses and phone numbers for nothing else: not advertising or marketing, not statistics, not training AI. Their names, email addresses and phone numbers are not sent to our usage-statistics provider (PostHog — the booking steps it receives show only how many companion names were filled in), to Google ad measurement, to our support chat assistant or translation service (Anthropic), to our operators' Telegram group, or in the KakaoTalk and text messages that notify places.
• To publish the reviews and review photos you write on the place's page.
• To show your trip plans back to you — on your Trip page, day by day next to your bookings, and on that day's map and route. We also count everyone's plans together to make statistics about how Trip is used — for example, how many plans are made in each area, which places to stay are most popular, how long trips last, and which countries the people using Trip signed up from (the country we estimate when you create an account, see section 1) — so we can improve millio and decide where to expand it. These statistics are shown only on millio's operator screens and seen only by millio's operators; we never publish them or give them to any place, partner or other third party. They include no names, email addresses or contact details, but they may show small counts — down to a single person — for a particular area, place or country. We also show your trip plans to the people you invite, and manage those invitations (whom you invited, and what each person can do). The label on a plan from a regional trip guide (section 1) is used for three things only: so that adding the same guide trip again does not repeat plans you already have — even if you have edited them; so that a plan from a guide is shown in the language you are using — only wording that is still exactly the guide's own is switched, never what you wrote; and for the check before a departure reminder is sent, described below. Other than the uses above — and the check before a departure reminder is sent, described below — we use trip plans for nothing else: they are not passed to any place, not put in any email (the departure reminders you turn on say only the region and how many days are left), not read by our support chat assistant, not sent to our usage-statistics provider, and not used for advertising or training AI.
• To show you first, when you browse millio.co, the places and picks that match the interests you picked. millio's operators can also see your interests when they help you with a booking or another request. We also count everyone's choices together to make statistics — for example, how many people pick each kind of place, overall and by country or language (the country we estimate when you create an account, and the language you use millio in) — to decide which kinds of places to add to millio and where to expand. Like the Trip statistics, these statistics are shown only on millio's operator screens and seen only by millio's operators; we never publish them or give them to any place, partner or other third party (the phrasebook screen in the next point is a separate screen). They include no names, email addresses or contact details, but they may show small counts — down to a single person — for a particular kind of place, country or language. Apart from the phrasebook point just below, we use your interests for nothing else — they are not passed to any place, not put in any email or text message, not read by our support chat assistant, and not sent to our usage-statistics provider or used for advertising.
• To see how the free phrasebook is used: millio's operators can see, account by account, who downloaded it, in which language edition, when, on what kind of device and from which country and city — next to what they can already see about that account (its email address, the site, ad or campaign that brought the person to millio, the country and city we estimated when the account was created, and the interests you picked, if any). We use this to learn which visitors the phrasebook reaches and which kinds of places they are interested in, to improve the phrasebook and millio, and to decide which kinds of places to add and where to expand. Only operators with full access can open that screen. It lists accounts one by one and shows counts by country, edition, device and interest even when the count is 1 or 2. We use these records for nothing else: they are not passed to any place, not put in any email or text message, not read by our support chat assistant, and not used for advertising or training AI. (Our server tells our usage-statistics provider only that a phrasebook was downloaded and in which language — not who downloaded it. The tap on the download button is seen like any other button, and in a browser that has made a booking it is linked to your email address there; see sections 4 and 7.)
• To count how “Build my trip” is used — how often it is opened, which answers people choose, which places show up in results and get saved, and which countries and languages it is used from — so we can improve millio and decide which places to add and where to expand. This counts times, not people: someone who opens it twice is counted twice. Unlike the Trip and interests statistics above, it also counts people who are not signed in, and its country is the country each visit came from, not the one we estimated when an account was created. millio's admin screens show totals only, seen only by millio's operators; we never publish them or give them to any place, partner or other third party. They may show small counts — down to a single time — for a particular country, region, place, place to book, interest, beauty service or start month. We use the counts for nothing else: they are not passed to any place, not included in any email, not read by our support chat assistant, not sent to our usage-statistics provider, and not used for advertising or training AI.
• To understand how millio is used — which pages and steps people use, where they give up, and which links bring them here — so we can improve it.
• To measure which of our Google ads lead to booking requests, so that we can tell whether our advertising works (section 7). We don't use this to show you personalised ads.
• To send booking confirmations and updates.
• To keep a record of the emails we send (section 1): to check that an email was sent, that it arrived and whether it was opened; to find out why one did not reach you — for example a payment request you never saw — so that our operators can try to reach you another way; to avoid sending again to an address that bounced or was marked as spam; and to settle a dispute about an email.
• To deliver updates about your booking by push notification and LINE message, as well as by email — push and LINE only if you turned them on: your request reached the place, a time was confirmed and payment is needed, the payment deadline is close, the deadline passed and the slot was released, the place proposed other times or asked you to choose a different time, the time to answer a proposal is running out, your booking is confirmed, your request didn't go through, the place cancelled your booking, your booking time changed, your visit is the next day, or the place sent you a message. We never use them for advertising or marketing. A notification never contains your email address or the text of your chat — only a headline (usually with the place's name and the date and time), one line on what to do next and a link to your booking.
• To let you chat about your booking on LINE: to pass what you send to our LINE official account to millio's operators, translated where needed (section 4), and to send you on LINE the replies our operators write, translated into your language, when LINE is where you last wrote to us from. Unlike the booking updates above, these replies contain the text of the chat. Replies the place writes in your booking's messages are never sent on LINE. We never use them for advertising or marketing.
• To let you chat about your booking on WhatsApp: to pass what you send to our WhatsApp number to millio's operators, translated where needed (section 4), and to send you on WhatsApp the replies our operators write, translated into your language, when WhatsApp is where you last wrote to us from. Within 24 hours of your last WhatsApp message, a reply is sent as it is. After that, we first send only a short notice that millio support has replied, without the reply itself, and the reply follows on WhatsApp the next time you write to us or tap the notice's button. Replies the place writes in your booking's messages are never sent on WhatsApp. We never use them for advertising or marketing.
• To send you booking updates on WhatsApp as well as by email, if your WhatsApp number is linked to your account (and you haven't switched them off) or to the booking, or — for payment and proposed-time updates only — you wrote it in the booking form (section 1): at the same moments as the updates above. Within 24 hours of your last WhatsApp message to us, an update is a short message — a headline with the place's name and, depending on the update, the date and time, one line on what to do next and a link to your booking. After that, WhatsApp only lets us send messages in a format it has approved in advance, so we send one only when missing it could cost you — payment is needed, the payment deadline is close, other times were proposed or the time to answer is running out, your booking time changed, the place cancelled, your visit is the next day, or the place or millio sent you a message about your booking — with the place's name and, depending on the update, the date and time or a deadline (never the text of a message), and a button to your booking. If you reply, your message reaches millio's operators, not the place. We never use them for advertising or marketing.
• To let you sign in with WhatsApp: to check with a one-time code that the number is yours, to sign you in or create your account, to link the number to your account, and to keep out automated and repeated sign-in requests.
• To send a booking's updates to the WhatsApp or LINE you connected on its booking page — the same updates and the same rules as above — and to show on the booking page whether they are on.
• To keep messenger records for a booking (section 1): so that our operators can see whether a payment request or a proposed time reached you on WhatsApp or LINE, and contact you another way if it didn't; to open the right booking from a short link; to stop a link in a payment email from being used to sign in twice; and to show our operators which booking a WhatsApp or LINE reply is about. We never use them for advertising, marketing or statistics.
• To keep one support chat history for each signed-in customer: to show you, in the chat window on any device where you are signed in, everything in your support chat — including what you sent and received on LINE or WhatsApp — and to let our operators answer you with the whole history in front of them. Your messages are translated into Korean for our operators where needed (the original is kept), and our operators' Korean replies are translated into your language (section 4). We pick that language from your account's language setting, or else the chat's earlier language, the language of your message or, for WhatsApp only, your number's country code; we don't read a language from your LINE or WhatsApp profile. We never use this history for advertising or marketing.
• To send the departure reminders you asked for — only if you ticked “Remind me before I go” when you added a regional trip guide's itinerary to your trip: one email about 14 days before the trip starts and one 3 days before (if you add it when the trip is 14 days away or less, the first goes out the next day, but only if at least 7 days remain on that next day — that is, if you added it 8 or more days before the trip starts; if you add it 4 to 7 days before, only the reminder 3 days before is sent, and nothing is sent if the trip starts within 3 days), and a notification or LINE message as well if you have turned those on. Apart from a short fixed note about booking your train or flight and a place to stay, a reminder says only the region and how many days are left, with a link to that region's public guide — never your plan's names, places, notes or prices, and never your booking number. We never use it for advertising or marketing. Just before a reminder is sent, our server checks that the trip is still in your plan; it reads plan names, dates and the guide labels (section 1) only for that check, and neither shows nor keeps them.
• To show a short introduction to millio's other services (for example the regional trip guides) in your booking confirmation email and your review-request email. It is part of that email, the same for everyone, and appears once per person in the first confirmation email and once in the first review-request email. It never contains your booking number, trip plans or interests, and it carries no prices or deals. To show it only once, we check your booking history (whether a booking was confirmed, and the visit time) when the email is sent and do not store the result.
• To email you news about new millio guides and features, only if you agreed. These are advertising emails, and each one says so: its subject line begins with “Ad:”, and at the bottom it says why you are receiving it (the date you agreed), who sends it and how to unsubscribe. Whether you get one depends on your agreement — we don't use your bookings, trip plans, interests or country to choose who gets one or to tailor it. Apart from the language you agreed in, the date you agreed and the unsubscribe link (which carries a signed code that points to your account), each email is the same for everyone: it never contains your name, a booking number, your trip plans, or prices or deals. We send it only by email — never by push notification or LINE — and only if you have confirmed the email address on your account and it is not on our list of addresses we no longer send to. We don't send these emails between 9 p.m. and 8 a.m. Korea time. Two years after you agree we stop sending, until you agree again.
• To provide customer support and issue coupons or discounts.
• To help you if signing in goes wrong during a booking: for example when you tell us you can't sign in, millio's operators can look at the record of your sign-in steps (section 1) on our admin screens to see which way you tried and where and why it stopped, and help you from there. We use this record for nothing else: not advertising or marketing, not statistics, not training AI. It is not sent to our usage-statistics provider (PostHog; this does not change what that provider otherwise receives), to Google ad measurement, to our support chat assistant or translation service (Anthropic), to our operators' Telegram group or to the places you book.
• To handle booking requests you send without an account: to email you the link to manage your booking, to show the place and millio's operators whether its email address has been confirmed, to link the booking to your account when you sign in to pay, and to keep out automated and repeated requests (section 1). We use the counts by IP address and email address for nothing else.
• To read and answer a partnership enquiry you send us, and to follow up on it.
• To prepare and deliver the recommendations you ask for in the optional place-recommendation service, and to talk with you about the request. AI helps with the research; our team reviews and approves what you receive (section 4).
• To book a place that isn't on millio when you ask us to: to check with the place whether your times are free, to add the place to millio, to send you a booking link, and to talk with you about the request.
• To let the owner of the digital business card save the contact details you shared back (section 1) to their phone and get in touch with you — just as after exchanging paper business cards — and to keep out automated and repeated sending (we use the count by IP address for nothing else).
• To keep the service secure and comply with legal obligations.

3. Who we share it with

We share the information needed to fulfil your booking with the place you booked — your name, your contact details, what and when you booked, how many people are coming (with the names of any companions you entered and, if you entered them, their email addresses and phone numbers), and, where your booking asks it, what will be on your nails.

When you book, the place sees only the number of no-shows recorded for you as described in section 2 — not which places or when. A no-show counts only when a place has recorded it; it is never added automatically when the time passes, a booking you told the place you could not come to is not counted, and if a no-show is corrected the number changes. millio's internal test accounts are not counted.

Only three people can open a reference photo, a link you pasted, or a note you wrote: the owner of the place you booked, the staff member assigned to your booking, and millio's own operators. No one else sees them. They sit in private storage in the Seoul region of Korea with no public address — this is not an “anyone with the link can open it” setup — and the place opens them inside the millio console, never by email.

A companion's email address and phone number reach the place the way the rest of your booking does: in the line for companions in the booking email we send the place, and in our database you (the person who booked), the owner of the place, the staff member assigned to your booking and millio's operators can read them — no one else. Where millio books on your behalf, that email comes to millio's operators instead, and they may pass on to the place, by phone or in writing, what the booking needs. We don't contact the companion, and we don't share these details with anyone else.

We don't share your trip plans with the places you book or with anyone else — unless you invite someone. A person you invite to see your trip plans — who has signed up or signed in and joined — sees all of your trip plans on their own Trip page: each plan's name, kind, dates, times, place (its name, address, position on the map, and its name in your language with the Korean pronunciation) and note; with edit access they can add, change and delete plans too. They don't see your bookings or payments, your email address or your phone number, only your display name — and you see theirs. Someone who opens an invitation link, even before signing up, sees your display name and the access you chose. You decide whom to invite: you can cancel an invitation, change the access or remove a person at any time, and they can leave at any time. Once a person is removed or leaves, your plans are gone from their page straight away. Your individual plans don't appear on millio's admin screens or on the screens the places use — millio's admin screens show only the statistics described in section 2, counted across everyone. When you type a place into a plan on your Trip page while signed in, what you type goes to Kakao as a search as you go (from 2 characters), and Kakao finds the matching places — only those words, never the rest of the plan (its name, dates, times or note). If you search in Japanese or Chinese and nothing is found, the same words also go to Anthropic, which turns them into the place's Korean name so we can search again. To show the places a search finds in your language, our server also sends Anthropic the name of each place found — as Kakao lists it — with the kind of place, its city and district, and the language to translate into, and Anthropic sends back the name in your language and how the Korean name is pronounced. What is sent is only those public names of businesses and landmarks: a name may happen to match what you typed, but your search words are not sent as such, and nothing says who you are. When we draw a day's map, the positions of its pins — coordinates only, never a name or a note — go to NAVER Cloud, which draws the picture. Our server sends these requests, not your device, so none of these companies receives your account, your device details or your IP address. If you tap Directions on a plan or open a day's map, NAVER Map or Google Maps opens in your browser with those places' names and positions, the same as for a booking.

We don't share your interests with the places you book or with anyone else, and they don't appear on the screens the places use.

The phrasebook download record is seen only by millio's operators, on millio's admin screens. We don't share it with the places you book or with anyone else, and it doesn't appear on the screens the places use.

The “Build my trip” counts (section 1) are seen only by millio's operators, on millio's admin screens, as totals counted across everyone. We don't share them with the places you book or with anyone else, and they don't appear on the screens the places use. The counts say nothing about who made them. In the database, nothing you use — your browser, your account — can read or write them; only our server can.

Push services and LINE only carry your booking updates — and the departure reminders you turned on — to your device or your LINE account (section 4). We don't use them to advertise to you.

The departure reminder record is not shared with the places you book or with anyone else, and it doesn't appear on the screens the places use. The reminder emails and notifications are delivered by the service providers listed in section 4.

The record of your trip-news agreement and the send records (section 1) are not shared with the places you book or with anyone else, and they don't appear on the screens the places use. On millio's admin screens they appear only as counts — how many people agreed, and how many an email would reach. Trip-news emails are delivered by the email provider listed below, and never by push notification or LINE.

The records of the emails we send you (section 1), trip-news emails included, are seen only by millio's operators, on millio's admin screens: next to the booking they concern, where there is one, and in the recent-activity list, which shows the recipient's email address, the subject and the time. We don't share them with the places you book or with anyone else, and they don't appear on the screens the places use.

A partnership enquiry is read only by millio's operators. We don't share it with the places you book or with anyone else; the service providers that handle it for us are named in section 4 and in the list of providers below.

A place-recommendation request is seen only by you and millio's operators, and it doesn't appear on the screens the places use. The steps where AI helps with the research, and where the draft reply is translated, send text to Anthropic (section 4).

A request to book a place that isn't on millio is seen only by you and millio's operators; we don't give it to the place or to anyone else, and it doesn't appear on the screens the places use. A booking you then make through the link we send follows the rules for bookings in this section.

Contact details you share back from one of our digital business cards (section 1) are seen only by the card's owner, on a screen that opens only when the owner is signed in to millio.co. We don't give them to the places on millio or to anyone else, we don't translate them, and no email or Telegram notification is sent about them. If the owner chooses to save them, the details you sent, with a note of the date you sent them, go into the contacts on the owner's phone.

The record of your sign-in steps during a booking (section 1) is seen only by those of millio's operators who have access to the relevant admin screen, to help people whose sign-in goes wrong. We don't share it with the places you book or with anyone else, and it doesn't appear on the screens the places use. In the database, nothing you use — your browser, your account — can read or write it; only our server can.

For a booking request you send without an account, the place you booked (on the screens the places use) and millio's operators see whether its email address has been confirmed: until it is, the request is marked “email not confirmed”. The counts that keep out automated requests (section 1) are not shown on any screen, to the places or to millio's operators: only our server reads them.

The record of a card hold (section 1) is seen by millio's operators, on millio's admin screens, next to the booking it concerns, and — as its status, amount and time only — by you, on your booking page. We don't pass the record on to the places you book or to anyone else (what our service providers receive is listed below and in section 4), and it doesn't appear on the screens the places use. In the database, nothing you use — your browser, your account — can read or write it; only our server can.

The record of the trip plans you unlock (section 1) is seen by you, as the plans in your account, and by millio’s operators on millio’s admin screens — for example to answer a question about a charge. We don’t share it with the places you book or with anyone else, and it doesn’t appear on the screens the places use.

Partners whose membership code or link you used receive the totals described in section 2. If you agree on the payment screen, we also give that partner your payment as follows — recipient: the partner whose link or code the booking came through; purpose: to show the partner what its link or code brought in and to settle its share; items: the payment date, the partner link or code used, the amount paid and the partner's share; kept: until our partnership with that partner ends. You can say no: your booking and payment stay the same, and the payment then counts only in the monthly totals. The membership record and the partner payment records (section 1) are seen only by millio's operators, on millio's admin screens; a membership shows as a mark on your booking requests and support chats so that we can handle them first. The places you book don't see them.

The record of problems you ran into (section 1) is seen only by millio’s operators, on millio’s admin screens. We don’t share it with the places you book or with anyone else.

Messages you send to our LINE official account (section 1) are seen by millio's operators only — not by the places you book — and, once they are in your support chat, by you as well when you are signed in. If your LINE is linked to your millio account, our operators also see that account and its bookings in progress, and may note which booking the chat is about; nothing is copied into the booking's messages.

Messages you send to our WhatsApp number (section 1) are seen by millio's operators only — not by the places you book — and, once they are in your support chat, by you as well when you are signed in. Your WhatsApp number and the link to your account are seen only by millio's operators. If your number is linked to your millio account, our operators also see that account and its bookings in progress, and may note which booking the chat is about; nothing is copied into the booking's messages.

WhatsApp carries your booking updates and sign-in codes to your WhatsApp account (section 4). The link between your WhatsApp number and your account, the WhatsApp number or LINE user ID linked to a booking, and your update settings (section 1), are seen only by millio's operators. The places you book don't send these messages and never see your WhatsApp number.

Your support chat (section 1) is seen only by you, when signed in, and by millio's operators — not by the places you book. Our operators reply once, in our admin inbox: the reply is kept in your support chat and is also sent to where you last wrote to us from — LINE if that was LINE, WhatsApp if that was WhatsApp (as described above), and otherwise to the chat window on the website. If the reply can't reach you on LINE or WhatsApp, or you last wrote on the website, we also email it to your account's email address (through our email provider, Resend — section 4).

We also use service providers to run the service on our behalf: cloud hosting, database and file storage (Supabase, Vercel), email — booking and account emails, partnership enquiries sent to us and, if you agreed, trip-news and new-feature emails (Resend), machine translation, AI-assisted research for the optional place-recommendation service, the translation of partnership enquiries and the support chat assistant (Anthropic), online payment, card holds and refunds (PayPal), a Korean messaging provider that notifies the place by KakaoTalk or SMS (Solapi), usage statistics (PostHog), measuring which of our Google ads lead to booking requests (Google), the mailbox that millio's operators use to receive and answer emails (Google Workspace), notifications that tell millio's operators about new sign-ups, booking messages, support chats and payments and let them reply (Telegram), and, for your Trip page, place search (Kakao) and maps (NAVER Cloud). We do not sell your personal information.

4. Where your data is processed, and transfers outside Korea

millio's database and application servers run in the Seoul region of the Republic of Korea, and the place you book is in Korea. Your booking record is stored there. Our hosting providers are companies headquartered outside Korea, but the region your data is stored and processed in is Korea.

Some features do send data outside Korea. Korea's Personal Information Protection Act (Article 28-8) requires us to tell you exactly which, so here they are:

• Resend, Inc. — United States. Sent over an encrypted connection each time we email you: your email address, your name, and the booking details contained in the message (the place, the item you booked — service, menu item, or rental item —, date and time, number of people, amounts, and your booking management link). The notification we send to the place also contains your country, the contact method you entered (phone number or messenger ID), the names of any companions you added and, if you entered them, their email addresses and phone numbers. A departure reminder you turned on is the same kind of email: your account's email address, the region's name, how many days are left, and two links — to the public guide and to turn the reminders off — with no plan details and no booking number. A trip-news email you agreed to is the same kind of email: your account's email address and the email itself — a subject and text that are the same for everyone, plus the date you agreed and a link to unsubscribe that carries a signed code pointing to your account, with no name or email address in it. A partnership enquiry you send us travels to our own mailbox in the same way: what you wrote in the form — your name, reply email address, phone number if you gave one, company or brand, country or region and message, with its Korean translation if one was made — is in the body of the email, together with the language of the screen you sent it from, and the subject of that email contains your company or brand name. The notification emails our systems send to millio's operators (listed under Google Workspace, below) travel the same way. Purpose: delivering that email. Retained until the purpose is met or our contract with the provider ends.
• Anthropic PBC — United States. Sent over an encrypted connection at the moment the feature runs: messages you exchange with the place (for translation), a note you wrote on a booking after ticking the separate box next to it (to translate it into Korean for the person doing your treatment), what you type into the support chat (to generate the reply), what you type into the place search on your Trip page when you search in Japanese or Chinese and nothing is found (to find the place's Korean name — the words only, with nothing that says who you are), and the place's listing written in Korean — its description, address, and the names of the items it offers (services, menu items, or rental items), and, where the place assigns staff, their names and profiles (for translation). Purpose: producing the translation, the reply, or the place's Korean name. Retained until the purpose is met or our contract with the provider ends. For the optional place-recommendation service, the box you tick when you send the request is your consent to sending your request preferences to Anthropic for AI-assisted review and research. In that step, your request preferences, requested dates and relevant conversation text, and the note our team writes for the review, are sent over HTTPS. When the draft reply is translated — when the draft is made, and again each time our team edits and saves it — only the text of the draft is sent. Account identifiers are not sent; email addresses and phone numbers that our system recognises are removed from the text, but this is not guaranteed in every case. Purpose: preparing an internal research draft and translating the draft reply. The team approves the draft before it is shared with you. Anthropic's retention follows the purpose and contract described here. You may decline by not submitting this optional request and continue browsing or booking listed places. A partnership enquiry you send through the form on our About page is also sent when it is translated into Korean for our team: the company or brand name, country or region, your name and the message — not your email address or phone number. Nothing is sent if all of it is written in Korean — a name or brand in Latin letters counts as not Korean. Purpose: translating the enquiry. Retained until the purpose is met or our contract with the provider ends. For a request to book a place that isn't on millio, the messages you and our team exchange about it are sent when they are translated — into Korean for our team and into your language for you; your name, phone number and email address from the request are not sent. Purpose: translating those messages. Retained until the purpose is met or our contract with the provider ends.
• PayPal — United States. Sent when you pay, when a card hold is placed, charged or released, or when you are refunded: the amount, the currency, and an identifier for your booking. Your card or PayPal account details are entered with PayPal directly and do not pass through millio. Purpose: processing the payment, the card hold or the refund. Retained for as long as PayPal must keep payment records.
• PayPal — United States, for trip plans from “Build my trip”. Sent when you pay for a plan or are refunded: the amount, the currency and an identifier for the order — not your answers or your plan. Purpose: processing the payment or the refund. Retained for as long as PayPal must keep payment records.
• PostHog, Inc. — United States. Sent over an encrypted connection, through an address on millio's own domain, while you use millio.co: the pages you open (their addresses, with the key part of booking-management and review links removed) and the page you came from; the links and buttons you tap, with the words on them — except in the parts of the site we keep out of it, such as your trip plans and the Directions and calendar links; the steps you take in a booking — the place, item and staff member you choose, how many days ahead you book, the number of people, the amounts shown, whether the booking and the payment went through, and the booking's number — and, for reference photos and links, only the number and file size of the pictures and the site a link is on; the star rating you give in a review; the site, ad or campaign that brought you here and the first page you landed on, with a random identifier; and the technical details your browser sends — IP address, browser, operating system, device type, screen size and language. When a booking goes through, we also send your email address, which links what this browser did on millio to it. Our server sends a few booking events of its own — when the place confirms or declines your request, when a payment goes through, and when we ask you for a review: the booking's number, the place, how its status changed and how long the place took to answer, and, for a payment, the PayPal order number. If you use Confirm faster, our server also sends when your card hold is placed, when it is released (with a short reason, such as that you cancelled or the request expired) and when the charge at confirmation does not go through (with a short reason), each with the booking's number — never the amount, any card details or PayPal's numbers; a charge at confirmation that does go through is sent as a payment going through, without PayPal's numbers. When a signed-in member downloads the free phrasebook, our server also sends that a download happened and in which language — not who downloaded it. The screens the place uses to handle your booking send nothing about you — not the words on the screen, and not your booking's number. What you type into forms and messages, your pictures, your trip plans, your interests and your phrasebook download record are not sent. Purpose: understanding how millio is used so we can improve it. Retained until the purpose is met or our contract with the provider ends. It is not deleted automatically when you delete your millio account — ask us and we will delete what is held under your email address and your bookings' numbers.
• Google LLC — United States. When ad measurement is on for you (section 7), it is sent over an encrypted connection straight from your browser to Google — not through our servers — by Google's tag on millio.co: the device and network information any web request carries, including your IP address and browser details; the ad click identifier in the page address, if you came from a Google ad; and, once a booking request goes through, a scrambled reference to that booking, which cannot be used to open it. We don't tell Google which page you are on: the address we give the tag is our home page's (plus the click identifier, if there is one), the page title is just “millio” and the page you came from is left blank. And we never send Google your name, email address, phone number, the services you picked or your booking-management link. Until you choose, in the regions where we ask first (section 7), the tag still loads from Google, so Google receives your IP address and browser details with that request; it runs with everything switched off and can send only limited signals that use no cookies. Purpose: measuring which of our Google ads lead to booking requests — not showing you personalised ads. Retained as Google's own policy provides.
• Google Workspace (Google LLC) — United States, where Google LLC is based; Google may keep the mailbox in data centres in several countries, so we cannot name a single country. The mailbox of millio's operators, at the support address and the Data Protection Officer's address listed in section 8, is hosted by Google Workspace, so Google receives and stores the emails that reach it. Delivered each time an email reaches that mailbox: an email you write to us arrives from your own email provider, normally over an encrypted connection where that provider supports one, and the notification emails our systems send to it travel through Resend (above). What reaches it: a partnership enquiry you send us (section 1); any email you write to us; and the notification emails our systems send to millio's operators — for example the message you write in the support chat (the first one, and a new one when you write again after our team has answered); a booking that millio places for you where it books on your behalf (your name, any companions' names and, if entered, their email addresses and phone numbers, your country, the contact method you entered and the booking details — for a booking that asks about your nails, also your answer and the number of reference photos and links — and the notices when you change its time or its payment deadline passes); an alert that a place has not answered your request within 24 hours (your name and the place); a new review you write (your name or email address, the rating and an excerpt of the text); and, when the text message to an operator's phone fails or text messaging is not set up, the first 60 characters of the first message you send in a booking chat, with your name and the place, and an alert that an email to you could not be delivered (your phone number, if your booking has one, the booking number and status, and the place). The email that tells our operators a place-recommendation request needs review carries only a link to it, not what you wrote. Purpose: letting millio's operators read and answer. Kept in the mailbox only for as long as our operators need them to answer or follow up (for a partnership enquiry, section 5); what Google itself keeps is governed by Google's own policy. You decide whether to write to us, send an enquiry, use the support chat or write a review; a booking millio places on your behalf is handled through these notices to our operators. For anything already in the mailbox you can ask us to delete it (section 6).
• Telegram Messenger Inc. — outside Korea. Telegram keeps chats in data centres in several countries and does not say which one holds a given chat, so we cannot name a single country. Our server sends it, over an encrypted connection, the notifications millio's operators read in a private Telegram group: when you create an account — your name or user name, your email address, your phone number if you gave one, how you signed up, the country and city estimated from your connection, the site, ad or search words that brought you here, the first page you visited and the page where you signed up, and the time; every message you and the place exchange about a booking — the original, its translation and any pictures attached — with your name, the place's name, the booking's date and time and part of its number; everything written in the support chat — your messages and pictures and the automatic replies — with the language of the chat; when a payment goes through, the place's name, the amounts and the booking's number; when you send a request to book a place that isn't on millio, the place's name or link as you wrote it, your preferred date and times and the number of people — not your name, phone number or email address; and, when you leave the card-hold step before sending your booking request, the place's name, the service, the number of people, your preferred dates and times, the language you use, your country, when and how many times you tried, whether you opened the PayPal window and whether you closed it or left it for 20 minutes, and a link that opens your account on our admin screen — not your name, phone number or email address. When an operator answers from that group, the answer reaches you through Telegram. Purpose: letting millio's operators know straight away and answer you. Retained in that group until we delete it. It is not deleted automatically when you delete your millio account — ask us and we will delete it.
• Google (Firebase Cloud Messaging), Apple, Mozilla or Microsoft, whichever push service your browser uses — United States. Only if you turned on web push. Sent over an encrypted connection each time we send you a notification: the notification, encrypted so that only your device can read it — the push service cannot — and the push address of your device. Which of them it is depends on your browser, not on us. For a departure reminder, what is encrypted is a title with the region and how many days are left, a fixed one-line guide and a link to the public guide. Purpose: delivering the notification to your device. Retained only until the notification is delivered, and no longer than it stays valid.
• LY Corporation (LINE) — Japan. Only if you signed in with LINE, or connected LINE from your booking page, and added our official account as a friend. Sent over an encrypted connection each time we send you a LINE message: the message — a headline with the place's name and, depending on the update, the date and time, one line on what to do next and a link to your booking — addressed to your LINE user ID, which LINE already holds. For a departure reminder, the message is a title with the region and how many days are left, a fixed one-line guide and a link to the public guide, in place of the booking management link. Purpose: delivering the message by LINE. Retained as LINE's own policy provides.
• LY Corporation (LINE) — Japan, for chatting on LINE. Only if you write to our official account. Sent over an encrypted connection each time millio's operators reply to you while LINE is where you last wrote to us from: the reply — the text in your language and, if a photo was attached, a line saying so — addressed to your LINE user ID. Purpose: delivering the chat on LINE. Retained as LINE's own policy provides. You can stop it by blocking or deleting our official account.
• Meta Platforms, Inc. (WhatsApp) — United States, for chatting on WhatsApp. Only if you write to our WhatsApp number; what you send there reaches us through WhatsApp. Sent over an encrypted connection each time millio's operators reply to you while WhatsApp is where you last wrote to us from, and when we send you a short automatic reply: the reply, addressed to your WhatsApp number. Within 24 hours of your last WhatsApp message, the reply is the text in your language and, if a photo was attached, a line saying so; after that, it is first only a notice that millio support has replied, with a button to see the reply, and the reply itself follows when you write to us or tap that button. Purpose: delivering the chat on WhatsApp. Retained as WhatsApp's own policy provides. You can stop it by blocking our WhatsApp number.
• Meta Platforms, Inc. (WhatsApp) — United States, for booking updates and signing in with WhatsApp. Only if your WhatsApp number is linked to your account or to a booking, you wrote it in a booking form (payment and proposed-time updates only — section 1), or you sign in with WhatsApp. Sent over an encrypted connection, addressed to your WhatsApp number, each time we send you a booking update or a sign-in code: within 24 hours of your last WhatsApp message to us, the update — a headline with the place's name and, depending on the update, the date and time, one line on what to do next and a link to your booking; after that, the place's name and, depending on the update, the date and time of the booking or a deadline, with a link to your booking; for signing in, the one-time code. Purpose: delivering booking updates and sign-in codes by WhatsApp. Retained as WhatsApp's own policy provides. You can stop booking updates with the switch in your account, or by sending STOP.
• Anthropic PBC — United States, for translating your support chat. Sent over an encrypted connection each time a message is added to your support chat, whichever way it came: your message, to translate it into Korean for our operators where needed, and our operators' reply, to translate it into your language — each with recent messages of the same chat for context. Not your account, your LINE user ID or your WhatsApp number. Purpose: translating the chat. Retained until the purpose is met or our contract with the provider ends.

Of what you add to a booking, a note you write is the one thing that does leave Korea: it goes to Anthropic to be translated into Korean, and only if you ticked the box next to it. It is never emailed, so it never reaches Resend.

Reference photos go to none of them. They are not attached to email (they never reach Resend), they are not translated (they never reach Anthropic), and they have nothing to do with payment (they never reach PayPal). They stay in private storage in the Seoul region of Korea.

Trip plans don't leave Korea either. They are stored in the Seoul region and go to none of the companies above. The place search and the map on your Trip page are run by Kakao and NAVER Cloud, both in Korea. Of what you add on your Trip page, the one thing that can leave Korea is a place search typed in Japanese or Chinese that finds nothing — the words alone, as described above. There is one more thing, though it is not something you add: the public names of the places a place search finds, with the kind of place, its city and district, and the language to translate into, go to Anthropic while you search — before you pick a result (section 3); a saved plan itself is never sent. Like the other Anthropic transfers above, they are kept until the purpose is met or our contract with the provider ends. They are names of businesses and landmarks as Kakao lists them, not information that says who you are, so they are described here rather than in the list above. You can avoid them by leaving the Place field empty (there is no separate switch), and your bookings and the rest of your Trip page do not depend on it.

Your interests don't leave Korea either. They are stored in the Seoul region and go to none of the companies above.

The phrasebook download record doesn't leave Korea either: it is stored in the Seoul region and goes to none of the companies above. (PostHog, described above, is told separately by our server that a download happened and in which language, with nothing that says who downloaded it — and it sees the tap on the download button like any other button.)

The “Build my trip” counts don't leave Korea either: they are stored in the Seoul region by our hosting and database providers (Supabase and Vercel, above) and go to none of the other companies above. Our usage-statistics provider (PostHog, above) is not sent these counts.

Companions' details leave Korea only inside the emails described under Resend and Google Workspace above. They are stored in the Seoul region; what goes abroad is the companions' names and any email addresses and phone numbers you entered, inside the booking email we send the place. That email passes through Resend and, where millio books on your behalf, reaches our operators' mailbox (Google Workspace). They are not sent to PostHog, Anthropic, Telegram or Google ad measurement. A companion's email address and phone number are not needed for a booking: if you leave them out, they are not sent abroad (the companions' names still go in the booking email to the place).

The record of your sign-in steps during a booking doesn't leave Korea either: it is stored in the Seoul region by our hosting and database providers (Supabase and Vercel, above) and goes to none of the other companies above. Our usage-statistics provider (PostHog, above) is not sent this record.

Booking requests you send without an account add no new company. The link to manage your booking, with its signed code, and the one-time sign-in code are emailed through Resend (above), like our other emails. The time your email address was confirmed and the counts that keep out automated requests (section 1) don't leave Korea: they are stored in the Seoul region by our hosting and database providers (Supabase and Vercel, above) and go to none of the other companies above.

You may refuse these transfers. Resend (for the booking emails we send), Anthropic and PayPal are how we email your confirmation, take payment and translate what the place writes to you, so refusing them means we cannot complete a booking for you. To refuse, or to ask anything about a transfer, contact us at the address below before you book. Place-search words are different: typing a place in English or Korean keeps the words in Korea, and your bookings are not affected. (The public names of the places a search finds are a separate matter: they are sent as section 3 describes, and leaving the Place field empty avoids that.) Usage statistics (PostHog) are not needed for a booking either. Turn them off with the button in section 7, or turn on Global Privacy Control or Do Not Track in your browser, and from then on this browser sends PostHog nothing; your bookings are not affected. That doesn't reach the booking events our server sends, so ask us at the address below and we will delete those along with what is held under your email address. Operator alerts (Telegram) are not needed for a booking either. We can't leave one person out of them, so if you don't want your details there, tell us at the address below and we will delete the alerts about you from the group; your bookings are not affected. Push notifications and LINE messages are not needed for a booking either: you turn them off yourself, as section 6 describes. Departure reminders are not needed for a booking either: they are sent only if you tick “Remind me before I go”, and you can turn them off at any time, as section 6 describes. Trip-news emails are not needed for a booking either: they are sent only if you agree, and you can withdraw at any time, as section 6 describes. Ad measurement (Google) is not needed for a booking either. Turn it off with “Ad measurement” at the bottom of millio.co (section 7; choose “No thanks”), or turn on Global Privacy Control or Do Not Track in your browser: pages you open after that load no Google ad tag in this browser, and your bookings are not affected. A partnership enquiry is not needed for a booking either: you decide whether to send one, and if you write it entirely in Korean, nothing is sent to Anthropic (a name or brand in Latin letters counts as not Korean). The mailbox of millio's operators (Google Workspace) is reached only when you email us, send a partnership enquiry, write in the support chat or write a review yourself, or when a booking millio places on your behalf creates a notice to our operators; for anything already there, ask us to delete it, as section 6 describes.

5. Retention

We keep your booking information while your account is active and for as long as needed to provide the service and meet legal, tax, and dispute-resolution requirements, after which it is deleted or anonymized.

No-show records are part of your booking records and are kept and deleted with them (above). The number shown to places is worked out from those records each time and is not stored separately.

Links you paste, and any note you write (with its Korean translation), are kept with the booking itself and go when it does — there is no separate schedule for them, because there is no file to delete. If you delete your account, we remove them from your past bookings straight away.

A companion's email address and phone number (section 1) are kept only until your booking is over, and are then deleted from the booking record we keep. A booking is over when it is completed, marked as a no-show, cancelled, declined by the place or expired — and, even if nobody has marked it, 3 days after your appointment time. A clean-up that runs every hour does the deleting, so it can happen a little after the booking ends. If you delete your account, we remove them from your bookings straight away, even if a booking is not over. These deletions apply to the booking record we keep. They do not reach the booking email we sent the place when you asked to book, which is already with the place (section 3), or the copies held by our email provider (Resend) and, where millio books on your behalf, in our operators' mailbox; those are handled as section 4 describes. A companion's name is different: neither this clean-up nor deleting your account removes it, and it stays for as long as the rest of the booking information does.

Reference photos are deleted on a fixed schedule, automatically — you do not have to ask:

• 90 days after the day you visited
• If the place never confirmed it and your booking stayed a request: 90 days after the date you had asked for
• If you added pictures but never sent the request: 24 hours after you uploaded them
• If you delete your account: straight away

Review photos stay while the review is up. If you ask us to take a review down, the pictures go with it. If you delete your account, we delete your review photos and the name and email attached to your reviews; the text stays, with nothing left to say who wrote it, because it is about the place's work rather than about you.

Trip plans are deleted automatically 30 days after their last day (Korea time) — you do not have to ask. You can delete a plan yourself at any time, and it is gone straight away. If you delete your account, all your trip plans go with it, straight away. An invitation record is deleted straight away when you cancel the invitation or remove the person, when the person leaves, or when either of you deletes an account. An invitation nobody has joined stops working 14 days after you made it, and its record is deleted when you make a new invitation or delete it yourself (otherwise when you delete your account). The plans a person you invited sees are your plans: when a plan is deleted — including after the 30 days above — it disappears for them too, and we keep no separate copy for them.

Your interests are kept until you change or clear them in your account — clearing them deletes them straight away — or until you delete your account, when they go with it.

The phrasebook download record is kept for up to 24 months from the download: after that we erase its link to your account and the device type, country and city, and keep only the edition and the time, as a count. If you delete your account sooner, the record goes with it, straight away.

The departure reminder record (section 1) is deleted straight away when you turn the reminders off — from the link at the bottom of a reminder email, or on your Trip page — when you delete that trip's plans (all of them), and when you delete your account. Otherwise it is deleted 30 days after the trip's start date (Korea time). A reminder that has already gone out can't be recalled, but nothing more is sent once the record is gone.

The records of the emails we send you (section 1) are kept for 1 year from the day each record was made — the day we sent the email or, for what our email provider tells us about it, the day we received that report — and are then deleted automatically; you do not have to ask. We keep them that long so that we can answer a question about an email and settle a dispute. If you delete your account, they are not deleted straight away: they stay until that year is over. The list of addresses we no longer send to is kept for as long as the address is still in use, so that we do not send to it again: we delete an address from the list once 1 year has passed since we were last told that an email to it bounced or was marked as spam, unless one of our accounts still uses that address or someone has made a booking with it in the last year. An address that we have taken off the list because it works again is treated in the same way.

A partnership enquiry (section 1): the copy of the enquiry email stored in our database — kept so that a retry never sends a second email or a different translation — is deleted automatically 30 days after it was made; you do not have to ask. The email itself, which reaches our own mailbox (hosted by Google Workspace), is kept there only for as long as we need it to answer you and follow up on your enquiry. The record of sending that email — its subject, which contains your company or brand name, and the time — is kept for 1 year like our other email records. If you want the stored copy or the email in our mailbox deleted sooner, ask us (section 6); the record of sending is kept for that 1 year.

A personal-recommendation request (section 1): the personal content of a request — your name and email address, what you wrote in it (the city, number of people, budget per person, must-haves, what you asked for, any reference links or extra conditions, and the site or ad that brought you here), your preferred dates, the messages and recommendations passed between you and our team about it (with their translations), the AI research drafts with the evidence behind them and the note our team wrote for the review — is deleted in two cases, and you do not have to ask. If you delete your account, we delete it straight away, for all your requests (if the deletion ever fails, the 365-day rule below still applies). Otherwise it is deleted automatically 365 days after the request ended — counted from the day it became “Request completed”, “We’re unable to take this request” or “Request closed” on your screen; notes our team adds afterwards do not extend it — or, if it never ended, 365 days after its last activity (when you made or changed it, any message, any reply, note or assignment by our team, a payment, or a step of the AI research). What stays is a basic record — its reference number, status, dates (including when you accepted the fee for custom picks), the language you used, the version of the fee terms, which of millio's operators acted, the time and type of each message (without its content) and any booking we proposed (place, menu, time and amount) — so that lists and counts still add up; if your account still exists, the record stays linked to it, and a booking made from the request follows the rules for bookings above. The payment record of the fee for custom picks — the amount, currency, PayPal order and capture numbers, the dates and the status — is kept for 5 years from the payment date, because Korea's Act on the Consumer Protection in Electronic Commerce requires payment records to be kept that long, and is then deleted; it no longer carries your name or email address. A fee record with no money movement (unpaid or cancelled) is deleted when the request is deleted. These requests have no uploaded files — reference links are only text. The records of the emails we sent you about the request (your address and the subject) are kept for 1 year, as described above. Deleting on our side does not change what a provider has already received: what was sent to Anthropic or PayPal (section 4) stays under the retention described there.

A request to book a place that isn't on millio (section 1) is deleted on the same schedule as a personal-recommendation request, and you do not have to ask: straight away if you delete your account, and otherwise 365 days after the request ended or after its last activity. We delete your name, phone number and email address, what you wrote in it (the place, what you'd like, the number of people and the site or ad that brought you here), your preferred date and times, and the messages passed between you and our team (with their translations). What stays is its reference number, status, dates and language, which of millio's operators acted, the time and type of each message (without its content) and the booking link we sent (the place, menu item, times and number of people); a booking you make through the link follows the rules for bookings above.

Contact details you share back from one of our digital business cards (section 1) are deleted automatically 1 year after we receive them — a clean-up runs every hour, and you do not have to ask. If you want them deleted sooner, write to us at the address in section 8 and we will delete them. The copy the card's owner saved to their phone is not part of this automatic deletion; when you ask, we delete that copy too. The record of each QR code (which card it belongs to, and when it was made and stops working) is deleted a day after it is made, and from then on your contact details no longer show which QR code they came through. The counts by IP address that keep out repeated sending are deleted automatically about a day after they start.

The record of your trip-news agreement and the send records (section 1) are kept for as long as your account exists, and are deleted straight away if you delete your account. If you withdraw, we keep the record of your agreement, marked as withdrawn, so that we stop emailing you and can show that you withdrew; if you agree again later, the new agreement replaces the earlier record. A “Not now” record is kept in the same way. Two years after you agree the emails stop, but the record stays until you delete your account or agree again.

Push subscriptions and the LINE details we keep (section 1) are deleted, or stop being used, in these cases, without you having to ask:

• Straight away when you turn web push off
• When you block or delete our LINE official account: we stop sending you LINE messages straight away and mark you as no longer a friend (your LINE user ID stays until you delete your account)
• Straight away when you delete your account — your push subscriptions go with it, and so does your LINE user ID
• Straight away when the push service tells us a subscription is no longer valid
• If sending to a device keeps failing: 90 days after the first failure
• A subscription with no account behind it — turned on without signing in: 90 days after it was last used

The statistics made from trip plans and interests are counted across everyone and contain nothing that identifies anyone, so we may keep those figures after the plans or interests they were counted from have been deleted.

The “Build my trip” counts contain nothing that identifies anyone, so we don't set a time limit on them and don't delete them. Nothing in them can be tied to you — no account, device or IP address — so they are not part of an access or deletion request, and deleting your account does not change them.

The record of your sign-in steps during a booking (section 1) is deleted automatically 180 days after it was made — you do not have to ask. If you delete your account, the lines connected to your account and the lines that carry your account's email address are deleted with it. A line connected to neither — for example, from a visit in which you never signed in — cannot be found that way, and it is deleted when the 180 days are up.

For a booking request you send without an account, the time your email address was confirmed (section 1) is kept with the booking and goes when the booking does. The counts that keep out automated requests are deleted automatically about a day after they start (a clean-up runs every hour); you do not have to ask. An account created when you sign in to pay is kept and deleted like any other account.

The record of a card hold (section 1) is a payment record. Korea's Act on the Consumer Protection in Electronic Commerce requires payment records to be kept for 5 years, so we keep it for 5 years from the day the card hold was placed. A card hold that was released without any charge is kept in the same way, because that record is what shows you were not charged. The record contains no name, email address or phone number — only the booking's number and the other items listed in section 1, such as the amounts, the dates, the status and PayPal's numbers — so deleting your account does not delete it. We will put in place a procedure for deleting records older than 5 years before that time comes, and describe it here.

The record of the trip plans you unlock (section 1) is kept for as long as your account exists, so that your plans stay available to you, and is deleted when you delete your account. The payment details of a paid plan — the amount, currency, PayPal order and payment numbers, dates and status — are a payment record: Korea’s Act on the Consumer Protection in Electronic Commerce requires payment records to be kept for 5 years, so we keep them for 5 years from the payment date, without your name or email address, and then delete them.

Your membership record (section 1) is kept for as long as your account exists. Partner payment records — the payment records described in section 1, and the partner link noted against a booking — are kept for 5 years from the payment, as the record of what we paid our partners. If you delete your account, we remove the link between these records and your account straight away; what is left — the partner, the dates, the amounts, the screen language, the kind of place and the country — no longer points to you, and is kept for up to 5 years.

The record of problems you ran into (section 1) is deleted 90 days after it was made, or when you delete your account.

Messages you send to our LINE official account (section 1) are kept like millio's other enquiries, in your support chat or in the separate enquiry. The LINE user ID kept with a chat or enquiry is deleted 90 days after the last message in it, or straight away if you delete the millio account your LINE is linked to.

Messages you send to our WhatsApp number (section 1) are kept like millio's other enquiries, in your support chat or in the separate enquiry. The WhatsApp number kept with a chat or enquiry is deleted 90 days after the last message in it, or straight away if you delete the millio account it is linked to. The link between your millio account and your WhatsApp number is kept until you delete your account. Reference codes are deleted within a day after they expire, and the message numbers we note to avoid handling a message twice — with no phone number or content — are deleted after 7 days.

The link between your millio account and your WhatsApp number, and your WhatsApp update setting (section 1), are kept until you delete your account, and go with it straight away. The record of a sign-in code we send (the scrambled forms of your number and the code, the number of tries and its times) is deleted automatically 24 hours after the code was sent. The counts that keep out automated sign-in requests are deleted automatically about a day after they start, and the one-way codes we keep to avoid sending the same update twice are deleted after 7 days.

The WhatsApp number or LINE user ID linked to a booking (section 1) is deleted 7 days after the booked time, when you turn it off on the booking page, or when you send STOP. Your “Not now” choice for a booking, and a note that you turned off its messenger updates or sent STOP, are kept until 7 days after the booked time so that we can keep honouring them; one-time codes are deleted a day after they expire. If the booking was linked to your account, the account's link is kept as described above.

Your support chat (section 1) is kept like millio's other enquiries; linking it to your account does not change how long it is kept. If you delete your account, the chat is no longer linked to it, and any LINE user ID or WhatsApp number kept with it is deleted straight away.

A record we delete can remain for up to 7 days in our daily database backups, and is gone from them after that.

6. Your rights

You may access, correct, or delete your information, and you can cancel eligible bookings from “My bookings”. To make a request, contact us using the details below.

If you were added to someone else's booking as a companion, the person who booked entered your details, not you. You can ask what we hold about you, and ask us to correct it, delete it or stop using it. Write to the address below and tell us which booking it was, so that we can find it; we check that you are that booking's companion before we act, and we tell you what we have done. We will also tell you where the details came from (the person who booked) and what we use them for (section 2). If you are the one booking, please add details only for people who have agreed to share them.

You can ask to see, and to have deleted, the record of your sign-in steps during a booking (section 1). Write to the address below and tell us which account or email address you tried to sign in with; we check that you are the person who uses that account or email address before we act, and we tell you what we have done. We find these lines by account and by email address, so a line that carries neither cannot be found. There is no separate switch to turn this record off (see section 7).

You can stop booking updates by push notification and LINE at any time. For web push, on your booking page tap “Change” and then “Turn off browser alerts” (or “Turn off” on the alerts card), or switch notifications off for millio in your browser's notification settings. For LINE, switch off “Updates on LINE” in your account, or block or delete our official account. Booking and payment work exactly the same, and updates keep arriving by email.

You can stop booking updates on WhatsApp at any time with the “Updates on WhatsApp” switch in your account. If you write to us on WhatsApp, we still answer you there. Booking and payment work exactly the same, and updates keep arriving by email.

You can stop a booking's updates on WhatsApp or LINE at any time: on the booking page, tap “Change” and then “Turn off messenger updates” — that booking's updates then go by email only, and if you are signed in, booking updates on WhatsApp and LINE are turned off for your account too (you can turn them back on in your account). You can also send STOP in WhatsApp or LINE to stop updates to that number or LINE account for all your bookings, including updates to a WhatsApp number you wrote in a booking form. Emails keep coming.

You can turn off departure reminders at any time, without signing in: tap “Turn off these reminders” at the bottom of any reminder email. If you are signed in, you can also use the switch on your Trip page. Reminders that arrive by notification or LINE stop the way described above (turn notifications off, block the official account). If you never tick “Remind me before I go”, no reminders are sent. Booking and payment work exactly the same either way.

You can stop trip-news and new-feature emails at any time, without signing in: tap “Unsubscribe” at the bottom of any of these emails (it opens a page where one more tap confirms), or tap the unsubscribe button your email app shows next to the email. If you are signed in, you can also turn the switch off in your account. Marking one of these emails as spam also counts as unsubscribing — but it also tells us to stop emailing that address altogether, so your booking emails would stop too; if you want those to keep coming, use one of the other ways. Withdrawing takes effect at once, and we check again just before every send. We don't ask why. Whether you agree, withdraw or never answer, your account, bookings, payments and booking emails work exactly the same. If you haven't agreed, nothing is sent: we ask on a card until you answer, and “Not now” means we don't ask on the card again — you can always turn it on in your account. Two years after you agree, the emails stop unless you agree again.

7. Cookies

We use cookies and similar storage in your browser to keep you signed in, remember your language, keep your choices while you sign in partway through a booking, keep your support chat on this device so you can pick it up again, and keep a trip you start before signing in on your device. We also use them for our own statistics: to remember the link or ad that first brought you to millio and the most recent one that did (for up to 2 years), which version of a page we showed you (for up to 90 days), and an identifier that PostHog uses to recognise this browser when you come back — a random one at first, and your email address once a booking goes through (kept in a cookie for up to 1 year after your last visit, and in this browser's storage until you clear it). We don't use them to advertise to you or to sell your data (measuring our own Google ads is described in the next paragraph). You can block or delete them in your browser settings. millio still works, but you will need to sign in again, your support chat on this device and a trip you started before signing in will be lost, and our statistics can no longer link your visits together — but blocking them doesn't stop usage statistics being sent. To stop that, use the button below or turn on Global Privacy Control or Do Not Track in your browser: this browser then sends PostHog nothing, and the identifier PostHog kept on it is deleted.

Ad measurement (Google). On millio.co we use Google's tag to measure which of our Google ads lead to booking requests. It is not used to show you personalised ads. Whether it is on depends on the country we estimate from your connection. In the European Economic Area, the United Kingdom and Switzerland, and where we can't tell your country, we ask first, in a notice on the page. Until you choose, the tag still loads from Google, so Google receives your IP address and browser details with that request; it runs with everything switched off and can send only limited signals that use no cookies. Ad cookies and booking measurement start only if you choose “Allow”. Everywhere else it is on by default. You can turn it off, or change your choice, at any time with “Ad measurement” at the bottom of millio.co — in the footer on a computer, and on a phone below the menu in My page, or at the bottom of the Sign in screen before you sign in (choose “No thanks” to turn it off). If you turn it off there, or turn on Global Privacy Control or Do Not Track in your browser, this browser loads no Google ad tag at all on the pages you open afterwards. While it is on, the tag sets cookies on millio.co whose names start with “_millio_ads”, for up to 90 days; choosing “No thanks” deletes them. When a booking request is measured, this browser tab also keeps a short note in its session storage, under a name starting “millio_ads_lead_”, so the same booking is not reported twice; it disappears when the tab is closed. Your choice is kept in this browser's storage under the name “millio_ads_measurement_v1”; we don't receive it. An “Allow” expires after 90 days, and then the rule for the country we estimate applies again. A refusal is kept for 90 days where we ask first (then we ask again), and where ad measurement is on by default it is kept until you change it or clear your browser's storage. Google's own domains may also set cookies when the tag contacts them; those fall under Google's privacy policy. Section 4 says what is sent to Google. Separately, we keep a daily total of visits that arrive from a Google ad, by campaign, ad content, keyword and landing page. The total stores no IP address, cookie, device or account identifier and puts nothing in your browser; the visitor's IP address is used only to limit abuse. A visit is counted whatever you choose under “Ad measurement”, and even if Global Privacy Control or Do Not Track is on.

Partner links. When you open a link or QR code from a millio partner (an address starting “millio.co/go/”), the page you land on carries the link's short name in its address for a moment, and we remove it straight away. Only if ad measurement is on for you (above), this browser then keeps a cookie named “millio_partner” saying which partner and which link it was and when you opened it — nothing about you or your device — for that partner's counting period, usually 30 days. Opening another partner link replaces it. Choosing “No thanks” under “Ad measurement”, or turning on Global Privacy Control or Do Not Track, deletes it. If you book while it is there, we note that partner link against the booking (section 1). Whatever you choose, we count how many times each partner link is opened each day, without recording who opened it. To count how many different people opened it, we keep, for that day only, a one-way value made from the date, the link, your IP address and your browser details; it cannot be turned back into those details, is seen only by millio's operators, and is deleted the next day.

“Build my trip” counts. Counting how “Build my trip” is used puts no cookie and nothing else in your browser: our server adds the count while it handles your request. There is no separate switch for it. Your use of “Build my trip” is counted even if you have turned usage statistics off with the button above, or turned on Global Privacy Control or Do Not Track in your browser, because the counts are totals that cannot be linked to you.

Sign-in steps during a booking. Recording these steps does not put anything in your browser: our server reads the random visit ID from the cookie described above, the one that remembers the link or ad that brought you to millio, and writes it into the record. There is one small exception, and it is not part of the record. If a sign-in fails and you are sent back to the booking screen, our server sets one cookie, “millio_login_error”, for 2 minutes, only so that the booking screen can show a short “please try again” line. Its value is just “1” — it holds nothing about you — and the booking screen deletes it as soon as it has read it. The record itself is made by our server (for an email sign-in, your browser reports the result to our server, which reads your account from your sign-in session), so it is made even if you have turned usage statistics off with the button above, or turned on Global Privacy Control or Do Not Track in your browser, and there is no separate switch for it.

Booking requests without an account. When you open the link from our email, the signed code in it is taken out of the page address and kept in that browser tab's session storage, under a name starting “millio_guest_key:”, so that your booking can still be linked to your account after you sign in with Google. It holds no email address, and it is gone when you close the tab. A link from our payment email, or a short link we send you on WhatsApp or LINE, is kept the same way under a name starting “millio_guest_pay:”, so that you can still pay from that tab after the page reloads; it too holds no email address and is gone when you close the tab.

Suggestions after a booking or at the end of a list. millio may show a short suggestion once after you send a booking request, after your booking is confirmed, at the end of a trip plan or at the end of the places list. To show it only at those moments and to put first the places you are likely to want, this browser keeps in its local storage: when a suggestion was shown or closed (names starting “millio_nsp”), the kinds of places you picked in the “What interests you?” question and when (“millio_nsp_interests”), and the kinds of places you recently opened, up to 8 (“millio_viewed_cats”). They hold no identifier and are not sent to us or anyone else; clearing your browser's storage removes them. If you are signed in, your answer to the question is also saved to your account (section 1). Separately, our server counts how many times these suggestions are shown, tapped and closed each day, by type of device (phone, tablet or computer) — totals that store no IP address, cookie or account.

Continue where you left off. To show a “Continue” card on the home page, this browser keeps in its local storage up to 3 recent activities for 14 days (names starting “millio_resume”): the type of place, area and date of your last search; the last place you opened and the service and date you picked there; your answers for the last trip plan you opened but hadn't unlocked; and when you closed the card. They hold nothing you typed (such as your name or contact details) and no identifier, and are not sent to us or anyone else; clearing your browser's storage removes them. Our server only counts how many times the card is shown, tapped and closed, in the same way as the suggestions above.

How you arrived. When you arrive at millio, this browser tab keeps in its session storage, under the name “millio_entry”, how you arrived (for example a Google ad or a search) and the first page you opened, so that our counts of visits and booking steps can be split by how people arrived. It holds no identifier, and it is gone when you close the tab.

8. Contact

We post a notice inside the service at least 7 days before an amendment to this policy takes effect.

Notice of amendment — leaving the card-hold step. Posted 2026-10-31; effective 2026-10-31 — the same day. If you leave the card-hold step before sending your booking request, our operators are now told on Telegram: the place, the service, the number of people, your preferred dates and times, your language and country, when and how many times you tried, whether you opened the PayPal window and whether you closed it or left it for 20 minutes, and a link to your account on our admin screen — not your name, phone number or email address (section 4). This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it collects nothing new, carries no name or contact details, and uses no new service provider.

Notice of amendment — digital business cards. Posted 2026-10-31; effective 2026-10-31 — the same day. When you scan the QR code of one of our digital business cards, you can now share your own contact details back with the card's owner if you choose to: your name, a phone number or an email address, and your company if you like (section 1). They are used so the owner can save them and get in touch with you (section 2), they are seen only by the card's owner and are not given to anyone else (section 3), and they are deleted automatically 1 year after we receive them, or sooner if you ask (section 5). Saving the owner's card to your phone does not ask for your name or contact details. There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it is a new, optional feature that only you can start — saving the card works without it — it collects only your name, contact details and company, it uses no new service provider, and before you send anything the screen tells you why we keep them, what we keep, for how long, and that sending is optional.

Notice of amendment — booking a place that isn't on millio. Posted 2026-10-28; effective 2026-10-28 — the same day. You can now ask us, free of charge, to book a place that isn't on millio: signed in, you give your name, phone number, the place, what you'd like, a date with up to 3 times and the number of people, and our team sends you a booking link (sections 1 and 2). The request is seen only by you and millio's operators and is not given to the place (section 3). Its messages are translated by Anthropic, and our operators are told of a new request on Telegram without your name, phone number or email address (section 4). It is deleted on the same schedule as a personal-recommendation request (section 5). Section 5 now also calls the fee for the place-recommendation service by the name the request screen uses (“custom picks”); the amount and the rules do not change. There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it is a new, optional request that only you can start, it collects only what we need to book the place for you, and it uses no new service provider.

Notice of amendment — operator statistics. Posted 2026-10-21; effective 2026-10-21 — the same day. Section 2 now says that the statistics on Trip, interests and “Build my trip” are shown only on millio's operator screens, are seen only by millio's operators, and are never published or given to any place, partner or other third party — and that, instead of hiding figures under 3, they may show small counts, down to a single person (a single time for “Build my trip”). They still include no names, email addresses or contact details, and we collect nothing new. It doesn't get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it, because it only changes what millio's own operators can see and collects no new information.

Notice of amendment — booking requests need an account. Posted 2026-10-21; effective 2026-10-21 — the same day. From the effective date you need to be signed in to a millio account to send a booking request. Section 1 now says so, and what it describes for booking requests sent without an account applies only to requests sent before that date. We collect nothing new. It doesn't get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it, because it only stops one way of sending requests and collects no new information.

Notice of amendment — partner memberships and partner links. Posted 2026-10-22; effective 2026-11-01. From 2026-11-01, you can start a 30-day membership with a code or link from a millio partner (for example the company you rent your home in Korea from), and millio partners can share links and QR codes to millio. Section 1 now lists what we record for a membership (including any booking-fee discount it gives) and for a booking or payment that comes through a partner, section 2 why (the membership's benefits, and paying the partner its agreed share of millio's booking fee), section 3 that partners receive totals, and a payment's date and amount only if you agree before paying, section 5 how long we keep these records (5 years for the payment records), and section 7 the partner link cookie, which is kept only if ad measurement is on for you, and how we count different people opening a partner link. If you don't use a partner's code or link, nothing changes for you. This notice replaces earlier notices of this amendment.

Notice of amendment — payment updates to the WhatsApp number in your booking. Posted 2026-10-19; effective 2026-10-19 — the same day. If you write a WhatsApp number as your contact method in the booking form, we may now send that number, from millio's WhatsApp business account, the updates for that booking that could cost you if you missed them — payment needed, payment deadline close, other times proposed or the time to answer running out, and payment you can still make after the deadline has passed — even if you haven't connected WhatsApp. They go through Meta Platforms, Inc. (WhatsApp) (sections 1, 2 and 4). They contain only the place's name, the date and time or a deadline, and a link to your booking. A mistyped number could receive them, and you can stop them at any time by sending STOP (sections 1 and 6). On the booking page, “Not now” (previously “Email only”) now only means we won't ask again; it no longer keeps these updates to email (section 1). Our record of booking updates sent on WhatsApp now covers these messages too (section 1). This browser can now also keep up to 3 of your recent activities for 14 days (names starting “millio_resume”) to show a “Continue” card on the home page; they are not sent to us (section 7). There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because customers have been missing payment deadlines that these messages are there to prevent, the messages use only a number the customer gave us for the same booking and details of that booking, and they can be stopped at any time with STOP; the “Continue” card's details stay in your browser.

Notice of amendment — paying from a link. Posted 2026-10-19; effective 2026-10-19 — the same day. From the link in a payment email you can now pay with one tap on “Continue as” followed by your partly hidden email address, which creates or signs in to the account for that booking's email address; the link works only for that booking, until shortly after the payment deadline, and only once for this, and the record of your sign-in steps during a booking now also covers it (section 1). A link we send you on WhatsApp or LINE lets you pay that one booking without an account and never signs you in; you can link the booking to an account later (section 1). Booking updates on WhatsApp and LINE now start with a headline that names the place and the date and time, then one line on what to do next and a short link to your booking (sections 2 and 4). We now keep a record of the booking updates we send you on WhatsApp or LINE — which messenger, when and whether it was sent — and show our operators which booking a WhatsApp or LINE reply is about when you connected that messenger on a booking page (sections 1 and 2). There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it applies only to booking requests sent without an account and to customers who connect WhatsApp or LINE, it uses details we already hold for the same bookings, and it shortens the steps to pay before a payment deadline passes.

Notice of amendment — interests question. Posted 2026-10-19; effective 2026-10-19 — the same day. Section 1 now lists a short “What interests you?” question, shown once after a booking request or a confirmed booking, as a place where you can pick your interests; if you answer it while signed in, your pick is added to the interests in your account. Section 7 now describes what these suggestions keep in your browser and the daily totals we keep, and says where “Ad measurement” is on a phone; section 1 no longer says the interests card is on My bookings, because it has moved. Nothing else changes. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because answering is optional, it is the same item we already keep for the same purpose, no new company receives it, and what stays in your browser holds no identifier.

Notice of amendment — how you arrived. Posted 2026-10-16; effective 2026-10-16 — the same day. Section 7 now describes one item in your browser tab's session storage, “millio_entry”: how you arrived at millio and the first page you opened, used only to count booking steps by how people arrived. Nothing else changes. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because the item holds no identifier, is gone when you close the tab, and is used only to measure booking steps.

Notice of amendment — no-show count. Posted 2026-10-14; effective 2026-10-14 — the same day. The number of no-shows shown to the places you book with now also counts visits before 14 October 2026 (section 2). Nothing else changes. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because no such no-shows were recorded before that date, so no one's number changes.

Notice of amendment — no-show records. Posted 2026-10-14; effective 2026-10-14 — the same day. When a place records a booking as a no-show and you had not told it you could not come, that no-show now counts towards a number shown to the places you book with — only the number, for visits from 14 October 2026 (sections 1, 2, 3 and 5). You can tell the place you cannot come from your booking page, and then it is not counted. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it.

Notice of amendment — booking updates on WhatsApp, and signing in with WhatsApp. Posted 2026-10-14; effective 2026-10-14 — the same day. If your WhatsApp number is linked to your millio account, we now send your booking updates on WhatsApp as well as by email, so that you don't miss a payment deadline; you can switch this off in your account (sections 1, 2 and 6). You can also sign in with your WhatsApp number, using a 6-digit one-time code we send you on WhatsApp, which links the number to your account; we keep only scrambled forms of the number and the code, for 24 hours (sections 1, 2 and 5). The record of your sign-in steps during a booking now also covers signing in with WhatsApp (section 1). Both go through Meta Platforms, Inc. (WhatsApp, United States), which this policy already names for chatting on WhatsApp; what it receives now also includes booking updates and sign-in codes (section 4). You can also connect WhatsApp or LINE from your booking page without signing in: you send one message from your app, and that booking's updates go there — or choose “Email only” (sections 1, 2, 5 and 6). Push notifications and LINE messages, if you turned them on, now also tell you when your request reaches the place, when your booking is confirmed or doesn't go through, when the place cancels, changes your time or asks you to choose another, when the time to answer a proposal is running out, and on the day before your visit — with the same contents as before (section 2). This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because the WhatsApp part applies only if you link WhatsApp to your account or sign in with it, and you can switch it off; for push and LINE, only the moments change, not what we collect.

Notice of amendment — booking requests without an account. Posted 2026-10-13; effective 2026-10-13 — the same day. You can now send a booking request without signing in or creating an account. You sign in, or create an account, only to pay once the place accepts — with Google, or with a one-time code we email you, with no password. This policy now describes what that involves (section 1): the link we email you to manage the booking, the time your email address was confirmed and the “email not confirmed” mark the place and our operators see until then, how the booking is linked to your account when you sign in to pay, and the counts by IP address and email address that keep out automated and repeated requests, deleted about a day after they start (section 5). The record of your sign-in steps during a booking now also covers signing in at the payment step, including with a code sent to your email (section 1). There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it applies only when you choose to send a request without signing in; if you are signed in when you book, nothing changes for you.

Notice of amendment — chatting with millio on WhatsApp. Posted 2026-10-13; effective 2026-10-13 — the same day. You can now chat with millio's operators on WhatsApp instead of coming back to the website. We read and keep the text and photos you send to our WhatsApp number, as an enquiry to millio's operators kept with your WhatsApp number (section 1). Only our operators read and answer them; the places you book don't see them (section 3). Our operators' replies are sent to you on WhatsApp, translated into your language — within 24 hours of your last message as they are, and after that with a short notice first (sections 2 and 4). This adds a new service provider outside Korea: Meta Platforms, Inc. (WhatsApp), in the United States (section 4). The WhatsApp number kept with an enquiry is deleted 90 days after its last message (section 5). Before this amendment took effect we neither read nor kept messages sent to our WhatsApp number. The same now applies to LINE: messages you send to our LINE official account go only to millio's operators — they no longer become messages in a booking or reach the place — and replies the place writes in your booking's messages are no longer sent on LINE (sections 1 to 5). If you are signed in, your support chat is now kept with your account as one history you can see on any device; messages from a LINE or WhatsApp linked to your account join it, and our operators' reply goes to where you last wrote from (sections 1 to 5). This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it applies only when you use our support chat while signed in, write to our WhatsApp number or LINE official account, or tap “Chat on WhatsApp”, and for LINE it only narrows who sees your messages; if you don't use these, nothing changes for you.

Notice of amendment — chatting with millio on LINE. Posted 2026-10-12; effective 2026-10-12 — the same day. You can now chat with us through our LINE official account instead of coming back to the website. We read and keep the text and photos you send there: as messages in your booking if your LINE is linked to your millio account and you have exactly one booking in progress, and otherwise as an enquiry to millio's operators, kept with your LINE user ID (section 1). The replies of the place or of our operators are sent to you on LINE, translated into your language and containing the text of the chat (sections 2 and 4). The LINE user ID kept with an enquiry is deleted 90 days after its last message (section 5). Before this amendment we neither read nor kept messages sent to our official account. There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because it applies only when you write to our official account or have linked your LINE to millio, and if you don't use LINE with millio, nothing changes for you.

Notice of amendment — problems you run into while signed in. Posted 2026-10-11; effective 2026-10-11 — the same day. If an error screen appears, or a payment or a trip plan unlock fails, while you're signed in, we now record it against your account (section 1) so that we can find and fix the problem and contact you if needed (section 2). Only millio’s operators see it (section 3), and it is deleted 90 days after it was made, or when you delete your account (section 5). There is no new service provider. This amendment does not get the full 7 days’ notice described above, and we say so openly: it takes effect on the day we post it. We did so because the record is kept only to fix problems that signed-in users run into and is seen only by our operators, and nothing changes for your bookings or for anyone who isn’t signed in.

Notice of amendment — paid trip plans (“Build my trip”). Posted 2026-10-10; effective 2026-10-10 — the same day. You now need a millio account to see a full plan from “Build my trip”; the first plan after signing up is free, and each new plan after that is a paid digital service (Terms of Service, section 3). This policy now describes the record we keep when you unlock a plan — a key that identifies the plan (not your answers), whether it was free or paid, when you unlocked it, the version of the no-refund notice you agreed to and, for a paid plan, the payment and PayPal’s numbers (section 1) — why we keep it (section 2), who sees it (section 3), what PayPal receives (section 4) and how long it is kept: while your account exists, and 5 years for the payment details of a paid plan (section 5). The “Build my trip” counts still contain no account information. There is no new service provider. This amendment does not get the full 7 days’ notice described above, and we say so openly: it takes effect on the day we post it. We did so because the record is made only when you unlock a plan yourself, and nothing changes for your bookings or for anyone who doesn’t unlock a plan.

Notice of amendment — Fast booking (card hold). Posted 2026-10-09; effective 2026-10-09 — the same day. Where millio offers Fast booking — an option on some booking requests to places where millio books on your behalf, described in the Terms of Service — this policy now describes what it involves. When you start a card hold, we record it against your booking so that we can charge it when the place confirms a time, release it when no time works, and make sure the same booking never gets a second card hold or a second charge (sections 1 and 2); the record is kept as a payment record for 5 years (section 5). PayPal receives the instructions to place, charge and release the card hold (section 4), and our usage-statistics provider (PostHog) is told, with the booking's number, that a card hold was placed or released, or that the charge at confirmation did not go through — never the amount, the card or PayPal's numbers (section 4). We do not receive your card number or payment-method details. If you don't choose Fast booking, none of this applies to you and nothing new is collected. There is no new service provider. This amendment does not get the full 7 days' notice described above, and we say so openly: it takes effect on the day we post it. We did so because Fast booking applies only if you choose it yourself when you send a request — a booking or request you have already made, and the ordinary way of requesting a booking, work exactly as before.

For any privacy question or request, contact Pinomad Corp. at support@millio.co.

• Data Protection Officer: Soyoung Park — kathy@millio.co
• Operator: Pinomad Corp. · Business registration number 535-86-03642
• Address: 3F 311-558, 127 Gimpohangang 10-ro 133beon-gil, Gimpo-si, Gyeonggi-do, Republic of Korea

Google Maps content

When you load Google reviews or photos, your browser may connect to Google to display images. Google may receive your IP address and device information. Review text and photos are not stored by millio.