Your personal information

Privacy notice

What TradeTraining collects about you, why, who else handles it, how long we keep it, and the rights you have.

Takes effect: [EFFECTIVE DATE]. Written on 22 October 2026 from what the site and app actually do.

This page describes what the site actually does, but it has not yet been reviewed by a solicitor. Details shown in [square brackets] are still being filled in or confirmed.

Who we are

TradeTraining, the website at www.tradetraining.app and the app you can install from it, is run by [OPERATOR NAME] (“we”, “us”). We decide how and why your personal information is used, which makes us its “controller” under UK data protection law: the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

Run by
[OPERATOR NAME]
Address
[REGISTERED ADDRESS]
Email
[CONTACT EMAIL]
ICO registration
[ICO REGISTRATION NUMBER]

For anything about your personal information, email [CONTACT EMAIL]. More ways to reach us are on our contact page.

The short version

  • You can try lessons as a guest without giving us an email address.
  • We keep your answers and progress so the app can work: your learning path, XP, streaks, leagues and reviews.
  • A few service providers help us run the app, and every one is listed below. We do not sell your personal information.
  • Analytics in your browser (PostHog, and Google Analytics on our public pages), and advertising tags from Meta and Google, run only if you say yes, and you can change your mind at any time.
  • Our server also records some things you do in the app, such as starting as a guest or keeping a streak, to run and improve it. That stores nothing on your device, and you can object to it.
  • You can ask to see, correct, download or delete your information, and you can complain to the Information Commissioner’s Office (ICO).

What we collect, and why

The law asks us to name a “lawful basis” for each use of your information. Ours are: contract (we need it to provide something you asked for), legitimate interests (a reasonable business need that does not override your rights), consent (you said yes and can take it back) and legal obligation (the law requires it).

When you visit the website

What
Our hosting provider, Vercel, handles every request your browser makes. That includes your IP address, browser and device details, the page you asked for and the time.
Why
To show you the pages, keep the site secure and find faults.
Lawful basis
Legitimate interests: running a website that works and is secure.

When you start as a guest

What
A guest account with a random identifier and a made-up nickname, such as “Jolly Sparky”. It has no real email address. The sign-in cookie on your device is the only way back into it, so if you clear your cookies or sign out before adding an email, we cannot reconnect you to that progress.
Why
So you can try lessons straight away and keep your progress while you do.
Lawful basis
Contract: providing the service you asked for.

When you create an account or save your progress

What
Your email address, a password (stored by Supabase in a scrambled form that we cannot read) and the display name you choose. Saving a guest account adds these to the same account, so your progress carries over. If you choose to continue with Google or Facebook instead, you sign in on Google's or Facebook's own page and they tell us your name, your email address and, where they share one, a link to your profile picture. We use the email address for your account, keep a made-up league name for you rather than your real name, and do not show the picture. We never post anything for you and do not ask for your contacts or friends list. Saving a guest this way also keeps the same account and progress. Before an email address counts as yours, we email it a link or a 6-digit code to check: until the code is used or runs out (15 minutes), we keep the address you typed and a scrambled copy of the code, and a count of recent attempts so the forms cannot be misused.
Why
So you can sign back in, on this device or another.
Lawful basis
Contract: providing the account you asked for.

When you use the app

What
Your answers to the opening questions (why you are here, your experience and your daily goal) and the course you picked; your settings, including timezone and email choices; each answer you give and whether it was right; the lessons and teaching cards you have done; XP, streaks, energy, crowns and quests; mock exam attempts; and the schedule for reviewing what you have learnt. If you use leagues or friends: your league, your weekly XP, and your friend requests, friends and blocks. If you ask us to delete your account: the request and any reason you give. If you send feedback from the app: what it is about, anything you type, the page, your screen size and the app version, and for a question you report, which question it was and the answer you gave; we may copy it to our private issue tracker on GitHub without your name, email address or account ID.
Why
To run your learning path, save your progress, decide what to review and when, and run leagues. We also look at how all learners answer each question, without names, to find questions that are confusing or wrong.
Lawful basis
Contract, for running your account. Legitimate interests, for improving questions from combined answer patterns.

When you use an AI feature

What
When AI features are switched on, we send some learning data to OpenRouter, which runs an AI model for us. For a practice summary: counts, percentages, topic names and your experience level. For an explanation of a question or feedback on a written answer: the question, the answer you gave, your experience level and, for a written answer, the text you typed. Explanations and feedback run only on questions that have passed trade review, and none has yet. We never send your name, email address or account ID, and the app refuses to send any request that looks as if it contains one. Please do not type personal details into written answers.
Why
To explain answers and summarise your practice. The AI does not make decisions about you: answers, including written ones, are marked by fixed rules in our code, not by the AI.
Lawful basis
Contract: providing a feature you use.

Emails

What
Streak reminders: if your account has an email address and “Streak reminders” is ticked in Profile settings, we email you on evenings when you have not practised. The box starts unticked. After your first finished lesson, we ask once whether you want to turn it on. You can change it at any time in Profile settings or use the one-click unsubscribe link in a reminder email. Reminders go only to an address you have confirmed is yours. Guest accounts never get emails. There is also a “Product updates” setting, but we do not send product updates at the moment. Account emails, such as confirming your address or resetting your password, are sent when you ask for them.
Why
To help you keep the learning habit you set up, and to let you into your account.
Lawful basis
Legitimate interests, for streak reminders, which you can switch off at any time. Contract, for account emails.

Analytics, if you accept analytics cookies

What
We use PostHog to see how the app is used. In your browser, and only if you accept analytics cookies, it records events such as starting or finishing a lesson, whether an answer was right, onboarding choices and opening the Plus page, with the page addresses, browser and device type that go with them and an approximate location worked out from your IP address; on our ad landing page it also records the ad campaign that brought you and the website you came from. Once you start as a guest or sign in, these events are linked to your account ID, so we can see which visit led to it; after you sign out, your browser is given a new random ID. It records nothing by itself: no clicks, no session recordings. This site sends that data to PostHog’s EU Cloud, in Frankfurt, Germany. On our public pages, and only while you are signed out, we also use Google Analytics, again only if you accept analytics cookies. It records the pages you view and their titles, with any ad campaign labels and the version of our landing page in the page address, and Google’s own ad-click ID only if you also accept advertising cookies, but no other part of it, the website you came from, your device, browser and language, and an approximate location worked out from your IP address. It sets its own cookies, _ga and _ga_<container-id>, to tell visits apart. It never runs inside the app or on the sign-in, sign-up, password, account-deletion or content-management pages, and records nothing else: no clicks and nothing you type. Its random ID is not replaced when you sign out, so later visits from the same browser can still be linked to the account it was linked to; turning analytics off deletes it. While our server’s Google Analytics events are switched on, it also tells Google Analytics when you start as a guest, finish the opening questions or finish your first lesson, so those steps join the visit that led to them. It does this only if you accepted analytics cookies and Google Analytics had already set its _ga cookie on one of our public pages, and it sends the step’s name, the random ID and current visit from Google Analytics’ cookies, and your account ID; for a guest start, also which of our public pages you started from and which version of it you saw. Your account ID is a random code, never your email address or name. We send it so we can link Google Analytics data to an account, and if you ask us to delete your account we also ask Google to delete the Google Analytics data linked to it. We never send Google your answers, scores, which lesson it was, or your IP address.
Why
To find problems, improve lessons, see how people find our public pages, and see which ads bring people who go on to learn.
Lawful basis
Consent: change your mind at any time in .

Events our server records

What
Whatever you choose in the cookie banner, our server records some product events for every account and sends them to PostHog, linked to your account ID: for example finishing a review, keeping a streak, earning a crown or starting as a guest. This uses no analytics or advertising cookie and stores nothing on your device. What brought you to us, such as the ad campaign and the page you started from, is added to them only if you accept analytics cookies. Google Analytics is not one of these: our server tells it about a few steps only if you accept analytics cookies, as described under analytics above.
Why
To run the service and improve it: to find faults and see whether people keep learning.
Lawful basis
Legitimate interests: running and improving the service. You can object to this (see your rights below).

The bot check when you start as a guest

What
Every guest start creates a real account, so the form has a hidden field that only automated scripts fill in, and, when our bot check is switched on, Cloudflare Turnstile checks that you are a person. It reads your IP address, your browser's user agent and the fingerprint of its secure connection, and gives our server a one-time pass that our server confirms with Cloudflare.
Why
To stop automated scripts creating fake accounts.
Lawful basis
Legitimate interests: keeping the service secure and free of fake accounts.

Advertising

What
Only if you accept advertising cookies. In your browser, the Meta Pixel and Google's ads tag load only on our public pages, and only while you are not signed in, as a guest or otherwise: never in the app, on the sign-in, sign-up and password pages, on the account-deletion page, or on content-management pages. There, Meta is told which pages you visit, and Meta and Google are told when you start as a guest. When you start as a guest, finish the opening questions or finish your first lesson, and again only if you accept advertising cookies, our server also tells Meta directly (its Conversions API), with your IP address, browser details and Meta's cookies or ad-click ID; without that consent our server sends Meta nothing. Meta and Google get the event's name and an ID, never your answers or scores, with your IP address, browser details and their own cookies. We never send them your email address or phone number.
Why
To find out which of our ads work, and to show them to people likely to be interested.
Lawful basis
Consent. Nothing loads until you choose, and you can change your mind at any time in .

Paying for Plus

What
Plus, the optional paid subscription, is not on sale yet. When it is, Stripe will take payments: you will type your card details into Stripe's own page, so we never see your full card number. We will keep a Stripe customer reference, whether your subscription is active, and the payment records the law requires us to keep.
Why
To sell and manage Plus subscriptions.
Lawful basis
Contract, for the subscription. Legal obligation, for tax and accounting records.

When you contact us

What
Your email address and whatever you tell us.
Why
To reply, and to fix anything you report, such as a mistake in a lesson.
Lawful basis
Legitimate interests: answering you and keeping our content accurate.

Security and preventing misuse

What
Sign-in records kept by Supabase, and a daily count of AI requests for each account.
Why
To protect accounts, and to stop the AI features being misused or running up costs.
Lawful basis
Legitimate interests: keeping the service secure and affordable.

We do not ask for sensitive information, such as your health, religion or ethnicity. Please do not include it in anything you type into the app.

What other learners can see

  • In a league, the other learners in it see your display name and your XP for the week.
  • Your friends also see your streak.
  • Other learners can find you by searching for your display name, to send a friend request. You can block someone from the Friends page.

Your display name is whatever you choose in Profile settings, so you do not have to use your real name. Guest accounts start with a made-up nickname.

Who we share it with

These companies handle personal information for us. Each receives only what it needs for its job. We do not sell your personal information.

Vercel

In use

What it does
Hosts the website and app, runs our server code and runs our scheduled jobs, such as the evening streak-reminder check.
What it receives
Everything your browser sends to the site passes through Vercel: your IP address, browser and device details, the pages you ask for and when. It keeps logs of those requests for [HOW LONG HOSTING LOGS ARE KEPT].
When
On every visit.
Where
Vercel is based in the United States. Our ready-made pages and files, and a check that refreshes your sign-in each time you open a page, are handled across Vercel's worldwide network, usually at the location nearest to you. Everything else our server code does on Vercel, including its scheduled jobs, runs in Vercel's Dublin region, in Ireland ([CONFIRM SERVER REGION]).
Its role
Service provider (a processor): it handles the data only on our instructions.

Vercel: privacy policy

Supabase

In use

What it does
Runs our database and sign-in. It stores your account, settings and learning progress, keeps you signed in, powers the live league tables, and runs our scheduled streak, energy and league jobs.
What it receives
Your email address if you add one, your password in a scrambled (hashed) form that we cannot read, your display name, and the learning records described in this notice. It keeps security logs of sign-ins. Supabase writes the emails that confirm your address or reset your password, and Resend (below) delivers them ([CONFIRM WHO SENDS SIGN-IN EMAILS]).
When
For every account, including guest accounts.
Where
Supabase is based in the United States. Our database is hosted on Amazon Web Services in Ireland, in the eu-west-1 region ([CONFIRM DATABASE REGION]).
Its role
Service provider (a processor): it handles the data only on our instructions.

Supabase: privacy policy

PostHog

In use

What it does
Product analytics: shows us how the app is used, so we can find problems and improve lessons.
What it receives
From your browser, only if you accept analytics cookies: events such as starting or finishing a lesson, whether an answer was right, onboarding choices and opening the Plus page, the page addresses, browser and device type that go with them, an approximate location worked out from your IP address ([CONFIRM WHETHER ANALYTICS KEEPS IP ADDRESSES]), and, on our ad landing page, the ad campaign that brought you and the website you came from. Once you start as a guest or sign in, these browser events are linked to your account ID; after you sign out, your browser is given a new random ID. From our server, for every account: events such as finishing a review, keeping a streak, earning a crown or starting as a guest, linked to your account ID. The ad campaign that brought you and the page you started from are added to the guest start only if you accept analytics cookies. Session recording: off, and our code keeps it off.
When
Events from our server: for every account. In your browser: only if you accept analytics cookies.
Where
Our code sends analytics to PostHog's EU Cloud in Frankfurt, Germany, unless it is configured otherwise ([CONFIRM ANALYTICS REGION]). PostHog is based in the United States.
Its role
Service provider (a processor): it handles the data only on our instructions.

PostHog: privacy policy

Google Analytics

Only with your consent

What it does
Measures how visitors find and use our public pages, and which of those visits lead to someone starting as a guest, finishing the opening questions and finishing a first lesson.
What it receives
From your browser, only on our public pages while you are signed out: the pages you view and their titles, with any ad campaign labels in the page address (utm_ values) and which version of our landing page you saw, but no other part of the address; the website you came from; your device, browser, screen size and language; an approximate location worked out from your IP address, which Google says it does not store for visitors in the UK; and Google Analytics' own random ID and visit cookies (_ga and _ga_<container-id>). A Google ad-click ID in the page address is sent only if you also accept advertising cookies. Nothing else you do on the page is sent: no clicks, nothing you type, and nothing from the AI job check. From our server, while this is switched on, and only if Google Analytics has already set its cookie on one of our public pages: when you start as a guest, finish the opening questions or finish your first lesson, the name of that step, with the random ID and current visit from Google Analytics' cookies, and your account ID; for a guest start, also which of our public pages you started from and which version of it you saw. Your account ID is a random code, never your email address or name; we send it so we can link Google Analytics data to an account, and if you ask us to delete your account we also ask Google to delete the Google Analytics data linked to it. Our server never sends Google your answers, scores, which lesson it was, or your IP address. Google signals and advertising personalisation are switched off, so Google Analytics is not used to choose which ads you see.
When
Only if you accept analytics cookies, and only on our public pages while you are signed out. Our server's three steps need the same consent, and the cookie Google Analytics set on a public page.
Where
Google is based in the United States and processes Google Analytics data there and in other countries.
Its role
Service provider (a processor): Google handles this data only on our instructions, under Google's data processing terms. We keep Google Analytics' data sharing with Google, and Google signals, switched off (checked in our account settings on 23 October 2026).

Google Analytics: privacy policy

Cloudflare Turnstile

Only when you use it

What it does
Checks that a guest start comes from a person rather than an automated script. Every guest start creates a real account, so this keeps fake accounts out.
What it receives
Your IP address, your browser's user agent and the technical fingerprint of its secure connection, which Cloudflare's check reads in your browser. It gives our server a one-time pass, which our server confirms with Cloudflare. Cloudflare says it uses these signals only to detect bots, not to identify or target anyone.
When
On pages with a button to start as a guest, while the bot check is switched on.
Where
Cloudflare is based in the United States and runs a worldwide network.
Its role
Service provider (a processor) for the bot check itself. Cloudflare also uses the signals, as its own controller, to improve its bot detection.

Cloudflare Turnstile: privacy policy

Resend

Only when you use it

What it does
Delivers every email we send: confirming your email address, resetting your password, the 6-digit codes that check an address is yours, and streak reminders.
What it receives
Your email address and the email we are sending you, including any link or code in it.
When
When you create an account, reset your password, or add or check an email address. Streak reminders only if your address is confirmed and the reminder setting is on. Guest accounts get no emails until you add an address.
Where
Resend processes the data in the United States.
Its role
Service provider (a processor): it handles the data only on our instructions.

Resend: privacy policy

OpenRouter

Only when you use it

What it does
Runs our AI features: the practice summaries on Insights and after a mock exam, and explanations and feedback on questions that have passed trade review. No question has passed it yet, so those two show the explanation we wrote instead.
What it receives
For a practice summary: counts, percentages, topic names and the experience level you chose. For an explanation or feedback: the question, the answer you gave, your experience level and, for written answers, the text you typed. Never your name, email address or account ID: the app checks every request and refuses to send one that looks as if it contains an email address, phone number, National Insurance number or account ID.
When
Only when you use an AI feature, and only while AI features are switched on.
Where
OpenRouter's servers are in the United States. It passes each request to the company that runs the AI model ([CONFIRM AI MODEL PROVIDER]).
Its role
Service provider (a processor): it handles the data only on our instructions.

OpenRouter: privacy policy

GitHub

Only when you use it

What it does
Holds the private list where we track problems and ideas to work on. When you send feedback from the app, we copy it there.
What it receives
The topic you chose and your message, with email addresses and phone numbers taken out; the page you were on, your screen size and the app version; for a reported question, which question it was, the answer you gave and whether it was marked right; and a code made from your account ID that lets us group your reports but does not reveal who you are. Never your name, email address or account ID.
When
Only when you send feedback from the app.
Where
GitHub is based in the United States.
Its role
Service provider (a processor): it handles the data only on our instructions.

GitHub: privacy policy

Stripe

Not live yet

What it does
Will take payments for Plus, the optional paid subscription, once it goes on sale.
What it receives
You would type your card details into Stripe's own checkout page, so we would never see your full card number. We would keep a Stripe customer reference and whether your subscription is active.
When
Not live: Plus is not on sale yet.
Where
Stripe processes data in several countries, including the United States.
Its role
Service provider for payments. Stripe also uses some payment data for its own legal and fraud-prevention duties.

Stripe: privacy policy

Google (sign-in)

Only when you use it

What it does
Lets you sign in, create an account or save a guest's progress with your Google account, only if you choose to.
What it receives
Only if you choose it. You go to Google's own page to sign in, and Google then tells us your name, your email address and, where it shares one, a link to your profile picture. We use the email address for your account. We do not show your name or picture to other learners: your league name is a made-up one, such as "Jolly Sparky", until you change it. We never post anything for you, and we do not ask for your contacts or friends list. Our pages load no Google script or image for this.
When
Only if you choose to sign in with it.
Where
Google is based in the United States.
Its role
A separate company: your account with it is covered by Google's own privacy policy.

Google (sign-in): privacy policy

Meta (Facebook sign-in)

Not live yet

What it does
Lets you sign in, create an account or save a guest's progress with your Facebook account, only if you choose to. This is separate from Meta's advertising measurement below.
What it receives
Only if you choose it. You go to Facebook's own page to sign in, and Facebook then tells us your name, your email address and, where it shares one, a link to your profile picture. We use the email address for your account. We do not show your name or picture to other learners: your league name is a made-up one, such as "Jolly Sparky", until you change it. We never post anything for you, and we do not ask for your contacts or friends list. Our pages load no Facebook script or image for this.
When
Not switched on yet.
Where
Meta processes data in the United States and elsewhere.
Its role
A separate company: your account with it is covered by Meta's own privacy policy.

Meta (Facebook sign-in): privacy policy

Apple (sign-in)

Not live yet

What it does
Would let you sign in with your Apple account, only if you choose to.
What it receives
If you chose it, Apple would tell us your name and email address, or a relay address if you ask Apple to hide yours.
When
Not switched on yet.
Where
Apple is based in the United States.
Its role
A separate company: your account with it is covered by Apple's own privacy policy.

Apple (sign-in): privacy policy

Meta (Facebook and Instagram ads)

Not live yet

What it does
Measures whether our Facebook and Instagram ads lead to people trying a lesson, and helps Meta show our ads to people likely to be interested.
What it receives
From your browser, on our public pages while you are signed out: the pages you visit, opening one of our ad landing pages, and starting as a guest. From our server, when you start as a guest, finish the opening questions or finish your first lesson, sent to Meta directly (its Conversions API). Each event is its name and an ID, never your answers or scores, with your IP address, browser details and Meta's cookies (_fbp, and _fbc if you came from a Meta ad) or ad-click ID. We never send Meta your email address or phone number.
When
Not switched on yet. Only if you accept advertising cookies. In your browser, only on our public pages while you are signed out: never once you start as a guest or sign in, inside the app, or on the sign-in, sign-up, password, account-deletion or content-management pages.
Where
Meta processes data in the United States and elsewhere.
Its role
Meta shares responsibility with us for collecting and sending this data (joint controllers), then uses it under its own privacy policy.

Meta (Facebook and Instagram ads): privacy policy

Google (ads measurement)

Not live yet

What it does
Measures whether our Google ads lead to people trying a lesson.
What it receives
When you start as a guest: an ID for that event, with your IP address, browser details and Google's advertising cookies (_gcl_au, and _gcl_aw if you came from a Google ad). The tag sends no page views and nothing about your answers or scores.
When
Not switched on yet. Only if you accept advertising cookies, and only on our public pages while you are signed out: never once you start as a guest or sign in, inside the app, or on the sign-in, sign-up, password, account-deletion or content-management pages.
Where
Google is based in the United States.
Its role
Google uses the data under its own privacy policy to measure ads.

Google (ads measurement): privacy policy

We would also share information if the law required it, for example to comply with a court order.

Data sent outside the UK

Several of these providers are based in the United States or use servers there, as each card above says. When personal information leaves the UK, the law requires a safeguard:

  • for the European Union and European Economic Area, the UK’s “adequacy regulations”, which recognise their protection as equivalent;
  • for a US company certified under the UK Extension to the EU–US Data Privacy Framework, the UK adequacy regulations that cover it;
  • otherwise, the ICO’s International Data Transfer Agreement, or its Addendum to the EU’s standard contractual clauses, in our contract with the provider.

Which one applies to each provider: [CONFIRM THE TRANSFER SAFEGUARD FOR EACH PROVIDER].

How long we keep it

We keep personal information only as long as we need it. Some of these periods have not been decided yet, and are shown in square brackets.

Your account and learning records
For as long as your account exists. Once a deletion request has been processed, the account and its learning records are deleted ([HOW LONG A DELETION REQUEST TAKES]), and copies in database backups are overwritten within [HOW LONG DATABASE BACKUPS ARE KEPT].
Guest accounts
Nothing deletes unused guest accounts automatically yet: [HOW LONG UNUSED GUEST ACCOUNTS ARE KEPT].
Analytics events in PostHog
[HOW LONG ANALYTICS EVENTS ARE KEPT]
Google Analytics
Event and user data: 14 months from collection; a later visit does not extend it. Google’s standard summary reports are not affected by that setting. Its cookies last about 6 months.
Hosting logs
[HOW LONG HOSTING LOGS ARE KEPT]
Security records
[HOW LONG SECURITY RECORDS ARE KEPT]
Emails you send us
[HOW LONG EMAILS TO US ARE KEPT]
Payment records, once Plus is on sale
[HOW LONG PAYMENT RECORDS ARE KEPT]
Cookies and browser storage
Each one is listed, with how long it lasts, in our cookie policy.

Your rights

Under UK data protection law you can ask us to:

  • give you a copy of the personal information we hold about you;
  • correct anything that is wrong. You can change your display name and settings yourself in Profile settings;
  • delete your account and learning data, from Profile settings or the account deletion page. Requests are processed by hand at the moment, and the account stays in place until then. We also ask Google to delete the Google Analytics data linked to your account ID;
  • restrict what we do with your information while a concern is sorted out;
  • stop anything we do on the basis of legitimate interests (you can object), including streak reminders, which you can also switch off yourself;
  • send you or another service the information you gave us, in a common machine-readable format;
  • withdraw consent at any time, for example by changing your choice in . Withdrawing does not affect what happened before.

We do not make decisions about you based only on automated processing that have legal or similarly significant effects. The app marks answers automatically and uses the result to unlock lessons, which affects only your progress in the app.

How to ask

Email [CONTACT EMAIL]. We may ask you to sign in first, so we know the account is yours. A guest account can only be identified from the device where it is signed in, so make a guest request from there, in Profile settings or on the account deletion page. The law gives us one month to respond, which can be extended by up to two more months for complex requests; we would tell you if so.

Complaints

If you are unhappy with how we have handled your information, please tell us first at [CONTACT EMAIL]. You can also complain to the Information Commissioner’s Office, the UK regulator, at ico.org.uk/make-a-complaint.

Cookies

We use cookies and similar technologies, such as your browser’s local storage. The ones needed to keep you signed in and to remember your choices are always on; analytics and advertising ones wait until you accept them. Our cookie policy lists every one. You can change your choice at any time in .

Age

TradeTraining is for people aged [MINIMUM AGE] and over. If you think someone younger has given us personal information, please contact us so we can delete it.

Keeping it secure

Connections to the site are encrypted (HTTPS). Database rules let each learner read only their own progress, and scores, streaks and other records can be changed only by our server, after it has checked your answer. Passwords are stored by Supabase in a scrambled form that we cannot read.

Changes to this notice

We will update this notice when what we do with your information changes, and change the date at the top. If a change affects you, we will tell you in the app.

Privacy Notice | TradeTraining