Terms of Service

These terms are the contract between your preschool, playschool or daycare (“you” or “the School”) and the company that builds and runs the software (“TantraDev”, “we” or “us”).

They apply to Kibiscope (“the Platform”), our preschool management software, and to this website. They start applying when you sign an order form, when you start a pilot or trial, or when anyone at your School first uses the Platform — whichever happens first.

An order form is the written summary of what you have signed up for: your student numbers, your price, your billing cycle and anything we have agreed that differs from this document. If an order form signed by both of us says something different from these terms, the order form wins for that point only.

TantraDev also publishes terms at tantradev.com/termsfor its custom software development work. Those terms cover project work billed by scope. They do not govern your subscription to the Platform. This document does.

One thing in those other documents does not carry over. Terms and policies TantraDev has published for its other services were written for business customers, and some of that wording says the service is not directed at children or is not for anyone under a stated age. None of it applies here and none of it is part of this agreement. The Platform exists to hold records about children under six. This document and our Privacy Policy govern that, and where anything else we have published says otherwise, these govern.

The person who accepts these terms must be at least 18 and must be authorised to commit the School. If you are signing on behalf of a trust, society or company that runs the School, you are confirming you have that authority.

The Platform is software your staff use to run the day-to-day administration of a preschool. Depending on what your School switches on, it holds and organises:

• student profiles and guardian details
• attendance, daily reports and photos uploaded by your staff
• health records, allergies and other documents your School keeps on a child
• fee invoices and records of payments your School has received
• incident reports
• messages between your staff and parents

Be clear about what this is: the Platform is a record-keeping and communication tool. It does not make decisions for you, and it does not discharge your School’s own legal duties — child safety, staff conduct, statutory registers, tax filings and anything your state education department requires all remain yours.

The Platform is new, and no school is running on it in production yet. It is sold after a booked demonstration rather than by public sign-up, and we will show you what actually works before you commit. If a feature is still in progress we will say so rather than let a demo imply otherwise. Anything we label early access, beta or preview is offered as it is, and the promises in these terms about availability and support do not extend to it.

This website is not the Platform. The only place this website asks you for anything is the demo request form — your name, school name, email, and optionally phone, city, approximate number of children and a message. That form does not send anything to a server of ours. It opens your own email application with what you typed already filled in and addressed to us, so nothing reaches us unless you choose to send that email. If we ever change that, we will say so on the form and in our Privacy Policy before the change goes live.

The site carries no analytics, no tracking pixels, no advertising cookies and no third-party code that profiles you. It is not entirely free of third parties, and we would rather say so: the page fonts are served by Google Fonts, so your browser fetches them from Google and Google can see your IP address when it does, and the company that hosts the site keeps ordinary server logs. Our Privacy Policy sets all of this out in full.

We improve the Platform continuously, so features change. We will not remove or materially reduce a feature your School is relying on without telling you in advance.

Your School controls its own accounts. You decide which staff get logins, what role each of them has, and when an account is closed. We do not create, change or remove staff accounts for you unless your named administrator asks us to in writing.

You are responsible for what happens under your School’s accounts. That includes what your staff upload, what they share with parents, and what they do with a login you have given them.

Parents do not have accounts with us. A parent or guardian gets access only because your School gives it to them, sees only the children your School has linked them to, and loses access when your School removes the link. If a family leaves, closing their access is your School’s job, and we will help if you ask.

Practical rules that keep this workable:

• one login per person — shared staff logins destroy the audit trail
• keep passwords private and do not reuse them from other systems
• keep your named administrator and their contact details current with us
• tell us at admin@tantradev.com as soon as you suspect an account has been compromised

Use the Platform to run your preschool. Do not use it to do any of the following.

• Break the law, or help someone else break it.
• Upload information about a child, parent or member of staff that you have no right to hold or share.
• Share a photo, video or report about a child with anyone the consent records do not allow.
• Store data that has nothing to do with running your School — another business’s records, for example.
• Resell, sublicense or give access to the Platform to anyone outside your School.
• Copy, decompile or reverse engineer the software, or try to extract its source code.
• Scan, probe or load-test our systems, or try to reach another school’s data. If you want to run a security test, ask us first and we will agree a scope in writing.
• Send bulk unsolicited messages through the Platform, or use it to market to parents on behalf of a third party.
• Upload malware, or deliberately interfere with the service for anyone else.

If you find a security weakness, please report it to admin@tantradev.com instead of exploiting it. We will not pursue anyone who reports a genuine problem responsibly and gives us a fair chance to fix it.

Everything your School, your staff and your parents put into the Platform is School Data, and your School owns it. TantraDev claims no ownership of it, now or after this agreement ends.

To be specific about what we will not do with School Data:

• we will not sell it, rent it or trade it
• we will not use it to advertise to you, to parents or to children
• we will not use it to train artificial intelligence models
• we will not use it to build products for other customers
• we will not disclose it to anyone except on your instruction, or where a law or a valid court order requires it — and where we are legally allowed to tell you first, we will

We handle School Data only to run the Platform for you and to do what you tell us. Using the Platform in the ordinary way is itself an instruction: when your staff share a daily report with a parent, that is you instructing us to deliver it.

Separately from School Data, we keep operational records — server logs, error reports, performance and usage metrics — that we need to keep the service running and secure. Those are ours, and we do not use them to look into the contents of your records.

The Digital Personal Data Protection Act, 2023 uses two terms that matter here. A Data Fiduciary is the organisation that decides why and how personal data is used. A Data Processor is the organisation that handles that data on the Fiduciary’s instructions, and nothing more.

Your School is the Data Fiduciary. TantraDev is the Data Processor. You decide what goes into the Platform, who may see it and how long it is kept. We process it only to provide the service to you. This section is the written contract the Act requires between a Data Fiduciary and the processor it engages.

This is children’s data, and Section 9 of the Act treats it more strictly than anything else. Under the Act a child is anyone under 18, so every child in your setting is covered, and so is every record you keep about them. As Data Fiduciary, your School is responsible for:

• obtaining verifiable consent from a parent or lawful guardian before the data is processed, and keeping that consent current
• checking, to the extent the Act requires, that the person giving consent really is the parent or guardian
• giving parents the notice the Act requires, in a language they understand
• deciding what is accurate, what is corrected and what is deleted
• answering the requests parents make about their child’s data
• making sure the staff you give access to actually need it

Section 9 also forbids two things outright, and they bind both of us. Children’s data may not be processed in a way that is likely to have a detrimental effect on a child’s wellbeing, and children may not be tracked, behaviourally monitored, or targeted with advertising. We do not profile children, track their behaviour across services, or serve advertising to anyone. The Platform is not funded by advertising at all, and we will refuse an instruction from you that would breach this.

As Data Processor, we will:

• process School Data only on your documented instructions, and tell you if we believe an instruction would break the law rather than simply carrying it out
• keep it confidential and limit access to the few people who need it to do their work
• keep each school’s data separated from every other school’s
• tell you about a personal data breach affecting your School without undue delay, and in any event within 72 hours of becoming aware of it, with what we know and what we are doing
• help you respond to a parent exercising their rights, and to the Data Protection Board
• place the same obligations on any sub-processor we use to run the service, and tell you who they are and when they change
• return or delete School Data when this agreement ends, as set out below

A breach does not end with us telling you. Under the Act it is the Data Fiduciary — your School — that must report a personal data breach to the Data Protection Board of India and to every affected parent, in the form and within the time the Act and its rules require. We give you in writing what we know so that you can do that; we do not make that report on your behalf. Where the CERT-In directions of 28 April 2022 apply to an incident on our own systems, we make the report they require within the six hours they allow.

Where your data sits. The Platform runs on third-party cloud infrastructure, and we use a small number of sub-processors to operate it — hosting, and delivery of the email the Platform sends. Before your School goes live we will tell you in writing who they are and in which country your data is stored, and we will tell you in advance of a change so that you can object. We will not transfer School Data to a country the Central Government has restricted under Section 16 of the Act. If your own regulator puts a localisation requirement on you, tell us in writing and we will either meet it or tell you plainly that we cannot.

Checking that we do this. Once in any twelve months, and again after any breach affecting your School, you may ask us for the information you reasonably need to satisfy yourself that we are meeting this section, and we will answer in writing. If your regulator requires a formal audit, we will cooperate with it, at your cost.

The Platform includes three things built specifically for this Act:

• an immutable consent ledger — consent given or withdrawn is recorded and cannot be quietly edited afterwards
• data principal rights requests — a request from a parent is logged and tracked with an audit trail of what was done
• a media consent gate — a photo or video cannot be shared to a parent without a consent check passing first

Full detail on what is collected, why, and for how long is in our Privacy Policy, which forms part of these terms.

The Digital Personal Data Protection Act is not the only law in play. The Information Technology Act, 2000 still applies, and so do the SPDI Rules made under it in 2011, for as long as they remain in force. Under those rules some of what your School keeps in the Platform is sensitive personal data or information: health records, allergies and medical history, and the passwords your staff log in with.

Two things follow. Section 43A of the IT Act requires whoever holds that data to maintain reasonable security practices, and the next section sets out exactly what ours are and are not, so that you can judge them for yourself. Section 72A makes it an offence to disclose personal information obtained under a contract without consent, and that binds our people as much as it binds yours.

Your School decides what health information it needs to hold. Please do not put more into the Platform than the care of the child actually requires.

These are the protections the Platform actually has today:

• database-level row security, so a request made in one school’s session is filtered to that school’s rows by the database itself and not only by application code
• passwords stored using argon2id hashing, never in a form we can read
• session tokens signed with RS256, and refresh tokens that rotate and are revoked if one is reused
• role-based access control, so a teacher and an administrator see different things
• rate limiting and standard security headers
• instrumentation and alerting on the running system — it records continuously, and we act on what it raises during working days rather than around the clock

And here is what we do not claim, because a school choosing software deserves the unflattering half too. We hold no security certification — not SOC 2, not ISO 27001, not any other — and no outside firm has penetration-tested the Platform. We do not claim encryption of data at rest, a managed key service, automatic scheduled backups, or a tested disaster recovery capability. Backups today are taken by hand, by an operator running a script, not on a schedule you can rely on. If any of that changes we will say so plainly and update this section; until then, please do not assume it.

Because of that, take your own copy of your data. You can ask us for a complete export at any time during your subscription and we will provide it in a machine-readable format at no charge. Be realistic about what that is: an operator produces it by hand, so allow us7 working days. There is no self-service export button in the Platform today, and if we build one we will say so here. Do not treat the Platform as the only place your School’s records exist.

Plan prices are published on our pricing page, confirmed in your order form, and are exclusive of GST. GST at the prevailing rate, currently 18%, is added to that figure. If the government changes the rate, the new rate applies from the date it takes effect. If your School is registered for GST, give us your GSTIN so it appears on your invoices. A school that supplies only exempt education generally cannot claim input tax credit on it, so for most preschools this GST is a cost rather than a credit — your own CA can confirm your position.

Whether that GST appears as CGST plus SGST or as IGST depends on the place of supply: your School’s GST registration, or, if it is not registered, the address we hold for it. For a School in Maharashtra it is CGST plus SGST, and for a School elsewhere in India it is IGST. The total is the same either way.

If your School is required to deduct tax at source on the fee, deduct it, pay us the balance, and give us the TDS certificate. We treat the invoice as settled when we have both the payment and the certificate.

Your plan is set by the number of students with an active record in your account. If that number stays above your plan’s limit for a full calendar month, we move you to the next plan and invoice the difference for the whole months left in your plan year; we do not move you down mid-year. A founding price, where it applies, continues for as long as your subscription does without a break, including after a move to a larger plan.

We do not take payments online. There is no payment gateway on this website or in the Platform. We never see, handle or store your card or bank credentials. What the Platform does is issue GST-ready invoices with proper gap-free numbering and record payments your School has received or made by other means. Fee collection from parents happens outside the software, the way it does now.

If we change the price we will give you at least 30 days’ written notice, and the new price takes effect at your next renewal, never mid-term. We do not raise a founding school’s price while its subscription continues.

We invoice on the cycle in your order form and send invoices by email to your named billing contact. Payment is due within 15 days of the invoice date.

If you think an invoice is wrong, tell us before the due date. We will put that line on hold while we check it, and you should pay the rest of the invoice in the meantime.

If an invoice goes unpaid:

• we will send a written reminder to your billing contact and your administrator
• we do not charge interest on a late payment — we would rather talk to you about it
• if it remains unpaid 15 days after the due date, we may put the account into read-only access after written warning first. Your records, attendance and pickup history stay readable: a late invoice is not a reason to cut a school off from a child’s data

Suspension for non-payment does not delete anything. Your data stays where it is and access is restored once the account is settled. We will never use a school’s records as leverage: even during a payment dispute you can ask for an export of your data and we will provide it.

Fees already paid are not refundable, except where these terms or our Refund & Cancellation Policy say otherwise — including when you leave a yearly plan early, if we end your subscription for our own convenience, if you reject a change to these terms and leave, or if either of us ends the agreement because an event outside our control has run on too long.

These terms do not promise an uptime percentage, and that is deliberate. The Platform is pre-launch. We have no operating history to base a number on, and a figure invented for a contract is worth nothing to you. We would rather tell you that than print “99.9%” and hope.

What we will do is work to keep the Platform available through the school day, give you advance notice of planned maintenance where we reasonably can, and keep it short and outside school hours where we reasonably can. The Platform runs on third-party infrastructure, and an outage there can take us down with it.

If you need a formal service level agreement, ask us for one. For multi-branch schools and chains we will negotiate a written SLA with defined uptime, response times, escalation contacts and remedies. A signed SLA overrides this section for the account it covers. We offer it on request rather than pretending everyone already has one.

We do not currently offer a contractual backup, restore or disaster recovery guarantee. That is why the export right above matters, and why we suggest you use it regularly.

Support is by email to admin@tantradev.com and by phone on +91 92703 85626. You can write to us at any hour; we work on requests during working days in India.

We aim for a first reply within one working day, Monday to Saturday, Indian time. We do not offer 24/7 or emergency out-of-hours support, and we are not going to claim we do. When several things are open at once we deal first with anything that risks losing data or affects a child’s safety.

Support covers questions about how the Platform works, bug reports, and help with settings and configuration. It does not cover data entry on your behalf, training beyond the onboarding agreed in your order form, or custom development. Custom work is a separate engagement under TantraDev’s development terms.

You may end it. Tell us in writing, by email, at any time; no notice period applies. Your subscription stops at the end of the month you tell us in. On a yearly plan, the months not yet started are refunded after the months used are charged at the monthly price, as our Refund & Cancellation Policy sets out; on the monthly option there is nothing to refund.

We may end it. We will give you at least 90 days’ written notice if we decide to stop serving your School or to withdraw the Platform, so you have time to move before a term begins, and we will refund the unused part of anything you have paid in advance.

Either of us may end it for breach. If one side breaks these terms in a serious way and does not fix it within 30 days of written notice, the other may end the agreement immediately. Either of us may also end it immediately if the other becomes insolvent or stops trading.

We may suspend access, in whole or in part, without waiting, if:

• an invoice is overdue and we have warned you in writing, as set out above
• an account is being used unlawfully, or in a way that puts a child at risk
• there is a live security threat and suspension is the way to contain it
• a law or a court requires it

A suspension will be limited to what the problem actually requires. We will tell you why it happened and what needs to change to lift it, and we will lift it as soon as the reason is resolved.

Ending the agreement does not change who owns the data. It is yours on the last day exactly as it was on the first.

For 90 days after the agreement ends, you can ask us for a complete export of your School Data and we will provide it in a machine-readable format at no charge. Ask early rather than late.

After that period we delete School Data from our live systems, and we remove it from the manually taken backup copies within a reasonable time after that. If you want written confirmation that deletion has happened, ask and we will give it.

Two exceptions. We keep invoices, payment records and related accounting entries for as long as Indian tax law requires — for GST records that is 72 months from the due date of the annual return for the year they belong to, and we keep our books of account for eight years. And if a law or a court order requires us to preserve something, we will preserve only that, and only for as long as required.

TantraDev owns the Platform — the software, its source code, its design, its documentation and its name — and keeps every right in it. Nothing in these terms transfers any of that to you.

While your subscription is running and your account is in good standing, you have a non-exclusive, non-transferable licence to use the Platform to run your School. That licence ends when the agreement ends.

If you send us an idea or a suggestion, we may use it to improve the Platform for everybody, without owing you anything for it. That does not give us any right to your School Data, which stays yours under the section above.

We will not use your School’s name, logo, photographs or a description of your setup in our marketing without your written permission first, and you can withdraw that permission later.

Each of us will learn things about the other that are not public: your fee structure, staffing and parent relationships on one side; our pricing, roadmap and technical design on the other. Neither of us will disclose the other’s confidential information to anyone else, or use it for anything other than performing this agreement.

This does not apply to information that is already public through no fault of ours, that the receiving side already knew, or that it worked out independently. If a law or a court requires a disclosure, the side being compelled may make it, and will tell the other first where it is legally allowed to.

These obligations continue for three years after the agreement ends. School Data is treated as confidential for as long as we hold it, and is also governed by the data protection section above.

Our total liability to you, for everything arising out of this agreement taken together, is limited to the fees you actually paid us in the twelve months before the event that gave rise to the claim. If you have paid us nothing in that period — during a free pilot, for example — that amount is nil.

Neither of us is liable to the other for indirect or consequential loss: lost profit, lost revenue, lost business, loss of goodwill or reputation, or savings you expected to make. That holds even if the loss was foreseeable or one of us had been warned it might happen.

None of this limits liability for fraud, for wilful misconduct, or for anything that Indian law does not permit to be limited. It does not cap what your School owes us under the indemnity in the next paragraph either.

We are not responsible for what your staff put into the Platform or for whether it is accurate, for decisions your School makes using it, or for your School’s own compliance duties. If someone brings a claim against us because your School put data into the Platform that it had no right to hold or share, or used the Platform unlawfully, you will cover our reasonable costs of dealing with it.

Read this section together with the security section. We have set out plainly which protections exist and which do not, and the price reflects that. If the risk that leaves is more than your School is willing to carry, tell us before you sign and we will talk about it, rather than let you discover it later.

Neither of us is in breach for a delay or failure caused by something genuinely beyond our control: natural disaster, fire, flood, epidemic, war or civil unrest, strike, a failure of power or internet infrastructure, or an act of government. We will tell you as soon as we can and work to limit the effect.

This does not excuse payment of fees for service already delivered. If the situation continues for more than 30 days, either of us may end the agreement in writing, and we will refund the unused part of anything paid in advance.

We may update these terms as the Platform grows and as the law changes. For a change that materially affects you, we will email your administrator at least 30 days before it takes effect. Smaller corrections take effect when we publish them.

If you do not accept a material change, tell us before it takes effect and you may end your subscription without penalty. We will refund the unused part of anything you have paid in advance. Continuing to use the Platform after the change takes effect means you accept it.

We will not apply a change retrospectively to something that has already happened, and a change to the price follows the notice rules in the fees section rather than this one.

Indian law governs this agreement.

Talk first. If a dispute arises, the side raising it will set it out in writing, and both sides will then have 30 days to negotiate in good faith, with someone senior enough to settle it involved on each side. Most disagreements end here.

If those 30 days pass without a resolution, the courts at Pune, Maharashtra have exclusive jurisdiction. Both sides agree to that and will not ask another court to hear it. This mirrors the jurisdiction in TantraDev’s existing published terms, and is deliberate.

Nothing here stops either side from asking a court for an urgent injunction to stop a breach of confidentiality or a misuse of data while the discussion is going on. Nothing here limits the powers of the Data Protection Board of India, or a parent’s right to complain to it.

The Digital Personal Data Protection Act, 2023 and the rules made under the Information Technology Act both require us to name someone you can complain to about personal data, and to say how quickly that person answers. Here they are, so that nobody has to go looking.

Write to the Grievance Officer if you believe personal data has been mishandled — by us, or by us acting on your instruction. We respond within 30 days of receiving a complaint, and faster where a child’s safety is involved.

Parents should go to their School first. Your School is the Data Fiduciary and holds the consent records, so a parent’s request about their own child goes to the School, and the School answers it. If a parent writes to us directly we will tell them that, pass the request to your named administrator, and help you answer it.

If our answer does not satisfy a complainant, the Act lets them take the matter to the Data Protection Board of India. Nothing in this agreement takes that right away.

• These terms, your order form and the Privacy Policy published on this website are the whole agreement between us on this subject, and replace anything said before it.
• The version of these terms in force is the one published on this page. Ask us and we will tell you in writing which version applied on any given date.
• If a court finds one clause unenforceable, the rest stays in force and that clause is read as narrowly as it needs to be to work.
• Not enforcing something once does not mean we have given up the right to enforce it later.
• You may not transfer this agreement to someone else without our written consent, which we will not withhold unreasonably — for example, if your School changes its legal entity. We may transfer it to a company that takes over this business, and we will tell you if that happens. The data protection obligations above travel with it unchanged.
• Neither of us is the other’s agent, partner or employee, and nobody outside this agreement gets rights under it.
• Formal notices go by email — to admin@tantradev.com for us, and to your named administrator for you. Keep that address current.

Questions about these terms, about an invoice, or about how your data is handled go to admin@tantradev.com or +91 92703 85626. We are at C1304, C1305, 41 Evoke, Ravet, Pune, Maharashtra 412101, India.

If your question is a complaint about personal data, the grievance section above says exactly who to write to and how long we take to answer.