What we know about you, and why.
A course platform needs an email address, a password and a record of which lessons you finished. Almost everything else on this page is us explaining what we deliberately do not collect.
Version 1.0 · last updated 30 September 2026
The short version
- We store your name, your email, a hash of your password, your quiz answers and your progress. That is the account.
- We never see your card details. The payment provider handles the money and the tax.
- Your Claude account and your Claude conversations never touch our servers. You do the exercises in your own Claude. We cannot see any of it.
- We do not sell data, we do not run ad trackers, and we do not build profiles for anyone else.
- Marketing email is opt-in and one click to leave. Service email — receipts, password resets, access notices — is not optional while you have an account.
- Ask us to delete your account and we delete it. Section 10 lists the two things that legally have to survive.
1 · Who is responsible for your data
The data controller is [LEGAL NAME], registered in [COUNTRY] under number [REGISTRATION NUMBER], at [REGISTERED ADDRESS]. One person, one inbox: hello@lagoon.academy.
Because we sell to people in the EU and the UK from outside them, our representative for data protection questions in the EU and the UK is [EU/UK REPRESENTATIVE]. You can contact them instead of us if you prefer.
2 · What we collect, why, and on what basis
| What | Why | Legal basis |
|---|---|---|
| Your name | To address you in emails and to print the certificate | Contract |
| Your email address | Logging in, password resets, your invoice, access and service notices | Contract |
| Your password, stored only as a salted one-way hash | So we can check a login without ever holding the password itself | Contract |
| Quiz answers — your role, your main goal, roughly how much time you have | To pick which version of each lesson and which 30-day plan you see | Contract |
| Progress — lessons opened and finished, module-check and final-test answers, saved prompts, your notes, your display preferences | To keep your place, mark the course complete and issue the certificate | Contract |
| Session records — a hash of your login token, when it was created and when it expires, your browser and device string, and the IP address the request came from | To keep you logged in and to let you see and end your own sessions | Contract, and our legitimate interest in account security |
| An activity log — account events such as signup, login, purchase and refund request, with a timestamp and the IP address | Fraud and abuse checks, and answering "what happened to my account" | Legitimate interest in keeping the platform and your account safe |
| Emails you send us, and our replies | To answer you, and to have a record of what was agreed | Contract, and legitimate interest in keeping support history |
| Marketing consent — whether you said yes, when, and the exact wording you saw | So we can prove consent rather than assert it | Consent, and legal obligation to evidence it |
| Order records — amount, currency, country, provider transaction and invoice references, refunds | Access rights, accounting and tax | Contract, and legal obligation |
If you sign in with Google or Apple, we receive your email address, your name and the identifier that provider uses for you. We do not receive your password and we ask for nothing else.
3 · What we deliberately do not collect
- Your Claude account, your prompts or your conversations. The exercises happen in your own Claude, in your own browser. We have no connection to it and no way to read it. If a lesson asks you to paste something, it is into Claude, never into us.
- Card numbers, expiry dates, CVVs or billing addresses. These never reach our server. Section 4.
- Your work documents. Nothing you upload to Claude comes to us.
- Date of birth, phone number, address, employer, photo. We never ask.
- Advertising and cross-site trackers. There are none on this site, and no data goes to an ad network.
- Special-category data. Health, politics, religion, biometrics — we have no field for any of it and ask you not to put it in a support email.
4 · Payment
Checkout is operated by [MERCHANT OF RECORD], who are the merchant of record and their own data controller for the payment. They collect your card details, your billing country and address and any tax number, and they decide the tax and issue the invoice. Their privacy notice covers that part, and it is linked from the checkout page.
What comes back to us is deliberately thin: your email address, the plan you bought, the amount and currency, your country, the provider's transaction and invoice reference, and the status — paid, refunded or disputed. That is enough to give you access and to close the books, and nothing more.
5 · Cookies and what sits in your browser
Cookies
One, and it is essential: lagoon_s, the login session. It holds a random token, nothing about you, is not readable by scripts, is not sent to other sites, and lasts 60 days or until you log out. There is no cookie banner because there is nothing to consent to.
Local storage in your browser
Your progress, your saved prompts and your display preferences are also kept in your own browser so a page loads instantly and survives a dropped connection. Clearing your browser data clears that copy; the server copy is what actually counts.
Analytics
We count page visits with [ANALYTICS PROVIDER], configured without cookies and without following anyone between sites. It tells us which pages get read, not who read them. If we ever add a tool that needs a non-essential cookie, we will ask first with a banner you can decline, and declining will not change what you can use.
The one third-party request
These pages load the Montserrat typeface from Google Fonts, so Google receives the IP address of the request when a page loads. That is the only outside connection the public pages make.
6 · Email
Sending is handled by [EMAIL PROVIDER] on our behalf. Two kinds go out, and we keep them apart on purpose.
Service email — not optional
Your access details, password resets, the invoice, a notice before a subscription renews, and anything about your account or a security problem. You cannot unsubscribe from these while you have an account, because they are how the thing you bought works.
Course and marketing email — opt-in
Lesson nudges, new material, occasional offers. You only get these if you ticked the box, and we store the exact sentence you ticked with the time you ticked it. Every one has a one-click unsubscribe that works without logging in and takes effect immediately.
When you unsubscribe we keep your address on a suppression list so a later import cannot add you back. That list holds the address and nothing else, and it is the one record that outlives a deletion request — which is the point of it.
8 · Where your data lives
The platform runs on one server operated by [HOSTING PROVIDER] in [SERVER LOCATION], and the account database sits on that machine. Backups are encrypted and stored with [BACKUP LOCATION].
We are based outside the EU and the UK, so your data is transferred out of them when you use the site. Those transfers rely on the European Commission's standard contractual clauses (and the UK addendum) with each provider, plus the practical safeguards in section 12. If you want copies of the clauses for a specific provider, ask and we will send them.
9 · How long we keep things
| What | How long |
|---|---|
| Account, quiz answers and progress | While your account is open. Deleted when you ask |
| An account with no purchase that has not been used | Deleted after 24 months of inactivity, after an email warning you first |
| Login sessions | Expire after 60 days and are deleted at expiry |
| Password-reset links | One hour, single use |
| Activity log with IP addresses | 90 days, then deleted — except rows attached to an open payment dispute |
| Support emails | 24 months after the conversation ends |
| Marketing consent records | While you are subscribed, plus 3 years — they are the proof you agreed |
| Unsubscribe suppression list | Kept, so you are not added back by mistake. Address only |
| Order and refund records | [RECORD RETENTION PERIOD], as tax law requires |
| Raw payment-provider notifications | 18 months, then the contents are purged and only the reference stays |
10 · Deleting your account — exactly what happens
Ask from your account settings or by email, and we will confirm it once. Then:
Gone
- Your name, your email address, your password hash, your avatar and any Google or Apple link.
- Your quiz answers, your progress, your notes, your saved prompts, your test answers.
- Every login session, immediately. Any device still logged in is logged out.
- Your certificate stops verifying, because it verifies against a live account.
What survives, and why
- The order records — amount, currency, date, provider reference. Tax law requires us to keep them for [RECORD RETENTION PERIOD]. After deletion they point at an account with no personal data in it.
- Your email address on the unsubscribe suppression list, so a future import cannot re-add you.
- [MERCHANT OF RECORD]'s own records of the payment. They are a separate controller with their own retention rules, and we cannot delete their copy for you. Their notice tells you how to ask them.
Deleting your account ends your access to the course and is not reversible. If you only want to stop the emails, unsubscribe instead and keep the course.
11 · Your rights, and how to use them
Wherever you live, you can ask us to: show you what we hold, give you a machine-readable copy, correct something wrong, delete it, restrict what we do with it, object to us relying on legitimate interests, or withdraw a consent you gave.
Email hello@lagoon.academy with "Data request" in the subject, from the address on the account. We will ask you to log in to prove it is you — never for a photo of an ID document. We answer within 30 days and usually within five working days, and we do not charge for it.
You can complain to a regulator without asking us first. In the EU it is your national data protection authority, in the UK the Information Commissioner's Office. We would rather hear from you directly, and we will not treat a complaint as a reason to close your account.
12 · How we protect it
- Every page and every request is served over HTTPS.
- Passwords are stored only as salted one-way hashes. We cannot read yours, and neither can anyone who takes the database.
- Login tokens are stored hashed too, so a stolen database does not hand over live sessions.
- The login cookie is not readable by scripts and is not sent to other sites.
- No card data and no billing address is ever stored on our server.
- Administrative access is limited to the owner of the business, over an authenticated connection.
- Backups are encrypted, and restoring one is tested rather than assumed.
No system is perfectly secure, and anyone who tells you otherwise is selling something. If you find a weakness, section 13 and the contact page tell you how to report it and what we promise in return.
13 · If something leaks
If personal data is exposed, we will tell the relevant regulator within 72 hours of becoming aware of it, and email the people affected. The email will say what happened, what data was involved, what we have done and what you should do — including the uncomfortable parts, and including the parts we do not know yet.
14 · Children, and changes to this notice
The course is sold to people aged 16 and over, and we do not knowingly hold data about anyone younger. If you believe a child has an account, email us and we will delete it.
We update this notice when what we do changes. The version and date at the top tell you which one you are reading. If a change materially affects you, we email you before it takes effect rather than editing the page quietly.
This document is written in English. The Russian translation is provided for convenience only; if the two versions differ, the English version governs.
Version 1.0 · 30 September 2026 · Terms of sale · Refund policy · Contact