Subscription agreement
Last updated 30 September 2026 · the terms of service for schools
Between Modulark Tech Systems, a sole proprietorship carrying on business at Tumkur, Karnataka, India (Udyam UDYAM-KR-25-0114587; GSTIN 29DGHPS9145G1ZR) ("Modulark", "we", "us"), and the school named on the Order Form, together with the trust, society or company that runs it (the "School", "you").
Read section 13 before signing. It limits what Modulark can be made to pay, and section 14 makes the School answerable for the personal data it decides to collect and the decisions it takes. Both are deliberate, both are reflected in the price, and the School should take its own advice on them. Plain language is used throughout; plain does not mean optional.
1. The documents, and which one wins
This agreement is made of the following documents. Where they conflict, the earlier in the list prevails, with one exception:
- the Order Form the School signs, which names the School, the contracted roll, the price and the start date;
- these terms;
- the data processing agreement (the "DPA"), which prevails over these terms on how personal data is handled;
- the service and support policy and the acceptable use policy;
- the Schedule of Services for the session.
The exception: section 13 (Liability) of these terms governs every document above, including the DPA. No other document, email, proposal, purchase order, tender condition or school policy increases Modulark's liability or adds to its obligations unless it is signed by Modulark and says expressly that it amends this agreement. Terms printed on the School's purchase orders or payment advices are excluded.
The agreement starts on the earliest of: the School signing the Order Form, paying any invoice, or any of its staff first using the Service (the "Start Date"). The person who signs, accepts or pays for the School confirms that they are authorised to bind the School and the body that runs it.
2. Words used here
- Service: Modulus, the school-management software we provide over the internet (the Office app, the Staff room and the Family app), with its documentation, as it stands from time to time.
- School Data: everything the School or its Users put into the Service, including personal data about pupils, families and staff.
- Users: the School's staff, pupils, parents and guardians, and anyone else the School gives access to.
- Session: an academic year, 1 April to 31 March.
- Fees: the amounts in the Order Form and the Schedule of Services.
- Third-Party Services: services the School connects to Modulus under its own accounts, including payment gateways, UPI, banks, SMS, email, WhatsApp and push-notification providers.
3. What we do
- Give the School and its Users a non-exclusive, non-transferable right to use the Service during the term, for the School's own administration and for nothing else.
- Provide the Service with reasonable skill and care, in line with the service and support policy.
- Keep School Data in a database and behind an authentication server used by no other school, take backups, and test that they restore.
- Give the School a named contact and answer support requests on the timetable in the service and support policy.
- Give at least 30 days' notice before removing a feature the School uses. We may change, improve and add to the Service at any time, and will not materially reduce its core functions (admissions, roll, attendance, marks, report cards, fees, staff) during a Session the School has paid for.
- Process personal data only as the DPA allows.
4. What the School does
4.1 The School decides, and answers for, its data. The School is the Data Fiduciary under the Digital Personal Data Protection Act, 2023. It decides what is collected about pupils, families and staff, why, and on what basis. It gives the notices, and obtains the consents, the law requires, including verifiable consent from a parent or guardian for every child. Modulark does not do this for the School and cannot check that it has been done.
4.2 The School checks what it relies on. Modulus records, calculates and prints: attendance, marks, grades, ranks, report cards, certificates, fee demands, concessions, late fees, receipts, payroll, deductions and statutory registers. The School is responsible for reviewing every output before relying on it, publishing it, issuing it or filing it. The School sets the rules the Service applies (fee structures, grading schemes, payroll components, tax and provident-fund settings) and is responsible for their being correct and lawful, including under fee-regulation law, education-board rules, labour law and tax law. Modulus is a tool; it does not give legal, tax, accounting, medical or educational advice.
4.3 The School controls access. It issues accounts to the right people, removes them when people leave, keeps credentials private, and switches on the second factor for office accounts (which the Service supports and can enforce school-wide). Everything done through a User's account is treated as done by the School. If the School has not enabled the second factor for office accounts, loss caused by a compromised office account is the School's.
4.4 The School runs its own connections. Third-Party Services are contracted by the School in its own name, on their own terms. The School is responsible for their fees, their availability, their registrations (such as telecom DLT registration and payment-gateway KYC), and for what they do with the data sent to them. Hardware, including smart ID cards and gate readers, is bought by the School from its supplier.
4.5 The School keeps its own copies. The Service lets the School export everything at any time. Where the law requires the School to retain a record (admission registers, fee records, payroll and tax records, transfer certificates), the School remains responsible for retaining it, and should export it at least once a term.
4.6 The School and its Users follow the acceptable use policy.
4.7 The School secures its own end. The School is responsible for the devices, browsers, networks and email accounts its staff use to reach the Service, for keeping them free of malware, and for training its staff not to disclose credentials. Modulark is responsible only for the Service itself.
4.8 The School carries its own risks. The School is responsible for deciding whether to insure against loss arising from its records, its decisions and its obligations to families and staff.
5. Suspension
We may suspend all or part of the Service, or any User's access, without liability, if we reasonably believe it is necessary to deal with a security threat, an attack on the Service, unlawful use, a breach of the acceptable use policy, or an order of a court or authority. We will limit a suspension to what the situation needs, tell the School as soon as we can, and lift it when the reason has gone. Suspension for non-payment is dealt with in section 7.
6. Fees and payment
- Price. As stated in the Order Form and the Schedule of Services: an annual licence per enrolled pupil, a one-time onboarding fee, and parent notifications beyond the included bundle, metered. If the roll moves more than 5% from the contracted figure, the licence is adjusted pro rata at the 31 July count.
- When. The onboarding fee and 50% of the first Session's licence on signing; the balance on go-live or 45 days from signing, whichever is earlier. After that, the licence annually in advance, invoiced in March. Metered notifications are invoiced monthly in arrears.
- Payment terms. Every invoice is payable within 30 days of its date. Modulark is a micro enterprise registered under the Micro, Small and Medium Enterprises Development Act, 2006 (Udyam UDYAM-KR-25-0114587). Under sections 15 and 16 of that Act, a buyer may not agree a period longer than 45 days, and an amount paid late carries compound interest with monthly rests at three times the bank rate notified by the Reserve Bank of India, from the due date until payment. The School agrees to pay that interest.
- Taxes. All amounts exclude GST, currently 18%, which is added. Tax deducted at source is adjusted against the invoice once Form 16A is received.
- Disputed invoices. The School must raise any dispute in writing, with reasons, within 15 days of the invoice, and pay the undisputed part on time. An invoice not disputed in that period is accepted.
- No set-off. The School pays in full, without deducting any amount it claims from Modulark.
- Non-refundable. Fees are for a Session, are payable whether or not the School uses the Service or all of it, and are not cancellable or refundable once invoiced, except as section 11.5 and the refunds policy expressly provide.
- Price changes. The per-pupil rate is held for the first Session. Any later increase is notified at least 90 days before renewal and never applies to a period already paid for.
- Family fees. Money families pay the School through the Service goes to the School's own account through the School's own Third-Party Services. Modulark never holds it, takes no share of it, and is not responsible for collecting, reconciling or refunding it.
7. If the School does not pay
We will remind the School in writing. If an invoice is unpaid 30 days after its due date, we may move the Service to read-only: the School and its families can still see and export every record, print a report card and download a receipt, but no new data can be entered. If an invoice is unpaid 90 days after its due date, we may terminate under section 11.3. Interest under section 6 runs throughout, and the School also pays the reasonable costs of recovery, including legal costs.
We will not lock a school out of its own records over an invoice. Read-only is the furthest non-payment goes during the term, and the export window in section 11.6 applies however the agreement ends.
8. School Data
8.1 It belongs to the School. The School grants Modulark the right to host, copy, process, back up and transmit School Data only as needed to provide, secure and support the Service, to comply with law, and as the DPA allows. We claim no other right to it.
8.2 Service data. We may collect and use technical information about how the Service itself performs (uptime, errors, response times, counts of feature use), provided it identifies no person and contains no School Data. We use it to run and improve the Service.
8.3 Backups are for disaster recovery. We keep backups on the schedule in the DPA. If School Data is lost or corrupted, our obligation is to restore it from the most recent backup available to us, at our cost. That is the School's only remedy for loss or corruption of data, and the reason section 4.5 asks the School to keep its own exports.
9. Ownership of the Service
Modulark and its licensors own the Service, its software, design, documentation and the Modulus and Modulark names and marks, and all rights in them. Nothing in this agreement transfers any of it to the School. The School must not copy, modify, resell, sublicense or reverse-engineer the Service, or use it to build a competing product, except where the law does not allow us to prevent it. If the School sends us suggestions, we may use them freely.
10. Availability and support
Availability, maintenance and support are described in the service and support policy. The remedies set out in that policy are the School's sole and exclusive remedies for the Service being unavailable or slow.
10A. School websites, domains and email
Where the Order Form includes them, Modulark will set up for the School a website, a domain name, and email accounts (the "Web Services"). On those:
- The domain is the School's. It is registered in the School's name as registrant, through a registrar, on the registrar's terms. Modulark may act as its technical contact. Renewal fees are charged to the School at cost plus any handling fee in the Order Form. If a renewal is not paid, or the School's details with the registrar are wrong, Modulark is not responsible for the domain lapsing or being lost.
- Email is provided by Google (Google Workspace, or Workspace for Education where the School is eligible) or another provider named in the Order Form, under that provider's own terms and privacy policy, which the School accepts. Modulark sets up the accounts and hands the School administrator access. Modulark does not provide, host or back up the email service, and is not responsible for its availability, security, data, pricing or changes, or for messages sent from the School's accounts.
- The website's content is the School's. The School supplies and approves all text, photographs and other material, and is responsible for having the right to publish them, including the consent of parents or guardians before any photograph or detail of a child is published. Modulark may remove content it reasonably believes is unlawful.
- Hosting and changes. The website is hosted and maintained while the Order Form says, on the same "as is" basis as the Service in section 12.2. Changes beyond those included are quoted separately.
- On ending. The domain and email accounts stay the School's. Modulark hands over any credentials it holds and a copy of the website's files, and stops hosting the website at the end of the export window in section 11.6 unless agreed otherwise.
- Sections 13 and 14 apply to the Web Services, and the School's indemnity in 14.1 covers website content and the School's use of email.
11. Term, renewal and ending
11.1 Term. From the Start Date to the end of the Session in which it falls, then renewing automatically for one Session at a time.
11.2 Ending by the School. The School may end the agreement at the close of a Session by giving at least 60 days' written notice before 31 March. Notice given later takes effect at the close of the following Session. If the School stops using the Service part-way through a Session, the Fees for that whole Session, including any first-Session balance, remain payable.
11.3 Ending by Modulark. We may end the agreement at the close of a Session on at least 90 days' written notice, and never in the middle of one. We may also end it at once by written notice if the School: materially breaches this agreement and does not put it right within 30 days of being told; leaves an invoice unpaid 90 days after its due date; becomes insolvent, is wound up, or closes or loses its recognition as a school; or uses the Service unlawfully.
11.4 Ending by the School for our breach. The School may end the agreement at once by written notice if Modulark materially breaches it and does not put it right within 30 days of being told in writing, with details.
11.5 Refund on our breach. If the School ends the agreement under 11.4, or we end it under our 90-day notice, we refund any Fees prepaid for the part of the Session after it ends. That refund, with the remedies in the service and support policy, is the School's sole remedy for the matters that led to it, subject always to section 13.
11.6 After it ends. All unpaid Fees become due at once. For 90 days the School may export all its data. After that we delete it from live systems within 30 days and from backups within a further 30 days, and confirm deletion in writing, as the DPA sets out. Sections 4.2, 6, 8.3, 9, 10A, 11.6, 12 to 16, 18 and 19 survive the end of the agreement.
12. Warranties and what we do not promise
12.1 We warrant that the Service will perform materially as described in its documentation, and that we will provide it with reasonable skill and care. If it does not, and the School tells us in writing with enough detail to reproduce the problem, we will correct it within a reasonable time. If we cannot, the School may end the agreement under section 11.4. Correction, or ending the agreement with the refund in 11.5, is the School's sole remedy for breach of this warranty.
12.2 Apart from 12.1, and to the fullest extent the law allows, the Service is provided "as is" and "as available". We do not warrant that it will be uninterrupted, error-free or free of every vulnerability; that it will meet requirements the School has not agreed with us in writing; that it satisfies any education board, regulator, auditor or inspector; or that outputs will be correct where the data or rules put in were not. All other warranties and conditions, whether express or implied by statute, custom or otherwise, including of merchantability, quality and fitness for a particular purpose, are excluded.
12.3 Features marked preview, beta, provisional or demonstration are provided without any warranty or commitment, and may change or be withdrawn.
12.4 Demonstrations, sample data, websites, brochures, presentations, proposals, roadmaps and conversations illustrate the Service and are not warranties, representations or commitments. Only this agreement binds Modulark.
13. Liability
13.1 What is not limited. Nothing in this agreement limits or excludes liability for fraud, or any liability that cannot be limited or excluded under Indian law. Nothing limits the School's obligation to pay the Fees and interest, or its liability under section 14.1.
13.2 Losses neither of us is liable for. Subject to 13.1, neither party is liable to the other, however it arises, for: indirect, incidental, special, consequential, exemplary or punitive loss or damage; loss of profit, revenue, business, contracts or anticipated savings; loss of goodwill or reputation; wasted staff or management time; or the cost of substitute services. Loss or corruption of data is dealt with only by section 8.3.
13.3 The cap. Subject to 13.1, Modulark's total aggregate liability arising out of or in connection with this agreement and every document that forms part of it, including the DPA, whether in contract, tort (including negligence), breach of statutory duty, under an indemnity or otherwise, is limited to the Fees actually paid by the School to Modulark under this agreement in the twelve months immediately before the event giving rise to the first claim. This is one cap for all claims together, not a cap per claim or per year. Service credits and refunds paid count towards it.
13.4 What Modulark is not responsible for. Modulark is not liable for loss caused by: School Data, its accuracy or lawfulness, or decisions taken on it; the School's settings, rules or instructions; anything done through a User's credentials, unless caused by our breach of the security obligations in the DPA; Third-Party Services, including payments or messages that fail, are duplicated, delayed or misdirected by them; the School's or Users' devices, networks, internet connections or hardware; preview features; the School's breach of this agreement or of law; or events under section 17.
13.5 Users and families. This agreement is between Modulark and the School only. Pupils, parents, staff and other Users have no rights under it, and any claim they have about the School's records or decisions is a matter between them and the School. The School will not bring a claim on their behalf that it could not bring for itself, and any such claim is inside the cap in 13.3.
13.6 Why. The Fees are set on the basis of the allocation of risk in sections 12 to 14, which the School has had the opportunity to review, negotiate and take advice on, and which the parties agree is reasonable. Each party is responsible for insuring its own risks.
13.7 Recourse. Subject to 13.1, the School will seek to satisfy any claim against Modulark only from the assets of the Modulus business and the proceeds of any insurance Modulark holds, and not from the personal assets of its proprietor, and in any case only up to the cap in 13.3.
13.8 People and suppliers. The School will not bring any claim arising from this agreement against Modulark's employees, contractors, advisers or sub-processors personally or directly. Each of them may rely on sections 12 and 13 as if they were a party.
13.9 Mitigation. The School will take reasonable steps to limit any loss, including using the export tools and its own copies under section 4.5, and Modulark is not liable for loss the School could reasonably have avoided.
14. Indemnities
14.1 By the School. The School will defend, indemnify and hold harmless Modulark, its proprietor, staff and contractors against every claim, demand, proceeding, penalty, fine, loss, liability, cost and expense (including reasonable legal fees) arising from a claim by a third party or an authority, including the Data Protection Board of India, that relates to:
- School Data, including any lack of a lawful basis, notice or verifiable parental consent for it;
- the School's breach of the Digital Personal Data Protection Act, 2023, the Information Technology Act, 2000, or any other law that applies to it as Data Fiduciary, employer or educational institution;
- a breach of this agreement or the acceptable use policy by the School or any User;
- any dispute between the School and a pupil, parent, applicant, member of staff, board or authority about admissions, fees, refunds, marks, attendance, discipline, certificates, employment, payroll or deductions; or
- anything done by Modulark in following the School's instructions or settings.
14.2 By Modulark. We will defend the School against a claim by a third party that the Service, as we provide it, infringes that party's intellectual property rights in India, and pay the damages and costs finally awarded or agreed in settlement. This does not apply to a claim arising from School Data, from the School's modification or misuse of the Service, or from combining it with anything we did not provide. If such a claim is made or likely, we may modify or replace the Service, obtain the right for the School to continue, or end the agreement and refund Fees prepaid for the rest of the Session. This section states our whole liability for infringement, and is subject to the cap in 13.3.
14.3 How. The party claiming an indemnity must tell the other promptly in writing, let it control the defence and any settlement, and give reasonable help at its cost. No settlement may admit fault on behalf of, or impose an obligation on, the indemnified party without its consent, which will not be unreasonably withheld.
15. Confidentiality
Each party will keep the other's confidential information confidential, use it only for this agreement, and disclose it only to people who need it for that purpose and are bound to the same duty. This does not apply to information that is or becomes public other than through a breach, was already known, is independently developed, or must be disclosed by law, in which case the disclosing party will give notice where it lawfully can. This lasts for the term and three years after it; School Data is protected by the DPA for as long as we hold it.
16. Publicity
Neither party will use the other's name or marks in publicity without written consent. We will not name the School as a customer unless it agrees.
17. Events beyond control
Neither party is liable for delay or failure caused by events beyond its reasonable control, including: natural disaster, epidemic, fire, flood, war, riot, strike, acts or orders of government or courts, failure or outage of power, telecommunications, the internet, or hosting or cloud infrastructure, and cyber attacks that occur despite the security measures in the DPA. The affected party will tell the other and do what it reasonably can to resume. This does not excuse payment of money due.
18. Disputes and law
18.1 This agreement is governed by the laws of India.
18.2 A party with a dispute will notify the other in writing, with reasonable details, and senior representatives will try in good faith to resolve it for 30 days. Neither party may start arbitration or proceedings (except for urgent interim relief or the recovery of unpaid Fees) until that period has ended.
18.3 A dispute not resolved in that time will be referred to and finally resolved by arbitration under the Arbitration and Conciliation Act, 1996, administered by the Arbitration and Conciliation Centre – Bengaluru (Domestic and International) under its rules, by a sole arbitrator appointed under those rules. The seat and venue of arbitration is Bengaluru, and the language is English. The award is final and binding.
18.4 Subject to 18.3, the courts at Bengaluru have exclusive jurisdiction, including for interim relief. Nothing in this section stops Modulark from recovering unpaid Fees through any competent court or by reference to the Micro and Small Enterprises Facilitation Council under section 18 of the MSMED Act, 2006.
19. General
- Entire agreement. This agreement is the whole agreement between the parties about its subject. Neither party has relied on any statement, brochure, web page, demonstration or proposal not set out in it; nothing in this clause limits liability for fraud.
- Changes. We may update these terms and the policies they refer to on at least 60 days' written notice. If a change materially reduces the School's rights, the School may end the agreement by notice before the change takes effect and receive a refund of Fees prepaid for the period after it. Changes required by law or for security may take effect sooner. Otherwise, a change to this agreement must be in writing and signed by both parties.
- Assignment. The School may not assign or transfer this agreement without our written consent. We may subcontract parts of the Service. We may assign or novate this agreement to a company or limited liability partnership that succeeds to the Modulus business, by written notice to the School, and the School consents to that now.
- Notices. Notices under this agreement are given by email to the address on the Order Form (for the School) or to mail@modularktech.com (for Modulark), and take effect on the next working day.
- Electronic execution. This agreement may be accepted and signed electronically and in counterparts, which the Information Technology Act, 2000 recognises.
- Relationship. The parties are independent contractors. Nothing creates a partnership, agency or employment.
- Severability and waiver. If a provision is held invalid, it is read down to the extent needed to be valid and the rest continues. Not enforcing a right is not a waiver of it.
Modulus is a product of Modulark Tech Systems, a sole proprietorship carrying on business at Tumkur, Karnataka, India (Udyam UDYAM-KR-25-0114587; GSTIN 29DGHPS9145G1ZR). mail@modularktech.com · +91 90192 95387