Privacy Policy
Last Updated: 19th October 2026
SOPHOS EDUCATION LTD (trading as “Studia”) | Company No. 14321333
10 St. Edmunds Square, London, England, SW13 8SA | studia.io
1. Introduction and Data Controller
This Privacy Policy explains how we collect, use, store, and protect personal information when you use the Studia platform.
| Data Controller | SOPHOS EDUCATION LTD (trading as Studia) Company Number 14321333 ICO Registration Number ZC191104 (registered 6 July 2026, renewal due 5 July 2027) |
| Company Number | 14321333 |
| Registered Office | 10 St. Edmunds Square, London, England, SW13 8SA |
| Website | studia.io |
| Privacy Contact | privacy@studia.io |
| Child Safety | safeguarding@studia.io |
| Data Protection Officer | Studia has not appointed a DPO at this time. We have designated a privacy contact (privacy@studia.io) and keep the need for a formal DPO appointment under regular review as the organisation grows. |
We protect personal data under the UK GDPR, the Data Protection Act 2018 as amended by the Data (Use and Access) Act 2025, the Privacy and Electronic Communications Regulations 2003 (“PECR”), and the ICO Age Appropriate Design Code (“AADC”). Because our platform is designed for students aged 13–18, children's privacy and safety are at the centre of everything we do.
This Privacy Policy should be read alongside our Terms of Service, Children's Privacy Notice, and Cookie Notice.
2. Who This Policy Applies To
This Privacy Policy applies to:
- Parents and Guardians — who create accounts for students under 13 (required) and who may link to accounts of students aged 13–17 for oversight
- Students — who use Studia for educational content, Livestreams, and 1-to-1 Sessions
- Tutors — who provide teaching content and tutoring services through the Platform
- Website visitors — who visit studia.io (for information about cookies and analytics)
If you are under 18, we encourage you to read this policy with your parent or guardian. A simpler version is available in our Children's Privacy Notice.
3. Information We Collect
We collect only the personal data that is necessary to provide our services, maintain safety, and comply with our legal obligations. We collect information in three ways: directly from you, automatically when you use the Platform, and from third parties.
3.1 Information You Provide Directly
| User Type | Data Collected | Purpose |
|---|---|---|
| Student | Name, date of birth, school name and school year, mobile number (required if no Parent is linked and you are 16 or over; otherwise optional from 13), profile photograph, subjects, exam boards, learning preferences and goals, SEND needs (if voluntarily disclosed — see Section 4), session activity, chat messages, poll responses, quiz answers | Deliver educational services, including lesson and livestream texts, personalise learning experience, safeguarding |
| Parent / Guardian | Name, email address, mobile number (required), billing and payment details, account settings and preferences | Account management, payments, parental oversight, service communications, lesson and livestream texts |
| Tutor | Name, email address, mobile number (required), postal address, profile information, qualifications, DBS verification status, bank and payment details, teaching materials | Identity verification, DBS checks, payments, platform listing, reminder texts for 1-to-1 Sessions |
We do not collect more personal data than is necessary to provide our services.
3.2 Information Collected Automatically
When you use the Platform, we automatically collect:
- Session recordings: Video and audio from Livestreams (see Section 9 for full details)
- Livestream participation data: Chat messages, poll responses, quiz answers, and AI Q&A interactions
- Device and connection data: IP address, browser type, device type, operating system
- Usage data: Lessons viewed, features used, session attendance, time spent on the Platform
- Lesson join times: When each person joins and leaves a 1-to-1 Session, used to review a missed-lesson report.
- Error and performance data: Technical logs to maintain Platform stability
3.3 Information from Third Parties
| Source | Data Received | Purpose |
|---|---|---|
| uCheck | DBS verification status and certificate reference number (NOT full certificate copies) | Tutor safeguarding verification |
| Stripe | Payment processing confirmations and transaction data | Payment management |
| Clerk | Authentication and login data | Account security |
| Third-party sign-in providers (e.g. Google) | Name, email address, account ID — only where you choose to sign in using a third-party account. See Section 11. | Account creation and authentication |
4. Special Category Data
Certain categories of personal data receive enhanced protection under UK GDPR Article 9 because of their sensitivity. These are known as “special category data.”
4.1 What Special Category Data We May Process
The only special category data we may process is health or medical information voluntarily disclosed by a Student or their Parent relating to Special Educational Needs and Disabilities (SEND) — for example, a diagnosis of dyslexia, ADHD, autism, or a physical or sensory impairment.
Disclosure of SEND information is:
- Entirely voluntary — we will never require it as a condition of using the Platform
- Used solely to help Tutors and the Platform support the Student's learning more effectively
- Never shared for any commercial, marketing or advertising purpose
- Used only to suggest suitable Tutors, never for advertising or commercial profiling
4.2 Legal Basis for Processing Special Category Data
Where a Student or Parent voluntarily discloses SEND information, we process it under:
- UK GDPR Article 9(2)(a): Explicit consent — the Student or Parent has clearly and actively chosen to share this information to improve their learning support.
Because this is Article 9 special category data, we apply enhanced security and access controls: only the relevant Tutor and, where a safeguarding concern arises, our Safety Team may access SEND information. It is not accessible to other staff, contractors, or third-party processors.
4.3 Your Right to Withdraw
You or your parent can ask us to remove SEND information from the profile at any time by emailing privacy@studia.io. Removing it will not affect your ability to use the Platform.
4.4 Criminal Offence Data (Tutors)
Information about a Tutor's DBS check is criminal offence data under Article 10 UK GDPR, not special category data, and a different regime applies to it.
We process a Tutor's DBS status, certificate reference number and check level to safeguard children. We rely on Article 6(1)(f) UK GDPR and on the condition in paragraph 18 of Schedule 1 to the Data Protection Act 2018 (safeguarding of children and of individuals at risk).
We do not receive or store copies of DBS certificates. DBS results are encrypted at rest and every access to them is logged.
5. How We Use Personal Data
We use your personal data for the purposes set out below. Each purpose is linked to a lawful basis under UK GDPR Article 6.
5.1 Processing Activities and Legal Bases
| Processing Activity | Legal Basis | Details |
|---|---|---|
| Providing tutoring services, Livestreams, and 1-to-1 Sessions | Contract (Art. 6(1)(b)) | Core service delivery to fulfil our agreement with you |
| Managing Subscriptions, bookings, and scheduling | Contract (Art. 6(1)(b)) | Payment processing, session management |
| Account creation and authentication | Contract (Art. 6(1)(b)) | Via Clerk; necessary to provide the service |
| AI-assisted learning support during Livestreams | Contract (Art. 6(1)(b)) | Real-time AI Q&A, answer checking, and hints during Livestreams |
| Payment processing | Contract (Art. 6(1)(b)) | Via Stripe; necessary to collect fees and pay Tutors |
| Service communications | Contract (Art. 6(1)(b)) | Necessary for service delivery |
| Lesson and livestream texts | Legitimate Interest (Art. 6(1)(f)) | Reminders, not-joined and missed-lesson texts, and changes and cancellations, sent to the account holder (a Parent, or a Student with no Parent linked), to a child aged 13 or over when their Parent chooses, and to Tutors about their own 1-to-1 Sessions. You can switch them off at any time in My account › Notifications, or as a Tutor in Settings › Account › Notifications. They never contain marketing. |
| Payment problem texts | Contract (Art. 6(1)(b)) | A text to whoever paid when a payment for lessons or a Subscription fails. These are needed to take payment for lessons you have booked, so they cannot be switched off. |
| Reviewing missed 1-to-1 Sessions | Contract (Art. 6(1)(b)) | Join times and the report decide whether a payment is refunded or paid out, under our Terms of Service and Tutor Agreement. |
| Session recording — Livestreams | Legitimate Interest (Art. 6(1)(f)) | Educational replay for Subscribers; quality assurance |
| Session recording — 1-to-1 Sessions | Legal Obligation (Art. 6(1)(c)) + Legitimate Interest (Art. 6(1)(f)) | Safeguarding duty under the Online Safety Act 2023 and KCSIE 2024; safety monitoring |
| Content moderation | Legal Obligation (Art. 6(1)(c)) + Legitimate Interest (Art. 6(1)(f)) | Online Safety Act 2023 compliance; child protection duties |
| Maintaining child safety and preventing harm | Legal Obligation (Art. 6(1)(c)) + Legitimate Interest (Art. 6(1)(f)) | Online Safety Act 2023 duties |
| DBS verification for Tutors | Legitimate Interest (Art. 6(1)(f)) | Safeguarding; see Section 4.4 |
| Training tutor-specific AI models from Tutor materials | Legitimate Interest (Art. 6(1)(f)) | Improving educational support for Subscribers of that Tutor. Tutors can request exclusion (see Section 8.3). |
| Analytics and platform improvement | Legitimate Interest (Art. 6(1)(f)) | Service improvement; data is aggregated and anonymised where possible |
| User research and feedback processing | Legitimate Interest (Art. 6(1)(f)) / Consent (Art. 6(1)(a)) | Understanding how to improve services. See Section 19 for details. |
| Safeguarding referrals to authorities | Legal Obligation (Art. 6(1)(c)) + Vital Interest (Art. 6(1)(d)) | Child protection reporting to Local Authority Designated Officers (LADO), police, or social services |
| Responding to legal requests | Legal Obligation (Art. 6(1)(c)) | Court orders, regulatory requirements |
| Marketing communications | Consent (Art. 6(1)(a)) | Only with explicit opt-in; you can withdraw consent at any time |
| Age verification and records | Legal Obligation (Art. 6(1)(c)) | Online Safety Act 2023 risk duties |
5.2 Legitimate Interests Balancing
Where we rely on legitimate interest, we weigh our interest against your rights and freedoms, giving particular weight to the fact that our users are children. In particular:
- Session recording (Livestreams): The educational benefit of replay access and quality assurance outweighs the limited privacy impact, given that Livestreams are group events and students participate via text only.
- Analytics: We use aggregated and, where possible, anonymised data. The benefit of improving the Platform outweighs the minimal privacy impact.
- User research: Understanding how the Platform is used helps us improve it. We use only anonymised or aggregated data for research unless explicit consent has been obtained for more.
- Lesson texts: A text before each lesson helps families and Tutors turn up, which is the service they came to us for. Each text holds only what it needs (a first name, the subject, the time and a link), never marketing, and anyone can switch them off in My account › Notifications (Tutors: Settings › Account › Notifications).
5.3 Whether Provision of Data Is a Requirement
Some personal data is necessary to create an account and use our services (for example, your name, email address, and date of birth). A mobile number is required for Parents, for Students aged 16 or over with no Parent linked, and for Tutors, so we can verify the account and send lesson texts. If you do not provide this data, we may not be able to provide the service. Where data is optional (for example, SEND needs or marketing preferences), we will make this clear at the point of collection.
6. Legal Bases for Processing Children's Data
Because Studia is designed for students aged 7–18, we apply additional protections to children's personal data.
6.1 Children Under 13
For children under 13, we require parental consent before any data processing, in accordance with Article 8(1) UK GDPR, which sets 13 as the UK age of digital consent. A Parent must create the account and give that consent. Children under 13 cannot add a mobile number, and we never send them text messages: texts about their lessons go to their Parent.
6.2 Children Aged 13–17
Children aged 13 to 17 may create their own account and consent to data processing, in accordance with Article 8(1) UK GDPR. We encourage parental involvement and offer a parental dashboard for oversight. Parents can link to their child's account at any time.
If a Parent is linked, the Parent chooses whether reminders for a child aged 13 or over go to the Parent or to the child, never both. If they go to the child and the child switches them off, they go back to the Parent. A linked child's Notifications page shows which texts their Parent receives. A child aged 13 to 15 with no Parent linked may add a mobile number but receives no texts. We never send marketing texts to children.
6.3 What We Never Do with Children's Data
We never:
- Use children's data for behavioural advertising or targeted marketing
- Use children's data for commercial profiling
- Sell children's data to any third party
- Use nudge techniques to encourage children to provide unnecessary data
- Track children's geolocation
- Share children's data with advertising networks, social media platforms, or marketing companies
These protections are in accordance with the ICO's Age Appropriate Design Code (AADC).
7. Age Appropriate Design Code (AADC) Compliance
We design the Platform with children's best interests as a primary consideration, meeting each of the ICO Age Appropriate Design Code's 15 standards:
| # | Standard | How Studia Meets It |
|---|---|---|
| 1 | Best interests of the child | Children's welfare is a primary consideration in all our data processing and design decisions. |
| 2 | Data protection impact assessments | We conduct DPIAs for features and services likely to be accessed by children. |
| 3 | Age-appropriate application | We apply protections at two age thresholds, under 13 and under 16, and treat an unknown age as under 13. |
| 4 | Transparency | We provide privacy information in age-appropriate language (see our Children's Privacy Notice). |
| 5 | Detrimental use of data | We do not use children's data in ways that could be detrimental to their physical or mental wellbeing. |
| 6 | Policies and community standards | Our Community Guidelines are published, upheld, and acted on. |
| 7 | Default settings | Protection for children is built in, not a setting a child can weaken. |
| 8 | Data minimisation | We collect only the data necessary to provide our educational service. |
| 9 | Data sharing | We do not share children's data unless there is a compelling reason to do so (see Section 12). |
| 10 | Geolocation | We do not track children's geolocation. Studia does not use geolocation features. |
| 11 | Parental controls | We provide age-appropriate parental controls via the parental dashboard (see Section 10). |
| 12 | Profiling | We never profile children commercially. We use subjects, year group and stated needs to suggest Tutors — nothing else. |
| 13 | Nudge techniques | We do not use nudge techniques to encourage children to provide personal data or weaken their privacy settings. |
| 14 | Connected toys and devices | Not applicable to Studia. |
| 15 | Online tools | Children and Parents can exercise their data rights at privacy@studia.io, explained in our Children's Privacy Notice. |
8. AI and Automated Decision-Making
We use AI systems on the Platform for safety and educational purposes. This section explains what AI does, what data it uses, and your rights in relation to automated decisions.
8.1 AI Systems We Use
1. Content Moderation AI — Every chat message sent on the Platform is checked automatically for safety risks, including grooming behaviour, bullying, inappropriate content and self-harm indicators. Moderation checks every message, whether or not anyone reports it, and nothing that passes through it is used to train any AI model. A trained member of our Safety Team reviews anything flagged before action is taken about a person.
8.2 AI Training Practices
| Data Type | Used for AI Training? | Details |
|---|---|---|
| Student session data and activity | No | Not used for AI training, behavioural profiling, or advertising. |
| Content checked by our moderation system | No | Every chat message passes through content moderation. Our moderation provider trains no model on it. |
8.3 Automated Decision-Making (UK GDPR Article 22)
Content moderation may result in automated actions for low-severity violations (such as message deletion or temporary chat restrictions). These actions do not produce legal effects or similarly significant effects on individuals.
No decision that significantly affects you, including removing content or ending your access, is made by an automated system alone. A person reviews it first.
You have the right to: contest any automated decision that affects you; request human review of any automated moderation action; and express your point of view and receive an explanation of the decision. To exercise these rights, contact privacy@studia.io or use the appeals process described in our Community Guidelines.
9. Session Recording and Safety Monitoring
All Livestreams and 1-to-1 Sessions on the Platform are automatically recorded. Recording is necessary for safeguarding, quality assurance, and regulatory compliance. You cannot opt out of recording, as it is required for child safety.
9.1 Recording Policy
| Session Type | Who Can View? | Retention Period |
|---|---|---|
| Livestreams | Students and Parents with an active Subscription can stream replays via the Content Library | Kept for as long as the Livestream is available in the Content Library, and for 12 months after it is withdrawn, then deleted |
9.2 Recording Storage and Security
- Livestream recordings are hosted by Mux in the United States. Other data remains on AWS (UK/EU).
- Livestream replays are accessible only to Students and Parents with an active Subscription to the relevant Tutor.
9.3 AI Transcripts and Summaries
AI-generated text transcripts and lesson summaries are provided for Livestreams to support learning. These are accessible to Students and Parents with an active Subscription.
9.4 Disclosure to Authorities
Recordings may be disclosed to law enforcement, safeguarding authorities, or other relevant bodies where we are legally required to do so (for example, in response to a court order or where we believe a child may be at risk).
10. Children's Data and Parental Controls
10.1 Parental Dashboard
Parents and Guardians can link to their child's account to access a parental dashboard for oversight and control. For Students under 13, parental linking is mandatory. For Students aged 13–17, parental linking is encouraged. Through the dashboard, Parents can:
- View session activity: See their child's session history, Tutor Subscriptions, and attendance.
- Access content: View Livestream recordings
- Manage Subscriptions and spending: Control, pause, or cancel Subscriptions.
- Set notification preferences: Choose which lesson and livestream texts you receive, whether a child aged 13 or over receives reminders instead of you, and whether to receive marketing emails and texts, separately. Payment problem texts cannot be switched off.
- Control cookie preferences: Cookie choices are per device: set them on your child's device (see Section 16).
- Report concerns: Email safeguarding@studia.io at any time.
- Exercise data rights: Correct their child's details in the dashboard; request export or deletion at privacy@studia.io (Section 14)
- Withdraw consent: Email privacy@studia.io to close their child's account at any time. There is no notice period.
10.2 Age-Appropriate Protections
We apply the following protections for children: protections are built in, not set by a child; no behavioural advertising or commercial profiling; no sale or sharing of children's data for marketing purposes; safeguarding@studia.io for reporting a concern; content moderation across all chat; and a parental dashboard showing sessions, subscriptions and spending.
11. Third-Party Authentication
Studia uses Clerk as our authentication provider, which supports sign-in via third-party services such as Google. This section explains what happens when you choose to sign in using a third-party account.
11.1 What Data We Receive
If you choose to create a Studia account or sign in using a third-party service (such as a Google account), we will receive the following information from that provider:
- Your name (as registered with the third-party provider)
- Your email address
- A unique account identifier issued by the third-party provider
When you sign in with a third-party account, we do not receive your password for the third-party service, your payment details held by the third-party provider, your contacts, your social connections, or any other data from your account with the third-party provider beyond what is listed above. Section 11.4 explains the one case where a Tutor gives us an app-specific password.
11.2 How We Use This Data
Data received from a third-party sign-in provider is used only to create and authenticate your Studia account. It is handled in exactly the same way as data you would provide if you registered directly with an email address and password.
11.3 Third-Party Provider's Privacy Policy
Studia's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We request only the calendar.readonly and calendar.events scopes, and do not sell this data, use it for advertising, or use it to train AI models.
11.4 Apple Calendar (iCloud)
Apple does not offer a way for apps to connect to iCloud Calendar with limited access. If you are a Tutor and choose to connect your Apple Calendar, you create an app-specific password for your Apple Account at account.apple.com and give it to us together with your Apple Account email address. An app-specific password lets whoever holds it sign in to your iCloud mail, contacts and calendars. We use it only to find one iCloud calendar that you own, normally your default calendar, when you connect, and then to read when you are busy in it and to add, move and remove your Studia lessons in it. We never read your email, your contacts or the entries in your other calendars, and we never store the titles, descriptions or attendees of your own calendar entries.
We store the password encrypted (AES-256-GCM) and it is never shown to anyone, including Studia staff. It is deleted as soon as you disconnect the calendar or close your Studia account. Disconnecting does not cancel the password at Apple: you can revoke it at any time at account.apple.com, and we then stop being able to use it.
11.5 Children's Accounts
For Students under 13, Parents create and manage the account. If a Parent uses a third-party sign-in to create or access a child's account, the above applies to the Parent's account, not the child's. Students under 13 do not sign in independently and therefore do not use third-party authentication.
12. Data Sharing with Third Parties
We share personal data only with third-party service providers that are necessary to operate the Platform. We have data processing agreements in place with each provider.
We never:
- Sell personal data
- Share data for advertising purposes
- Share children's data with social media platforms or advertising networks
12.1 Third-Party Data Processors
| Provider | Purpose | Data Shared | Region | Transfer Safeguard |
|---|---|---|---|---|
| Stripe | Payment processing | Payment details, billing information, transaction data | UK/EU or US | Standard Contractual Clauses (SCCs) |
| Daily.co (Planned) | Video and audio for 1-to-1 Sessions | Video and audio streams, session metadata | US | UK Extension to the EU–U.S. Data Privacy Framework |
| Neon Postgres | Primary database hosting | Platform data (encrypted at rest and in transit) | UK/EU (London) | UK/EU processing |
| Amazon Web Services (AWS) | Media and chat data storage (S3, CloudFront, DynamoDB) | Uploaded media, attachments, chat data | UK/EU (London/Dublin) | UK/EU processing |
| Clerk | User authentication | Email address, name, login credentials | UK/EU or US | Standard Contractual Clauses (SCCs) |
| uCheck | DBS verification (Tutors only) | Tutor identity details, DBS application data | UK only | UK data processing — no international transfer |
| Checkstep | Content moderation | Chat messages, the account identifier of the person who sent them, and the session they were sent in | EU (primary) | UK Adequacy Regulations |
| Mux (Planned) | Video hosting and playback analytics | Livestream video and recordings, playback and quality data | United States | UK Extension to the EU–U.S. Data Privacy Framework |
| Google Analytics 4 (Google LLC) | Aggregate usage analytics (Google Analytics 4). Retention: 14 months. Registered address: 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. | Usage events, page paths, device information, account-linked identifiers | United States | UK Extension to the EU–U.S. Data Privacy Framework |
| PostHog (PostHog Inc.) | Product analytics. Retention: 12 months. Registered address: 2261 Market St #4008, San Francisco, CA 94114, USA. EU data region served from PostHog's Frankfurt-hosted infrastructure (eu.posthog.com). | Usage events, device information, anonymised interaction data | EU (Frankfurt) | EU hosting — no transfer outside the EEA; Data Processing Agreement in place |
| Vercel | Web hosting and delivery | Web traffic data, request logs | UK/EU or US | Standard Contractual Clauses (SCCs) |
| Sentry | Error monitoring | Error reports, technical diagnostic data | EU (Germany) | EU processing |
| Mailchimp Transactional (Intuit) | Transactional email delivery | Email address, name, transactional message content | United States | United States, UK International Data Transfer Addendum |
| Klaviyo | Marketing email, and text messages (SMS): service texts about lessons and livestreams, and marketing texts where you have opted in | Email address, name, phone, DOB, marketing and text-message preferences, and the lesson details a text contains (subject, first name of the tutor or student, date and time) | United States | UK International Data Transfer Addendum |
| Pipedrive | Customer relationship management (CRM) | Name, email address, contact and enquiry details | EU | EU processing |
| Inngest | Background job processing | Job payloads and related account identifiers | United States | United States, UK International Data Transfer Addendum |
| Typesense Cloud | Search indexing | Searchable platform content and metadata | To be confirmed | Cloud — European Union (Frankfurt) |
| Google Calendar / Microsoft Outlook / Apple iCloud Calendar | Optional tutor calendar synchronisation | Calendar event data, availability; for Apple, the tutor's Apple Account email and an encrypted app-specific password | UK/EU or US | UK Extension to the EU–U.S. Data Privacy Framework |
| Calendly | Tutor onboarding interview scheduling | Name, email address, interview booking times | United States | United States, UK International Data Transfer Addendum |
| Cookiebot (Usercentrics) | Cookie consent management | Consent state, anonymised IP address | EU | EU processing |
| Zendesk | Customer support — ticketing, Help Centre (help.studia.io), and support chat | Name, email address, support-conversation content, technical metadata | To be confirmed | UK Extension to the EU–U.S. Data Privacy Framework |
| ModSquad | Outsourced support agents handling support requests within Zendesk | Support-conversation content and associated account details, accessed within Zendesk | To be confirmed | United States, UK International Data Transfer Addendum |
12.2 When We May Disclose Data
In addition to our data processors, we may disclose personal data:
- To law enforcement or safeguarding authorities where required by law or where we believe a child may be at risk.
- To courts or regulatory bodies in response to a valid legal request, court order, or regulatory requirement.
- To a successor organisation if Studia (SOPHOS EDUCATION LTD) is involved in a merger, acquisition, or asset sale, provided the successor agrees to be bound by this Privacy Policy.
13. International Data Transfers
13.1 Where Your Data Is Stored
Our primary database is on Neon Postgres in London, and media, attachments and chat data on AWS in London and Dublin. Live 1-to-1 video runs through Daily.co in the United States and Livestream video through Mux, also in the United States (see 13.2).
13.2 Transfers Outside the UK
Some of our third-party service providers may process data in the United States or other countries outside the UK. Where personal data is transferred outside the UK, we ensure it is protected by one of the following safeguards, in accordance with UK GDPR Articles 44–49 and the Data Protection Act 2018:
- Standard Contractual Clauses (SCCs): We have entered into UK-approved Standard Contractual Clauses with providers that process data outside the UK (including Stripe, Clerk, Vercel, and Google LLC for Google Analytics 4).
- EU-US Data Privacy Framework: UK Extension to the EU–U.S. Data Privacy Framework: Daily.co, Mux, Google LLC (Analytics and Calendar), Microsoft Corporation, Apple Inc. (iCloud Calendar) and Zendesk are each self-certified to the UK Extension. We check each certification remains current.
- UK Adequacy Regulations: Where the UK Government has determined that a country provides an adequate level of data protection, transfers may proceed under that adequacy decision.
- Data Processing Agreements: Every provider we use is bound by a written data processing agreement requiring them to protect personal data to at least the standard the UK GDPR requires, to process it only on our instructions, and to help us answer your requests.
13.3 Countries Where Data May Be Processed
| Country | Providers | Safeguard |
|---|---|---|
| United Kingdom | Neon Postgres, Amazon Web Services (AWS), uCheck | Domestic processing |
| EU/EEA | Amazon Web Services (Dublin), Checkstep, PostHog (Frankfurt), Typesense Cloud, Pipedrive, Sentry, Cookiebot, Zendesk | UK Adequacy Regulations |
| United States | Daily.co, Mux, Stripe, Clerk, Vercel, Google LLC, Microsoft Corporation, Apple Inc., Mailchimp Transactional, Klaviyo, Inngest, Calendly, ModSquad | UK Extension to the EU–U.S. Data Privacy Framework where the provider is certified; otherwise the UK International Data Transfer Addendum |
You may request further information about our international transfer safeguards by contacting privacy@studia.io.
14. Your Rights under UK GDPR
Under the UK GDPR, you have the following rights in relation to your personal data. Parents and Guardians may exercise these rights on behalf of their children.
14.1 Your Rights
| Right | Description | Article |
|---|---|---|
| Access | Request a copy of the personal data we hold about you. | Art. 15 |
| Rectification | Ask us to correct inaccurate or incomplete data. | Art. 16 |
| Erasure | Request deletion of your data (“right to be forgotten”). Subject to our legal retention obligations (see Section 15). | Art. 17 |
| Restriction | Ask us to restrict the processing of your data in certain circumstances. | Art. 18 |
| Data Portability | Ask us at privacy@studia.io for your data in a structured, machine-readable format, or for transfer to another controller where feasible. | Art. 20 |
| Object | Object to processing based on legitimate interests. We will stop processing unless we demonstrate compelling legitimate grounds. | Art. 21 |
| Withdraw Consent | Where processing is based on your consent (for example, marketing communications or optional cookies), you may withdraw consent at any time. Withdrawal does not affect the lawfulness of processing before withdrawal. | Art. 7(3) |
| Automated Decisions | Not be subject to decisions based solely on automated processing that produce legal effects or similarly significant effects. You may contest such decisions and request human review. | Art. 22 |
| Complain to Studia | Complain to us directly about how we have handled your personal data, before or instead of going to the ICO. We acknowledge within five working days and answer within one calendar month. | Data Protection Act 2018, as amended by the Data (Use and Access) Act 2025 |
14.2 How to Exercise Your Rights
Contact us at privacy@studia.io. We will acknowledge your request within five working days and respond within one calendar month. A Student can make a request themselves, whatever their age, and we will explain it in language suited to their age. If your request is complex or we receive a large number of requests, we may extend this period by up to two additional months, in which case we will notify you within the first month. Exercising your rights is free of charge. We may need to verify your identity before processing your request.
14.3 Right to Erasure — Limitations
The right to erasure is not absolute. We may need to retain certain data where:
- We are required to do so by law (for example, financial records for HMRC — see Section 15)
- The data is needed for the establishment, exercise, or defence of legal claims
- The data is subject to a safeguarding hold or ongoing investigation
- Archiving purposes in the public interest or for compliance (for example, OSA audit records)
Ask us at privacy@studia.io to delete your data (“right to be forgotten”), subject to Section 15. Art. 17. If we cannot fully comply with an erasure request, we will explain why and what data must be retained.
15. Data Retention Schedule
We retain personal data only for as long as is necessary for the purpose for which it was collected, or as required by law. Once the retention period expires, data is securely deleted or anonymised.
| Data Type | Retention Period | Legal Basis for Retention |
|---|---|---|
| Livestream Recordings | For as long as the Livestream is available in the Content Library, and 12 months after it is withdrawn Educational service; Content Library feature for Subscribers | Livestreams are recorded automatically so Subscribers can watch them again and so we can check quality and safety. 1-to-1 Sessions are not recorded. Livestream recording cannot be turned off. Educational service; Content Library feature for Subscribers. |
| Account details (all users) | 30 days after the account is closed | Contract; account recovery; storage limitation (Art. 5(1)(e)) |
| Payment records | 6 years from financial year end | s.388 Companies Act 2006; HMRC |
| DBS verification logs | 6 months after engagement | Safeguarding; DBS Code of Practice |
| Age verification records | Kept with the account | Contract; Online Safety Act 2023 |
| Chat messages and transcripts (Livestream) | Duration of Subscription + 30 days | Safeguarding; service provision |
| Chat messages and transcripts (1-to-1) | 90 days | Safeguarding; consistent with session recording retention |
| Lesson join times (1-to-1) | 12 months from the session | Contract; reviewing missed lessons and the Tutor Reliability Ladder’s 12-month count |
| Safeguarding incident records | 7 years from incident (or until the child turns 25, whichever is longer) | KCSIE 2024 requirements; potential legal proceedings |
| Content moderation logs | 3 years | Online Safety Act 2023 compliance; preservation of appeal rights |
| Marketing consent records | Duration of consent + 2 years | GDPR accountability obligations |
| Text-message settings (the date texts were switched on or off, and the notice shown) | Kept with the account, and deleted 30 days after the account is closed | Legitimate interest in showing which texts were sent and why |
| SEND and special category data | Until removed by the user or account closure, whichever is sooner | Explicit consent (Art. 9(2)(a)); deleted promptly on request |
| User research data (anonymised) | Up to 5 years | Legitimate interest (statistical/educational research) |
| Support conversations | 2 years from the date the request is closed | Contract; legitimate interest in resolving and auditing support requests |
| Cookie data | See Section 16.5 (Cookie Retention) | PECR compliance |
16. Cookies and Similar Technologies
This section explains how we use cookies on studia.io and the Studia learning platform. It fulfils our obligations under the Privacy and Electronic Communications Regulations 2003 (PECR), Regulation 6. For a full list of the specific cookies we use, please see our Cookie Notice.
16.1 What Are Cookies?
Cookies are small text files stored on your device when you visit a website or use an online service. We also use similar technologies, such as local storage and session storage, for login functionality and session participation.
16.2 Types of Cookies We Use
Strictly Necessary Cookies (Always On — No Consent Required): These cookies are essential for the Platform to function. They include authentication tokens, security cookies, platform operation cookies for Livestreams and 1-to-1 Sessions, and cookie consent records.
Preferences Cookies (Optional — Consent Required): These store personal settings to improve your experience: display settings, language preferences, and accessibility preferences.
Analytics and Performance Cookies (Optional — Consent Required): We use Google Analytics 4 and PostHog to understand how lessons are used and to improve the Platform. Neither loads or sets a cookie until you consent. We have turned off advertising features in Google Analytics, and PostHog's automatic click capture and session replay are off, so no recording of your screen is made. We do not track browsing behaviour outside Studia, social connections, emotional state, attention scoring, or any data used for advertising.
16.3 Cookies We Do Not Use
We never use:
- Targeted advertising cookies
- Third-party advertising network cookies
- Cross-site tracking cookies
- Behavioural profiling trackers
- Cookies used to score, rank, or profile children
Studia is an education platform, not an advertising platform.
16.4 Consent
When you first visit Studia, we display a cookie banner asking whether you want to allow optional cookies. You may choose to accept or reject each category of non-essential cookie separately. Strictly necessary cookies are always enabled. Consent is informed, specific, and freely given — we do not use pre-ticked boxes. Change your cookie settings at any time under Settings > Account > Manage cookies, or in the footer. Cookie choices are stored per device, not per account.
| Cookie Type | Retention Period |
|---|---|
| Login / Security Cookies | End of browser session, or up to 30 days |
| Preferences Cookies | Until deleted or reset by the user |
| Analytics Cookies | Google Analytics: 2 years. PostHog: 12 months |
17. Data Security
We take the security of your personal data seriously and implement appropriate technical and organisational measures to protect it, in accordance with UK GDPR Article 32. Our security measures include:
- Encryption: Data is encrypted both in transit (using TLS) and at rest.
- Access controls: Access to personal data is granted by role. Access to Tutor DBS information is separately restricted and every access is logged.
- Infrastructure security: Our hosting providers (Neon, Amazon Web Services, and Vercel) maintain industry-standard security certifications and practices.
- Regular assessments: We review our security controls at least annually and whenever we make a significant change to the Platform, and we act on the findings.
- Incident response: We have breach detection, response, and notification procedures in place (see Section 20).
- Staff training: Everyone at Studia with access to personal data completes data protection and information security training. Outsourced support agents are contractually required to complete equivalent training before they are given access.
While we use commercially reasonable measures to protect your data, no method of electronic transmission or storage is completely secure. We cannot guarantee absolute security, but we are committed to protecting your information to the highest practicable standard.
18. Support Team Account Access
In exceptional circumstances — for example, when you contact us about a technical problem that cannot be diagnosed without examining your account — a member of our support team may need to access your account.
18.1 What Access Involves
Support may be provided by Studia staff or by agents of ModSquad, our outsourced support partner, working under contract to us and under the same obligations. To reproduce a problem you have reported, a member of the support team may sign in to your account and see the Platform as you see it. A banner is shown on the account throughout, and certain actions are blocked.
If a support team member accesses your account, they may be able to see:
- Your account details and profile information
- Your Subscription history and booking records
- Usage data and session history relevant to the issue you have reported
18.2 Our Commitment
We will only access your account with a clear support purpose and will not browse, retain, or use account data for any purpose other than resolving the issue you have raised. Account access by support staff is logged and auditable.
If you have concerns about support team access to your account, you may contact us at privacy@studia.io.
18.3 Children's Accounts
For Students under 13, any support team account access will be handled in accordance with our children's data protections in Section 6. We will contact the Parent or Guardian if account access is required in connection with a child's account.
19. User Research and Feedback
19.1 How We Use Feedback
When you submit feedback, suggestions, ratings, or responses to surveys about the Platform or our services, we may use that information to:
- Improve the Platform's features, usability, and educational effectiveness
- Understand which aspects of the Platform are working well and which need improvement
- Develop new features or adjust existing ones
- Inform our internal reporting and business decisions
We process feedback under our legitimate interest in improving our services. You are never obliged to respond to surveys or submit feedback, and your use of the Platform is not conditioned on doing so.
19.2 User Research
We may occasionally invite users to participate in user research activities — for example, interviews, usability testing sessions, or surveys — to understand how the Platform is used and how it can be improved. Participation is entirely voluntary.
Where we conduct user research:
- We will explain the purpose and scope before you participate
- We will ask for your explicit consent before recording any research session
- We will anonymise or aggregate research findings before using them internally
- We will never identify individual users in any research output without their prior written consent
For children, any user research participation requires prior parental consent, and we will apply additional protections appropriate to the child's age.
19.3 Educational Research Partnerships
We may occasionally use anonymised, aggregated Platform data to contribute to or participate in educational research — for example, research into how young people learn online, the effectiveness of AI-assisted tutoring, or exam preparation outcomes.
Any such research:
- Uses only anonymised or aggregated data that cannot be linked back to individual users
- Is conducted in accordance with applicable research ethics standards
- Never involves sharing identifiable personal data with research partners without explicit consent
If you do not wish for anonymised data about your use of the Platform to be included in research, you may opt out at any time by contacting privacy@studia.io.
19.4 Intellectual Property in Feedback
By submitting feedback or suggestions to us, you grant Studia a non-exclusive right to use that feedback to improve the Platform and our services. We will not compensate you for feedback, and by submitting it you confirm that you are free to share it with us. You retain no ownership rights in any improvements Studia develops based on feedback you provide.
20. Data Breach Notification
We have incident detection, response, and notification procedures in place in accordance with UK GDPR Articles 33 and 34 and the Data Protection Act 2018.
20.1 Notification to the ICO
If a personal data breach occurs that is likely to result in a risk to the rights and freedoms of individuals, we will notify the Information Commissioner's Office (ICO) within 72 hours of becoming aware of it, unless the breach is unlikely to result in such a risk.
20.2 Notification to Individuals
Where a personal data breach is likely to result in a high risk to your rights and freedoms, we will notify you directly, without undue delay. A “high risk” breach is one that could, for example:
- Result in unauthorised access to your personal data
- Expose sensitive information, including SEND data or session recordings
- Enable identity theft, fraud, or financial loss
- Put a child's safety at risk
For children's accounts specifically: if a breach affects the personal data of a child, we will notify the Parent or Guardian directly by email, without undue delay. We will explain what data was affected, what we are doing to address the breach, and what steps, if any, you should take.
Where a breach does not meet the threshold for individual notification (because the risk to individuals is not high), we will record it internally but are not required to notify you directly. In such cases, we may still choose to notify you as a matter of good practice.
20.3 What We Will Tell You
In any breach notification to individuals, we will include: a description of the nature of the breach; the categories and approximate number of individuals and records affected; the likely consequences of the breach; the measures we have taken or propose to take to address the breach; and a contact point for further information.
21. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements.
- Material changes: We will notify you by email and/or by prominent notice on the Platform before the changes take effect.
- Updated date: The “Last Updated” date at the top of this policy will be revised.
- Regular review: We encourage you to review this Privacy Policy periodically.
- Children's Privacy Notice: If we make changes that affect how we process children's data, we will also update the Children's Privacy Notice.
22. Contact and Complaints
22.1 Contact Us
| Purpose | Contact |
|---|---|
| Privacy enquiries and data rights | privacy@studia.io |
| Safeguarding concerns | safeguarding@studia.io |
| General support | support@studia.io |
| Legal matters | legal@studia.io |
| Postal address | Studia (SOPHOS EDUCATION LTD), 10 St. Edmunds Square, London, England, SW13 8SA |
| Company number | 14321333 |
22.2 Right to Complain to the ICO
If you are not satisfied with our response to a privacy concern, or you believe we are processing your personal data in a way that is not lawful, you have the right to lodge a complaint with the Information Commissioner's Office (ICO):
- Website: www.ico.org.uk
- Telephone: 0303 123 1113
- Post: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF
You have the right to complain to us at privacy@studia.io about our handling of your data. This does not affect your right to go to the ICO.
This Privacy Policy should be read in conjunction with our Terms of Service, Children's Privacy Notice, Cookie Notice, Community Guidelines, and, for Tutors, the Tutor Terms of Service.