Legal

Privacy Policy

How KIDUART collects, uses, stores, shares, and protects personal data across its website, school ERP platform, demo requests, and related services.

Last updated: 28 May 2026

We collect information needed to run our website, respond to demo requests, onboard schools, and operate KIDUART services.

We may process school, staff, parent, student, finance, attendance, communication, and device-related data depending on modules used.

Schools using KIDUART are responsible for ensuring they are authorized to share personal data with us.

You may contact us to exercise privacy rights, withdraw consent where applicable, or raise grievances.

1

Introduction

At KIDUART, we value the privacy of schools, administrators, teachers, parents, students, staff members, website visitors, and every individual who interacts with our website, platform, and services.

This Privacy Policy explains what information we collect, how we use it, when we share it, how long we keep it, and what choices or rights may be available to you.

2

Who We Are

KIDUART is a school ERP and education technology platform designed to support school administration, academic workflows, attendance, fee management, reporting, communication, and operational efficiency for educational institutions.

Our primary contact email is support@kiduart.com and our current business location is Noida, Uttar Pradesh, India.

3

Scope of This Policy

  • Visitors to our public website and landing pages.
  • Individuals submitting contact, enquiry, support, newsletter, or demo request forms.
  • Schools and institutions evaluating, onboarding, or using KIDUART services.
  • Authorized users such as administrators, teachers, finance staff, HR staff, parents, and students using KIDUART-enabled services.
  • This policy does not apply to third-party websites, integrations, or services that maintain their own privacy practices.
4

Information We Collect

The exact categories of data we process depend on how KIDUART is used, which modules are enabled by a school, and what information a school or user chooses to submit.

CategoryExamplesWhy it may be collected
Identity and contact dataName, email address, phone number, job title, institution nameDemo requests, onboarding, communication, and support
Institution dataSchool name, branch details, address, board or affiliation, class structureAccount setup, service configuration, and reporting
User account dataLogin identifiers, roles, permissions, profile detailsAccess control, authentication, and administration
Student and parent-related dataStudent name, class, roll number, guardian contact details, attendance, academic records, communication history, fee-related recordsDelivering ERP services requested by the school
Employee and staff dataStaff profile, department, attendance, payroll-related or role-related details where applicableHR, administration, and school operations
Technical and usage dataIP address, browser type, pages viewed, device type, logs, timestamps, referral URLsSecurity, diagnostics, analytics, and performance improvement
5

How We Collect Information

  • Directly from you when you fill forms, request a demo, contact us, subscribe, or communicate with us.
  • From schools or authorized institutional representatives during onboarding and service use.
  • From user activity within the platform, including logins, actions, and administrative workflows.
  • Automatically through cookies, server logs, analytics tools, device data, and similar technologies.
  • From integrations or third-party tools enabled by the school or required for service delivery.
6

Why We Use Information

  • To provide, maintain, configure, and improve our website and school ERP services.
  • To create and manage school accounts, authorized user access, roles, and permissions.
  • To operate attendance, fee tracking, student records, timetable, communication, and reporting features.
  • To respond to enquiries, schedule demos, provide onboarding, and offer customer support.
  • To authenticate users, monitor misuse, prevent fraud, and protect platform security.
  • To comply with contractual, regulatory, legal, accounting, and audit-related obligations.
7

School and Institution Responsibility

Important

In many cases, schools decide what information is uploaded to KIDUART, which modules are used, and which users are authorized to access the system. The school is responsible for ensuring that it has the required authority, notices, consents, permissions, or other lawful basis to share personal data with us for service delivery.

8

Children's and Student Data

KIDUART may process information relating to students, including minors, where such data is provided and managed by a school or institution for legitimate educational and administrative purposes.

We do not intend for children to independently create public consumer accounts on our website unless specifically supported and authorized through a school-managed workflow.

9

Sharing and Disclosure

  • With authorized school administrators and users according to assigned roles and permissions.
  • With service providers who help us host, secure, support, analyse, or operate the platform.
  • With payment, communication, analytics, or integration providers where required for selected services.
  • With legal, regulatory, or government authorities when required by law or necessary to protect rights and security.
  • With successors in connection with a merger, acquisition, restructuring, or business transfer, subject to appropriate safeguards.
10

Cookies and Analytics

Our website may use cookies, server logs, pixels, and analytics technologies to understand usage, improve page performance, secure the website, and remember user preferences.

You can control cookies through your browser settings, but disabling certain cookies may affect website functionality.

11

Data Retention and Security

We retain information only for as long as reasonably necessary for service delivery, school account administration, legal compliance, billing, security, audit, dispute resolution, and legitimate operational needs.

KIDUART uses access controls, encryption, backups, monitoring, and administrative safeguards designed to protect data against unauthorized access, loss, misuse, alteration, or disclosure.

12

Your Rights and Choices

  • You may contact us to request access, correction, update, deletion, or review of personal data, subject to applicable law and institutional control.
  • Where processing is based on consent, you may request withdrawal of consent where applicable.
  • For school-controlled student or parent records, we may direct requests to the relevant school administrator for verification and action.
  • You may raise privacy concerns or grievances using the contact details provided on this page.
13

Changes to This Policy

We may update this Privacy Policy from time to time to reflect product, legal, operational, or security changes. The updated version will be posted on this page with a revised effective date.