Privacy Notice

What this site stores, who else touches it, where in the world it goes, how long it stays, and what actually deletes it.

Who is responsible

The operator of this site is a business registered in the Republic of Korea. The details below are printed in Korean because that is the form they are registered in.

Service

haeva, korea

상호 · Company

창업 플러스

대표자 · Representative

이민우

사업자등록번호

226-38-01619

통신판매업신고

제2026-인천연수구-0049호

주소 · Address

인천광역시 연수구 인천타워대로 301, 송도센텀하이브 B동

전화 · Phone

1566-2303

이메일 · Email

hello@haevakorea.com

문의 · Get in touch

Instagram DM @haeva.korea

개인정보 보호책임자

이민우 — Korean law asks for a named person here, not a department

Effective date: 2026-08-03.

What is stored, exactly

This section is written from the database schema rather than from a template, so it can be checked against the software.

When you buy something

An order record holds order_ref (the reference shown to you), sku, lang (which language edition), price_minor and currency (the price at the moment of the order), status, the payment provider's paypal_order_id and paypal_capture_id, buyer_email — the address the payment provider passes to us, which you never type here — the time you agreed that downloading ends the refund window, and timestamps for creation, payment, and refund.

It also stores your ip address and ua (browser identification string). We are naming these because they are personal data and most notices quietly omit them.

When you download

A download record holds a one-way hash of the link token, an expiry time, a download counter, and the last_ip that used it. Links last 30 minutes and allow up to 5 downloads. The token itself is stored only as a hash, so nobody — including us — can read a live link out of the database.

When you answer the itinerary questions

If you bought a custom itinerary, your answers are stored as one record against your order: your dates, arrival time, hotel address or neighbourhood, the regions you want, your pace, the language for the PDF, anything else you write, and a contact_email for the reply — which may differ from the payment address. A staff note and a delivery timestamp sit on the same record.

Allergies — this one is treated differently

One of those questions asks about allergies and foods you avoid. Under Korean law an answer to that question is sensitive personal information, in the same category as health data, and it may not be processed on the same footing as the rest. 개인정보 보호법 제23조 — 사상·신념, 노동조합·정당의 가입·탈퇴, 정치적 견해, 건강, 성생활 등에 관한 정보는 별도의 동의 없이 처리할 수 없다.

So the field is optional, it is blank unless you fill it, and there is a separate tick box next to it that you must tick before it will be accepted. Ticking it is recorded with a timestamp. The purpose is narrow — so that a plan does not send you somewhere you cannot eat — and it is used for nothing else. If you would rather not write it down, leave it empty and tell us in person; the plan still gets written.

If you have an account

Accounts are live. A user record holds your email, a one-way hash of your password (never the password), your language, whether you asked for the occasional email, the timestamps at which you agreed to the Terms and this notice, the referral code you arrived with, your account status, and the ip and ua from the moment you signed up. A signed-in session is a separate record: a hash of the session token, an expiry, and the ip and ua that last used it.

To stop abuse

A short log of ip, the kind of request, and the time, used to rate-limit repeated attempts.

When you comment on the journal

A comment record holds the text you wrote, which article it is on, which comment it replies to, whether it has been taken down, and the time it was written. It is linked to your account by user_id — the comment table itself holds no email address.

The name shown beside your comment is stored once on your account as display_name, not on each comment, so changing it changes every comment at once. Your email address is never shown with a comment. We see it in the admin screen, because when the same person posts advertising on ten articles that is the only way to tell.

A like stores only which article and which account, and the time — the pair is the primary key, which is what makes one like per person per article true in the database rather than in code. Nobody, including you, is shown who liked an article.

When you book a 1:1 call

A booking record holds the half-hour slot you chose (stored as a UTC timestamp), the order it belongs to, the address the Zoom link should go to, the date the follow-up window closes, and the Zoom link itself once we create it. Your answers to the short pre-call form — your name, when the trip is, how many of you, what you most want out of the call, what is already booked, and anything you add — are stored as one record against that booking. We do not record the call. No audio, no video, no transcript; nothing of the half hour itself is kept beyond notes we write for ourselves.

What it is used for

Taking payment, delivering what was bought, letting you get a fresh download link, writing the itinerary you asked for, answering you when you write to us, keeping the tax and refund records Korean law requires, and blocking abuse. Not advertising, not profiling, and not sold or handed to anyone for their own purposes.

Who else processes it, and where

All of these are outside Korea. Using this site means your data crosses a border, so the law requires the specifics rather than a list of names — the items below are the ones it asks for.

The legal basis for the first three is that they are the processing and storage needed to perform the contract with you, disclosed here in this notice. 개인정보 보호법 제28조의8 제1항 제3호 가목 — 정보주체와의 계약의 체결 및 이행을 위하여 개인정보의 처리위탁·보관이 필요한 경우로서 제2항 각 호의 사항을 개인정보 처리방침에 공개한 경우.

Handing it to anyone else

Beyond the processors above, nothing is given to a third party for their own use. Nothing is sold. The one exception is a demand we are legally obliged to answer — a court order or a lawful request from an authority — and we do not have a way to promise otherwise.

How long it is kept

Some of these periods are ours to choose. Some are not — Korean commerce law fixes them, and it fixes them as a minimum, which means deleting an order record early is not an option even if you ask. 전자상거래 등에서의 소비자보호에 관한 법률 시행령 제6조 제1항 — 표시·광고에 관한 기록 6개월 · 계약 또는 청약철회 등에 관한 기록 5년 · 대금결제 및 재화등의 공급에 관한 기록 5년 · 소비자의 불만 또는 분쟁처리에 관한 기록 3년.

Order and payment records

5 years — required, not chosen

Complaints and disputes

3 years — required

Advertising and display records

6 months — required

Account

Until you close it. Closing strips the record of everything that identifies you — email, password hash, sign-in provider, IP, browser string — and unlinks your orders from it. The paid order records themselves survive, because the law above says they must

Itinerary answers, including the allergy field

1 year after the plan is delivered, then the answers are erased from the record while the order itself stays

1:1 call bookings and pre-call answers

1 year after the call, then the answers are erased from the record while the booking and its order stay. The Zoom link is removed at the same time

Journal comments and likes

Kept while the article is up. Closing your account erases the name you chose and unlinks you from the comment; the text stays so the conversation around it still reads. Deleting your own comment removes it outright unless someone has replied

Sign-in sessions

30 days after they expire or you sign out

Download and questionnaire links

30 days after they expire

Rate-limit log (IP)

30 days

Payment provider notifications

1 year

How it is actually deleted

A retention period that nothing enforces is a sentence, not a practice. So the deletions in the table above are done by code, not by remembering: once a day, when the site next receives a request, a routine removes everything past its period. Rows are deleted outright — they are not flagged, hidden, or moved to an archive — and files are deleted from storage in the same pass.

Two things are deliberately not automatic. Order records past their five years, and the files attached to them, are removed as a reviewed operation rather than by a background job, because a job that can delete financial records unattended is a worse risk than the one it solves. And closing an account takes effect at that moment, not on the next daily run.

Cookies and local storage

Signing in sets kbl_session, which is how the site knows the next page you open is still you. It holds a random token and nothing else — no name, no email — it is marked HttpOnly and Secure so that scripts cannot read it, and it disappears when you sign out.

We also count visitors with Google Analytics, and whether that sets a cookie depends on where you are. If you are in the European Economic Area, the United Kingdom or Switzerland, it sets none: the tag starts in a refused state and is never switched on, so nothing is written to or read from your device, and you are counted only by a request that carries no identifier. Everywhere else it sets _ga (two years) and _gid (24 hours) — a random identifier, not your name, but one that follows you between visits, which is what makes it a tracking identifier. Where you are is decided by our server from the address your request arrives on, not guessed in your browser; if it cannot tell, it assumes the stricter answer and sets nothing. No advertising cookie is set anywhere, and Google's advertising storage is refused in every country. The transfer this involves is described above under who else processes it.

The questionnaire pages are excluded from this counting altogether, because their address contains the key that opens them.

We also keep a count of our own, on our own server, so that we can see it next to the orders instead of in someone else's dashboard. It writes one row per page you open, holding the date and time to the minute, the path, the language, the two-letter country your request arrived from, and the site you came from if you followed a link — the host only, never the full address. It holds no cookie, no identifier, no IP address and no browser string, so one row cannot be tied to you and two rows cannot be tied to each other. Nothing about it leaves Korea's and Cloudflare's infrastructure, and rows are deleted after a year. The same questionnaire pages are excluded here too.

Separately, your browser's local storage holds kbl_lang — whether you chose English or Japanese. That never leaves your device and is not sent to us.

What you can ask for

You can ask what is held about you, ask for it to be corrected, ask for it to be deleted, ask us to stop processing it, and withdraw a consent you gave — including the allergy one, which you can withdraw without giving up the plan. Write to the address at the top; we answer within 10 days.

If an order has been paid, deleting your account does not delete the order record — see retention above for why. If you think we have handled this badly you can complain to Korea's Personal Information Protection Commission (개인정보보호위원회, privacy.go.kr, 국번없이 182), and if you live outside Korea, to the equivalent authority where you are.

Children

This site is not built for children and does not knowingly collect their data.

Changes

When this notice changes in a way that matters — a new processor, a new purpose, a longer retention — the effective date at the top changes with it, and the previous version is what applied to anything collected before that date.