School data

Data protection for schools

Juno Labs Limited (company number 17347135) provides JunoClass. Registered office: 281 Lidgett Lane, Leeds, England, LS17 6PD. This page is a summary. The privacy policy and a signed data processing agreement take priority if they say something different.

• Roles

  When a school or teacher uses JunoClass for a class, the school is usually the controller of pupil data and Juno Labs Limited is the processor. Juno Labs Limited is the controller of teacher accounts, and of students who sign up themselves.

• What we store

  Name, email, role, optional school name, class membership, class codes, invitations, seats, payments, teacher-written questions, and attempts (answers, correctness and times).

• Sign-in

  Google, Microsoft, or email and password through Firebase Authentication. We do not check that an email is on a school domain.

• Who can see what

  Teachers see the classes they own or collaborate on. Students see their own work. There is no school-admin area and no search across every pupil in a school.

• Companies we use

  Firebase Authentication (Google) for sign-in, Supabase to store application data, and Stripe for card payments. Microsoft also processes data if someone signs in with Microsoft.

• DPA and IT questionnaires

  Email hello@junoclass.com from a school address. We will answer in writing and can provide a data processing agreement. There is no downloadable IT pack in the product.

• Retention and deletion

  Data stays while the account and classes are needed to run the service. A school can ask us to delete pupil records. We will ask for enough detail to verify the request.

• Payments

  Seat purchases go through Stripe when card payments are enabled. We keep the payment records needed to fulfil seats and to meet accounting rules.

Questions? Contact us or email hello@junoclass.com.