How KIDUART collects, uses, stores, shares, and protects personal data across its website, school ERP platform, demo requests, and related services.
The modules your school switches on decide what data exists section 5 maps each functional area to the data it processes.
Access follows role: a parent sees their own children, a teacher their classes, an accountant the fee book.
Schools using KIDUART are responsible for ensuring they are authorized to share personal data with us.
You can export everything and ask us to remove it; we do not sell school data or train models on student records.
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.
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.
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.
| Category | Examples | Why it may be collected |
|---|---|---|
| Identity and contact data | Name, email address, phone number, job title, institution name | Demo requests, onboarding, communication, and support |
| Institution data | School name, branch details, address, board or affiliation, class structure | Account setup, service configuration, and reporting |
| User account data | Login identifiers, roles, permissions, profile details | Access control, authentication, and administration |
| Student and parent-related data | Student name, class, roll number, guardian contact details, attendance, academic records, communication history, fee-related records | Delivering ERP services requested by the school |
| Employee and staff data | Staff profile, department, attendance, payroll-related or role-related details where applicable | HR, administration, and school operations |
| Technical and usage data | IP address, browser type, pages viewed, device type, logs, timestamps, referral URLs | Security, diagnostics, analytics, and performance improvement |
KIDUART ships functional module areas, and a school switches on only the ones it uses. Because the modules decide what data exists in the system, this table maps each area to the data it processes so you can see exactly what turning a module on means for personal data.
If your school does not use Transport, no route or vehicle allocation data exists for your students. The same is true for Hostel, Library, and every other area.
| Module area | Personal data processed | Purpose |
|---|---|---|
| Admission | Enquiry details, applicant and guardian names, contact numbers, application documents, interview evaluations | Running the admission pipeline from enquiry to registration |
| Student Management | Student profile, enrolment, class and section history, documents, promotion and transfer records | Maintaining the student record every other module reads from |
| Parent Management | Guardian records, parent-student linking, portal accounts, communication log | Giving parents access to their own children's information |
| Academic | Attendance, timetable allocation, assignments, class diary, exam marks, grades, report cards, discipline and PTM records | Delivering day-to-day teaching and assessment workflows |
| Finance & Fee Management | Fee structures assigned to a student, concessions, payments, receipts, dues, refunds | Fee collection, reconciliation and financial reporting |
| HR & Staff Management | Staff profiles, department and designation, attendance, leave records, payroll and appraisal data | School HR administration and salary processing |
| Communication | Notices and announcements sent, recipient groups, message delivery records | Sending and evidencing school communication |
| Library Management | Membership, borrowing history, reservations, fines | Running circulation without paper registers |
| Transport Management | Route and stop allocation for a student, vehicle and driver records, tracking data | Operating school transport safely (only if the module is enabled) |
| Hostel Management | Room and bed allocation, hostel attendance, mess records, visitor log | Residential care and accountability (only if the module is enabled) |
| Security & Authentication | Login identifiers, hashed passwords, MFA enrolment, session and device records, IP address, audit entries | Authenticating users, protecting accounts and evidencing sensitive actions |
| Reports, Dashboards & Analytics | Aggregated academic, attendance and financial data derived from the records above | Reporting to school leadership and statutory bodies |
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.
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.
Some parts of the service require a third party, and those choices are yours to make with us during onboarding. Where a school brings its own account a payment gateway or SMS provider, for example that provider's own terms and privacy policy also apply to the data it handles.
| Provider category | What it handles | Data involved |
|---|---|---|
| Payment gateway (for example Razorpay or Stripe) | Online fee payments made by parents | Payer name and contact, amount, transaction reference. Card and bank credentials are handled by the gateway, not by KIDUART |
| SMS provider | Attendance alerts, fee reminders, OTP messages | Recipient mobile number and message content |
| WhatsApp Business API | Template notices and reminders to parents | Recipient number and template message content |
| Email delivery provider | Circulars, receipts, verification and reset emails | Recipient email address and message content |
| Cloud hosting and storage | Running the platform and storing uploaded documents | All school data held in the platform, within the tenant separation described in our security page |
| Identity providers (Google, Microsoft) | Optional school-account sign-in | The account identifier used to sign in, where a school enables it |
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.
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.
Academic and financial history is retained while a school needs it, because schools are required to keep it a transfer certificate needs the enrolment history and a fee dispute needs the ledger. Operational and diagnostic logs are kept for a limited window and then removed.
Security controls include role-based permissions, password hashing, optional authenticator-app multi-factor authentication, session and token management, tenant-level separation of each school's data, optional IP and location restrictions, and audit logging of sensitive actions. These are described in plain language, including what we do not yet claim, on our security page.
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.
