Contents
1. Introduction
This Cookie Policy explains how TeacherWave ("TeacherWave", "the Platform", "we", "us", "our") uses cookies and similar technologies on the TeacherWave website, platform, and related services.
This Cookie Policy should be read together with the TeacherWave Privacy Policy and Terms and Conditions.
2. What Are Cookies?
Cookies are small text files placed on a device when a user visits a website or uses an online service. Similar technologies may include local storage, scripts, and tokens used to operate websites, apps, and online platforms.
Cookies may be session cookies, which expire when the browser is closed, or persistent cookies, which remain for a set period or until deleted.
3. How We Use Cookies
TeacherWave uses cookies and similar technologies only for purposes that are necessary to operate the Platform and keep it secure. We use them to:
- operate essential platform functions;
- keep users logged in;
- protect accounts and platform security;
- support subscriptions, payments, and checkout;
- detect and prevent fraud, abuse, and suspicious activity;
- remember preferences such as language, region, and display settings;
- remember which tutor invited you, when you arrive through a link a tutor shared to invite other tutors;
- store your cookie choices;
- understand how the Platform is used — through Microsoft Clarity, which produces heatmaps and session replays — so we can improve it;
- measure whether an advertisement led to someone creating a tutor or academy account, through the Google Ads tag.
The last two purposes — analytics and advertising measurement — are non-essential, and are used only after you consent. Everything else is essential, remembers a preference, or remembers an invitation you followed (see section 4). Neither is ever used on a screen a student sees (see sections 4 and 5), and TeacherWave does not use email open or click tracking for marketing.
4. Types of Cookies We Use
TeacherWave uses only the following categories of cookies and similar technologies:
Essential cookies. These are needed for the Platform to work. They may support login sessions, account security, checkout, payment flows, fraud prevention, consent storage, and core platform functionality. The Platform may not work properly without them.
Preference cookies. These remember choices such as language, region, display preferences, saved settings, or cookie choices.
Invitation codes. If you open a link that a tutor shared to invite you to join TeacherWave, we keep the code from that link in your browser's local storage for up to 30 days, so that the tutor who invited you is credited if you create a tutor account. It holds only that code — nothing about who you are — and it is deleted when you create a tutor account, or after 30 days. If you open another tutor's link in the meantime, the newer code replaces the older one.
Analytics cookies. TeacherWave uses one third-party analytics service, Microsoft Clarity, provided by Microsoft, to understand how the Platform is used — which pages and features are used, where people get stuck and where errors occur — so we can improve it. Clarity builds heatmaps and session replays: a reconstruction of how a visit moved through the site, including the pages viewed, what was shown on them, clicks, scrolling and mouse or touch movement, together with your IP address, your approximate location and details about your browser or device. Anything typed into a form field is never included. Where a tutor is signed in, what was shown on their screens can include information about their own students, such as names and messages.
Signed-in visits are linked to your account. When you are signed in, we give Clarity your TeacherWave account reference — a random identifier that does not reveal who you are, and which Clarity scrambles in your browser before it is sent — together with whether you are a tutor and which screen you are on. This lets us look at the visits of one account when that person reports a problem. We do not send Clarity your name, email address or phone number. We also note three steps — a visitor asking for their free month, a tutor creating an account, and a tutor starting their subscription — so we can see where people get stuck on the way.
Clarity is never used for students. It is not used on any screen a student sees: not once a student is signed in, and not on the invitation page a student joins their tutor through. If Clarity is already running when a student reaches one of those screens — for example, a student who read our home page before signing in — we tell it to stop and to delete the cookies it set.
Clarity is not loaded until you accept optional cookies. It is not placed on the page at all unless and until you accept, so before that it records nothing and sends Microsoft nothing. If you later withdraw your consent using the cookie preference tool, we tell Clarity to stop and to delete the cookies it set. We use Clarity only to understand and improve the Platform, never to build advertising profiles. Analytics cookies are non-essential, and you can change your choice at any time.
Advertising measurement cookies. TeacherWave advertises its service, and uses one advertising technology — the Google Ads tag, provided by Google — to measure whether an advertisement led to someone creating a tutor or academy account. It sets cookies in your browser that let Google recognise that the visit which followed one of our advertisements ended in a sign-up. Section 5 describes what it does and does not do, and it is subject to the same consent and the same student exclusion as analytics.
Security and fraud-prevention cookies. These help detect suspicious activity, protect accounts, prevent abuse, identify fake accounts, support payment security, and protect the Platform.
5. Advertising and Conversion Tracking
TeacherWave advertises its service. Only after you accept optional cookies, it uses the Google Ads tag, provided by Google, for one purpose: to measure whether an advertisement led to someone creating a tutor or academy account. When an account is created, we tell Google that a sign-up happened, so that it can be matched to the advertisement the visit followed.
We do not tell Google who you are. We do not send Google your name, your email address, your phone number or your TeacherWave account reference, and we do not upload customer lists. What Google receives is that a sign-up occurred in a browser it already recognises from our advertisement.
It is never used for students. The Google Ads tag is not placed on any screen a student sees: not once a student is signed in, and not on the invitation page a student joins their tutor through. If it is already running when a student reaches one of those screens, we tell it to stop using storage for advertising and to delete the cookies it set. A student account can only ever be created through a tutor's invitation, so no sign-up we measure is a student's.
It is not loaded until you accept optional cookies. It is not placed on the page at all unless and until you accept, so before that it loads nothing and sends Google nothing. If you later withdraw your consent using the cookie preference tool, we tell Google's tag to stop using storage for advertising and delete the cookies it set.
TeacherWave places no other advertising or conversion-tracking technology — no Google Analytics, no Google Tag Manager container, no Meta Pixel and no Reddit Pixel. We do not use remarketing, we do not build advertising audiences or profiles from your visit, and we do not report your visits, sign-ups or subscriptions to any advertising platform from our servers.
TeacherWave also does not use email open or click tracking for marketing, and does not sell your personal data. If this changes, TeacherWave will update this Cookie Policy and ask for your consent before the change takes effect.
6. Third-Party Providers
TeacherWave relies on certain service providers that may set or read cookies strictly to deliver and protect the Platform, such as:
- payments and checkout (for example, Stripe and PayPal);
- hosting, security, and cloud infrastructure;
- classroom, video, communication, or support tools;
- cookie consent management.
PayPal is the one of these you have to ask for. If your tutor shows you their own PayPal subscription button, PayPal's software — and any cookie it sets — loads only after you open that page AND press the button on it. It does not load anywhere else on the Platform, and it does not load on that page until you press. What PayPal then sets is governed by PayPal's own cookie and privacy notices.
In addition, and only after you accept optional cookies, TeacherWave uses Microsoft — Microsoft Clarity, for product analytics, heatmaps and session replay, as described in section 4 — and Google, for the advertising measurement described in section 5. Each processes that data under its own privacy terms, and neither is used on a screen a student sees.
These providers process data under their own privacy and cookie policies where applicable. The exact providers used may change over time as TeacherWave develops the Platform, and this policy will be updated accordingly.
7. Cookie Duration
Cookies may remain on a device for different periods depending on their purpose and provider.
Session cookies usually expire when the browser is closed. Persistent cookies may remain for a fixed period or until deleted by the user. TeacherWave will aim to use cookies for no longer than reasonably necessary for the purposes described in this Cookie Policy. The invitation code described in section 4 is kept for no more than 30 days.
8. Managing Cookies
Users may manage cookies through:
- the TeacherWave cookie preference tool, where available;
- browser settings;
- device settings.
You can accept or decline non-essential analytics cookies, or change your choice at any time, using the cookie preference tool. Blocking or deleting cookies may affect login, checkout, account settings, classroom access, preferences, security, or other platform functionality.
9. Cookie Consent Records
TeacherWave may store your cookie choices and related technical information as a record of your preferences and for compliance. This may include consent status, timestamp, region, device or browser information, and cookie-preference records.
10. Do Not Track and Browser Signals
Some browsers or devices may send "Do Not Track" or similar signals. TeacherWave may respond to legally recognised browser consent or privacy signals where technically available and legally required.
11. Global Users
TeacherWave operates from Greece and may be accessed by users in different countries. Cookie and tracking rules may vary by location. TeacherWave will aim to apply appropriate consent and notice standards based on applicable law, user location, and the cookies or technologies used.
12. Changes to This Cookie Policy
TeacherWave may update this Cookie Policy from time to time, including if it introduces any new cookies or technologies. Where changes are material — for example, if any non-essential or tracking cookie is added — TeacherWave will provide notice and, where required by law, seek consent before such cookies are used.
13. Contact
For questions about this Cookie Policy or TeacherWave's use of cookies and similar technologies, please contact:
See also the TeacherWave Privacy Policy and Terms and Conditions.