CampusKaro · Legal
Privacy Policy
This policy explains how CampusKaro (campuskaro.in) handles your data. We describe actual practices implemented — not marketing claims.
Effective · 17 October 2026Last updated · 17 October 2026
For final legal publication, have this policy reviewed by a qualified legal professional.
Browse policy sections
- 01 · Scope and Policy Version
- 02 · Our Role for Different Data
- 03 · Information We Collect
- 04 · Student and Guardian Records
- 05 · Children’s Information
- 06 · Photographs and Documents
- 07 · Teacher and Staff Records
- 08 · Fees, Payments and Receipts
- 09 · How We Use Information
- 10 · Institute-Directed Messages
- 11 · CampusKaro Communications
- 12 · Sharing and Disclosure
- 13 · Service Providers
- 14 · Security Safeguards
- 15 · Retention and Backups
- 16 · Access, Correction and Requests
- 17 · Cookies and Device Data
- 18 · Account Closure and Data Export
- 19 · Incident Handling
- 20 · Policy Changes and Contact
- 21 · Provider Identity
01
Scope and Policy Version
This policy describes how CampusKaro handles information through its website, registration and sign-in flows, school and coaching workspaces, APIs, support channels and related services that link here. It applies to institute owners and staff who use accounts, and to student, guardian, teacher and other information an institute enters into its workspace. Read it with the Terms & Conditions and any order or service terms for the selected plan. Effective and last updated: 17 October 2026. This page is the current version; earlier versions may be available on request where retained.
02
Our Role for Different Data
An institute decides which student, guardian, academic, staff and fee records to enter, why it needs them and which staff may see them. For those institute-directed activities, CampusKaro provides the software and processes information to deliver the configured service. The institute is responsible for its notices, instructions, access choices and legal authority to use those records.
CampusKaro separately handles information needed to register and administer an account, verify an owner/admin, manage subscriptions, secure the service, answer support requests and meet applicable obligations. The exact legal role of each party depends on the activity, agreement and applicable law; labels in this policy do not replace that assessment.
CampusKaro separately handles information needed to register and administer an account, verify an owner/admin, manage subscriptions, secure the service, answer support requests and meet applicable obligations. The exact legal role of each party depends on the activity, agreement and applicable law; labels in this policy do not replace that assessment.
03
Information We Collect
- Account and institute details: institute name and type, address, owner/admin name, email, phone, verification and approval information, selected plan and billing status.
- Authentication and support: protected password credentials, account recovery and session information, support messages and details needed to resolve a reported issue. Never send us your plaintext password or one-time code.
- Workspace records: admissions, student IDs and profiles, classes, sections, courses and batches, teacher/staff profiles, fee settings, dues, payments, salary entries, receipts, reports, notes and documents entered by an institute.
- Transactions: subscription plan, amount, billing period, payment status, provider reference and invoice/order details. Payment credentials are handled by the payment provider where used; do not enter them in ordinary record or support fields.
- Technical and activity data: IP address, browser/device user agent, request identifiers, sign-in and error events, and activity records for important actions such as admission, payment or settings changes, where configured.
- Messages and preferences: recipient, delivery status and message content or template information needed when an institute uses an enabled communication feature; account communication preferences where collected.
04
Student and Guardian Records
Student and guardian records are supplied and managed by the institute. Depending on its features, these may include names, institute-issued student identifiers, admission and enrolment dates, class/course/batch, academic status, guardian relationship, phone number, fee plan, balance, payment history, receipt details, attendance or other institute records. The institute should collect only information reasonably needed for its educational and administrative purposes, check it for accuracy and restrict staff access by role.
CampusKaro does not sell identifiable student or guardian records and does not use their phone numbers to advertise CampusKaro. The institute remains the primary contact for questions about why a student record was collected or how it is used there; CampusKaro will assist with relevant platform requests as appropriate.
CampusKaro does not sell identifiable student or guardian records and does not use their phone numbers to advertise CampusKaro. The institute remains the primary contact for questions about why a student record was collected or how it is used there; CampusKaro will assist with relevant platform requests as appropriate.
05
Children’s Information
The platform may be used by institutions serving children. The institute must determine what notice, parental/guardian permission or other authority is required before entering a child’s personal information, and use it for its legitimate institute purpose. Avoid placing sensitive details in free-text notes or uploading documents unnecessary for the workflow.
The school and coaching workspace is intended for authorised adult institute personnel, not for children to create independent accounts. We do not knowingly use children’s records for behavioural advertising or unrelated profiling. If you believe a child’s information was entered without authority, contact the institute and our privacy contact so it can be reviewed.
The school and coaching workspace is intended for authorised adult institute personnel, not for children to create independent accounts. We do not knowingly use children’s records for behavioural advertising or unrelated profiling. If you believe a child’s information was entered without authority, contact the institute and our privacy contact so it can be reviewed.
06
Photographs and Documents
An institute may upload a student photograph or supporting document where a feature allows it. Material is displayed to authorised users for the institute workflow for which it was provided. It is not intended for public promotion, facial recognition, biometric identification or unrelated profiling. The institute should confirm its authority to upload it, limit access and remove it when no longer needed, subject to recordkeeping obligations.
07
Teacher and Staff Records
Teacher and staff profiles may include name, contact and employment details, joining date, role, salary arrangements, payment history and generated salary receipts. The institute controls those records and must give staff appropriate notice, verify entries and limit access to authorised personnel. Salary entries and receipts show information recorded in the workspace; they do not independently confirm a bank transfer or employment entitlement.
08
Fees, Payments and Receipts
The workspace can store fee schedules, student dues, collections, payment methods, dates, references, collector details and receipt numbers, as well as teacher salary payments. These entries are supplied or confirmed by institute users. A platform receipt records the transaction details entered; it is not a bank statement, settlement confirmation or independent audit of cash received. Institutes should reconcile records against their own books and payment sources.
CampusKaro subscription billing is separate from fees an institute records for students. When a processor is used for a CampusKaro plan, it receives information needed to complete and reconcile that transaction and handles payment credentials under its own terms and privacy information.
CampusKaro subscription billing is separate from fees an institute records for students. When a processor is used for a CampusKaro plan, it receives information needed to complete and reconcile that transaction and handles payment credentials under its own terms and privacy information.
09
How We Use Information
- To create and administer institute accounts, authenticate authorised users and provide enabled school or coaching workflows.
- To store and display institute records, calculate balances from configured data, generate receipts and reports, and apply role and organisation access.
- To process subscriptions, show plan status and history, handle billing questions and investigate suspected misuse or fraud.
- To provide support, diagnose errors, maintain service reliability, protect accounts and improve features using operational information.
- To send essential account, verification, security, billing, subscription and service-change notices to institute owners/admins.
- To comply with applicable law, enforce agreements, respond to lawful requests and establish or defend legal claims.
10
Institute-Directed Messages
If an authorised institute user chooses to send a fee reminder or other institute notice, the selected recipient’s phone number and message content may be passed to the configured communication provider. The institute chooses the recipient, purpose and message and is responsible for authority to send it, number accuracy, appropriate wording, consent/objection handling and compliance with telecom and other rules. Delivery depends on the provider and recipient network; a displayed delivery status does not guarantee a message was read.
Institute contact lists are used for institute-directed workflows. CampusKaro does not repurpose parent or guardian lists for its own promotions.
Institute contact lists are used for institute-directed workflows. CampusKaro does not repurpose parent or guardian lists for its own promotions.
11
CampusKaro Communications
We may send necessary service communications to the owner or administrator about sign-in, verification, security, subscription, billing, outages, material product changes and support. These operational messages may continue while the account or related obligation is active.
Optional CampusKaro offers are separate from service notices. A phone number supplied for account verification, or acceptance of this policy or Terms, is not by itself permission for promotions. We will send promotions only where a separate, voluntary and recorded choice is available and applicable preferences and law permit it. A recipient may withdraw that choice; withdrawal does not stop necessary service notices. This policy does not represent that an optional marketing programme is currently enabled.
Optional CampusKaro offers are separate from service notices. A phone number supplied for account verification, or acceptance of this policy or Terms, is not by itself permission for promotions. We will send promotions only where a separate, voluntary and recorded choice is available and applicable preferences and law permit it. A recipient may withdraw that choice; withdrawal does not stop necessary service notices. This policy does not represent that an optional marketing programme is currently enabled.
12
Sharing and Disclosure
We do not sell identifiable student, guardian, teacher or institute-user information. Information may be disclosed as needed to: (a) providers that host, store, secure or support the service; (b) a payment or communication provider when its feature is used; (c) the institute and authorised workspace users; (d) professional advisers or a successor involved in a permitted business reorganisation, subject to appropriate safeguards; or (e) a public authority where legally required or permitted.
We limit disclosures to information reasonably relevant to the purpose. Aggregated or de-identified operational information may be used to understand service performance, provided it is not used to identify an individual. Workspace access is governed by account and organisation permissions; report access you believe is incorrect.
We limit disclosures to information reasonably relevant to the purpose. Aggregated or de-identified operational information may be used to understand service performance, provided it is not used to identify an individual. Workspace access is governed by account and organisation permissions; report access you believe is incorrect.
13
Providers process information under their service arrangements and may publish their own privacy terms. Their availability, delivery and processing are also subject to their systems and policies. Specific providers can change as the service evolves; material changes to data use will be reflected here where appropriate.
Service Providers
- Infrastructure, hosting, database, storage, backup, monitoring and security providers that help operate and protect the application.
- Email, SMS, WhatsApp or other communication providers when a related account or institute messaging feature is enabled and used.
- Payment processors for CampusKaro subscriptions when online payment is enabled; they are not automatically processors of institute-collected student fees.
- Support, professional or operational providers where access is needed to resolve a request or maintain the service.
Providers process information under their service arrangements and may publish their own privacy terms. Their availability, delivery and processing are also subject to their systems and policies. Specific providers can change as the service evolves; material changes to data use will be reflected here where appropriate.
14
Security Safeguards
We use safeguards intended to reduce the risk of unauthorised access, disclosure, alteration or loss. Depending on the deployed feature and environment, these may include protected authentication credentials, session controls, role-based access, organisation scoping, rate limits, security logging, restricted operational access and backup practices.
Security depends on correct configuration and safe use. No website, database, transmission or storage system can be guaranteed completely secure. Institutes should use unique passwords, promptly remove former staff, protect devices, avoid shared accounts and report suspected compromise. We do not claim a certification unless separately identified and verifiable.
Security depends on correct configuration and safe use. No website, database, transmission or storage system can be guaranteed completely secure. Institutes should use unique passwords, promptly remove former staff, protect devices, avoid shared accounts and report suspected compromise. We do not claim a certification unless separately identified and verifiable.
15
Retention and Backups
We keep information for the period reasonably needed to provide the service, administer accounts and subscriptions, maintain security and audit records, resolve disputes and meet legal, tax or accounting duties. The period depends on record type, account status, institute instructions and applicable obligations; this policy does not set one universal deletion date.
On account closure or a deletion request, we act under the service terms and law. Some records may be retained for legal claims, security, financial reconciliation or statutory recordkeeping. Information removed from active systems may persist for a limited period in protected backups and is removed through the ordinary backup lifecycle.
On account closure or a deletion request, we act under the service terms and law. Some records may be retained for legal claims, security, financial reconciliation or statutory recordkeeping. Information removed from active systems may persist for a limited period in protected backups and is removed through the ordinary backup lifecycle.
16
Access, Correction and Requests
Account owners can review and correct many workspace records using dashboard features. A student, guardian, teacher or staff member with a question about an institute record should normally contact that institute first, because it controls the purpose and content. The institute may ask CampusKaro to help locate, correct, export or delete records within the platform.
For information CampusKaro handles for account administration, security, billing or support, contact us below. We may verify identity and authority before responding. We will handle requests within the time and limits required by applicable law; some information may be retained or access limited where a legal exception applies. Nothing here reduces a right available under law.
For information CampusKaro handles for account administration, security, billing or support, contact us below. We may verify identity and authority before responding. We will handle requests within the time and limits required by applicable law; some information may be retained or access limited where a legal exception applies. Nothing here reduces a right available under law.
17
Cookies and Device Data
Sign-in uses essential session cookies to keep authorised users signed in and protect account flows. These cookies are not designed to deliver advertising. Browser and request information may also be processed for security, troubleshooting and service operation. Cookie availability and names can vary by environment and may change with the authentication system.
This policy does not claim optional analytics or advertising cookies are in use. If non-essential tracking or analytics is introduced, we will update this disclosure and provide any choice or notice required by law. Disabling essential cookies may prevent sign-in or core features from working.
This policy does not claim optional analytics or advertising cookies are in use. If non-essential tracking or analytics is introduced, we will update this disclosure and provide any choice or notice required by law. Disabling essential cookies may prevent sign-in or core features from working.
18
Account Closure and Data Export
An institute owner may request account closure or an available export through support. We may verify the requester controls the account and ask which records or format are needed. Export options depend on features and account status; closure is not automatic, immediate erasure of every legal or accounting record.
Before closing an account, the institute should export records it needs, reconcile fee and salary ledgers, retain receipts required for its obligations and remove access for staff who no longer need it. We then restrict or remove access as appropriate and retain or delete information under the rules above and applicable agreement.
Before closing an account, the institute should export records it needs, reconcile fee and salary ledgers, retain receipts required for its obligations and remove access for staff who no longer need it. We then restrict or remove access as appropriate and retain or delete information under the rules above and applicable agreement.
19
Incident Handling
If we become aware of a security incident affecting information processed through the service, we will assess and respond under applicable procedures and law. Where required, we will notify the relevant institute, affected persons or authority within the applicable time and provide information reasonably available to support mitigation. Not every service interruption or unsuccessful attack is a reportable personal-data breach.
Institutes should promptly contact support if they suspect account compromise, data exposure or a misdirected message. Include the affected workspace and approximate time; do not include passwords, one-time codes or unnecessary sensitive records in ordinary email.
Institutes should promptly contact support if they suspect account compromise, data exposure or a misdirected message. Include the affected workspace and approximate time; do not include passwords, one-time codes or unnecessary sensitive records in ordinary email.
20
Policy Changes and Contact
We may revise this policy when the service, providers, data practices or applicable requirements change. The current text and update date will appear here. If a change materially affects information handling, we will provide notice through the service or another appropriate channel where required. Continued use does not remove a notice or consent requirement imposed by law.
For privacy questions, requests or incident reports, contact info@campuskaro.in or use our contact page. Identify the institute and your authority to act, but do not send passwords or more personal information than needed.
For privacy questions, requests or incident reports, contact info@campuskaro.in or use our contact page. Identify the institute and your authority to act, but do not send passwords or more personal information than needed.
21
Provider Identity
CampusKaro is the product name and website brand. The legal person or entity providing a paid service should be identified in the applicable registration confirmation, order or invoice; the brand name alone does not represent that a company has been incorporated. The provider’s legal name and business/contact address should be completed in those documents before a paid service is offered. Contact info@campuskaro.in for privacy matters. If a statutory grievance or privacy contact is required for the operating model, its current details should be published here before launch.