Privacy policy
Version 1.3 · effective 26 October 2026
Contents
SOYL Academy is a website and Android app where teachers and tutors set interactive homework and practice in maths, physics and chemistry for pupils in Grades 1–10. 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, their teacher’s feedback and marks, and which phones or computers are signed in. Your child has 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, 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.
- 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’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.
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. |
| 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. |
| Teacher feedback, marks, corrections and AI summaries the teacher asked for | Teaching and feedback. |
| Signed-in devices: a type label (for example “Android app”), 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 only needs a code once per device. |
| 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. |
| 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. |
| 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. |
| A record of important actions (for example publishing work or recording consent), with ids only | Security and accountability. |
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 pupils’ email addresses or phone numbers, photos of pupils, precise location, contacts, advertising identifiers or anything from the camera. 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 only for internet access.
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 two 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.
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 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): 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. Pupils do not type messages to the AI: asking is a button. 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.
- 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: until the device is signed out or its sign-in expires (up to 180 days) |
| 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 |
| 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 |
| soyl-prefs, soyl-device-id (local storage) | Sound and motion settings; a random reference for this browser, sent with answers | Until cleared |
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, wellbeing check-ins, feedback, marks, summaries | 24 months after the assignment’s due date by default (each school can set 6 to 120 months), then deleted automatically |
| Pupil sign-in codes (stored as hashes) | 30 days |
| 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 |
| Email delivery records | 90 days |
| 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 |
| 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, 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) and answer as soon as we can, within the time the law requires.
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 one-time code from their teacher: no email address, phone number or password.
- 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.
- Signing out of a shared computer or phone removes the pupil’s saved work from it.
- 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. 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.
See also our terms of use.
Back to top