01
How this works
A cookie is a small text record your browser stores for a website and sends back on later visits. It has a name, a value, an expiry and a set of flags that decide who can read it. Browsers also offer local storage and IndexedDB, which are similar but never leave your device on their own.
We sort every cookie into one of three groups. Necessary cookies keep you signed in, protect your account and record the decision you made on our banner. Functional cookies remember something you did, such as choosing Korean or clicking one of our campaign links. Everything else waits for your consent and stays off until you give it.
We do not run Google Analytics, advertising audiences, session replay, or any cookie of our own that follows you across other websites. The Meta and Naver cookies in Section 3 load only with your consent. Section 2 lists every cookie by name.
- Necessary
Set without asking. Needed to sign in, protect your account or record your banner choice.
- Functional
Set when you do something that needs them, such as picking a language or clicking one of our links.
- With consent
Set only after you press Accept on the banner or Turn on above.
03
Scripts that wait for your consent
To see whether our ads work and how the site performs, we load three vendors' scripts. None of them load until you press Accept on the banner or Turn on at the top of this page, and each disappears again on the next page load after you turn them off.
Meta Pixel and Conversions API
Facebook and Instagram ad attribution
- Records page views, starting or finishing the free diagnostic, opening our KakaoTalk consultation, and checkout and purchase events.
- Sets _fbp and, after an ad click, _fbc under our domain.
- Our server also sends the same events to Meta (each carries an id, so Meta counts it once), plus a sign-up event that only the server sends. That copy carries a hashed email, a hashed phone number if we have one, a hashed internal id, your IP address, browser type and the two Meta cookie values. Meta matches the hashes against its own records; the email, phone number and id are sent only as hashes, never in the clear.
- When you start a checkout we keep a copy of those two cookie values, your IP address and browser type with the order, so the purchase can be reported to Meta after payment. That copy also records whether you had accepted, and is only sent if you had.
Naver Premium Log Analysis
Naver search ad attribution
- Records page views, and a conversion when you finish the free diagnostic or make a purchase, so Naver can credit the search ad you clicked.
- Relies on the NaPm cookie Naver sets on our domain.
- We never pass a name, email or phone number to Naver. Purchase events carry only the amount.
Vercel Analytics and Speed Insights
Anonymous usage and performance metrics
- Counts page views, measures how fast pages load for real visitors, and on the free practice pages records whether a test was started, finished or led to a sign-up click (test id and skill only, no answers or scores).
- Sets no cookie. Data is aggregated and is not used to identify you.
- We still ask for consent, because it sends data about each session to a third party.
What we do not use, at any setting
- Google Analytics, Google Ads or any Google audience product
- TikTok, LinkedIn, Kakao Moment or other ad pixels
- Retargeting lists or lookalike audiences built from your visit
- Session replay, heat maps or keystroke recording
Change your mind at any time with the card at the top of this page or the Cookie settings link in the footer. We also record each change in our consent log, using the tt_vid cookie described above. Each entry holds your decision, the version of our consent terms in force, where you decided (banner, footer or this page), your IP address, browser type and the time, so we can show what you chose and when. The log is kept for the period stated in the Privacy Policy.
04
Storage on your device
Some features keep data in your browser without a cookie. Unlike a cookie, it is not attached to every request; a few items (campaign parameters, a pending diagnostic, recordings waiting to upload) are sent when you submit something. It is read and written by code running on your device and cleared when you clear site data.
Local storage
- Practice and exam progress: your in-progress answers and the end time of any countdown, so a refresh or dropped connection does not lose your work.
- Drafts of things you are writing: assignment answers (14 days), practice runs, an unsent message to your teacher, and your onboarding answers.
- Summaries of free practice tests you finished before signing up (score and date, 90 days). The full runs are in IndexedDB below.
- A copy of dashboard data you have already seen (profile, schedule, group chat, results) so pages open faster. Kept for up to 24 hours, keyed to your account, removed when you sign out. We also keep the id of the last account signed in on this browser.
- An anonymous device key for free practice, so a later sign-up can claim the history saved on this browser.
- A diagnostic test you took before signing up (its anonymous session id and the result), waiting to be attached to the account you are about to create.
- Campaign parameters from the link you arrived on, kept for 30 days or until you sign out.
- Display preferences: theme, sidebar and pane sizes, audio volume and mute, reading font size and skim speed, camera appearance in live classes, which result tab you last opened, which assistant conversation you last opened, whether you have seen a tutorial or left the assistant panel open.
- A marker used only while a staff member views your dashboard on your behalf, so the two sessions are never mixed up.
Session storage
- A note that your diagnostic result has already been verified in this tab, so the check does not run again on every refresh.
- A flag that we already warned you about recording limits on iOS Safari.
- If you join a live class as a guest, a ticket for your place in the waiting room.
Cleared when the tab closes.
IndexedDB
- Full free practice runs you complete on this browser before signing up, kept for up to 180 days or until you sign out.
- Audio you record during a timed exercise, so a refresh does not lose it. Removed when you submit or, for a test taken before signing up, once it has been attached to your account. Recordings older than 24 hours are cleared when your browser runs low on space.
- Speaking recordings that are waiting to upload. If an upload fails, the recording is kept for up to 7 days and sent the next time you open the dashboard, then removed.
Apart from the items above, we do not store your profile, group membership or other account details in the browser. Anything not listed here is fetched fresh from our servers each time.
05
Other services with their own cookies
A few features embed another company's page or player. That company may set cookies on its own domain under its own privacy policy. We do not read those cookies and cannot control them.
- Toss Payments
- At checkout you are sent to Toss's payment page, and on the Mock Pass page Toss loads its card payment widget. Either may set cookies on tosspayments.com for fraud prevention and session continuity.
- Google Sign-In
- If you sign in with Google, Google sets its own cookies during its sign-in flow. We only receive the identity token that completes the sign-in.
- Kakao Sign-In
- Same as Google. Kakao sets its cookies on kakao.com and we never see them.
- Bunny.net video
- Recorded classes, lesson videos and the sample lesson on our marketing pages stream through Bunny.net. Its player may set short-lived cookies for signed links and player state, scoped to its own domain. If a lesson embeds a YouTube or Vimeo video instead, that company sets its own cookies.
Our hosting (Vercel), database (Neon), cache (Upstash) and error reporting (Sentry) set no cookies on your device. Error reports have cookies and sign-in credentials stripped in your browser before they are sent.
06
Legal basis
The Personal Information Protection Act of Korea (PIPA) requires a lawful basis for each cookie. Where the GDPR applies because you are in the European Economic Area, the matching article is shown alongside.
| Category | PIPA | GDPR |
|---|---|---|
| Necessary | Article 15(1)(4), performing the contract with you, and Article 15(1)(6), our legitimate interest in keeping a record of your consent decision | Article 6(1)(b) and 6(1)(f) |
| Functional | Article 15(1)(6), legitimate interest, limited to remembering an action you took yourself | Article 6(1)(f) |
| With consent | Article 15(1)(1), consent, obtained separately and before anything loads as Article 22 requires, and withdrawable at any time under Article 37 | Article 6(1)(a) |
The banner appears on your first visit and on every visit until you answer. Accept and Decline are equal choices, and declining never limits the service.
The consents you give when creating an account (Privacy Policy, Terms, third-party transfers, marketing messages) are separate from cookies. They are stored with your account. Marketing consent can be switched off in Settings at any time; the Privacy Policy, Terms and the third-party transfers needed to provide the service are required to keep an account.
07
Where the data goes
Our own cookies are read by servers hosted in Singapore (Vercel, Neon, Upstash). The Privacy Policy's section "Transfers outside Korea" describes these transfers, the safeguards in place and your rights.
Cookies set by Toss, Google, Kakao and Bunny.net stay with those companies. Meta and Naver receive the events described in Section 3 only after you have accepted.
08
Managing cookies in your browser
Every major browser lets you view, block and delete cookies per site or globally. The official guides:
Blocking the sign-in cookie signs you out and prevents signing back in. Blocking the sign-up consent cookie means you are asked to accept the terms again right after signing up. Deleting the banner cookie simply means we ask again.
Private or incognito windows discard all cookies when closed. The service works fully in that mode; you will be signed out and asked about cookies each time.
09
Changes to this policy
We update this page when we add or remove a cookie, change a vendor, or when the law changes. The date at the top always shows the current version. If a change materially affects your rights, we notify you inside the service or by email before it takes effect.
Version 1.2 (September 2026) added the Naver script and the language, campaign-parameter, diagnostic result hand-off, sidebar and phone verification cookies, corrected the sign-up consent cookie lifetime, and corrected the storage durations in Section 4.
10
Contact
Questions or complaints about cookies go to our privacy inbox below. We answer within 10 days.
LORA English Remote Academy (Tier One English)
Business registration 650-94-02234
Representative: Chanhee So
- Privacy
- privacy@tieroneenglish.com
- Support
- support@tieroneenglish.com
- Phone
- 070-8018-6673
- 2nd floor, Room 2525, 19 Hakdong-ro 2-gil (Nonhyeon-dong, Sail Building), Gangnam-gu, Seoul, Republic of Korea