Privacy notice
Last updated 18 November 2026
On this page
- Who we are
- What we collect
- Why we use it, and our lawful basis
- Our legitimate interests
- Do you have to give us your data?
- Who else handles your data
- Data leaving the UK
- How long we keep it
- Deleting your account
- How we keep it safe
- Automated decisions
- Your rights
- How to use your rights
- Complaints
- Cookies
- Children
- Changes to this notice
Who we are
Lazy Sailors Club is a trading name of Lazy Sailors Club Ltd, a private limited company registered in England and Wales (company number 17500955), registered office Suite RA01, 195-197 Wood Street, London E17 3NU. We are the controller of the personal data described here, which means we decide how and why it is used.
We are registered with the Information Commissioner's Office (ICO), the UK data protection regulator, under number ZC271454.
For anything about your data, email admin@lazysailorsclub.com. It is our only contact address. We haven't appointed a data protection officer, as a business of our size and type isn't required to.
What we collect
What you give us
- Your email address and password. The password is stored hashed (scrambled one way) by our sign-in provider, Supabase. We never see it.
- Your phone number. You give it when you create an account (it's required). We use it to contact you about your account if we need to. We don't use it for marketing, never share it, and it's deleted with your account.
- Your study progress and settings, such as your study plan, what you've covered, your quiz and mock exam scores, and any notes you write on questions.
- About you, if you tell us. Your name, college and how you heard about us, and, if you used the three questions on our home page (what you're here for, when your orals are, how much time you have a day), your answers. We use them to know who our members are and which ways of finding us work. They're optional, never shared, and deleted with your account.
- Your email address, if we give you a free month. If we set up a free month for you before you have an account, we store the address you gave us so the month can be applied when you sign in with it. If it isn't used within a year it lapses; you can ask us to delete it sooner.
- A calendar link, if you make one. If you press Add to calendar, we create a private link that your calendar app (for example Apple or Google Calendar) uses to fetch your study plan's dates and task names and your orals date. Whoever has the link can see those, and nothing else, so only add it to your own calendar. Your calendar provider then holds a copy under its own privacy terms. You can turn the link off at any time in the app (Plan or Settings, then Stop sharing); it is also deleted with your account.
- Your agreement at checkout. Before you pay, you tick a box agreeing to the Terms, expressly asking for immediate access to the content and acknowledging that you lose your 14-day right to cancel once access starts. We record that tick with your account, the version of the Terms, the date and time, your IP address and your browser's user agent (the line of text that says which browser and device you're using).
- Fault reports. If you report an error, we store the kind of fault, your description (up to 2,000 characters) and the details the report form shows you before you send it: the screen you were on, the question (if you reported one) and where you opened the form from, the app build, screen size, theme, browser and time. Answer text is never stored. The report is linked to your account and emailed to our inbox (the email carries your account ID, not your email address). Your IP address is stored only as a salted hash (a scrambled form that doesn't show the address), used to limit how many reports can be sent.
- Emails you send us, and whatever is in them.
What's created as you use the service
- Content access log. The app fetches content one topic at a time. Each fetch is logged with the time and topic (for a search, the words you searched for) against a pseudonymised identifier: a salted hash of your account ID, not your name or email. In law that's still your personal data, because we could link it back to you, but it keeps the day-to-day log from naming anyone.
- Where you came from, when you sign up. The website that sent you to us (just its name, such as google.com, not the page) and, if the link you followed had one, the campaign tag on it (for example, which post you clicked). We record it once, when you create your account, and keep it with your account. We don't track you across other sites and we don't use it for advertising.
- Sign-in records. When you sign in, and when signing in on another device signed a previous one out.
- Limit records (we call them abuse flags). A note when an account trips one of our anti-sharing or anti-scraping checks.
- Subscription records. Whether you're subscribed, your renewal dates, and a record of each renewal reminder email we've sent you.
- Error logs. Technical records of things that went wrong on the site.
- Connection data. Like any website, your browser sends its IP address and details about itself when it connects. Our hosting, database and email providers use these to run the service and keep it secure, and keep them in their own technical logs (see How long we keep it).
What we get from Stripe
Stripe runs the checkout and takes your payment. It tells us your Stripe customer ID, the status of your subscription and payments (for example paid, failed, refunded or cancelled) and the dates involved. We keep a log of these payment notifications.
What we don't collect
Your card details: Stripe handles the payment and we never see or store them. We don't ask for any sensitive (“special category”) data, and we collect nothing for advertising. Visits to our public pages are counted without cookies and without identifying you (see Counting visits below).
Why we use it, and our lawful basis
Data protection law says we need a lawful basis for each use. Contract means we need the data to provide what you signed up for. Legal obligation means the law requires it. Legitimate interests means it's necessary for an interest of ours that we've weighed against your privacy (see the next section).
- Running your account
Data: email address, phone number, password (stored hashed), your signed-in session.
Basis: contract. - Providing the study app
Data: study progress and settings, quiz and mock exam results; fetching content topic by topic.
Basis: contract. - Your subscription and payments
Data: we send Stripe your email address and an account reference so it can set up your checkout; we keep your Stripe customer ID, subscription status and the payment notification log.
Basis: contract. - Service emails
Data: email address. Your subscription confirmation (which repeats what you agreed to at checkout), password reset, an email to confirm your address if we ask for one, and a renewal reminder before a renewal payment in every six-month period, plus our record that each reminder was sent.
Basis: contract. - Replying when you email us
Data: your email and whatever you tell us.
Basis: contract when it's about your account or subscription; otherwise legitimate interests (answering people who contact us). - Tax and accounting records
Data: Stripe customer ID and payment records.
Basis: legal obligation. - Evidence of your checkout agreement
Data: the tick record (Terms version, date and time, IP address, user agent). It shows you expressly asked for immediate access and acknowledged losing the 14-day right to cancel, which the Consumer Contracts Regulations 2013 require before we can supply digital content straight away.
Basis: legitimate interests (being able to show what you agreed to if there's ever a dispute). - Handling your data protection requests and complaints
Data: whatever the request needs.
Basis: legal obligation. - Security, stopping account sharing and scraping, and enforcing our Terms
Data: one active device per account, sign-in records, request limits, the content access log, and limit records. We use these records if we need to suspend or close an account for sharing, scraping, automated access, reselling or getting round our protections.
Basis: legitimate interests. - Fixing faults
Data: fault reports and error logs.
Basis: legitimate interests. - Backups
Data: a nightly copy of our database.
Basis: legitimate interests. - Counting visits to our public pages (the home page, pricing, sign-in, the free-month page
and these legal pages; never the study app)
Data: the page visited, the site that sent you, your country, and your device, browser and operating system type. Vercel Web Analytics collects this without cookies and without storing anything on your device, and it can't tell who you are or follow you to other sites.
Basis: legitimate interests (knowing which pages work, so we can improve them). - Knowing which ways of finding us work
Data: how you heard about us, your home-page answers, the site and campaign tag that sent you.
Basis: legitimate interests (knowing which of our free posts and pages bring members, and what members need, so we spend time on what works).
We don't rely on your consent for anything at the moment, because we send no marketing and use no non-essential cookies.
Our legitimate interests
- Protecting the content and the business. The answers, mind maps and question rankings are what subscribers pay for. Account sharing, scraping, automated downloading and reselling would undermine the service and its price. One device at a time, the request limits and the logs are how we prevent that, and how we enforce our Terms and Acceptable use policy.
- Keeping the service and your account secure.
- Keeping the service working and the answers accurate, by fixing the faults you report and the errors our logs catch.
- Being able to recover if something fails or data is lost, through backups.
- Answering people who contact us.
- Knowing what works. Which sites and posts bring people to us, and what they're preparing for, so we can improve the site and our free material. We keep only the site name, never the page, and only from the moment you sign up.
We've weighed these against your privacy. We log only what these checks need, use a pseudonymised identifier in the content access log, store fault-report IP addresses only as hashes, delete logs on a fixed schedule (below), and use none of it for advertising or marketing. You can object to any of this; see Your rights.
Do you have to give us your data?
- You need an email address and password to create an account. Without them we can't provide the service.
- To subscribe, you need to tick the checkout box and pay through Stripe. Without that we can't sell you a subscription.
- The records created as you use the service (sign-ins, the content access log, limit records) are part of how it works, so it can't be used without them.
- Fault reports and emails to us are up to you.
No law requires you to give us any of this. It's needed only for the contract.
Who else handles your data
We use a small number of providers. These act as our processors: they handle data only on our instructions, under contracts that require them to protect it.
- Supabase Inc. provides our database, sign-in system and file storage. US company; your data is held in its EU (Ireland) region.
- Vercel Inc. hosts the website and runs the code behind it, and counts visits to our public pages (Vercel Web Analytics, cookie-free). US company with a global network, so your requests may be handled outside the UK.
- Resend (Plus Five Five, Inc.) sends our emails: subscription confirmations, password reset, address confirmation, renewal reminders, and fault-report notifications to our inbox. US company; emails are sent from its EU region.
- Zoho Corporation runs our inbox at admin@lazysailorsclub.com, so it holds emails you send us and the fault-report notifications. EU data centre.
- GitHub Inc. stores our nightly database backups, encrypted at rest, for 30 days. US company.
Stripe. Payments are handled by Stripe (Stripe Payments Europe and Stripe, Inc.). We are the seller. For payment data, Stripe acts as an independent controller, not our processor, and its own privacy notice (on its website) applies. We send them your email address and an account reference. They send us your customer ID and the status of your subscription and payments.
Anyone the law requires us to share with, for example HMRC, or anyone named in a court order.
We don't sell your data, and we don't share it with anyone for their marketing or advertising.
Data leaving the UK
Our database is held by Supabase in its EU (Ireland) region. Several of our providers are US companies or handle data in other countries:
- Vercel serves the site from a global network, so your requests may be handled outside the UK, including in the US.
- Supabase, Resend and GitHub are US companies, so data they handle may be accessed or stored in the US.
- Zoho holds our inbox in its EU data centre, and Resend sends our emails from its EU region. UK law recognises the EU and EEA as giving adequate protection.
- Stripe handles payment data in the US and elsewhere, under its own privacy notice.
Where we send your data to the US, we rely on the UK Extension to the EU–US Data Privacy Framework if the provider is certified under it. If not, we rely on the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses. Email us and we'll tell you which applies to each provider and send you a copy of the safeguards.
How long we keep it
An automatic job runs every day and deletes records when their time is up.
- Content access log: 90 days.
- Error logs: 90 days.
- Sign-in records: 12 months.
- Payment notification log: 12 months.
- Limit records (abuse flags): 12 months.
- Fault reports: 24 months.
- Renewal reminder records: 24 months.
- Your account (email, phone number, progress, settings, home-page answers, how you found us and subscription records): for as long as your account exists. If your subscription ends, we keep your account until you delete it, so you can pick up where you left off.
- After your account is deleted: only your Stripe customer ID and your checkout agreement records, kept under a hash rather than your account, for 6 years from the end of the UK tax year (which ends on 5 April) in which your account is deleted. That's for HMRC record-keeping, and as evidence that you asked for immediate access.
- Backups: taken nightly, each kept for 30 days and then deleted. Deleted data can therefore survive in a backup for up to 30 days.
- Emails you send us, and fault-report notifications in our inbox: our mail provider doesn't delete them automatically. We keep them while we need them to deal with what you asked and any follow-up, and delete them within 24 months of the last message in the conversation.
- Technical logs kept by our hosting, database and email providers: Vercel (hosting) keeps request logs for up to 1 day; Supabase (database and sign-in) keeps its logs for up to 7 days; Resend (email) keeps a record of each email it sends, including the address and content, for 30 days.
Stripe decides how long it keeps payment data, as its privacy notice explains.
Deleting your account
You can do it yourself on the Account page: choose to delete your account, enter your password and type DELETE. This:
- cancels your Stripe subscription immediately, with no refund of the current period unless the law requires one (see Refunds);
- deletes your account, email address, progress and settings;
- keeps only your Stripe customer ID and checkout agreement records, under a hash, for the period above.
Some records sit outside your account and are deleted on their normal schedule rather than straight away: the pseudonymised content access log, and sign-in records, limit records and fault reports, which are unlinked from you (the link to your account is removed) when the account is deleted. Backup copies are gone within 30 days.
How we keep it safe
- Connections to the site are encrypted (HTTPS).
- Your password is stored hashed by Supabase. We never see it.
- We never see or store your card details.
- The database only lets your browser read your own subscription, progress and scores, and only from the device that's currently signed in. Logs, payment records and fault reports can't be read from a browser at all.
- The content access log uses a pseudonymised identifier, and fault-report IP addresses are stored only as hashes.
- Only one device can be signed in to your account at a time. A device that gets signed out is shown a message, so if someone else signs in to your account, you'll notice.
- Backups are encrypted at rest and deleted after 30 days.
- Records are deleted automatically on the schedule above.
No system is perfectly secure. If a breach puts your data at risk, we'll report it to the ICO within 72 hours where the law requires, and tell you without undue delay if it's likely to put you at high risk.
Automated decisions
We don't make any decisions about you based solely on automated processing that have legal or similarly significant effects on you.
Some things do happen automatically:
- Request limits. Each account can fetch content up to 30 times a minute and 300 times a day. If you reach a limit, access to content pauses automatically and temporarily. Both limits are rolling: the per-minute limit counts the last 60 seconds and the daily limit the last 24 hours, so access comes back as older requests drop out of the count. Nothing else changes. Your account, subscription and progress are untouched. The first time in any 24 hours that an account reaches the daily limit, we keep a limit record. If you think you've been paused by mistake, email us.
- One device at a time. Signing in on a new device signs out the previous one, which shows a message saying so. You can sign back in whenever you like.
- Payments. If a payment fails, access continues for up to 7 days after the end of the paid period while Stripe retries it. If the current month's payment is refunded in full, access stops straight away.
None of these suspends or closes your account. Decisions to suspend or close an account (for sharing, scraping, automated access, reselling or getting round our protections, as the Acceptable use policy explains) are made by a person, not automatically.
Your rights
You have the right to:
- be informed about how we use your data, which is what this notice is for;
- access your data: get a copy of it and information about how we use it;
- rectification: have inaccurate or incomplete data corrected;
- erasure: have your data deleted, unless we have to keep it (for example the tax and checkout records above);
- restriction: ask us to limit what we do with your data, for example while we check whether it's accurate or consider an objection;
- portability: get the data you gave us in a machine-readable format, or have us send it to someone else where that's technically feasible;
- object to anything we do on the basis of legitimate interests. We must then stop unless we have compelling grounds that override your interests, or need the data for legal claims. One device at a time and the request limits are part of how the service works for every subscriber, so if we can't switch them off for you, we'll explain why;
- withdraw consent at any time, where we rely on it. We don't at the moment. If we ever do, withdrawing will be as easy as giving it, and won't affect anything done before;
- not be subject to automated decisions with legal or similarly significant effects. We don't make any (see above);
- complain, to us and to the ICO (see below).
How to use your rights
- Get a copy of your data: on the Account page, choose Download my data. You'll get a JSON file (a standard, machine-readable format) containing your account details (account ID, email address, when you joined and last signed in), your subscription records, your study progress and settings, your quiz and mock exam results, your checkout agreement records (including the IP address and user agent), your Stripe customer ID, your fault reports and your sign-in history. It doesn't include the content access log, limit records or renewal reminder records; for a full copy, including those, email us.
- Delete your account: on the Account page (see Deleting your account above).
- Anything else: email admin@lazysailorsclub.com, ideally from the address on your account. We may ask you to confirm it's you.
It's free. We'll reply within one month. The month starts once we have your request and anything we reasonably need to confirm who you are, and it pauses if we need you to clarify what you're asking for. If a request is complex, or you've sent several, the law lets us take up to two more months; we'd tell you within the first month. As the law allows, we may refuse, or charge a reasonable fee for, a request that is manifestly unfounded or excessive, and we'd explain why.
Complaints
If you're unhappy with how we've handled your data, please tell us first: email admin@lazysailorsclub.com with “Data complaint” in the subject. We'll acknowledge it within 30 days, look into it without undue delay, keep you updated and tell you the outcome.
You also have the right to complain to the regulator, the ICO, at ico.org.uk/make-a-complaint or on 0303 123 1113.
Cookies
We use only cookies that are strictly necessary for the service to work. These are our own
(first-party) Supabase sign-in cookies, named like
sb-<project-ref>-auth-token (sometimes split into parts ending .0, .1), which
keep you signed in and are deleted when you sign out (otherwise your browser keeps them for up
to 400 days after your last visit), and a
short-lived cookie used during sign-in and password reset. There are no analytics or advertising
cookies, so there's no cookie banner. Details are on the Cookies page.
Children
Lazy Sailors Club is a study aid for people preparing for a professional exam. It isn't aimed at anyone under 16, and you must be 16 or over to subscribe. We don't knowingly collect data from anyone younger. If you think a child has given us their data, email us and we'll deal with it.
Changes to this notice
When what we do changes, we'll update this notice and the date at the top. Before we use your data for a new purpose, we'll tell you, by email if you have an account.
Questions about your data: admin@lazysailorsclub.com