← Back to NIKSHA OS

NIKSHA OS — Terms & Conditions

Version 5.0 · Last updated 7 October 2026

Provider: NIKSHA Technologies ("NIKSHA Technologies", "we", "us", "our") Applies to: the NIKSHA OS mobile app (Android package com.nikshaos.app, and any iOS version we make available), the NIKSHA OS web application, and the related backend services (together, the "Service").

Terms at a glance

This summary is here to help you. It is part of these Terms, but if it and the detailed sections below ever differ, the detailed sections apply.

• Your school runs NIKSHA OS for you. You cannot sign up yourself. Your school (the "Institution") creates your account and decides your role.
• You sign in with your mobile number and a one-time password (OTP). One mobile number belongs to one person. Never share your OTP.
• Your school is in charge of your data. Under India's Digital Personal Data Protection Act, 2023, the school is the Data Fiduciary for student, parent and staff records. NIKSHA Technologies is its Data Processor — we process that data only to run the Service for the school.
• Children use NIKSHA OS through their school and their parents. A child never signs up alone, and we never use children's data for advertising, tracking or profiling.
• We do not sell personal data and we show no advertising.
• AI features can be wrong. They are on by default for each school, and a person must check what they produce before relying on it.
• School messages may reach you by app notification, SMS or WhatsApp, depending on what your school has switched on. You can reply STOP to WhatsApp messages from your school to stop them.
• Fees are between you and your school. Your school sets fees and refunds. We do not charge parents, students or staff for using the app.
• You can delete your account in the app at Profile → Delete account. Your school keeps the school records it is required to keep.
• The Service is provided "as is", and our liability is limited (§19–§20).
• Indian law applies. If something goes wrong, contact your school or our Grievance Officer first (§23, §25).

1. About these Terms

1.1 Acceptance. These Terms are a legal agreement between you and NIKSHA Technologies. You accept them by tapping Accept on the in-app acceptance screen. If you do not agree, do not use the Service.

1.1A Users under 18. A person under 18 cannot enter into a binding contract under Indian law. If you are under 18, these Terms are accepted by your Institution and your parent or lawful guardian, who are responsible for your use of the Service; you must still follow the rules in §7 and the Acceptable Use Policy.

1.2 Electronic record. These Terms are an electronic record under the Information Technology Act, 2000 and the rules made under it. They are accepted electronically and do not need a physical or digital signature. We keep a record of which version you accepted, when, and from which device (§24.3).

1.3 Accepting for an Institution. If you accept on behalf of an Institution (for example as its principal, director, owner or administrator), you confirm that you are authorised to bind it.

1.4 The documents that make up our agreement. These Terms are the umbrella agreement. These documents sit under them and form part of them:

1.5 If documents conflict. On matters of personal data, the Privacy Policy controls. Otherwise, a more specific document controls on its own subject — for example, the Institution Agreement controls on an Institution's fees and term. In every other case, these Terms control.

2. Definitions

In these Terms:

• "Institution" means the school, college, school group or educational organisation that has agreed with us to use the Service, and that creates and manages accounts for its people.
• "School administrator" means a person the Institution has given an administrative or leadership role in the Service — for example a principal, director, owner, HR manager or administrator.
• "User" or "you" means anyone who uses the Service: a school administrator, teacher, staff member, parent, guardian or student.
• "Parent" includes a parent or lawful guardian whom the Institution has linked to a student.
• "Child" means a person under 18 years of age, as defined in the Digital Personal Data Protection Act, 2023.
• "Institution Data" means the personal data and records that the Institution, or its users, put into the Service — for example student, parent, staff, attendance, academic, fee, transport, hostel and health records.
• "Your Content" means files, photographs, documents and messages that you upload or send through the Service.
• "AI Feature" means any feature that uses an artificial-intelligence model to produce text, summaries, suggestions, scores or predictions.
• "Data Fiduciary", "Data Processor", "Data Principal" and "personal data" have the meanings given in the Digital Personal Data Protection Act, 2023 (the "DPDP Act").
• "Business day" means a day other than a Saturday, Sunday or public holiday in Andhra Pradesh.

3. Eligibility and accounts

3.1 No public sign-up. Accounts are created only by or on behalf of an Institution. You cannot create a NIKSHA OS account yourself. If your Institution has not created an account for you, you cannot use the Service.

3.2 Your mobile number is your login. You sign in with your mobile number and a one-time password (OTP). There is no password to set.

• One mobile number belongs to one person. If you hold more than one role — for example a parent who is also a teacher, or a staff member at two schools — the same login carries each role; you do not get a second account.
• Changing your mobile number changes your login. Only an authorised person at your Institution (or, for an Institution's owner, our platform administrators) can change it; the old sign-in sessions are ended, and the change is logged.
• Keep your number current. If you stop using a number, tell your Institution, so that the next holder of that number cannot reach your account.

3.3 Keep your OTP secret. You are responsible for activity under your account. Never share your OTP — not with school staff, not with us, and not with anyone who calls or messages you asking for it. We will never ask you for your OTP. Anyone who has your OTP can act as you. Tell your Institution immediately if you think someone else has used your account, and report it to support@nikshaos.in.

3.4 Role-based access. You may see and do only what your role allows. A parent sees only their own children; a teacher sees only the classes assigned to them. Do not try to reach anything else.

3.5 Children and students.

• A child never signs up alone. A student appears in the Service because their Institution enrolled them.
• Where an Institution gives a student their own login, the student sees only their own records. The Institution — and, where the law requires, the parent — is responsible for the lawful basis and any consent for that account. Students are not asked to accept these Terms in the app themselves; the Institution and the parent accept the terms that apply.
• Where the law requires verifiable consent of a parent for processing a child's personal data, the Institution obtains and records it. See Children's Data & Consent.
• If you are a parent, you are responsible for how your own account is used to view your child's information.
• Parent or guardian confirmation and consent. By accepting these Terms as a parent or guardian, you confirm that you are the parent or lawful guardian of the child or children linked to your account, and you (a) consent to your child's school-provisioned student account, and (b) allow your child to take part in live online classes where your school offers them, including your child's microphone and camera when the teacher enables them and any recording the teacher chooses to save (Privacy Policy §3.7A). You may withdraw this permission at any time by contacting your school or by using Delete account. Withdrawal does not undo processing already carried out, and your school may then be unable to provide the student account or live classes to your child.

3.6 Leaving an Institution. Your access to an Institution's data ends when that Institution removes your role, or when your relationship with it ends. If you still hold a role at another Institution, you keep access there.

4. Who is responsible for your data

4.1 The Institution is the Data Fiduciary. For Institution Data, the Institution decides what is recorded, why, and for how long. It is responsible for having a lawful basis, for giving any notice the DPDP Act requires, for obtaining any consent the law requires, and for answering requests from Data Principals (for example a parent asking to correct their child's record).

4.2 NIKSHA Technologies is the Data Processor. We process Institution Data only on the Institution's instructions and only to provide, secure and support the Service, as set out in the Data Processing Addendum of the Institution Agreement.

4.3 Where we are the Data Fiduciary. We are the Data Fiduciary for the limited account, device, security and operational data we need to run the Service itself — for example sign-in records, audit logs and policy-acceptance records. The Privacy Policy explains this data.

4.4 What this means for you. For questions, corrections or removal of school records, start with your Institution. For questions about how we run the Service, or if your Institution has not resolved your concern, contact our Grievance Officer (§25).

5. The Service

5.1 What NIKSHA OS is. NIKSHA OS is a school-management platform. Depending on what the Institution has enabled and the plan it has agreed with us, it may include admissions, student records, attendance, examinations and results, homework, timetables, fees and receipts, transport and vehicle tracking, hostel, library, health and infirmary records, staff and HR administration, communication and notifications, dashboards, reports, and AI assistance.

5.2 Modules vary by Institution. Not every module is available to every Institution or every role. We may add, change or remove features (§24.5).

5.3 Live online classes. Where an Institution uses them, the Service includes live audio/video classes, which a teacher may record where recording is available. How class audio, video and recordings are handled, and how long recordings are kept, is set out in the Privacy Policy §3.7A. The Institution decides whether to use live classes and recording, and is responsible for any consent the law requires for recording a child's voice or image. Behave in a live class as you would in a classroom, and follow §5.4 and the Acceptable Use Policy.

5.4 Protection of class content. Where class content is shown — a lesson, a recording or a live class — the app asks the device's operating system to block screenshots and screen recording of that screen. You must not try to get around this, and you must not copy, record or share class content, or another person's image or voice, without permission. This protection stops the operating system's own capture features only; it cannot stop someone photographing the screen with another device.

6. Institution and school-administrator responsibilities

The Institution — not NIKSHA Technologies — is responsible for:

• Who gets an account and what role they hold, and for removing access promptly when a person leaves.
• The accuracy and lawfulness of the data it records, including student, parent and staff data, and for correcting it when asked.
• Every notice and consent the law requires, including verifiable parental consent for children's data where the law requires it, and consent for any optional feature it switches on (for example face verification for staff attendance, or WhatsApp messages to parents).
• How it configures the Service — which modules, messaging channels and AI Features are on, and which roles can see what.
• Its own decisions. The Service supports the Institution's work. It does not replace the Institution's professional judgement or its legal duties — including on child safety, examinations, finance, discipline and health or medical care.
• Its fee arrangement with parents (§12).
• Keeping its own copies of records it is legally required to retain (§13).

The Institution warrants that it has the authority and a lawful basis to give us the personal data it uploads and to instruct us to process it.

School administrators must use their wider access only for the Institution's legitimate purposes, follow the Institution's own policies, and take particular care with children's data, health records, staff records and financial records.

7. Acceptable use

You must follow the Acceptable Use Policy. In particular, you must not:

• access, or try to access, data belonging to another Institution, school, family or student, or data your role does not allow;
• use another person's account, or share your own account or OTP;
• try to defeat access controls, role restrictions, the in-app acceptance screen, location (geofence) checks, device-biometric checks or face verification — including with mock-location or spoofing tools;
• upload malware, or content that is unlawful, defamatory, obscene, harassing, hateful, or that endangers a child;
• upload personal data you have no lawful basis to provide;
• scrape, bulk-extract, reverse-engineer, decompile or resell the Service, except where the law expressly allows it;
• interfere with the Service's operation, security or availability, or put it under unreasonable load;
• use the Service to send spam or messages unrelated to the Institution's legitimate purpose; or
• enter false financial records, or tamper with invoices or receipts.

We may suspend access, remove content or notify the authorities where the law requires, as described in §18 — without notice where a child's safety or the security of the Service is at risk.

8. Your content and Institution Data

8.1 Institution Data belongs to the Institution. We claim no ownership of it. We process it as the Institution's Data Processor (§4).

8.2 Your Content stays yours. You keep ownership of Your Content. You give us a limited, non-exclusive, royalty-free licence to host, store, copy, process, transmit and display it only to operate, secure and support the Service for your Institution. This licence ends when the content is deleted from the Service, subject to backups (§13) and the Institution's retention of its own records.

8.3 You are responsible for what you upload. Upload a photograph, document or message only if you are entitled to, and only if the person it concerns has the protection the law requires. Take special care with photographs of children.

8.4 Removal. We may remove or disable content that breaches these Terms, the Acceptable Use Policy or the law, and may report it to the authorities where the law requires.

8.5 What we never do. We do not sell personal data. We do not use student data for advertising. We show no advertising in the Service.

9. Staff attendance: location, device biometrics and face verification

This section applies to staff only. We do not track the personal location of students or parents, and we do not perform face recognition on students.

• Location for attendance. When a staff member checks in or out, the app takes a single location reading while the app is in use and compares it with the school's configured area.
• Location on a driver's phone. Where the Institution runs the transport module, the phone of the driver or transport staff member running a trip reports the school vehicle's position for the length of that trip — including while the screen is off, with an ongoing "trip in progress" notification on Android. It stops when the trip ends. No other user's location is collected in the background.
• Device biometrics. If you turn on the optional app lock, you unlock the app with your phone's own fingerprint or face unlock. That check happens on your device, by its operating system. We never receive your fingerprint or your device's face data. (This applies to all users, not only staff.)
• Face verification. Where the Institution enables it, a staff check-in may also be verified against a face template held by the Service. How this works, what is stored and what is never stored is set out in the Privacy Policy §3.5. It needs your own consent, recorded in the app, and the Institution must offer an alternative if you decline. You enrol once; a reset is made by an authorised person at your Institution.

Do not try to defeat any of these checks (§7).

10. AI features

• AI Features are assistive only. Their output may be inaccurate, incomplete or out of date, and a responsible person must review it before relying on it, sharing it with parents, publishing it, or using it in any decision about a student, parent or staff member.
• Do not treat AI output as authoritative for any academic, financial, disciplinary, medical or legal decision. Predictions and risk scores are statistical estimates, not judgements about a person.
• AI Features are on by default for each school. An Institution may ask for them to be limited or switched off.
• The in-app assistant answers most questions itself, from the school's own records, without sending your words to an AI model. For school staff, a question it cannot answer that way may be sent — with the school data needed to answer it — to a third-party AI provider outside India. Other AI Features (for example parent insights and summaries) also send the relevant school data to that provider. What you type is stored as your conversation history. See the Privacy Policy §3.6 and Sub-processors.
• AI Features work within your role's access: they do not reveal data your role cannot already see.
• Do not enter personal data you are not authorised to process, and do not use AI Features to create content that breaches §7.
• The AI Usage & Disclaimer forms part of these Terms.

11. Notifications and messages

11.1 How we reach you. Depending on what your Institution has switched on, the Service may send you:

• in-app and push notifications — for example results published, fees due, attendance, notices and transport updates;
• SMS — login OTPs and, where your Institution has switched them on, alerts such as fee receipts and exam results;
• WhatsApp messages — only where your Institution has switched WhatsApp on and your number is recorded as opted in: school notifications sent through Meta's WhatsApp Business Platform, which processes them outside India. A message can include your child's name, class, attendance, fee amounts, marks or similar school details. Login OTPs by WhatsApp are not active today; they are sent by SMS; and
• email, where enabled.

11.2 Who sends what. Messages about your school are sent on behalf of your Institution, which decides what to send and to whom. The third parties that deliver messages are listed in Sub-processors.

11.3 Your choices.

• WhatsApp: reply STOP to a WhatsApp message from your school to stop that school's WhatsApp messages to your number. If we cannot tell which school a STOP was meant for, we stop WhatsApp messages to your number from every school. After you opt out, a school administrator cannot opt you back in — only you can, for example by replying START to that school's message or by using the WhatsApp setting in the app, where available.
• Push notifications: you can turn them off in your device settings.
• Essential messages — such as a login OTP — are needed to use the Service and cannot be turned off while you use it.

11.4 No advertising to children. We do not use the Service to send our own marketing to parents or children. An Institution may send its own school communications and is responsible for them; it must not use the Service's messaging to advertise to children or to send content unrelated to its legitimate purpose (see the Acceptable Use Policy).

11.5 Delivery is not guaranteed. Messages depend on networks and third-party providers. A message may be delayed or not delivered. Do not rely on an SMS, WhatsApp or push message as the only way to learn of something urgent — check the app or contact your school.

12. Fees, payments and subscriptions

12.1 The Institution pays us. Access to the Service is licensed to the Institution. Subscription or licence fees, the plan and its entitlements, the billing cycle, taxes and the term are set out in the Institution's order form, quote or plan under the Institution Agreement.

12.2 Messaging charges. Some message types — for example WhatsApp messages — may be charged to the Institution per message, from a prepaid balance the Institution tops up with us. When the balance is too low, those messages are not sent until it is topped up. The applicable rates are made available to the Institution.

12.3 Individual users are not charged by us. We do not charge parents, students or staff any fee to use the app. Any fee, late fee or convenience charge that appears on a school invoice is set by your Institution. If we ever plan to charge individual users, we will tell you in advance and you will have to agree before you are charged.

12.4 School fees are between you and your Institution. Your Institution sets its fees, due dates, concessions, refunds and penalties. We record transactions for the Institution; we are not a party to the fee arrangement between a parent and the Institution. Send fee questions, refund requests and disputes to your Institution, not to us.

12.5 Online fee payment. Online fee payment is available only where your Institution has switched it on and we have confirmed in writing to the Institution that it is live. Until then, a payment recorded in the app creates a receipt in the school's records but does not contact a payment gateway and does not move any money. Where online payment is live, it is processed by our payment provider (see Sub-processors): we do not receive or store your card or bank details — you enter them in the provider's own checkout. A payment is complete only when the provider confirms it.

13. Storage, quotas and backups

• Storage allowance. Each Institution has a storage allowance. We may warn the Institution as it nears its limit, and may decline further uploads once it is exceeded, until usage is reduced or more capacity is agreed.
• File limits. Uploads are subject to file-size and file-type limits.
• Private storage. Files are stored privately and are served only through short-lived expiring links. Where data is stored is explained in the Privacy Policy §6.
• Backups are for disaster recovery, not an undo button. We take encrypted backups for disaster recovery. We do not guarantee that any particular record deleted or overwritten by a user can be restored, and we do not commit to a specific recovery point or recovery time unless the Institution Agreement or order form says so.
• Deleting a record does not currently guarantee that an underlying stored file is erased. We say this plainly rather than claim an erasure capability that does not yet exist.
• Keep your own copies. Institutions must keep their own copies of records they are legally required to retain. Do not treat the Service as your only copy of a statutory record.

14. Third-party services

The Service relies on third-party providers listed in Sub-processors — including database hosting, SMS delivery, WhatsApp delivery, push-notification delivery, AI processing, file storage and, where live, payment processing. Using some features may also make you subject to those providers' own terms (for example WhatsApp's terms when you use WhatsApp). We choose these providers carefully and bind them to protect data, but we are not responsible for services outside our control beyond our obligations in these Terms and our policies.

15. Intellectual property and feedback

15.1 Our property. The Service — its software, design, content we create, and trademarks including the name "NIKSHA OS" — is owned by NIKSHA Technologies or its licensors and is protected by law.

15.2 Your licence. We grant you a limited, non-exclusive, non-transferable, revocable licence to use the Service for its intended purpose while your access lasts. You may not copy, modify, reverse-engineer, decompile, resell or create derivative works of the Service, except where the law expressly allows it.

15.3 Your rights are preserved. You keep ownership of Your Content and the Institution keeps ownership of Institution Data (§8).

15.4 Feedback. If you send us feedback or suggestions, you allow us to use them to improve the Service, without any obligation to you.

16. Availability, support and app updates

16.1 Best effort, no guaranteed uptime. We work to keep the Service available and reliable, but it is provided on an "as available" basis. We do not promise any particular uptime or response time, and these Terms contain no service-level agreement, unless the Institution's order form says otherwise. Planned maintenance, outages, and failures of networks or third-party providers can interrupt the Service.

16.2 Maintenance. We try to schedule disruptive maintenance outside school hours where practical.

16.3 Pilot and beta features may be offered for evaluation and may change or be withdrawn.

16.4 Support. Users should first contact their Institution. Institutions and users can reach us at support@nikshaos.in.

16.5 App updates. We release updates through Google Play and, where available, Apple's App Store. Updating keeps your data — we will never ask you to uninstall the app or clear its data in order to update. From time to time we may set a minimum supported version for security or compatibility. If your app is older than that, it will ask you to update through the store before you continue. A new version being available does not, by itself, sign you out.

17. Security

• We apply the technical and organisational security measures described in the Privacy Policy and the Security & Responsible Disclosure Policy, including encryption in transit, role-based access, separation between Institutions, and audit logs.
• You must keep your device and your OTP secure, use a device with a current operating system, not bypass security controls, and report a lost device or suspected compromise promptly.
• The Institution must manage role assignments, remove access when a person leaves, and configure its modules appropriately.
• Personal-data breaches. If a breach affects Institution Data, we notify the affected Institution without undue delay and help it meet its own obligations under the DPDP Act and Rules.
• Reporting a vulnerability. See the Security & Responsible Disclosure Policy. Report responsibly and do not exploit or take data.

No system is perfectly secure, and we cannot guarantee that unauthorised access will never happen.

18. Suspension, termination and account deletion

18.1 Suspension by us. We may suspend or restrict access — for a user or an Institution — for breach of these Terms or the Acceptable Use Policy, for security or legal reasons, for an Institution's non-payment, or to protect the Service or its users. Where practical we will give notice first; where a child's safety, the security of the Service, or the law requires it, we may act immediately.

18.2 Termination by an Institution is governed by the Institution Agreement.

18.3 Deleting your account. You may delete your account yourself:

• in the app: Profile → Delete account; or
• on the web, if you can no longer sign in: https://nikshaos.in/delete-account.

In the app, deletion is confirmed by OTP, takes effect immediately and cannot be undone. A web request is verified first, acknowledged within 7 days and completed within 30 days. What is erased, and what your Institution keeps, is explained in the Privacy Policy and the Parent & User Terms §9.

18.4 Institution records survive account deletion. Academic, attendance, financial, health and staff-employment records belong to the Institution and are often subject to legal retention. Deleting your login does not, and cannot, delete them. Send requests about them to your Institution.

18.5 Restoring access. An authorised person at your Institution can restore your access to your existing record — your linked children and a student's history are unaffected. Restoration does not bring back the personal data that was erased. Only authorised Institution roles can do this, only for a person already recorded at that Institution, and every restoration is logged.

18.6 What happens on termination. When your access ends, your right to use the Service ends. Data on an Institution's exit is handled under the Institution Agreement and the Data Retention & Deletion Policy. Outside account deletion, the Service does not currently delete most personal data automatically.

18.7 Survival. Sections that by their nature should continue after termination — including §8, §15, §19, §20, §21, §22, §23 and §27 — continue.

19. Disclaimers

To the maximum extent permitted by law, the Service is provided "as is" and "as available", without warranties of any kind, express or implied, including implied warranties of merchantability, fitness for a particular purpose and non-infringement. We do not warrant that the Service will be uninterrupted, timely or error-free, that defects will be corrected, that any message will be delivered, or that AI output will be accurate.

Location and bus tracking. Vehicle positions, estimated arrival times and attendance location checks depend on GPS, the driver's phone, battery and mobile networks, and can be delayed, missing or inaccurate. They help the Institution and parents but are not a safety system: do not rely on them as the only way of knowing where a child is, and contact the school when in doubt.

NIKSHA OS is a tool that supports the Institution. It does not replace the Institution's professional judgement or its legal responsibilities, including for child safety, examinations, finance, discipline, and health or medical care. Nothing in the Service is medical, legal, financial or educational advice.

20. Limitation of liability

To the maximum extent permitted by law:

• We are not liable for indirect, incidental, special, consequential or punitive damages, or for loss of profits, revenue, goodwill, business or data, arising from your use of, or inability to use, the Service.
• Our total aggregate liability for all claims relating to the Service is limited to the greater of (a) the amount paid to us for the Service in the 12 months before the event giving rise to the claim, and (b) ₹10,000.
• For an Institution, the liability terms of the Institution Agreement also apply.
• Nothing in these Terms limits liability that the law does not allow to be limited — including liability for fraud or fraudulent misrepresentation, for death or personal injury caused by negligence, any liability under the DPDP Act that cannot be excluded by contract, or your rights under the Consumer Protection Act, 2019 where it applies to you.

These limits are a reasonable allocation of risk, taking into account how the Service is priced.

21. Indemnity

If you deliberately misuse the Service, act fraudulently or unlawfully, upload content you know you are not entitled to, or knowingly mishandle someone else's personal data, you are responsible to NIKSHA Technologies for the third-party claims, losses and reasonable costs this causes — only to the extent caused by you. A parent, student or staff member using the Service in good faith is not asked to give any wider indemnity. An Institution's indemnity, and ours to the Institution, are set out in the Institution Agreement.

22. Governing law and jurisdiction

These Terms, and any dispute or claim arising out of or in connection with them or the Service, are governed by the laws of India. Subject to §23 and to any mandatory consumer protection that applies to you, the competent courts of Andhra Pradesh have exclusive jurisdiction.

23. Dispute resolution and grievances

23.1 Talk to us first. Most problems are solved quickly. Before starting any formal proceedings, please contact your Institution (for school records) or our Grievance Officer (§25), and give us a fair chance to resolve the matter in good faith.

23.2 How we handle grievances. We acknowledge a grievance within 24 hours of receiving it and aim to resolve it within 15 days; a complaint about content or misuse of the Service (see the Acceptable Use Policy §8) is resolved within 7 days. In every case we respond within the time the law requires (under the DPDP Rules, not more than 90 days). Tell us who you are, which Institution you belong to, and what happened. Where the grievance concerns Institution Data, we pass it to your Institution, tell you that we have done so, and follow up.

23.3 Data Protection Board of India. If you are not satisfied with how a grievance about your personal data was handled, you may complain to the Data Protection Board of India. Under the DPDP Act you must first use the grievance process of the Data Fiduciary — usually your Institution, or us for data where we are the Data Fiduciary.

23.4 Courts. If a dispute is not resolved, either party may go to the courts named in §22. Nothing in this section stops anyone from seeking urgent relief from a court to protect a child, to prevent a security incident, or to protect intellectual property, and nothing in §22 or §23 stops a consumer from approaching a consumer commission where the Consumer Protection Act, 2019 allows.

24. Changes to these Terms and to the Service

24.1 Why we change these Terms. We may update these Terms as the Service, the law or our providers change.

24.2 Notice. Every change is recorded in the CHANGELOG, and the version number and date at the top of this page are updated. For a material change — one that affects your rights, how data is used, or your obligations — we tell Institutions directly at least 15 days before it takes effect, and ask you to accept it in the app (§24.3). A change needed urgently by law or for security may take effect sooner; we will explain why.

24.3 Re-acceptance. When we publish a new version, you will be asked to review and accept it in the app before you continue. We record the version you accepted, the date and time, your role and Institution, your IP address, and the device and app version you used. Until you accept, features that use personal data are paused for your account; signing out and deleting your account always remain available. A temporary fault in checking your acceptance will not by itself lock you out of your account; the app asks again later.

24.4 If you do not agree. If you do not accept a new version, do not continue to use the Service. You can delete your account (§18.3), and your Institution can explain any alternatives it offers.

24.5 Changes to the Service. We may update, add or remove features. We will not make a change that materially reduces the core functionality an Institution is paying for without telling it in advance.

25. Grievance Officer and contact

• Grievance Officer (also the person who answers questions about personal data on our behalf): N. Surendra, Grievance Officer / Owner, Niksha OS — support@nikshaos.in. Acknowledgement within 24 hours; resolution aimed within 15 days, or 7 days for a complaint about content or misuse (§23.2).
• Provider: NIKSHA Technologies, 9-68 Main Bazar, Panyam, Andhra Pradesh 518112, India
• Support: support@nikshaos.in · Privacy: support@nikshaos.in · Security: support@nikshaos.in
• Account deletion without the app: https://nikshaos.in/delete-account

If your issue is about your own school records — marks, attendance, fees, a child's details — please contact your Institution first; it holds and controls those records.

26. Laws these Terms are written to follow

These Terms are written to be consistent with, as they apply to the Service:

• the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (notified 14 November 2025, with substantive obligations applying from 13 May 2027);
• the Information Technology Act, 2000, including the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, and the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 to the extent they apply;
• the Consumer Protection Act, 2019, where it applies to you; and
• the policies of Google Play and, where applicable, Apple's App Store.

If a law gives you a right that these Terms do not mention, you still have that right.

27. General

• Severability: if any part of these Terms is unenforceable, the rest stays in effect.
• No waiver: not enforcing a right is not giving it up.
• Assignment: you may not transfer these Terms without our consent. We may transfer them as part of a reorganisation or a sale of the business, subject to your data-protection rights, and we will tell you if we do.
• No third-party beneficiaries, except as these Terms expressly say.
• Force majeure: neither party is liable for failure to perform caused by events beyond its reasonable control.
• Language: if these Terms are translated, the English version controls.
• Entire agreement: these Terms and the documents listed in §1.4 are the entire agreement on this subject and replace every earlier version.

Version history. Version 5.0 (7 October 2026) replaces version 4.0 (drafted the same day and never published) and version 3.0 (9 August 2026). The full history is in the CHANGELOG.