Privacy Policy
Version 1.3 · Effective date: 21 November 2026
This policy explains how Wio Ltd collects and uses personal data when you use Wio APP and our website. We follow the UK GDPR, the Data Protection Act 2018 and, where it applies, the EU GDPR.
Short version for young users: We only collect what we need to help you learn. We keep it safe. We never sell it or use it for adverts. You or your parent can ask to see it or delete it at any time by emailing hello@wio.org.
1. Who we are
Wio Ltd (company number 17509391, Flat 3, 2 Lower Oldfield Park, Bath, BA2 3HL, United Kingdom) is the data controller for the data described here. Contact: hello@wio.org.
When a school or business uses our Service for its own users, that organisation is the controller of its users' data and we act as its processor. In that case, please also read the organisation's own privacy notice.
2. What data we collect
| Type | Examples | Where it comes from |
|---|---|---|
| Account data | Name, email, password (encrypted), role | You |
| Learning data | Progress, answers, scores, activity | Your use of the Service |
| Payment data | Billing name, address, last 4 card digits | You, via Stripe |
| Support data | Messages and emails to us, and any files attached | You |
| Technical data | IP address, device, browser, log files | Automatically |
| Cookie data | See our Cookie Policy | Automatically |
We do not store full card numbers. We do not knowingly collect special category data (such as health data). Please do not upload it.
If your school or employer set up your account, we receive your name, email and class or group details from them.
Emails and messages to us: When you email hello@wio.org, or send us a message through the contact form on wio.org, we keep your name, email address and message, and any attachments, so we can reply. The contact form asks for your name, your email address, your school or trust (optional), your role (optional), what your message is about and your message. A message from the form is treated like an email: it becomes a ticket, it goes through the same checks, and we reply by email. The form does not set any cookies. Attachments are checked for viruses by software on our own server. To block spam and scams, we use simple rules first. If an email looks doubtful, we send three things to Anthropic, the company behind the Claude AI service: the part of the sender's address after the @, the subject, and the first part of the message text. Anthropic tells us if it looks like spam. We never send attachments. Anthropic acts as our processor under its data processing terms, and does not use this data to train its models. Emails that look like spam are kept apart for 30 days, then deleted. We do not reply to them.
Teachers: Your name (as entered by you or your school, for example "Mr Smith") is shown next to your class on the class page of each student in that class. Students in your class and staff at your school can see it. If your school set up your account, your school decides how your name is shown. Please contact your school if you have concerns.
Signing in with Google or Microsoft: If your school turns this on, you can sign in with your school Google or Microsoft account instead of a Wio APP password. When you do, Google or Microsoft tells us only your name, your email address and a unique account number. We never see your Google or Microsoft password, and we cannot read your email, files or calendar. We keep a record of which Google or Microsoft account is linked to your Wio APP account so we can recognise you next time. Staff accounts are linked automatically when the email address matches a domain your school has approved, and anyone can link or unlink their own account from the Sign-in options page. Your school can also turn on two ways to join: students can create their own account by typing a class code from their teacher and then signing in with their school Google or Microsoft account (the account is made from their first name and surname only, and we do not keep a student's email address), and staff can ask to join by signing in with their school account (no account is made until a school administrator approves the request). Google and Microsoft handle your sign-in under their own privacy terms and your school's agreement with them. We use this information to provide the Service you or your school asked for (contract), and for school accounts, on the school's instructions.
3. Why we use it and our legal basis
| Purpose | Legal basis |
|---|---|
| Provide and run your account | Contract |
| Take payment and keep accounts | Contract; legal obligation |
| Customer support | Contract; legitimate interests |
| Read and answer emails and contact form messages to us; block spam and scams | Legitimate interests (answering you, and keeping our inbox and our staff safe) |
| Keep the Service secure and fix problems | Legitimate interests |
| Improve the Service using usage statistics | Legitimate interests |
| Send service emails (e.g. receipts, changes) | Contract |
| Send marketing emails | Consent (you can opt out at any time) |
| Non-essential cookies | Consent |
| Show a teacher's name to students in their class | Legitimate interests (helping students find the right class and teacher); for school accounts, on the school's instructions |
4. Children
The Service may be used by students. Users under 13 need consent from a parent or guardian, or must be signed up by their school. An account a student creates with a class code counts as signed up by their school: the teacher decides who receives the code, and it only works with the school's own email domains. We collect only what is needed, switch off non-essential tracking for children by default, and do not use children's data for marketing. If you think a child has given us data without proper consent, contact us and we will delete it.
5. Who we share data with
We do not sell your data. We share it only with:
- Service providers who help us run the Service (hosting, email, payments, and spam filtering). See our Sub-processor List.
- Your school or organisation, if it set up your account.
- Professional advisers (lawyers, accountants).
- Authorities, when the law requires it.
- A buyer, if Wio Ltd is sold. They must protect your data in the same way.
6. International transfers
Our main hosting is with Oracle Cloud Infrastructure in London, UK, and our backups are also kept in the UK. Some of our service providers process data outside the UK: Cloudflare, which protects and routes visits to our websites, Brevo, which sends our service emails from the EU, and Anthropic, which checks doubtful emails sent to us for spam and is based in the United States. When data leaves the UK, we use legal safeguards such as UK adequacy regulations or the UK International Data Transfer Agreement or Addendum. Our full list is in the Sub-processor List.
7. How long we keep data
We keep account data while your account is open, and delete it within 90 days after closure unless we must keep it longer. We keep billing records for 6 years for tax law. We keep an email ticket (your emails and contact form messages to us, our replies and any attachments) while it is open. After we close it, we keep it for 6 years so we can deal with later questions, complaints or disputes, and then it is deleted automatically. Emails we mark as spam are deleted after 30 days. See our Data Retention Policy for details.
8. Your rights
You have the right to:
- see a copy of your data;
- correct wrong data;
- have your data deleted;
- limit or object to how we use it;
- get your data in a portable format;
- withdraw consent at any time.
Email hello@wio.org. We will reply within one month. It is free.
We do not make decisions about you using only automated processing that have legal or similarly significant effects on you.
If you are unhappy, please tell us first so we can try to put it right. You also have the right to complain to the Information Commissioner's Office (ico.org.uk, 0303 123 1113). EU users can complain to their local data protection authority.
9. Security
We use encryption, access controls and regular backups to protect your data. See our Security Statement.
10. Changes
We will post updates here and tell you by email about important changes.
Terms of ServiceCookie PolicyAcceptable Use PolicyData Processing AgreementSecurity StatementSub-processor List
