Contents
SOYL Academy is a website (app.soylai.com) and Android app where teachers and tutors set interactive homework and practice for pupils from Grade 1 to Class 12: maths, physics and chemistry, from Grade 6 also biology, coding, earth and space, and social science, and in Classes 11 and 12 the subjects of the science, commerce and humanities streams. Colleges also use it for their undergraduate and postgraduate students (see College students). This policy explains, in plain English, what personal data SOYL Academy keeps about teachers, pupils and parents, why, who can see it, how long it is kept and what you can ask us to do. It is written for India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”).
For parents: the two-minute version
- Your permission comes first. Your child cannot sign in or be given work until permission is recorded: either you confirm it yourself with a secure link we email you, or your child’s school records that it has your permission (for example a signed form). You can withdraw it at any time; your child is then signed out of every phone and computer at once.
- What we keep about your child: their name, grade and class, the school’s admission number if the school gives it, their answers and attempts, the hints they used and when they worked, any practice they do after their teacher has looked at their work, the weekly “Revisit” questions they answer if their teacher turns these on, when they opened their teacher’s feedback, their teacher’s feedback and marks, and which phones or computers are signed in. Your child signs in with a student code and a PIN they choose (we keep the PIN only in a form that cannot be read back); they have no email address or password with us. We do not collect photos, location, contacts or anything from the camera or microphone.
- What we keep about you: the name, relationship, email address (and phone number, if given) that the school or tutor recorded, and the record of your permission.
- Who sees it: your child’s teachers and school administrators; you (your child’s homework, hand-in dates and teacher feedback, and, for SOYL Future Builders, your child’s portfolio of handed-in work, after signing in with a code sent to your email); and SOYL staff only to run and support the service. There are no adverts, no selling of data, no advertising or analytics trackers, no chat between users and no public profiles.
- Emails: if your child’s school or tutor turns it on, a short weekly email about your child’s homework, only to an email address you have proved is yours. It never contains marks or comparisons with other children, and every one has a link to stop them.
- AI: only if you say yes separately. Then, when your child asks for help, the question, its answer for the teacher and your child’s recent tries at it may be sent to Microsoft’s Azure OpenAI service to write the next hint, and the teacher may ask for an AI summary of the work. Your child may also type a short message to their companion (one of SOYL’s five cartoon characters, chosen by your child), speak an answer in a mission, or read a sentence aloud for speaking practice in English; the AI turns speech into text or gives pronunciation feedback, and the recording is not kept. In missions, the AI may ask your child to explain their thinking, score that explanation for the teacher, and suggest which idea your child may have mixed up; a teacher checks every suggestion. Your child’s name is never sent. This AI processing may happen outside India.
- If your child writes something worrying: if something your child writes suggests they may be unsafe or very unhappy, their teachers see their exact words privately, so they can check in with them under the school’s own safeguarding process.
- Where and how long: data is stored on Microsoft Azure in India. Your child’s work is deleted automatically 24 months after each assignment’s due date (the school can choose 6 to 120 months).
- Your rights: you can ask for a copy, a correction or deletion of your child’s data, and withdraw permission. Ask your child’s school or tutor, or write to us at outreach@soyl.cloud.
Who we are
SOYL Academy is provided by SOYL AI Private Limited (“SOYL”, “we”, “us”). For anything about privacy, including requests and complaints, write to outreach@soyl.cloud. Our grievance officer is Ryan Gomez. Postal address: B1301, Satna Power Tower, 7th Cross, Bengaluru 560043.
Schools and tutors choose to use SOYL Academy for their pupils. A school or tutor decides which pupils use it and what work they are set, and records or requests the parents’ permission. SOYL runs the service for them and handles the data as this policy describes. A school may also have its own privacy notice for parents.
Back to topWhat we collect, and why
We collect only what the service needs. Each table says what we keep and what it is for.
| What | Why |
|---|---|
| Name, grade, class or batch, school or tutor, admission number (if the school gives it) | So the right work reaches the right pupil and the teacher knows whose work it is. |
| Answers, attempts, the result of each automatic check, hints used (including the exact text of any AI hint), and when each answer was given | So the teacher can see progress, give feedback and decide marks. |
| Reports a pupil sends with “Report this help” about an AI hint: which hint, an optional reason (for example “confusing”) and when | So the teacher can see AI help that went wrong, and so SOYL can count reports by school and reason (without names) to improve the help. |
| Future Builders AI lab runs, only when the teacher switched the live AI model on for a task and the pupil has AI permission: the question the pupil typed and the matching parts of the notes, or the agent task’s goal, settings and steps; the AI’s reply; the automatic check of its quotes; and whether the pupil approved a save, and when | So the teacher can see exactly what the AI said and check the pupil’s judgements about it, and so the pupil’s work can be marked against what really happened. |
| Wellbeing check-ins: when something a pupil writes in an answer suggests they may be unsafe or in distress, the exact words, the assignment and question, when, which automatic check noticed it, and whether a teacher has marked it handled (by whom and when) | So the pupil’s teachers can check in with them. Only the teachers of the pupil’s class and the school’s administrators see check-ins; not parents (in the parent area), other pupils, other schools, or SOYL’s administration console. Nothing is emailed. The school’s own safeguarding process decides what happens next. Check-ins are left out of a data copy unless the school decides to include them after a safeguarding review. |
| Activity events in simulators (for example a measurement taken), with a random device reference and the device’s clock time | So answers sync correctly from phones that were offline and the teacher can see how the pupil worked. |
| When work was handed in, and whether that was after the due date | So the teacher (and the parent) can see it; late work is accepted. |
| When the pupil opened their teacher’s feedback (first and last time), and a scrambled fingerprint of the feedback they saw (never the text again) | So “New feedback” shows only for feedback the pupil has not read yet, on every phone or computer, and shows again if the teacher changes it. |
| “Try these again” practice after the teacher has looked at the work: which questions were copied, the pupil’s practice answers and the result of each automatic check, and the hints shown (including the exact text of any AI hint and any report of it) | So the pupil can practise what they did not get right first time, and the teacher can see how the practice went. Practice never changes the work that was handed in, its feedback or its mark. |
| “Revisit” sets (only if the teacher turns them on for the class): which earlier questions each weekly set held, the pupil’s answers and the result of each automatic check, the reviewed hints shown, and the pupil’s conversation with their companion about a question in the set (AI-written only for pupils with AI permission, and only if the teacher leaves the companion’s AI help on for the class; this is the default for new classes) | So the pupil can practise what they learnt weeks ago, and the teacher can see what they can now do on their own. A set never changes the work that was handed in, its feedback or its mark. |
| Short checks a teacher sets before and after a unit, and once again a few weeks later (no help, one answer per question, no marks shown to the pupil): the pupil’s answers and the result of each automatic check | So the teacher can see what the class learnt and kept. The teacher sees each pupil’s results; SOYL sees only counts for the whole class (for example “4 of 6 did better”), never names, to check whether the programme helps. |
| Missions: which part of the mission the pupil reached, how long they were active in it, the items they were given and why, their answers and the explanations they wrote or spoke (as text), how sure they said they were, what they chose to answer with (for example writing or speaking), and their reflection at the end | So the mission can choose the next step for the pupil, and so the teacher can see how the pupil worked and what they understood. |
| Messages a pupil types to their companion, the teaching companion (up to 500 characters each; in their work, in practice after their teacher has looked at it, and in “Revisit” sets), the choices they tap (for example “Give me a nudge”), the companion’s replies and where each reply came from (AI, the teacher’s hint or SOYL’s own reviewed lines), which of the five characters the pupil had at the time, the automatic checks run on each reply, and when; and when the companion offered help, and whether the pupil took it; and when it stopped offering help because fewer than 3 of the pupil’s last 10 tries were right (no feelings or moods are recorded) | So the companion can help with the question in front of the pupil, so the teacher can see what the pupil asked and what the companion said, and so the teacher gets a private note to check in with a pupil who is finding the work hard. |
| How the pupil has set up their companion: which of SOYL’s five characters helps them (Arth, Karm, Josh, Lekha or Sach; Arth unless they choose another), whether it offers help and reads aloud, and a voice choice if we add one. Saved to the pupil’s account so the companion is the same on every device; teachers do not see it. The look a pupil chose for the earlier companion before November 2026 (its age, colour and what it wore) is still stored until we delete it, is no longer used, and is included in a data export | So the companion looks and behaves the way the pupil chose. |
| Whether the pupil has chosen to show or hide their garden (a flower for each piece of work handed in). Saved to the pupil’s account; teachers do not see it | So the pupil’s pages look the way they chose. |
| Shown back to the pupil on their own Home and Progress pages, worked out each time from the answers already listed above and not stored again: the dates on which they checked an answer (“learning days”), how many answers they checked today (the daily goal), and five counts of how they worked (fixed an answer after another try, explained in their own words, used a hint and then got it, came back to work on another day, tried a simulator question). No marks, no speed, no comparison with other pupils | So pupils can see their own effort. Nobody else is shown these figures; teachers already see the answers they come from. |
| In missions, the companion’s questions about the pupil’s reasoning (“Defend”), the pupil’s answer and its score (0–3, written by AI only with AI permission) | So the teacher can see whether the pupil can explain their thinking in their own words. |
| Misconception labels: an idea the pupil may have mixed up (for example “power and energy treated as the same”), how sure SOYL is, where the label came from (SOYL’s rules, AI or a teacher), the evidence it rests on (the pupil’s answers, simulator actions or words), and the teacher’s decision to confirm, change or reject it | So the teacher can plan the next lesson and send a short follow-up to the pupils who need it. Teachers’ decisions are kept to make the labels more accurate. |
| The Thoughtprint at the end of each mission: what the pupil can now do, where their thinking changed, what was found and fixed, a short quote of their best reasoning and the teacher’s comment. It never shows a mark, and never quotes words that raised a wellbeing check-in or look like contact details | So the pupil, their teacher and their parents can see what the pupil learnt and how. |
| Teacher feedback, marks, corrections and AI summaries the teacher asked for | Teaching and feedback. |
| Future Builders build records: what the pupil types about a real build they made in class (the parts used, the checks ticked, their readings beside the simulation’s, the tests, what went wrong and how they fixed it, their own part in a team project). No photos. These are the pupil’s own reports, labelled “student-reported”; SOYL measures nothing | So the teacher can see the evidence of the real build beside the simulation it was planned on. |
| Future Builders portfolio comments: a teacher’s short comment on one piece of the pupil’s Future Builders work, who wrote it and when | So the pupil, and the parents who can sign in, see the teacher’s view of each piece of work in the pupil’s portfolio. The portfolio itself is put together from the pupil’s handed-in work each time it is opened; it has no public link. |
| A student code and a PIN, stored only as a one-way hash (the school sees the code, never the PIN); a temporary setup PIN from the teacher, also only as a one-way hash; when the pupil last signed in; and how many wrong PINs were typed in a row, with any pause or lock that caused | So the pupil can sign in on any device, including a shared school computer, without an email address, and so guessing a PIN is stopped. |
| Signed-in devices: a type label (for example “Android app” or “Shared computer”), whether it was a shared computer, when added and last used; the sign-in credential only as a one-way hash | So a lost phone can be signed out and a pupil’s sign-in on a shared computer ends on its own. |
| Consent records: which permission, how it was given, when, by whom and the notice version | To show that permission was given before the pupil used the service. |
| What | Why |
|---|---|
| Name, relationship, email address and phone number, as recorded by the school or tutor | To ask for and record permission, and to let you sign in to see your child’s progress. |
| Your decision on permission, with your email or phone kept only as a one-way hash and a masked form (like “p•••@example.com”) | Proof of your decision without keeping a second copy of your contact details. |
| Parent sign-in: a one-way hash of your email address, when sessions started and ended, your last sign-in time | To keep your sign-in secure and let you or the school sign you out. |
| Email delivery records: the template, outcome and a hash and masked form of the address (never the message itself) | To know whether an email reached you. |
| Weekly summary email (only if the school or tutor turns it on, and only to an address you have proved is yours with a code): what was set, handed in and late that week, the first line of new teacher feedback, the number of days your child worked and a question to ask them, built from what your child can already see; never marks or comparisons with other children. A record that each weekly email was planned and sent (ids and the outcome, not the message), and, if you unsubscribe, a one-way hash of the address that unsubscribed | To keep you in touch with your child’s homework. Every email has a link to stop them. |
| What | Why |
|---|---|
| Name, role, school, classes taught; the email address an invitation was sent to; an identifier from Microsoft Entra sign-in | To sign you in and show you only your school’s classes. |
| Invitation emails: when each was sent and the outcome, with a hash and masked form of the address (never the message itself) | To email your invitation and show your school whether it went. |
| Daily email settings: on or off, the hour you chose, and the email address it goes to (the one you were invited with, signed up with, or signed in with when you saved the settings); a record that each day’s email was planned and sent (ids and the outcome, not the message) | To email you, on days with something waiting, the hand-ins to review, drafts ready and work not started (counts and assignment titles, never pupils’ names), until you turn it off. |
| For tutors who sign up: name, email, city, subjects and grades taught, the terms version accepted and when, trial and payment status | To run your workspace and trial. |
| For schools: a contact name and email, city and board | To run the school’s account. |
| Your teaching materials: pasted or spoken notes (as text; recordings are not kept), uploaded files (PDF, Word, photos), drafts, published assignments and visuals | To create assignments for your pupils. |
| Your school’s assignment library: the content of each assignment your school publishes (questions, answers, hints, simulator settings and learning-outcome codes; never notes, uploaded files or their names, or anything about pupils). If a teacher chooses “Share with every school”, SOYL reviews it and may make that content available to teachers in other schools | So your teachers can reuse your school’s work instead of starting again, and, once SOYL has reviewed it, teachers elsewhere can too. |
| A record of important actions (for example publishing work or recording consent), with ids only | Security and accountability. |
| How long you are actively using the screens for making and reviewing assignments: a number of seconds per day and assignment, counted only while the page is open in front of you and you used it in the last minute (never what you type or what is on the screen), kept 24 months; and, if you choose to answer, your own estimate of how long an assignment takes you without SOYL | To show you the time you spend in SOYL each month, and so SOYL can see, as averages across schools and never person by person, whether it saves teachers time. |
From everyone: when you use the website or app, our servers handle your internet (IP) address and browser or app details to answer the request. We use the IP address briefly, in memory, to limit repeated sign-in attempts; we do not store it with your account. See Logs and error monitoring.
We do not collect school pupils’ email addresses or phone numbers (college students’ college email addresses are the exception: see College students), photos of pupils, precise location, contacts or advertising identifiers. The camera is used only when someone taps Scan QR code in the Android app: the code is read on the phone, and no picture is kept or sent to us. The microphone is used only when a teacher chooses to speak their notes (see AI processing); pupils’ microphones are never used. The Android app asks for internet access, and for the camera only when Scan QR code is first used.
Back to topParents’ permission comes first
A pupil’s data is used only with the permission of a parent or lawful guardian, and a pupil cannot use SOYL Academy until that permission is recorded. Permission is recorded in one of three ways:
- The parent confirms with a secure link. The school or tutor enters the parent’s email address; we email the parent a personal link (valid for 7 days). The parent reads what we keep, proves the email is theirs with a 6-digit code (valid for 10 minutes) and chooses yes or no. Tutors must always use this method. Schools may.
- The school records the parent’s permission. Many schools collect permission on their own forms. A school administrator then records in SOYL Academy that the parent gave permission, naming the guardian and where the evidence is kept (for example “Signed form on file, 2026–27”). In this case the school, not SOYL, collects and holds the parent’s decision.
- The school confirms it holds permission for every pupil it adds. A school that asks parents for permission on its admission or annual forms may confirm this once, saying where the forms are kept and whether they also cover AI features. Pupils the school then adds are recorded as having permission under that confirmation; we record who confirmed it and when. The school, not SOYL, collects and holds the forms. This never overrides a parent: a parent who refused or withdrew permission stays refused. Tutors cannot use this method.
There are two separate permissions:
- Using SOYL Academy (required): without it the pupil cannot get a sign-in code or be given work, and our database refuses the sign-in even if something else goes wrong.
- AI features (optional): AI hints and AI summaries. Without it, the pupil gets the teacher’s own hints and nothing is sent to the AI about their work.
A parent who confirmed by link can withdraw at any time with the link in the confirmation email. Otherwise ask the school or tutor, or write to outreach@soyl.cloud. Withdrawing permission to use SOYL Academy also withdraws AI permission and signs the pupil out of every device at once, and the Android app removes any of their work saved on the phone.
Back to topCollege students
When a college uses SOYL Academy, the college adds each student with their name, college email address, year, class and (if the college gives it) roll number or university seat number, and says whether the student is 18 or older. We email the student an invitation to sign in, and each time they sign in we email a 6-digit code to that address; there is no password. We keep the address and a scrambled form of it to find the student at sign-in, and we keep the codes only in scrambled form, for at most a day.
- If you are 18 or older, you decide. The first time you sign in, we show you what SOYL Academy keeps about you and ask whether you agree to use it; AI help is a separate choice. We record your answer, the date and the version of this policy you saw. You can turn AI help on or off, or withdraw your permission, at any time in Privacy and permissions; withdrawing signs you out everywhere at once. Your college can also record a withdrawal if you ask it to. Parent features (the parent view, parent emails and summaries) are not used for students who are 18 or older.
- If you are under 18, your college records your parent’s or guardian’s decision before you can sign in, exactly as a school does, and parent features may be used.
- Your college decides how long your coursework is kept, can give you a copy and can erase it; erasing removes your college email and roll number with the rest of your record.
Everything else in this policy about pupils applies to college students too: what is kept about their work, AI processing (only with their AI choice), who sees it, and their rights.
Back to topQR codes in class and guest practice
QR codes in class. A teacher can show a QR code on the classroom screen so that pupils can start an assignment. While the code is shown (at most 90 minutes), anyone who opens it sees the first name and last initial of each pupil in the class who was given the work; a pupil signs in by tapping their name and typing their PIN. We record which pupils started the work through the code and delete that record 30 days after the code ends. A pupil’s sign-in card can carry their own QR code. In Grades 1–5, scanning it signs the pupil in without a PIN, so please keep the card safe: the school can replace a card’s code at any time or turn these codes off. From Grade 6 the pupil still types their PIN.
Guest practice. A teacher can share a public link so that anyone can try an assignment without an account. We do not ask guests for a name, an email address or any other details, and we use no AI for guests. To keep a guest’s place we store a random identifier in a cookie that ends when the browser closes (we keep only a scrambled form of it). For each question we keep whether the answer was right, the choice or number given when it was not, and which common misconception it showed, so the person who shared the link can see how the group did. Written answers are not part of guest practice. Guest answers never become part of any pupil’s record and are deleted 7 days after the link ends.
Back to topDemo events at our stall
Trying an assignment. At an exhibition stall, anyone can scan our QR code and try assignments on their own phone. You type a name, your email address and your age in years; you do not need an account. The name is shown with your stars on the stall’s screen, so use any name you are happy for people nearby to see. We ask your age for two reasons: to keep children under 13 off the stall’s public screen (they still see their own place on their phone; our stall team can choose to show everyone, for example at a school event), and to learn which ages SOYL suits, as counts by age group. Your age is never shown on the stall’s screen. Your email lets you carry on with the same name and stars on another phone (typing the same email brings them back), and we keep it, with your name, on the stall’s list of visitors. We do not email you unless you tick “Keep me posted about SOYL”, which is optional. To keep your place we store a random identifier in a cookie that ends when the browser closes (we keep only a scrambled form of it). For each try we keep whether it was right, the answer given (a choice, a number or a simulator setting: written questions are not part of the demo), which hint you saw and when, so that we can show your stars and, at the end, what a teacher would see of how you worked. The stall’s screen shows only names, stars and the room’s totals.
Quick feedback. When you finish an assignment or tap “I’m done”, we may ask a few optional questions: how it felt, whether you are a student, teacher, parent, school leader or something else, whether the hints helped, whether you would want your school to use SOYL, and one optional line on what would make it better. Teachers in a demo workspace get the same questions about making an assignment. You can skip them. We keep your answers with your visit, to improve SOYL Academy; please do not put personal details in the optional line. They are deleted with the rest of your visit, and only the counts are kept.
Live help at the stall. While you try an assignment, the helper can give live AI help: it guides you with questions and steps, never the answer. What you choose or type to the helper, with the question, your tries and the teacher’s own hints, is sent to the AI model as described under AI processing. Before anything you type is sent we remove things that look like a phone number, an email address or a home address, and we keep the conversation (with those removed) so that the helper can follow it. If something you type suggests you may be unsafe, the helper shows where to get help and nothing is sent to the AI model; there is no teacher at a stall to tell. The AI help a stall can use each day is limited; when it is used up, the helper gives the teacher’s own hints instead.
Your name, email, age, tries, quick feedback and conversation with the helper are deleted 7 days after the event ends; we keep only counts, and the email addresses of visitors who ticked “Keep me posted about SOYL” (below).
Teachers at the stall. A teacher (or anyone 18 or over) can start a demo workspace with their name and email address. Nothing is emailed. You stay signed in on the phone or browser you started on; typing the same email again opens the workspace only there, and only while the stall’s event is running. It holds only your own drafts and a synthetic class, it cannot invite or email anyone, and we keep the name and email on the stall’s list of visitors. The workspace becomes read-only after 7 days and is deleted, with the email address and the name, after 30 days. Its class is synthetic: no real pupils. If you tick “Keep me posted about SOYL”, an optional choice, we also keep your email address and name to send you news about SOYL Academy until you ask us to stop (see Contact and complaints); then we delete them. We never share the stall’s list or these addresses, and we do not use them for anything else. Drafts you ask the AI to write in a demo workspace are processed as described under AI processing.
Back to topAI processing
Some features use AI models from Microsoft’s Azure OpenAI service, through Azure AI Foundry. Our AI resource is in India, but the models are deployed globally, so a request may be processed in a Microsoft data centre outside India. What is sent:
- Drafting assignments (teachers): the teacher’s notes, the text of uploaded files and, for photos or scanned pages, the images, with the grade, subject and learning outcome. Teachers must not put pupils’ personal details in their materials. If a teacher speaks their notes instead of typing, the recording is sent to the AI to be turned into text and is then deleted; we never store it, and only the text the teacher keeps is saved.
- AI hints (pupils, only with AI permission and only when the teacher turned AI hints on, in the work and in “Try these again” practice): each time a pupil asks for the next hint on a question, the grade, the question and its choices, the answer reference for that question (the correct choice or value, or the teacher’s marking guidance for a written answer), up to the pupil’s last 6 attempts at that question, the help already shown on it (up to 6 earlier hints) and the teacher’s own hint for that step. Asking for a hint is a button; typed messages go to the companion (below). The answer reference is there so the hint can point at the pupil’s mistake; the pupil never receives it, and every hint is checked automatically before it is shown so that it does not give the answer away. The reply also says, privately, whether the pupil’s answers suggest they may be unsafe or in distress (see “Wellbeing check-ins” above); Microsoft’s content filter can do the same when it blocks a request. To keep costs down, a pupil may be shown an AI hint that was first written for another pupil who gave exactly the same answer choice or number to the same question; it is checked again before it is shown. Hints about typed (written) answers are never reused. Reused hints are stored without any information about who received them, and are deleted after 30 days.
- Future Builders AI labs (pupils, only with AI permission and only when the teacher switched the live model on for a task): in the grounded-assistant lab, the question the pupil types and the few parts of the teacher’s notes (or the lab’s own handbook) that best match it; in the agent lab, the task’s goal, the list of lab tools and the steps so far, which describe made-up maintenance records. The AI only proposes; SOYL runs every step itself, the lab has no tool that sends messages, buys anything or controls a device, and nothing is saved without the pupil’s approval. Without permission, or with the live model off, the lab uses its own simulated assistant and nothing is sent to the AI.
- The teaching companion (pupils, only with AI permission and only when the teacher left the companion on): when a pupil taps a choice such as “Give me a nudge” or types a message to their companion (up to 500 characters; typing is on from Grade 4, and the teacher can turn it off), the same details as for an AI hint, the last 6 messages about that question, the pupil’s message and which character the pupil chose (so the reply is in that character’s voice). Before it is sent, anything in the message that looks like a name, phone number or email address is removed. The message is treated as information, never as instructions to the AI. Every reply is checked so that it does not give the answer away and stays on the question; each question allows a few AI replies, after which the companion suggests asking the teacher. Without AI permission, or with AI help off, the companion answers only from the teacher’s reviewed hints and its own reviewed lines, and nothing is sent to the AI. AI replies are labelled “AI help · your teacher can see this”.
- Live help at a demo stall (visitors trying an assignment, see “Demo events at our stall”): the same as for the companion above: the question, its answer reference, the visitor’s tries, the teacher’s hints and the last 6 messages about that question, with anything that looks like a name, phone number, email address or home address removed from what the visitor types. The visitor’s name and email address are never sent. The same checks apply to every reply. No teacher sees a stall conversation; it is deleted 7 days after the event ends.
- Speaking an answer in a mission (pupils, only with AI permission): a pupil can choose to speak an answer instead of typing it. The recording is sent to the AI only to turn it into text. The text appears in the pupil’s answer box, where they can read and change it before sending. We do not keep the recording, and we do not keep the text unless the pupil sends it as their answer; then it is stored like a typed answer. Each pupil has a daily speaking limit. If we later keep short voice clips as evidence of a pupil’s reasoning, we will update this policy and ask for permission first.
- Speaking practice in English (“Speak it right”; pupils only with AI permission, and visitors trying it at our stall or through a practice link): the pupil or visitor records one short sentence (up to 30 seconds). The recording, and the sentence it should match, are sent to Microsoft’s Azure AI Speechservice only to recognise the words and to give pronunciation feedback on each word. We do not keep the recording or the words it heard. We keep only the result: which words were clear, nearly there, to practise, missed or extra, how smoothly it was said and the service’s pronunciation scores (shown to the teacher, never to the pupil as marks); a visitor’s results are deleted with their visit, 7 days after the event or practice link ends. It is pronunciation practice, not a test of accent. Each pupil has a daily speaking-practice limit.
- Explaining their thinking in a mission (pupils, only with AI permission): the question, the teacher-approved template for the companion’s question and its marking guide, and the pupil’s earlier answers on that idea, so the AI can word the companion’s question; then the pupil’s answer, so the AI can score it from 0 to 3 for the teacher. Without AI permission, the companion asks the teacher-approved question as written and the teacher scores the answer.
- Suggesting misconception labels (teachers, only when the school has AI permission for the pupil): pupils’ written answers in a mission, each under a random reference number and without the pupil’s name, and the list of ideas the mission listens for. The AI may only choose from that list, and a teacher confirms, changes or rejects each suggestion.
- AI summaries (teachers, only with AI permission): the questions, the expected answers or marking guidance, and the pupil’s answers, attempts and hints, each under a random reference number.
- Visuals and search (teachers): the teacher’s description of a diagram or search words.
No names, email addresses or other identifying details of pupils or parents are sent to the AI. Pupils’ answers can contain whatever a pupil chooses to write, and are sent as written. Every request is made with storage turned off (store=false), which asks Microsoft not to keep the response for later retrieval. Microsoft states that it does not use this data to train its models; under Microsoft’s standard terms it may keep requests for a limited time to detect abuse.
AI only suggests. Teachers review and approve every AI-drafted assignment before pupils see it, AI hints are checked so they do not give away answers, and AI never decides a pupil’s mark.
Back to topWhere the data is kept
- The database, uploaded files and logs are kept on Microsoft Azure in the Central India region.
- Backups of the database are kept for 14 days, with a copy in Azure’s paired region in India.
- Email to parents is sent through Azure Communication Services with its stored data located in India. Emails travel to your own email provider.
- AI requests may be processed outside India (see AI processing).
Cookies and storage on your device
We use only cookies and storage that the service needs to work. There are no advertising or analytics cookies.
| Name | What it is for | How long |
|---|---|---|
| soyl_session, soyl_refresh, soyl_oidc | Keeps a teacher or pupil signed in (encrypted; not readable by page scripts) | Staff: hours to 14 days. Pupils on their own device: until signed out or the sign-in expires (up to 180 days). Pupils who chose “Shared computer”: until the browser closes, they sign out, 30 minutes without activity, or 12 hours, whichever comes first |
| soyl_tenant | Remembers which school a teacher who works in more than one school is using (a school reference; not readable by page scripts) | Up to 14 days; deleted at sign-out |
| soyl_parent | Keeps a parent signed in (encrypted) | Up to 30 days |
| soyl_guest | Keeps a guest’s place in guest practice (a random identifier; not readable by page scripts) | Until the browser closes |
| Browser storage (IndexedDB and a service-worker cache) | Saves a pupil’s work on the device so nothing is lost offline | Deleted when the pupil signs out, and on a shared computer when their sign-in ends. Work that could not be sent yet is kept for that pupil only, until they sign in there again or for 14 days |
| soyl.draftUpdates.since.* (local storage, staff only) | When the staff app last checked for finished AI drafts, so a “draft ready” notice is shown once | Until cleared |
| soyl-prefs, soyl-device-id, soyl-sign-in-device, soyl-last-pupil, soyl-kept-pupils, soyl-last-activity (local storage) | Sound and motion settings; a random reference for this browser, sent with answers; whether this browser is a shared computer; which pupil last signed in here (ids only, no names), so their data can be deleted after they leave; when the page was last used | Until cleared, or deleted with the pupil’s data |
The parent permission page sets no cookies. The Android app keeps a pupil’s work in an encrypted store on the phone, with the key in the phone’s secure key storage, and wipes it when the pupil signs out or permission is withdrawn. The app has no advertising, analytics or crash-reporting software from other companies, and phone backups of its data are turned off.
Back to topLogs and error monitoring
- Our servers log each request’s route, result, timing and a request number. Logs never contain answers, teachers’ notes, AI prompts or replies, sign-in codes or links.
- We use Azure Application Insights to find and fix errors. It records technical details of requests and errors (such as the page or route, the error type and timings), not the content of anyone’s work, and not names or email addresses. When something breaks in the website or app, it can send us a short error report with personal details removed.
- Logs are kept for up to 180 days. Azure’s own infrastructure logs (for example file storage access) can include IP addresses.
How long we keep data
| Data | Kept for |
|---|---|
| Pupils’ work: answers, attempts, events, hints, reports of AI hints, Future Builders AI lab runs, wellbeing check-ins, feedback, when feedback was opened, practice after review, Revisit sets, marks, summaries | 24 months after the assignment’s due date by default (each school can set 6 to 120 months), then deleted automatically |
| Teachers’ previews of the Future Builders AI labs (a question or an agent run, and the AI’s reply) | 30 days |
| Pupil one-time sign-in codes (stored as hashes) | 30 days |
| Student codes, PIN hashes, setup PINs (hashes; each works for 7 days) and the count of wrong PINs | While the pupil uses SOYL Academy; deleted when the pupil is erased. A new setup PIN or a new student code replaces the old one at once |
| Signed-in devices | Until signed out or expired (up to 180 days), then 90 days |
| Parent permission links and codes | Links 7 days, codes 10 minutes; the withdrawal link works for 2 years |
| Parent sign-in | Codes 1 day; sessions 30 days after they end |
| College students’ email sign-in codes (stored as hashes) | 1 day |
| Records of which pupils started work through a classroom QR code | 30 days after the code ends |
| Guest practice answers (no names or contact details) | 7 days after the link ends |
| Demo event visitors: name, email address, age, tries, stars, quick feedback and conversations with the helper; teachers’ quick feedback at the stall | 7 days after the event ends (counts are kept) |
| Demo workspaces at our stall, with the teacher’s email address and name | Read-only after 7 days, deleted after 30 days |
| News list from our stall (only if the visitor or teacher ticked “Keep me posted”): email address and name | Until the person asks us to stop |
| Email delivery records, and the records of daily and weekly emails | 90 days |
| Daily email settings; a parent’s unsubscribe from the weekly email | While the person uses SOYL Academy; a parent’s unsubscribe is deleted with the guardian’s details |
| Class-list uploads (CSV) | Details removed after 30 days (counts are kept) |
| Server logs | Up to 180 days |
| Database backups | 14 days |
| Pupils’ names and classes, parents’ details, consent records | While the pupil uses SOYL Academy, until the school or tutor removes or erases them |
| A pupil who has left the school (they can no longer sign in, hold no place and are in no class; their parents’ access ends) | Kept so the school can answer questions or export it, until the school erases it or, at the latest, the school’s retention period after they left (24 months by default), then erased automatically |
| Records of class lists fetched from the school’s own system (counts and record ids, never names) | 90 days; the fetched list itself is kept only until the school applies it, at most 24 hours |
| Teachers’ materials, drafts and published assignments | While the school or tutor uses SOYL Academy; deleted when they leave or ask (this is a manual step today) |
When a pupil’s data is erased, we delete their work, devices, guardians and parent sign-ins. We keep only what we must to show that the law was followed: the consent history with the guardian’s details removed, a record that the erasure happened, and audit entries that contain ids only. Erased data disappears from backups as they expire (within 14 days).
Back to topYour rights, and how to use them
Under the DPDP Act you (or a parent or guardian on behalf of a child) can:
- Get a summary or a copy of the personal data held and how it is used (a school can download a copy of everything SOYL Academy holds about a pupil: their work, activity events, help steps and any help they reported, permission and email records, their student code and sign-in record (never the PIN), and their parents’ sign-ins. Wellbeing check-ins are left out unless the school decides to include them after a safeguarding review);
- Correct or update it (for example a misspelt name or a new email address);
- Have it erased when it is no longer needed or permission is withdrawn;
- Withdraw permission at any time, as easily as it was given;
- Nominate someone to use these rights for you if you die or cannot act yourself;
- Complain to us, and then to the Data Protection Board of India if you are not satisfied with our answer.
The quickest way is usually to ask your child’s school or tutor: they can export, correct and erase data in SOYL Academy straight away. You can also write to outreach@soyl.cloud. We will check that the request comes from you (for example by replying to the email address on record), acknowledge it within 7 days and resolve it within 30 days (the DPDP rules allow at most 90). If you are not satisfied with our answer, you can complain to the Data Protection Board of India.
Back to topKeeping children safe
- No public profiles, no chat or messages between users, and no way for pupils to see each other’s work.
- Pupils sign in with a student code and a PIN they choose themselves (4 digits in Grades 1–5, 6 from Grade 6): no email address, phone number or password. Teachers never see the PIN. After 5 wrong PINs in a row the code is paused for 15 minutes, and after 10 it is locked until a teacher resets the PIN. A pupil may also start from a QR code (see QR codes in class). College students sign in with a code sent to their college email instead.
- Teachers approve all content before pupils see it, including anything AI drafted.
- No advertising, no in-app purchases for pupils, and no links to social media.
- We do not track children across other apps or websites, build profiles of them for advertising or any other commercial purpose, or use their data in any way that could harm them. Their activity in SOYL Academy is used only for their teaching and their safety.
- Signing out of a shared computer or phone removes the pupil’s saved work from it. On a school computer, pupils choose “Shared computer”: they are signed out when the browser closes or after 30 minutes without activity, and their work is removed from the computer.
- If something a pupil writes suggests they may be unsafe or in distress, their teachers see their words privately (a wellbeing check-in); if it is about harming themselves, the pupil is also shown where to get help. These automatic checks will miss things: they support, and never replace, the school’s own safeguarding.
Security
Data is encrypted in transit, and at rest on our servers and in the Android app. Work saved in a web browser is not encrypted, so it is deleted when the pupil signs out. Each school’s data is separated inside the database itself, not only by the app. Pupils’ PINs, sign-in codes, device credentials, parent links and sessions are stored only as one-way hashes. School staff join only by invitation from their school. If a personal data breach happens, we will tell the affected schools, tutors and parents and the Data Protection Board as the law requires.
Back to topChanges to this policy
The version and effective date are at the top of this page. If we make an important change, we will tell schools and tutors before it takes effect and, where the law requires, ask parents for permission again.
Back to topContact and complaints
SOYL AI Private Limited. Email: outreach@soyl.cloud. Grievance officer: Ryan Gomez. Post: B1301, Satna Power Tower, 7th Cross, Bengaluru 560043.
See also our terms of use.
Back to top