Legal
Privacy Policy
Last updated 20 October 2026
Most people using IndusVidhara are children, or parents acting for them. This page says plainly what we hold, who can see it, and how to get it removed.
1. Who we are
IndusVidhara is operated from India and provides software to tuition teachers and coaching institutes. In data-protection terms we are the data fiduciary for account data, and a data processor for the teaching material and student records an institute puts into the platform — that content belongs to the institute, not to us.
For anything in this policy, write to privacy@indusvidhara.com.
2. Children's data
Students on this platform are usually minors, and an account is often created and operated by a parent or guardian. We treat that as the normal case rather than an exception.
- By creating a student account for a child, the parent or guardian confirms they consent to this policy on that child's behalf.
- We do not show advertising to students, and we do not profile children for advertising.
- We run no analytics of any kind on pages a student is signed in to. Nothing a child does inside the platform is measured or sent anywhere. See clause 7.
- We do not ask students for a photograph. A teacher's profile photo is optional and public; a student's is not collected.
- Students cannot see each other's profiles. There is no public student directory, no student-to-student messaging and no comments.
- A parent may ask us to delete their child's account and data at any time, and we will do so subject to clause 8.
3. What we collect
Everyone. Name, email address, phone number, password (stored only as a hash — we never see it), and basic sign-in records such as time and device.
Students. Class or grade, school name, date of birth, and the name and phone number of a parent or guardian. Attendance, fee records, marks and anything a teacher records about their learning.
Teachers. Qualifications, institution, graduation year, subjects, languages, city, fee range, and — where you choose to provide one — an identity document used only to verify that you are who you say you are before you are allowed to teach children.
Payments. When online payments are enabled, card and bank details are handled by the payment provider and never reach our servers. We keep the amount, date and status of a transaction.
4. Why we hold it
- To run the service you signed up for — classes, attendance, fees, material and messaging between a teacher and their own students.
- To verify teachers. We check qualifications and identity before a teacher can enrol children or appear publicly. This is the single most important thing we do with personal data.
- To review teaching shorts before students can see them.
- To take payment, issue invoices and meet tax obligations.
- To keep the platform secure and investigate abuse.
5. Who can see it
- A student's own teacher sees their profile, parent contact, attendance and fees. Other teachers cannot.
- Our team sees what is needed to review a teacher application, moderate a video or answer a support request. Access to identity documents is logged.
- A teacher who receives a join request sees the student's name, class and message — not their email or phone. Contact details are shared only once the teacher accepts.
- Nobody else. We do not sell personal data, and we do not share it for anyone else's marketing.
6. Where it is stored, and third parties
Account data sits in a managed PostgreSQL database. Files — notes, recordings, images — are stored either in our own object storage or, if an institute connects one, in their own Google Drive, Dropbox or OneDrive. Where an institute uses their own storage, that provider's terms apply to those files as well as ours.
Some teaching shorts are hosted by YouTube, Vimeo, Instagram or Facebook rather than by us. When you play one, that company can see that a video was viewed and may set its own cookies. We cannot control what they collect, and their privacy policy applies to that playback. Video we host ourselves involves no third party.
We use email and payment providers acting on our instructions, and servers located in India and, in some cases, elsewhere.
7. Cookies and website analytics
We use Google Analytics to count visits to our public pages — the home page, the teacher directory, the sign-in and registration pages, and these legal pages. It is deliberately set up to count visits rather than to recognise people, and it is switched off everywhere else.
- Never behind a sign-in. Analytics does not load on any page inside a student, teacher or administrator account. A child's activity on this platform is never measured.
- No cookie and no device identifier. Nothing is stored on your device for analytics, so you are not recognised on a later visit. A returning visitor is counted as a new one — we accept the less useful figure in exchange for not following anybody.
- No advertising. Google's advertising, remarketing and cross-device identity features are turned off. Nothing collected here is used to target an advertisement anywhere.
- Your IP address is shortened before it is recorded, and is used only to tell which country or region a visit came from.
- Names and identifiers are removed from the address. A teacher's public profile is reported as
/teachers/profile/:idrather than with their name or number, and anything after a?in a link is never sent.
What Google receives, then, is: which public page was opened, roughly where in the world the visit came from, what kind of browser and device was used, where the visitor arrived from, and when. We use it to see which pages people find and which they leave — nothing more.
If you would rather not be counted at all, Google publishes a browser add-on that blocks it, and any tracker-blocking extension or browser setting will also stop it. Nothing on this site stops working if you do.
8. How long we keep it
Account data is kept while the account is open. When an account is closed we delete personal data within 90 days, with two exceptions:
- Financial records — invoices, payments and fee history — are retained for eight years, because Indian tax law requires it.
- Safety records — a rejected teacher application, a content takedown, a report about a child's safety — are retained so the same problem cannot simply be re-registered.
Archived batches and courses are hidden but not deleted, so a teacher keeps the history of classes that have already run.
9. Your rights
Under the Digital Personal Data Protection Act, 2023 you may ask us to show you the data we hold about you, correct it, delete it, or withdraw a consent you previously gave. A parent may exercise these rights for their child.
Write to privacy@indusvidhara.com. We will respond within 30 days. If you are not satisfied, you may complain to the Data Protection Board of India.
Some data cannot be deleted on request — see clause 8. We will tell you if that applies and why.
10. Security, and what happens if it fails
Passwords are hashed, traffic is encrypted, access to sensitive records is restricted by role and identity-document access is logged. Paid material is served through short-lived links rather than public URLs.
No system is perfect. If a breach affects your personal data we will notify you and the Data Protection Board as the law requires, and tell you what was involved rather than only that “an incident occurred”.
11. Changes
If we change this policy in a way that materially affects you, we will tell you by email and in the app before it takes effect. The date at the top always reflects the current version.