Legal
How CloudCampuZ collects, uses, and safeguards data belonging to schools, students, and families — in line with India's Digital Personal Data Protection Act.
Last updated: 26 July 2026 · Applies to cloudcampuz.in and the CloudCampuZ platform
This Privacy Policy explains how Kalix Technologies Pvt. Ltd. ("Kalix", "CloudCampuZ", "we", "us") collects, uses, shares, and protects personal data in two contexts:
We built CloudCampuZ around India's Digital Personal Data Protection Act, 2023 (DPDP Act). This policy uses that Act's terms: a Data Fiduciary is whoever decides why and how personal data is processed; a Data Principal is the individual the data is about.
Kalix Technologies Pvt. Ltd. is a company incorporated in India, headquartered in Hyderabad, Telangana.
Our role differs depending on context:
If you're a student, parent, or staff member with a question about your own data, your school is usually the fastest place to start, since they control your record. We're glad to help too — see Section 11.
When you submit the "Request a Demo" form, we collect your name, role at school, school name, approximate student strength, phone/WhatsApp number, email address, and anything you write in the optional message field. We use this solely to respond to your enquiry.
Once a school subscribes, its authorised staff enter the data below into the platform as part of admissions, HR onboarding, and day-to-day school operations. We do not collect this data directly from students or parents ourselves — the school does, and instructs us to process it.
| Category | Examples |
|---|---|
| Identity & contact | Full name, date of birth, gender, photo, address, parent/guardian name, mobile number (used as the primary login credential via OTP), email, emergency contact |
| Government ID | Aadhaar number (students and staff), PAN (staff), and for campus visitors: ID type and number (Aadhaar/PAN/Passport/Driving Licence/Voter ID) |
| Health | Blood group, height/weight, vaccination status, allergies, medical conditions, emergency medication needs, primary doctor's contact, disability status |
| Family & socio-economic | Parents' occupation and annual income, caste category, religion, mother tongue, nationality, and concession-eligibility flags (e.g. EWS, sibling/staff-child, scholarship) used for fee concessions and statutory reporting |
| Academic | Attendance, homework, timetable, exam marks and results, report cards, syllabus progress |
| Financial | Fee structures, payments, receipts, concessions/refunds; for staff: bank account number, IFSC code, payroll records |
| Documents | Birth certificate, transfer certificate, previous report card, medical certificate (students); resume, qualification and experience certificates, offer letter (staff) |
| Transport | Bus route and stop assignment. Stops use fixed, pre-set map coordinates for route planning — we do not track live GPS location of students, staff, or vehicles, and our platform disables browser location access by policy. |
| System & usage | Login timestamps, audit logs of actions taken in the platform, device/browser information |
We understand this is a broad list. Most of it exists because Indian schools are required to collect it for admissions, board compliance, safety, or concession eligibility — CloudCampuZ is the system schools use to record it, not the reason they collect it.
We (or the school we're processing data for) use personal data to:
We do not use personal data for advertising, do not run behavioural tracking or analytics scripts on the platform, and do not sell personal data to anyone.
Most CloudCampuZ users are students under 18. Under Section 9 of the DPDP Act, processing a child's personal data requires verifiable consent from a parent or lawful guardian, and prohibits tracking, behavioural monitoring, or targeted advertising directed at children.
In practice: schools obtain parental/guardian consent as part of their own admission process (typically via the admission form parents sign), and instruct us to process that data within the platform accordingly. CloudCampuZ does not run advertising or behavioural-tracking of any kind, for students or anyone else. If your school has not yet obtained appropriate consent for platform use, please raise this with them directly — we're happy to support schools with template consent language on request.
Platform data is stored on Supabase's cloud infrastructure with encryption in transit, and access is restricted by role: every account is scoped to its own school, and staff only see the modules their role permits. Login sessions are protected using secure, server-verified cookies rather than storing credentials in the browser.
No system is completely immune to risk, and we can't guarantee absolute security — but we design access controls, encryption, and audit logging specifically to limit who can see what, and to leave a trail when something is accessed.
We retain personal data for as long as a student is enrolled or a staff member is employed, and afterwards for as long as applicable education, tax, or labour recordkeeping laws require. When a student or staff record is deactivated, it is marked inactive and the person can no longer log in — the underlying record is not immediately erased, so that schools can meet statutory recordkeeping obligations (e.g. producing historical academic or payroll records on request).
If you'd like your data erased earlier than that, contact us or your school (Section 9 and 11) and we'll process the request, subject to any legal retention obligations that override it.
As a Data Principal under the DPDP Act, you have the right to:
For platform data, we'll typically ask you to route the request through your school first, since they control the underlying record as Data Fiduciary — but you're welcome to contact us directly and we'll coordinate with the school on your behalf.
For any question, request, or grievance regarding your personal data, reach out to:
Grievance Officer — Kalix Technologies Pvt. Ltd.
Email: info@cloudcampuz.com
WhatsApp: +91 90143 44150
Hyderabad, Telangana, India
We may update this policy as the platform, our providers, or the law change. Material changes will be reflected by updating the "Last updated" date at the top of this page, and where appropriate, we'll notify schools directly.