About SchoolOS

SchoolOS terms and conditions

Last updated: 18 October 2026

These Terms govern the use of SchoolOS (the SchoolOS apps, including apps published under a school’s own name, the SchoolOS web app and this page), built and run by Kreare Tech, Visakhapatnam, Andhra Pradesh, India ("Kreare Tech", "we", "us"). By using SchoolOS you agree to these Terms. Read the SchoolOS privacy policy alongside them: it explains what data we collect and why.

1. Who these Terms apply to

SchoolOS is used by three kinds of Users: (a) Schools, who subscribe to SchoolOS and are responsible for configuring it and for the accuracy of the data they enter; (b) School staff (teachers, admins, principals), whose access is provisioned by their school; and (c) Parents/guardians, whose access is provisioned by their school and linked to their own child(ren). A school's agreement to these Terms binds the school; staff and parent Users agree to these Terms individually when they first sign in.

2. What SchoolOS is (and isn't)

SchoolOS is a communication and record-keeping tool for schools: notices, attendance, homework, fees tracking, report cards, certificates, admissions, staff management, and related modules described on our features page. SchoolOS is not a payment processor, a government-recognised academic record-issuing authority, a substitute for a school's own statutory registers, or a payroll/accounting system — see Sections 5 and 6 below for what this means in practice.

3. School accounts & responsibilities

  • A school is responsible for the accuracy of student, parent, and staff data it enters or imports (including via CSV import).
  • A school is responsible for obtaining any consent from parents/guardians required under applicable law before enrolling a student's data in SchoolOS, and for informing parents that SchoolOS will be used to process their and their child's data.
  • A school controls who among its staff has admin/principal access, and is responsible for that access being used appropriately (e.g. only issuing certificates or admitting students through legitimate school process).
  • Certificates, admission records, and similar registers generated in SchoolOS are tools to help a school keep accurate records — the school itself, not SchoolOS, is the legal issuer of any certificate or official document it generates.

4. Parent & staff accounts

  • Your login is personal to you. Do not share your password or, where enabled, allow another person to register their fingerprint/face for check-in on your behalf.
  • You are responsible for keeping your contact details (phone/email) up to date so the school can reach you.
  • You may request a copy of, or correction to, your own or your child's data at any time via your school or via SchoolOS directly.

5. Fees — SchoolOS never touches your money

Where a school uses SchoolOS's fee module, parents pay fees directly to the school's own UPI ID — the payment never passes through SchoolOS, and SchoolOS has no access to any school's bank account, UPI credentials, or transaction settlement. SchoolOS records the amount due and lets a parent submit the UTR (transaction reference number) from their own payment app as proof of payment; a school's staff then verifies that proof and marks the due as paid. SchoolOS is not a party to any fee payment, is not liable for payment disputes between a parent and a school, and does not guarantee that a UTR submitted by a parent is genuine — verification is the school's responsibility, using its own bank statement, exactly as it would with any offline UPI payment.

6. What SchoolOS does not do

  • Payroll: SchoolOS records staff attendance as day-counts (present/absent/late/half-day/leave) for a school's own accountant to use. SchoolOS never calculates, stores, or is responsible for salary, PF, ESI, TDS, or any other payroll figure.
  • Biometric storage: as described in our Privacy Policy, fingerprint/face check-in never sends biometric data to SchoolOS — it stays on the user's device.
  • Legal certification: SchoolOS helps a school generate and register transfer certificates, bonafide certificates, and similar documents, but does not itself certify, notarise, or guarantee the legal validity of any document — that responsibility rests with the issuing school.
  • Live 24/7 tracking: where a school opts into transport tracking, positions are visible only while a driver is actively on a route with the app open, not continuously.

7. Acceptable use

You agree not to:

  • Use SchoolOS to harass, threaten, or send unlawful content to another user;
  • Attempt to access another school's data, or another user's account, without authorisation;
  • Upload content you do not have the right to share (e.g. copyrighted material, or another child's photo without appropriate school authorisation for the gallery/notices features);
  • Attempt to disrupt, reverse-engineer, or probe the security of SchoolOS beyond good-faith, non-destructive testing disclosed to us in advance.

8. Products, subscription, billing & cancellation

SchoolOS is offered as two products, and every module is included in both:

  • SchoolOS Go — the SchoolOS app, published on our store accounts, with the school's name, logo and colours shown inside the app after its school code is entered. Every Go school's data is held on one shared backend that we operate, kept separate by database rules (see our Privacy Policy).
  • SchoolOS Signature — the school's own app, published in the school's own Apple and Google developer accounts, on its own separate backend and web address.

The yearly price depends on the product and on the school's band, which is set by the number of students actually enrolled (not by capacity), as set out in the school’s quote or as separately agreed in writing (e.g. for founding-school terms). Signature also has a one-time setup fee. GST at 18% is added to every invoice. The price is fixed for 12 months from the start date; at renewal the band is reviewed against actual enrolment. Existing schools keep their current price until renewal.

Go is paid yearly, or term-wise in 3 instalments; Signature is paid yearly in advance, or in 2 instalments, directly between the school and SchoolOS (bank transfer, UPI, or as invoiced) — this billing relationship is separate from, and unrelated to, the in-app fee-collection feature described in Section 5, which only ever moves money between a parent and the school. SMS and email are charged separately at cost plus 20%; payment gateway fees and custom features requested by one school (quoted separately) are also charged separately. A Signature school pays for its own Apple and Google developer accounts. A school may cancel at the end of its current billed term; we do not offer automatic renewal without prior notice to the school.

Overdue renewals. If a renewal is not paid, access is limited in stages from the renewal date: first a reminder is shown to the school's admins; 15 days after the renewal date SchoolOS becomes read-only (everything can be viewed, nothing can be changed); 30 days after it, access is paused until the renewal is paid. A school's data is never deleted because a payment is late, and the school can still ask for an export of it.

Moving between products. A Go school can move to Signature at any time; we move all of its data, sign-ins and files to its own backend, and up to one term of Go fees already paid counts towards the Signature setup fee. A school that leaves SchoolOS receives an export of its data on request.

Ownership. The school owns its data and, for Signature, its own store accounts and listings. The SchoolOS software, its source code, and the SchoolOS and "Powered by Kreare Tech" names remain ours; they are licensed to the school for the subscription term, not sold, and may not be copied, resold, or run on another backend.

9. Availability & support

We aim to keep SchoolOS available and responsive, but as with any software service we do not guarantee uninterrupted availability. We do not guarantee delivery of any specific push notification or SMS (delivery depends on device settings, network conditions, and third-party providers), though critical-notice escalation is designed to reach parents who have not opened a notice through a fallback channel where enabled.

10. Limitation of liability

SchoolOS is provided "as is." To the maximum extent permitted by Indian law, SchoolOS and its operator are not liable for indirect, incidental, or consequential loss arising from use of the platform, including but not limited to loss arising from a disputed fee payment (Section 5), a missed notification, or data entered inaccurately by a school or parent. Nothing in these Terms limits liability that cannot be excluded under applicable Indian consumer-protection or data-protection law.

11. Data protection

Our handling of personal data, including students' data, is described in full in our Privacy Policy, which forms part of these Terms. We process personal data in accordance with India's Digital Personal Data Protection Act, 2023.

12. Changes to these Terms

We may update these Terms from time to time; the date at the top will change when we do. Continued use of SchoolOS after an update constitutes acceptance of the revised Terms. For material changes affecting a school's rights or obligations, we will notify the school directly.

13. Governing law

These Terms are governed by the laws of India. Any dispute arising from these Terms or use of SchoolOS will be subject to the exclusive jurisdiction of the courts of Visakhapatnam, Andhra Pradesh.

14. Contact

Email support@krearetech.com, or call or WhatsApp +91 93983 40399.