Skip to content
ReadoyeSign inBook a demo

Privacy policy

Readoye is a digital library for schools, a service operated by KVA Labs. Children use it through their school, so we collect as little as we can and we treat the school as the party responsible for its students. This page explains what we hold, why, and for how long.

Who is responsible

Each school that uses Readoye is the data fiduciary for its students' data under India's Digital Personal Data Protection Act, 2023 (DPDP Act). The school decides which students get accounts and obtains the consent of parents or guardians. KVA Labs acts as the school's service provider (data processor) and processes that data only to run the library for that school.

For visitors to this website, school staff and people who contact us, KVA Labs is the data fiduciary.

What we collect about students

A student account is created by the school. It holds:

  • the school, the class and section;
  • a login code and a PIN, stored only as a salted hash (we cannot read the PIN);
  • the first name or nickname the school or student entered;
  • the time of the last sign-in;
  • reading position in each book (book, chapter, place on the page);
  • daily reading totals: minutes read, pages turned, books touched, books finished, streak and badges, used for the class and school leaderboards;
  • for each book the student has opened: the minutes read on it, the first and last day it was read and whether it was finished.

If the school uploads a class list in Students & codes, we also keep, for each child, the full name, class and section, roll number and admission number the school entered. They are used only so that code slips can be printed and re-printed for the right child. They can be seen by the school's administrators (not by other schools), and they are deleted together with the student.

We do not collect a student's date of birth, phone number, email address, home address, photograph or location, and we do not run advertising or profiling on student accounts. We do not store IP addresses against a student; see "Sign-in protection" below for the short-lived counters.

School administrators, and the teachers of the student's class, can see in the school's Reading reports which books a student has opened, how far they have got, the minutes spent on each and when they last read it. Other students, other classes' teachers and other schools cannot. These per-book records are deleted when the student is deleted.

Leaderboards show a first name and class to students and staff of the same school. Students from other schools never appear: the all-schools board lists school names with school totals only.

What we collect about school staff

  • name, work email and a password (stored only as a hash). A one-time password given by an administrator stops working after 7 days;
  • the school and classes they manage, and for teachers the class list entry the school uploaded (name, email, subject, classes);
  • for the school admin: school name, city, state, board, GSTIN, the school logo if uploaded, and billing and invoice records.
  • We email staff (through Resend) to verify an address and to reset a password. Students never receive email from us.

Visitors and enquiries

If you fill in the demo form we keep the details you enter (name, school, role, city, phone, email, message, and your consent choice) so we can reply. We keep them until you ask us to delete them or we no longer need them. Payments are handled by Razorpay; we do not see or store card or bank details.

Cookies and tracking

Signing in uses two strictly necessary, httpOnly cookies (a session token and a refresh token). Reader settings, class choice and, when signed out, reading position are kept in your browser's local storage. We do not use advertising cookies.

While you are signed in, the books you open are also saved on your device (in the browser's storage; picture-book images in a service worker cache) so an open reader keeps working when the internet is slow or off, together with your reading place and reading time that could not be sent yet. We do not store pages or your login token for offline use. They are kept only for your account, stop being available after 20 minutes without use on the device, are removed when you sign out, when you are signed out for inactivity, when another person signs in on the same device, or when your school's access ends, and are not used to identify or track you.

We use Vercel Web Analytics on our pages, including the signed-in library, to count visits and page views. As described by Vercel, it sets no cookies and does not keep your IP address; it records the page, referrer, country, browser and device type. We do not combine this with student accounts.

How we use data

  • to let students and staff sign in and continue reading where they left off;
  • to show class and school reading activity and leaderboards;
  • to invoice and support schools;
  • to keep the service secure and fix faults.

We do not sell personal data, and we do not use it for advertising or profiling children.

Where data is kept and who processes it

Data is stored with our infrastructure providers, who process it for us under their own security terms: Convex (database and uploaded school logos), Vercel (hosting and page-view analytics), Cloudflare (book and encyclopedia images), Resend (staff email) and Razorpay (payments). We will list the service locations here once the production setup is final.

When a school uploads a class list in an unusual layout, our AI provider (OpenAI) may process the spreadsheet's sheet names, column headings and a few sample rows with every name hidden (only the first and last letter of each word; a sheet name is shown as it is only when it is just a class such as 5A), only to read the layout. We never send the list of students' names to it.

Retention and deletion

  • A school admin or class teacher can delete a student at any time; the code, PIN hash, names (including the class list entry), sessions, reading progress and activity records are then removed together. A school admin can delete the whole school the same way.
  • Every day a check lists student accounts with no sign-in for 12 months. Today we review that list and delete those accounts ourselves; we may switch this to automatic deletion later and will update this page if we do. Schools should still delete a class's accounts at year end. Sign-in sessions last at most 30 days, and anyone (student, teacher, admin) is signed out automatically after 20 minutes without activity.
  • Schools that sign up but never subscribe and show no activity for 90 days are listed the same way and removed after review.
  • We do not yet delete a school's data automatically when its subscription ends. The school can delete it itself, or ask us to, at any time.
  • Sign-in protection counters (below) are deleted within a day or two.
  • Billing and invoice records are kept for as long as tax law requires. Enquiry-form details are kept until you ask us to delete them or we no longer need them.

Your rights

You, or the parent or guardian of a student, can ask to see, correct or delete the data held about you or the student, and can withdraw consent, by contacting the school or by writing to us. We will respond within a reasonable time and in line with the DPDP Act.

Grievance officer: KVA Labs. Grievances and data requests: support@kvalabs.com. If you are not satisfied with our reply you may complain to the Data Protection Board of India once it is operational.

Security

PINs and passwords are hashed, connections use HTTPS, and access to data is limited to the school's own staff and to us.

Sign-in protection: to stop people guessing student PINs, we count wrong sign-in attempts per student code or typed name, per school and per network address (IP address). These counters hold no readable name (a typed name is kept only as a one-way code made with a secret key), are not linked to a student's profile and are deleted within a day or two. Students sign in with their school code, their name and a PIN; to find the student, the sign-in keeps a one-way code of the name on the slip, made with a secret key (HMAC), never the name itself. New PINs are 6 digits.

No system is perfectly secure; if there is a breach that affects personal data we will tell the affected schools and the authorities as the law requires.

Children

Readoye is for school use. Students do not register themselves; their school creates their accounts. If you think a child's data was added without proper consent, contact the school or us and we will remove it.

Changes and contact

We may update this policy and will change the date on this page when we do. Questions, requests and grievances: support@kvalabs.com (KVA Labs, Mumbai). See the contact page for details. Last updated: 21 October 2026.

Privacy · Terms · Refunds · Contact