Privacy policy
Last updated 2026-08-16
1.Who is responsible
The data controller for the Saasworld service is [Company legal name], [Registered address]. Privacy questions and requests: [privacy email]. If we appoint a data protection officer, their contact will appear here.
This policy is written to meet the GDPR / UK GDPR because our database lives in the EU and many of our learners do too. It applies to everyone who uses the Service, wherever they are.
2.What we collect, why, and for how long
We collect what the product needs to work and very little else. There is no third-party advertising or tracking on the site.
| What | Why | Legal basis | How long |
|---|---|---|---|
| Email address (and, with Google login, your Google account id, name and avatar URL) | To create and secure your account, sign you in with a one-time code, and reach you about billing and your account. | Contract | Life of the account + 30 days |
| Display name and avatar | Shown to you in the app. Not public. | Contract | Life of the account |
| Onboarding answers — where you heard of us, motivation, experience level, goal, minutes per day | To build your course path and pick a daily goal. Also, aggregated, to see which paths work. | Contract; legitimate interest (product improvement) | Life of the account |
| Learning progress — exercises seen, scores, hints taken, skips, chapters cleared, badges, XP, streak, daily activity, review items for the drill | It is the product: what you've done, what to show next, what to review. | Contract | Life of the account |
| Written answers to explain-tasks and questions asked of the tutor | To grade them and give feedback. Sent to Anthropic's API for that purpose (see Processors). | Contract | Score kept for the life of the account; the answer text is not stored by us after grading. Anthropic's API retention applies to the request (see below). |
| Course ratings and written feedback | To improve the courses. | Legitimate interest | Life of the account, then anonymised |
| Plan and purchases — Pro subscription status, add-ons owned, provider, timestamps | To unlock what you've paid for and keep accounting records. | Contract; legal obligation (bookkeeping) | Life of the account; billing records for the statutory bookkeeping period |
| Settings — teacher, daily goal, email notifications, theme | To remember how you like the app. | Contract | Life of the account (theme: your browser only) |
| Product analytics events — page and funnel events with a random anonymous id (signed out) or your user id (signed in), the event name and small properties like a course slug | To see where people get stuck and which courses get finished. Stored in our own database, not sent to an analytics vendor. | Legitimate interest | 24 months, then deleted or aggregated |
| Server logs — IP address, user agent, request path, timestamps | Security, abuse prevention, debugging. Kept by our hosting provider. | Legitimate interest | Up to 30 days |
| Emails we send you and whether they bounced | Sign-in codes; a nudge if you lapse (at most one per 14 days, off in Settings); account and billing notices. | Contract; legitimate interest (the nudge, with an easy opt-out) | Delivery logs up to 30 days at the email provider |
Signed out, we keep almost nothing: a cookie that marks the one free task as used, a random anonymous id in your browser for analytics, and your progress in your browser's localStorage (which we don't see until you sign up and it's merged into your account).
3.Legal bases
- Contract (GDPR art. 6(1)(b)) — the processing needed to give you the Service you signed up for: account, progress, grading, purchases.
- Legitimate interest (art. 6(1)(f)) — product analytics in our own database, security logs, course feedback, and one lapse email per 14 days with a one-click unsubscribe. We've balanced these against your interests; none involves profiling with legal effects, and you can object at any time.
- Legal obligation (art. 6(1)(c)) — keeping billing records for as long as tax and bookkeeping law requires.
- Consent (art. 6(1)(a)) — not currently relied on for anything; if we ever add non-essential cookies or marketing email, we'll ask first.
4.AI processing of your answers
When you submit a written answer to an explain-task or ask the tutor a question, the text you typed — together with the task, the lesson excerpt and a rubric — is sent to Anthropic's Claude API, which returns a score, feedback, or a hint. We do not send your name, email or user id with it. Anthropic processes API inputs to provide the service and, per its usage policies, does not use them to train its models; retention is limited to what its API terms state.
Practical advice: keep answers about the task. Don't paste personal data, secrets or confidential material into them. The grade is automated and used only inside the Service (XP, progress); a person will review any grade you dispute — write to [support email].
5.Who we share data with (processors)
We don't sell personal data and we don't share it with advertisers. These companies process it on our behalf, under data-processing agreements, only to provide the Service:
| Processor | What they do for us | Where / transfer basis |
|---|---|---|
| Supabase, Inc. | Database, authentication and storage for the whole Service. All account and progress data lives here. | EU — AWS eu-west-3 (Paris) |
| Vercel, Inc. | Hosts and serves the website and API; keeps request logs. | Global edge network; functions run in the region we configure. Vercel is DPF-certified and offers EU SCCs. |
| Anthropic, PBC | Grades explain-task answers and powers the tutor and some hints. Receives the answer or question text, the task and rubric, and no account identifiers. | United States. Anthropic's commercial API does not train on API inputs; standard retention is limited (see Anthropic's data policy). Transfers rely on the EU–US Data Privacy Framework and/or SCCs. |
| Resend, Inc. | Sends transactional email — sign-in codes, lapse nudges, account notices. Receives your email address and the message. | United States; DPF / SCCs. |
| Google LLC (only if you sign in with Google) | OAuth identity provider. We receive your Google account id, email, name and avatar; Google sees that you signed in to Saasworld. | United States; DPF / SCCs. Governed by Google's privacy policy. |
| [Payment processor — not yet connected] | Will handle card payments when connected; we'll update this policy before that goes live. | — |
We may also disclose data if the law requires it, to protect the Service or its users from abuse, or as part of a merger or sale — in which case this policy continues to apply and we'll tell you.
7.International transfers
Your account data is stored in the EU (Paris). Some processors — Vercel, Anthropic, Resend, Google — are in the United States and receive the limited data described above. Those transfers rely on the EU–US Data Privacy Framework where the processor is certified and otherwise on the European Commission's Standard Contractual Clauses (and the UK Addendum), with supplementary measures where needed. Copies of the relevant clauses are available on request.
8.Retention and deletion
We keep account data for as long as you have an account. When you delete your account (email [support email] from your account address; a self-serve button is planned), we delete your profile, progress, answers, review items and onboarding answers within 30 days. Billing records are kept for the statutory bookkeeping period; analytics events are stripped of your user id; backups roll over within 30 days.
Accounts with no sign-in for 3 years may be deleted after we've emailed you a warning.
9.Your rights
Under the GDPR (and similar laws elsewhere) you can ask us to:
- Access — get a copy of the personal data we hold about you;
- Rectify — fix anything wrong (name, email and settings you can change yourself in the app);
- Erase — delete your account and data;
- Restrict or object — including objecting to legitimate-interest processing such as analytics or the lapse email;
- Port — receive your data in a machine-readable format (JSON);
- Withdraw consent — where processing is based on it.
Write to [privacy email]. We answer within a month. You can also complain to your local supervisory authority — for the EU, the list is at edpb.europa.eu; in the UK, the ICO.
10.Security
Data is encrypted in transit (TLS) and at rest by our database provider. Access to your rows in the database is enforced by row-level security policies, so even our own API cannot read another user's data with your session. Sign-in uses one-time email codes or Google OAuth; we don't store passwords. No system is perfect: if we learn of a breach affecting you we'll notify you and the regulator as the law requires.
11.Children
The Service is for people aged 16 and over. We don't knowingly collect data from anyone younger; if you believe a child has created an account, tell us at [privacy email] and we'll delete it.
12.Changes to this policy
We'll update this policy when the Service changes — for instance when a payment processor is connected. Material changes are announced by email or in the app before they take effect. The date at the top is the current version.
13.Contact
[Company legal name], [Registered address]. Privacy: [privacy email]. General: [support email].