Privacy

Accounts are created by the school from its own roster. The school decides who has an account, what class they are in, and when an account ends. GyanSaar processes that data on the school’s instructions; the school remains responsible for it.

Questions about a particular child should go to the school first, because the school holds the record of who each account belongs to. You can also write to shruti.kaksha@gmail.com.

• Account details. A display name, the role the school gave you (pupil, teacher, guardian, principal), and the class you are in. Nothing else identifies you.
• A sign-in address. At a school that uses Google sign-in, this is the school Workspace address — it is what authenticates you, so we have to hold it. At a school that does not, we hold no email or phone number for a pupil at all: the sign-in name is a roll number, and only the school knows whose it is.
• Lesson recordings and transcripts. A teacher chooses to record a lesson. The recording is transcribed so the class summary and homework can be drawn from it.
• Homework you hand in — the pages you upload, what our software read from them, and the marks and feedback a teacher released.
• Questions you ask through the portal, and the answers given.

• Pupils’ voices. A lesson recording is filtered on the teacher’s phone before anything is sent. Only the teacher’s speech leaves the device; the rest, including every pupil who speaks, is discarded there and never uploaded.
• Any profile of what a child struggles with. When you ask a question, it is used to find the right part of the lesson and then discarded. It is never kept in a form that could be searched or clustered to build a picture of you.
• Scores or rankings of pupils or teachers, of any kind, at any level.

• Your marks are yours. A pupil sees their own work and their own marks. Another pupil cannot, and this is enforced by the database rather than by the screen.
• No mark is visible until a teacher has released it. Software proposes; a teacher decides. Until then you see “being marked”, never a provisional figure.
• The questions a pupil asks in the portal are private to that pupil. Not the teacher, not a parent. Teachers see only which topics a class is struggling with, with no names attached. Questions asked in a family WhatsApp thread are different and are visible to that household, because the handset is shared.
• Nobody can listen to a lesson recording — not a teacher, not a parent, not the principal, not us. The audio and the raw transcript are readable only by the software that processes them.

Where a school uses it, signing in with Google tells us your name and your school email address, and nothing else. We ask Google for no other permission — not your mail, not your files, not your contacts, not your calendar.

Your Google password is never seen by GyanSaar. Signing in happens on Google’s own pages.

GyanSaar runs on services that store or process data on our behalf: Supabase (database and accounts), Cloudflare R2 (files), Vercel (hosting), Sarvam AI (turning speech into text), and model providers reached through OpenRouter (drafting summaries and proposed marks). Where a school uses the WhatsApp channel, Meta processes those messages.

None of them is permitted to use this data for their own purposes. We do not sell it, and there is no advertising in GyanSaar.

You can ask what is held about you, ask for it to be corrected, or ask for it to be deleted. A parent may make that request on behalf of a child. Ask the school first — it holds the record of whose account is whose — or write to us at the address above and we will work with the school.