Cookie Policy

This page lists every cookie we set, what each one is for, and who else we let set one.

Why we ask

No advertising or statistics tag from the companies listed below runs until we switch them on, so none of them sets a cookie yet. We will update this page when we do. Google's Tag Manager, the script that would run them, may already load on the terms below, but it has no tag to run. The rest of this page says what happens once we switch them on.

In the EU, the EEA, the United Kingdom and Switzerland we show a short banner before we load anything from another company. Say no and the site works the same. To change your answer later, press "Cookie settings" at the bottom of this page, or the same button in the footer.

Everywhere else we load them without asking, because the law there does not require it. If we cannot tell which country you are in, we ask.

We also count visits ourselves, on our own servers, and your answer does not change that. Those counts need no consent because they cannot point at a person: no name, no account, no address, no device number, and the time kept only to the hour. What each one holds is the step it counts, the subject, the language you read in, whether the professional speaks it, the kind of session, whether you are on a phone or a computer, which ad brought you if one did, and which version of our home page headline you saw. Together they tell us how many people arrived, searched, signed up or paid.

The cookies we set

• ed_session: keeps you signed in. Readable only by our servers, never by a script on the page. Lasts seven days from your last visit.
• ed_eligible: records that you answered the age question, so we do not ask again on every page. Lasts until you sign out.
• ed_consent: remembers for one minute that you have accepted the current terms, so every page does not have to ask again.
• ed_post_login: remembers the page you were heading for when you signed in. Thirty minutes.
• ed_code_method: remembers which sign-in code you were sent while you type it. Readable only by our servers. Fifteen minutes.
• payout_code_method: remembers which email code you were sent while you save payout details. Readable only by our servers. Fifteen minutes.
• ed_device: a random number that identifies this browser. It is there for security only: to spot a batch of accounts made from one machine to abuse payments or trials, to enforce booking limits, to warn you when someone signs in to your account from a browser it has not seen, and to record which browser a staff action came from. We set it only when you open the sign-in page, sign in or sign up, and while you are signed in. Just reading the site sets none. It carries nothing about your device and no personal data, and clearing your cookies resets it. Readable only by our servers. One year.
• ed_cookie_consent: your answer to the banner, when you gave it, and which version of the question you answered. Page scripts can read this one, so we can act on your answer without asking you again. One year.
• ed_dismissed_announcements: remembers which site notices you closed, so they stay closed. One year.
• NEXT_LOCALE: remembers the language you chose. One year.
• tz: the timezone your browser reports, so a lesson time reads correctly before you have signed in. It holds a zone name such as Europe/Tallinn and nothing else. It ends when you close your browser.
• ed_admin_session: the same as ed_session, for our own staff tools. Only our staff ever receive it. Ends twelve hours after their last action there.
• ollinter_admin_code_method: the same as ed_code_method, for our own staff tools. Only our staff ever receive it. Fifteen minutes.

Cookies set by other companies

The privacy policy says what role each company plays.

The four below arrive through one script from Google, its Tag Manager. In the countries named above it loads only after you allow statistics or advertising, and only the category you allowed is used, so a no sends nothing to any of them. Everywhere else it loads when you arrive, without asking. Each company's own policy says how long its cookies last.

• Google Analytics (statistics): counts visits and what people do on the site. Google's privacy policy.
• Google Ads (advertising): tells Google which ad brought you here, so we can buy ads better. Same policy as above.
• Meta Pixel (advertising): the same, for ads on Facebook and Instagram. Meta's privacy policy.
• TikTok Pixel (advertising): the same, for ads on TikTok. TikTok's privacy policy.

Other things stored in your browser

Some things live in your browser's own storage rather than in a cookie. None of them is sent to us on its own, and most are conveniences: an unsent draft, a panel you folded, a tip you have already read. The ones worth naming:

• ed_passkey_used remembers that you have used a passkey on this device, so we offer it first next time.
• ed-push-token holds the address your browser gives us for push notifications, and exists only if you turned them on.
• payout-wise-draft remembers which kind of account you picked while you fill in your payout details. It holds that choice and nothing else, never a number or a name, and it ends when you close the tab.
• ed-purchase-signalled marks a payment we have already reported to the companies above, so a reload does not report it twice. One mark per booking or package, written only while those tags are running.

Clearing them

Your browser can delete all of it, cookies and browser storage together. Signing out clears the sign-in cookies. If we asked you about cookies, deleting the consent cookie means we ask again on your next visit. Deleting the device cookie makes you look like a new visitor to our fraud checks, which is the honest limit of what that check can do.

Questions

Write to legal@ollinter.com. What else we hold, and for how long, is in the privacy policy.