Privacy policy

Who runs this site

kpoptrips.com is run by an individual operator in Korea. Contact: hello@kpoptrips.com.

What we collect and how long we keep it

E-mail alerts: the e-mail address you enter, the artist you chose, your language, the page you signed up on, when you signed up, when you confirmed and when we last sent you an alert. We use them only to send the alerts you asked for. Kept until you unsubscribe (every mail has a link; mail stops at once and you leave the list) or ask us to delete it. The Japanese Act on Regulation of Transmission of Specified Electronic Mail requires a sender to keep a record of your consent for one month after the last advertising mail sent on the basis of that consent. We therefore keep that record (the address, artist, language, the page you signed up on, sign-up, confirmation and unsubscribe times, and when we last mailed you) separately after you unsubscribe, use it for nothing else, and delete it automatically 31 days after the last alert mail or the unsubscribe, whichever is later (by the daily clean-up, so up to one day more). If you have not confirmed, we resend the same confirmation mail only once, at least 24 hours after the first mail and within the 7-day confirmation-link validity period. If you still do not confirm, we send no further mail. Mail is sent through Resend (USA), and the list is kept on our server at Amazon Web Services; both act on our behalf outside Japan.

Trip notes (遠征ノート, Japanese/Chinese pages): the venue, artist, date, seat, your answers, your text, an optional nickname and an optional photo. The photo is resized in your browser before sending, so location and camera data never reach us; we re-save it again before publishing. Notes are published only after review and stay until you ask for removal (link on every note). If you enter the monthly draw, your contact (e-mail or X username) is stored separately from the note, used only to run the draw and send the prize, never published, and deleted after the prize is sent or the draw ends. A monthly, salted hash of the IP is kept to spot repeat entries.

Login (Japanese/Chinese pages, optional): if you log in with LINE we keep your LINE user ID (to recognise you and, if you added our LINE account as a friend, to send the alerts you asked for), the user name and display name you choose, whether you are our LINE friend, which notes are yours, the LINE alerts you asked for (show, artist, language and when you asked), and a login session (stored as a hash, 30 days). We do not keep your LINE profile name, photo, e-mail or LINE access tokens. Account pages carry no analytics or ad tags. Kept until you delete the account on My page; deleting removes all of this, and your published notes stay as "former user" unless you ask for them to be removed. The data is stored on our server in the Amazon Web Services Tokyo region (Japan).

Going list (Japanese and Chinese concert pages, optional): the shows you mark as going. Only you can see the list; it is never published, and saving a show does not sign you up for any alerts. When you are not logged in, the list is kept only in your browser and is not sent to us. A show saved in your browser is removed the first time you open a kpoptrips page in that browser on or after the 30th day after the show's last day; until then it stays in that browser unless you delete it or clear your browser data. When you are logged in, we keep the show, language and time saved in your account and delete each entry from our server automatically 30 days after the show's last day (an hourly job, so it can run a little late). Deleting your account deletes the list kept in it. Stored on our server in the Amazon Web Services Tokyo region (Japan). You can view and delete entries on My Page; for anything else, write to hello@kpoptrips.com.

Writer profile (logged in, optional): only if you choose to make it public, we publish your display name, user name and links to the published notes you pick on a profile page, and show a link to the profile on those notes. It is private by default. Your going list and upcoming shows are never shown on it. You can make it private again on My Page at any time; the profile stops showing right away. Stored on our server in the Amazon Web Services Tokyo region (Japan). You can view and correct the setting, the notes shown and your display name on My Page; to delete, delete your account on My Page or write to hello@kpoptrips.com.

Questions to the operator (a trial on some Japanese concert pages): the question text, the show, language and time, and a key that changes daily instead of your IP address (to stop repeated posting). If you add an e-mail address and agree, we also keep it and use it only for one mail telling you an answer is ready (sent from hello@kpoptrips.com). The address is stored apart from the question and deleted after that mail, or 60 days after the question at the latest (an hourly job, so it can run a little late). Questions are never published; we use them to prepare answers and improve pages, and delete them a year after they were sent. Stored on our server in the Amazon Web Services Tokyo region (Japan). To view, correct or delete a question, write to hello@kpoptrips.com with the time you sent it and the show (and the e-mail address, if you gave one).

Campaign tag: if you arrive through a link that carries a campaign tag (utm_source, utm_medium, utm_campaign, for example a link in a video description), your browser keeps the first such tag for 30 days (localStorage on this site; clearing this site's data removes it). One exception: arriving through one of our own paid test campaigns, registered in advance for this purpose, replaces an older tag from a different campaign — in your browser, on an e-mail sign-up that is not confirmed yet, and on a LINE login record that does not yet have an active LINE alert (an alert while you are our LINE friend) — so that the sign-up is counted for that test. A confirmed subscription is never re-tagged. When you sign up for e-mail alerts or for your first LINE alert, the tag is sent with the sign-up. Our server keeps only campaign names we registered in advance (for example youtube / video / shimai1); any other value is kept only as "other". We use the tag only to count how many sign-ups each link brought. With e-mail alerts it is stored on that subscription and deleted when you unsubscribe (it is not part of the consent record we keep after that). With LINE alerts it is stored on your LINE login record and deleted when you remove your last LINE alert or delete the account. Separately, the time of your first sign-up and the tag are written to our sign-up count log, next to a salted one-way hash instead of your e-mail address or LINE user ID. The tag is kept there for 12 months from that first sign-up and then deleted. The rest of that entry (the hash and the time) is not deleted when you unsubscribe or delete the account. With measurement consent, the browser also keeps the last subscription button position for each channel for up to 7 days, solely to measure completed sign-ups. This position is not stored in your server subscription record; declining removes it. Country is measured by Google Analytics, not added to that record. To measure completion after returning to the site, a one-time confirmation ticket also carries language and campaign tags; it is deleted when used, or expires after 7 days and is removed at the next ticket cleanup.

Share links: the "send on LINE" and "copy link" buttons on a concert page add a share code to the link (?kref=…). The code is a random value our server issues to your browser the first time you tap one of these buttons (not when you only open the page); it is not made from your e-mail address, LINE ID or anything else about you. Your browser keeps the code (localStorage "kpt_myref") and a random browser ID ("kpt_vid") so the same code is reused; both stay until you clear this site's data in your browser. Each time you share, our server checks the stored code; a code older than 365 days (or otherwise no longer valid) is replaced by a new one at that share. When someone opens a shared link, their browser asks our server whether the code is valid and, if so, keeps it for 30 days from the last valid shared link they opened (localStorage "kpt_ref"; opening a valid shared link again, including the same one, restarts the 30 days); once the 30 days have passed, it is deleted the next time this site is opened in that browser (until then it stays stored but is no longer used). If the code was not valid or has expired, the browser keeps only that reason and the date for 30 days, deleted on the next visit after that ("kpt_ref_miss"). The browser ID is created on that visit too. A code kept this way is sent with an e-mail or LINE alert sign-up made in those 30 days and saved on that sign-up record; it is deleted with the unsubscribe, the last LINE alert or the account. Our server keeps each code with the date, page and language it was issued for, for 365 days. It also keeps a log for up to 400 days. Recorded in the log: the share code itself, a one-way hash of the browser ID, the kind of event (code issued; share tap, LINE or copy; shared link opened, valid or why it was ignored; return visit within 14 days of the first opening, with the day number; sign-up), its date and time, the page and the language, and for a sign-up the channel (e-mail or LINE) and whether it came with a code or why not. Not recorded: your e-mail address, LINE ID, IP address or the browser ID itself. We use this only to count how often shared links bring visitors and sign-ups; there is no reward and nothing is shown to the person who shared.

Feedback form: your message, the contact details you choose to add, the page and language, the time, and a key that changes every day instead of your IP address. Kept so we can fix the site, until you ask us to delete it.

Route box on show pages: the hotel name or address you type is looked up from our server in the Korea Tourism Organization's TourAPI and in OpenStreetMap. The answer is cached on our server for a day; it is not stored with anything about you.

Server access logs: IP address, browser, page and time, kept for up to 30 days to count visits and stop abuse.

Outbound buttons (ticket sellers, hotels, maps): clicks are counted without cookies, with a key that changes every day instead of your IP address.

In your browser only: your currency choice and the hotel you typed in the route box (used for the Korean taxi card). They stay on your device.

Services that receive data

Google Analytics (Google): cookies and page/click events, to understand visits in aggregate. Google Analytics itself keeps running if you decline in the banner; only its advertising features depend on your choice. It runs with Google signals and ad personalization turned off. Google keeps user-level data for the retention period set on our property (Google's default is 2 months). We advertise kpoptrips on Google. The Google tag's advertising features run only if you agree in the banner: Google Ads conversion measurement (cookie _gcl_au) and, because our Analytics property is linked to our Google Ads account, recording visits for audience lists. Until you agree, and after you decline, the tag runs with Google Consent Mode denying ad storage, ad user data and ad personalisation: no ad cookie is set and no ad user data is sent, though Google may still receive cookieless signals for aggregate measurement. We use these to see whether our ads bring visitors.

Microsoft Clarity (Microsoft), only if you agree in the banner: session replay — it records how you use the page (clicks, taps, scrolling, mouse and touch movement) so that Microsoft can replay it like a recording, with the text you type masked; it also sets cookies (_clck, _clsk) and builds heatmaps. We use it to fix confusing pages. Microsoft keeps recordings for 30 days (after that only a small sample, up to 13 months) and heatmap and click data for 13 months.

Resend: sends our confirmation and alert e-mails, so it receives your e-mail address and the mail.

LINE (LY Corporation): delivers the LINE alerts you asked for, so it receives your LINE user ID and the message text, only to deliver the message.

Klook: the "before or after the show" attraction cards on concert pages are served by Klook in a frame, which loads only when you scroll to it and uses Klook's own cookies and analytics.

Meta and X ad tags (Japanese and Chinese (Taiwan) pages only): with your consent, those pages load the Meta Pixel and the X website tag. They send Meta and X the address of the page you view (including any search words or dates in it), the referring page and basic browser information, and set cookies — some on this site's own domain (e.g. Meta's _fbp). We use this to measure our ads on Instagram, Threads and X and to show our ads to people who visited. Automatic event collection and advanced matching are off; form contents such as your email are not sent. When an alert sign-up is completed on these pages (a LINE alert with the LINE friend added, or a confirmed e-mail alert), the Meta Pixel also sends a 'CompleteRegistration' event with the page address, a random event ID and the channel (LINE or e-mail) — never your LINE ID or e-mail address. These tags load only after you choose 'Agree' in the ad-measurement banner; until you choose, and if you choose 'Decline', no Meta or X tag is loaded and nothing is sent to Meta or X. Your choice is kept in this browser (localStorage), and you can change it at any time under 'Ad measurement & analytics settings' at the bottom of every page (the section below). Declining also deletes the Meta and X cookies on this site's own domain (_fbp, _fbc, _twclid); if the tags are already running, our page stops calling them and reloads, which removes the tags (what Meta's and X's own scripts do before the reload is not something we have verified). Deleting this site's data removes your choice, and the banner asks again. Meta's Ad preferences and X's Personalization and data settings change how Meta and X use data they already have.

Travelpayouts (affiliate partner), only if you agree in the banner: its script is an affiliate tool. It sends Travelpayouts the address of each page you view, watches clicks on links, can read the page text and rewrite links into tracked affiliate links (via tp.media), and checks your browser's storage features. When you follow a link marked PR, it passes through Travelpayouts (tp.media), which records the click and sets cookies so a booking can be credited to us. The shop you land on applies its own policy.

Amazon Web Services: hosts our server in its Tokyo region (ap-northeast-1, Japan), where the data above is stored.

Korea Tourism Organization TourAPI and OpenStreetMap: receive only the hotel text you type in the route box, from our server, not your IP address.

We don't sell personal data. Apart from the Meta and X ad tags described above (page views and completed alert sign-ups, used to measure and show our ads, only with your consent), we don't share it for advertising. We advertise this site elsewhere; those platforms' own policies apply there. Ticket sellers and hotels we link to have their own policies.

Your choices

Unsubscribe with the link in any alert mail. Block or delete cookies in your browser settings. For a copy or deletion of anything above, write to hello@kpoptrips.com.

2026-10-20