Legal
Privacy Policy
Product: Nexus School ERP
Platform: Web Application, Android Application and iOS Application
Last Updated: January 1, 2026
Nexus School ERP ("Nexus School ERP", "Nexus ERP", "we", "us", or "our") is a comprehensive school management platform designed to help educational institutions manage academic, administrative, financial, communication, transportation, human resources, and other school-related operations through web and mobile applications.
This Privacy Policy explains how we collect, use, process, store, disclose, protect, and otherwise handle information when schools, administrators, teachers, staff, students, parents/guardians, transport personnel, accountants, management, and other authorized users ("Users") access or use Nexus School ERP through our website, web application, Android application, iOS application, APIs, integrations, or related services (collectively, the "Service").
By using Nexus School ERP, you acknowledge that you have read and understood this Privacy Policy.
1. Scope of This Privacy Policy
This Privacy Policy applies to information processed through:
Nexus School ERP web applications
Nexus School ERP Android applications
Nexus School ERP iOS applications
School administration portals
Teacher and staff portals
Student and parent portals
Mobile applications
APIs and integrations
Payment gateway integrations
Communication and notification services
School websites or portals integrated with Nexus School ERP
Customer support and service channels
Other services directly operated by Nexus ERP
This Privacy Policy does not apply to third-party websites, applications, payment providers, social media platforms, or other services that are independently operated by third parties.
2. Our Role in Processing Personal Data
Nexus School ERP may process information on behalf of schools and educational institutions using the platform.
Depending on the circumstances, Nexus ERP may act as:
A service provider or data processor for schools and educational institutions;
A controller or independent data handler for certain account, billing, security, technical, and operational information; or
A service provider processing information according to instructions from an authorized school or institution.
Schools and educational institutions are generally responsible for determining what student, parent, teacher, staff, and other information is collected through their use of Nexus School ERP and how that information is used.
If you are a student, parent, teacher, employee, or other user of a school that uses Nexus School ERP, your school may be the primary organization responsible for your personal information. Questions about school-specific data practices may therefore need to be directed to your school.
3. Information We Collect
We collect information necessary to provide, secure, operate, maintain, and improve Nexus School ERP.
The type of information collected depends on the features enabled by the school.
3.1 Account and User Information
We may collect:
Full name
Username
Email address
Mobile/telephone number
Profile photograph
Date of birth
Gender where required by the institution
User role
Employee/student/parent identification number
School identification information
Department
Designation
Class and section
Academic session
Address
Emergency contact information
Login credentials
Account preferences
Communication preferences
Passwords are intended to be stored using appropriate security mechanisms rather than in plain text.
4. Student Information
Depending on the modules activated by a school, Nexus School ERP may process student-related information including:
Student name
Admission number
Roll number
Date of birth
Gender
Photograph
Class
Section
Academic session
House information
Student identification information
Parent/guardian details
Contact information
Address
Admission information
Previous school information
Academic history
Attendance records
Examination records
Marks
Grades
Assignments
Homework
Learning information
Certificates
Discipline records
Library transactions
Transport information
Fee information
Scholarship information
Communication history
Documents uploaded by the school or authorized users
Schools should only collect information that is necessary and appropriate for legitimate educational, administrative, legal, or operational purposes.
5. Parent and Guardian Information
The system may collect:
Parent/guardian name
Relationship with student
Mobile number
Email address
Address
Occupation
Emergency contact information
Login information
Communication preferences
Fee/payment information
Communication history
Student relationship information
Documents provided to the school
Parents and guardians may receive notifications regarding attendance, fees, examinations, homework, events, transport, announcements, and other school activities depending on the school's configuration.
6. Teacher and Staff Information
Nexus School ERP may process information relating to teachers and employees, including:
Name
Employee ID
Photograph
Contact information
Address
Date of joining
Department
Designation
Qualification
Experience
Attendance
Leave records
Payroll-related information where the payroll module is enabled
Performance-related information
Assigned classes and subjects
Timetable information
Work schedules
Documents
Training records
Login and access information
7. Academic and Learning Information
Depending on enabled modules, the platform may process:
Subjects
Classes
Sections
Timetables
Lesson plans
Homework
Assignments
Online learning information
Examination schedules
Examination results
Marks
Grades
Report cards
Rankings
Academic progress
Teacher comments
Student performance information
Access to academic information is controlled according to user roles and permissions configured by the school.
8. Attendance Information
Nexus School ERP may process:
Student attendance
Teacher attendance
Staff attendance
Date and time of attendance
Present/absent/late status
Leave information
Attendance remarks
Attendance reports
Attendance-related notifications
Where schools use biometric, RFID, QR-code, GPS, device-based, or other attendance technologies, additional information may be processed depending on the specific technology and configuration.
9. Fees and Financial Information
The platform may support school fee management, including:
Fee structures
Tuition fees
Admission fees
Examination fees
Transport fees
Hostel fees
Other school charges
Discounts
Scholarships
Concessions
Outstanding balances
Receipts
Payment status
Refund information
Transaction references
Invoice information
Financial reports
Nexus ERP generally does not need to directly store complete payment card information when payment processing is performed by a third-party payment gateway.
10. Payment Gateway Integration
Nexus School ERP may integrate with multiple third-party payment gateways and payment service providers.
Depending on the gateway selected by the school, users may be able to make payments using methods such as:
Credit cards
Debit cards
Net banking
UPI
Bank transfers
Digital wallets
Other payment methods supported by the payment provider
When a payment is initiated, the payment provider may independently collect and process payment information according to its own privacy policy and terms.
Nexus ERP may receive information such as:
Transaction ID
Payment reference number
Order ID
Amount
Currency
Payment status
Payment date and time
Gateway response
Refund status
Failure information
Nexus ERP does not intentionally request or store payment card PINs, CVVs, passwords, or other sensitive authentication information unless specifically required and legally permitted by an applicable payment integration.
Users should review the privacy policies and terms of the relevant payment provider before completing a transaction.
11. Transport and School Bus Information
Where the transport module is enabled, Nexus School ERP may process:
Student transport assignments
Bus routes
Stops
Driver information
Vehicle information
Transport staff information
Pickup and drop-off information
Route schedules
Transport attendance
GPS/location information
Vehicle tracking information
Emergency transport information
Parent transport notifications
Location information may only be collected where the relevant feature is enabled and appropriate authorization has been provided.
12. Library Information
The library module may process:
Library member information
Book records
Book issue and return history
Due dates
Fines
Reservations
Library transactions
Reading/activity records
13. Hostel Information
Where applicable, the hostel module may process:
Hostel allocation
Room information
Bed allocation
Hostel attendance
Visitor records
Warden information
Hostel fee information
Leave records
Emergency information
14. Examination and Assessment Information
The platform may process:
Examination schedules
Examination subjects
Marks
Grades
Internal assessments
Practical assessments
Assignments
Report cards
Academic performance
Teacher comments
Examination attendance
Result publication information
15. Communication Information
Nexus School ERP may support communication through:
Push notifications
Email
SMS
In-app notifications
WhatsApp or similar integrations where enabled
Announcements
Circulars
Notices
Messages
Parent-teacher communication
Event notifications
Emergency alerts
Communication content may be stored where necessary to provide the service, maintain records, prevent abuse, or comply with legal requirements.
16. Documents and Files
Users or schools may upload documents such as:
Student documents
Identification documents
Certificates
Admission forms
Employee documents
School documents
Academic documents
Fee documents
Medical or emergency documents where enabled by the institution
Other documents required for school administration
Schools are responsible for determining whether a document should be collected and who should have access to it.
17. Location Information
Certain features may require location information, including:
School transportation
Bus tracking
Driver applications
Attendance verification
Location-based school services
Security features
School operations
Location access may be collected only when the relevant feature is enabled and the applicable device permissions are granted.
Users may generally control location permissions through their device settings.
Disabling location access may prevent certain features from functioning correctly.
18. Device Information
When using our web or mobile applications, we may collect technical information such as:
Device type
Device model
Operating system
Operating system version
Application version
Browser type
IP address
Device identifiers
Network information
Language settings
Time zone
Crash information
Performance information
This information may be used for security, troubleshooting, compatibility, analytics, and service improvement.
19. Usage and Log Information
We may automatically collect:
Login date and time
Logout date and time
Pages or screens accessed
Features used
Search activity
Error logs
Security events
Session information
IP address
Browser information
Application activity
Interaction information
This information helps us maintain reliable and secure services.
20. Cookies and Similar Technologies
Nexus School ERP may use cookies, local storage, session technologies, pixels, SDKs, and similar technologies.
These technologies may be used for:
Authentication
Maintaining login sessions
Security
Remembering preferences
Performance monitoring
Analytics
Troubleshooting
Improving user experience
Users may control certain cookies through browser settings. Disabling essential cookies may affect the functionality of the Service.
21. Mobile Application Permissions
Depending on the application and enabled functionality, the Android and iOS applications may request permissions for:
Internet/network access
Notifications
Camera
Photo/library access
Files/storage
Location
Microphone where required for an enabled feature
Calendar where required for an enabled feature
Other permissions required for specific functionality
Permissions are requested according to the requirements of the relevant feature.
Users can manage permissions through their device settings.
22. How We Use Information
We may use information to:
Create and manage accounts.
Provide Nexus School ERP services.
Manage schools and educational institutions.
Manage students, parents, teachers, and staff.
Process attendance.
Manage examinations and academic records.
Manage fees and payments.
Generate invoices and receipts.
Support payment gateway transactions.
Manage transportation.
Manage libraries.
Manage hostels.
Manage employee and HR information.
Send school communications.
Provide notifications.
Provide customer support.
Diagnose technical problems.
Detect and prevent fraud.
Protect accounts and systems.
Monitor security.
Improve application performance.
Develop and improve features.
Conduct analytics.
Maintain backups.
Meet contractual obligations.
Comply with applicable laws and regulations.
Respond to lawful requests from authorities.
Protect the rights, safety, and property of Nexus ERP, schools, users, and others.
23. Legal Bases for Processing
Where applicable law requires a legal basis for processing personal information, Nexus ERP may process information based on one or more of the following:
Performance of a contract
Compliance with legal obligations
Legitimate interests
Consent
Protection of vital interests
Instructions from an educational institution
Other lawful bases permitted by applicable law
The applicable legal basis may vary depending on the type of information and the purpose of processing.
24. Children's and Student Data
Nexus School ERP is designed to support educational institutions and may therefore process information relating to students who are minors.
Nexus ERP does not intend to use student information for unrelated commercial purposes.
Schools and educational institutions are responsible for ensuring that they have the appropriate authority, notices, permissions, parental/guardian consent where required, and lawful basis for collecting and providing student information to Nexus ERP.
We take reasonable measures to protect student information and restrict access according to authorized roles.
We do not knowingly sell children's personal information.
Where applicable law provides additional protections for children's information, Nexus ERP will take reasonable steps to comply with those requirements.
25. Sensitive Personal Information
Depending on the features enabled by a school, the Service may process information that could be considered sensitive or specially protected under applicable laws.
Examples may include:
Government identification information
Financial information
Student records
Health or emergency information
Biometric information where supported by an authorized integration
Precise location information
Information concerning minors
Such information should only be collected and processed where there is an appropriate legal, educational, administrative, or operational purpose.
Schools are responsible for configuring access controls appropriately.
26. Health and Medical Information
If the school chooses to maintain health, medical, emergency, disability, allergy, medication, or similar records within Nexus School ERP, such information may be processed on behalf of the school.
Access should be limited to authorized personnel who have a legitimate need to access such information.
Nexus ERP does not independently determine a student's medical treatment or provide medical advice.
27. Biometric Information
Certain schools may use third-party biometric attendance or identification systems.
Where biometric information is integrated with Nexus School ERP:
Processing may depend on the third-party system.
The school is responsible for determining whether biometric processing is lawful.
Appropriate notices and permissions should be obtained where required.
Access should be restricted to authorized personnel.
Biometric information should not be used for unrelated purposes.
Nexus ERP does not require biometric information unless the relevant feature or integration is specifically enabled.
28. How We Share Information
We may share information with:
Schools and Authorized Institutions
Information may be made available to the school or institution that manages the relevant account.
Service Providers
We may use third-party providers for:
Cloud hosting
Database services
Backup
Email
SMS
Push notifications
Payment processing
Analytics
Customer support
Security
Authentication
Maps
Transportation services
File storage
Communication integrations
Software infrastructure
Service providers are expected to process information according to applicable contractual and legal requirements.
Legal Authorities
Information may be disclosed when reasonably necessary to:
Comply with applicable law
Respond to legal processes
Respond to government requests
Protect rights and safety
Investigate fraud or abuse
Enforce agreements
Protect the security of the Service
Business Transfers
If Nexus ERP undergoes a merger, acquisition, restructuring, financing, sale of assets, or similar transaction, personal information may be transferred as part of that transaction, subject to applicable legal requirements.
29. Third-Party Integrations
Nexus School ERP may integrate with third-party services, including:
Payment gateways
SMS providers
Email providers
WhatsApp or communication providers
Cloud infrastructure
Google services
Apple services
Maps and location services
Analytics services
Biometric systems
Accounting systems
Learning platforms
Other school technology providers
Third-party services have their own privacy policies and terms.
Nexus ERP is not responsible for the privacy practices of independent third parties.
30. Payment Security
Payments may be processed through third-party payment gateways.
Where payment processing is outsourced to a payment provider:
Payment credentials may be collected directly by the payment provider.
Nexus ERP may receive transaction confirmation information.
Payment information may be subject to the provider's security and privacy policies.
Payment processing may be governed by applicable financial and payment regulations.
Users should never share OTPs, PINs, passwords, CVVs, or payment authentication credentials with Nexus ERP employees or school staff.
31. Data Security
We implement reasonable technical and organizational measures designed to protect information from unauthorized:
Access
Disclosure
Modification
Loss
Destruction
Misuse
Security measures may include:
Encryption in transit
Encryption or appropriate protection of stored data
Password protection
Role-based access control
Authentication controls
Access logging
Security monitoring
Backup systems
Infrastructure security
Application security
Vulnerability management
Incident response procedures
However, no internet-based system can be guaranteed to be completely secure.
32. Role-Based Access Control
Nexus School ERP may provide different access levels for:
Super administrators
School administrators
Management
Principals
Teachers
Staff
Accountants
Librarians
Transport managers
Drivers
Students
Parents/guardians
Other authorized users
Users should only receive access appropriate to their role.
Schools are responsible for configuring user permissions and promptly disabling accounts when users leave the institution or no longer require access.
33. Data Retention
We retain personal information only for as long as reasonably necessary for:
Providing the Service
Maintaining school records
Supporting contractual obligations
Security
Financial/accounting requirements
Legal obligations
Dispute resolution
Backup and disaster recovery
Legitimate business purposes
Retention periods may vary according to the type of information and the requirements of the school or applicable law.
When information is no longer required, it may be deleted, anonymized, aggregated, or securely disposed of, subject to applicable legal and backup requirements.
34. Data Backup
Nexus ERP may maintain backups to protect against:
Hardware failures
Cybersecurity incidents
Accidental deletion
System failures
Disaster events
Data corruption
Backup copies may remain for a limited period after information is deleted from active systems.
35. Data Storage and International Transfers
Nexus ERP may use cloud infrastructure and service providers located in different countries.
As a result, information may be processed or stored outside the country where the school or user is located.
Where applicable law requires safeguards for international data transfers, we seek to use appropriate legal and contractual safeguards.
36. Data Accuracy
We aim to maintain accurate and reliable information.
However, because schools, teachers, administrators, parents, students, and other authorized users may enter or modify information, the school and authorized users are responsible for ensuring that information entered into the system is accurate and current.
37. User Rights
Depending on applicable law, users may have rights including:
Right to access personal information
Right to correct inaccurate information
Right to request deletion
Right to restrict processing
Right to object to certain processing
Right to data portability
Right to withdraw consent where processing is based on consent
Right to lodge a complaint with a relevant data protection authority
Right to receive information about data processing
Some rights may be subject to legal limitations.
If your account is managed by a school, you may need to submit your request directly to the school.
38. Requesting Data Deletion
Users may request deletion of their personal information where permitted by applicable law.
Requests may be submitted to:
Email: support@ambastunity.org
For school-managed accounts, Nexus ERP may refer the request to the relevant school or institution.
Deletion may not be possible where information must be retained to:
Comply with legal requirements
Complete financial transactions
Resolve disputes
Prevent fraud
Maintain security
Fulfill contractual obligations
Maintain required educational records
39. Account Deactivation
Schools or authorized administrators may deactivate user accounts.
Deactivation generally prevents normal access to the account but does not necessarily result in immediate deletion of all associated information.
Certain information may continue to be retained according to the school's requirements, legal obligations, backup policies, or legitimate business purposes.
40. Marketing Communications
Nexus ERP may send service-related communications such as:
Security alerts
Account notifications
System updates
Payment notifications
Maintenance notifications
Support messages
Important service announcements
Where legally permitted and where appropriate consent is obtained, we may also send promotional communications.
Users may opt out of non-essential promotional communications.
Transactional and security-related communications may continue even after marketing preferences are changed.
41. Push Notifications
Mobile applications may use push notifications for:
Attendance alerts
Homework notifications
Examination notifications
Fee reminders
Payment confirmations
School announcements
Transport notifications
Emergency alerts
Account/security notifications
Users can manage notification permissions through Android or iOS device settings.
42. Analytics
We may use analytics and monitoring technologies to understand:
Application usage
Performance
Feature adoption
Errors
Crashes
User interactions
System performance
Analytics information may be aggregated or otherwise used to improve Nexus School ERP.
43. Artificial Intelligence and Automated Technologies
If AI-powered features are introduced into Nexus School ERP, information may be processed to provide features such as:
Automated assistance
Report generation
Data summarization
Educational recommendations
Administrative assistance
Communication assistance
Analytics
Support
AI features should not be used as the sole basis for making significant decisions about students, employees, or other individuals where prohibited by applicable law.
Schools remain responsible for reviewing important educational or administrative decisions.
44. Data Used for Product Improvement
We may use aggregated, anonymized, or de-identified information to:
Improve system performance
Develop new features
Identify trends
Understand product usage
Improve reliability
Conduct analytics
Detect technical problems
We will not intentionally use identifiable student information for unrelated product development purposes without an appropriate lawful basis or authorization.
45. Security Incident and Data Breach
If Nexus ERP becomes aware of a security incident involving personal information, we will take reasonable steps to:
Investigate the incident.
Contain and mitigate the incident.
Assess potential impact.
Implement corrective measures.
Notify affected customers or individuals where required by applicable law.
Notify relevant authorities where legally required.
46. User Responsibilities
Users are responsible for:
Keeping passwords confidential.
Using strong passwords.
Not sharing account credentials.
Logging out from shared devices.
Protecting mobile devices.
Providing accurate information.
Using the platform lawfully.
Accessing only information they are authorized to access.
Reporting suspected security incidents.
Not attempting to bypass access controls.
Schools are responsible for managing user roles and permissions appropriately.
47. School Administrator Responsibilities
Schools using Nexus School ERP should:
Collect information lawfully.
Provide appropriate privacy notices to users.
Obtain consent where legally required.
Maintain accurate records.
Configure role-based access correctly.
Protect administrator credentials.
Remove inactive users.
Handle student and parent requests appropriately.
Follow applicable education and privacy laws.
Avoid collecting unnecessary information.
Ensure that third-party integrations are appropriately authorized.
48. Children's Privacy Responsibilities of Schools
Because schools may use Nexus School ERP for children and minors, schools should ensure:
Appropriate parental/guardian notices where required.
Appropriate consent where legally required.
Collection of only necessary information.
Appropriate access restrictions.
Appropriate retention periods.
Compliance with applicable child-protection and education laws.
Nexus ERP does not knowingly sell or rent children's personal information.
49. Third-Party Websites and Services
Nexus School ERP may contain links or integrations to third-party websites and services.
Examples may include:
Payment gateways
Government portals
Maps
Communication platforms
Learning platforms
Social media services
Cloud services
When users leave Nexus School ERP or interact with an external service, the third party's privacy policy applies.
50. International Users
Nexus School ERP may be used by schools and organizations in different countries.
We aim to operate the Service in accordance with applicable privacy and data protection requirements, which may include, where applicable:
General data protection principles
Data security requirements
Children's privacy requirements
Data access and deletion rights
Cross-border transfer requirements
Electronic communications requirements
Applicable local education and privacy regulations
Where local law provides stronger privacy protections, those requirements may apply.
51. GDPR-Related Rights
For individuals protected by the European Union or European Economic Area data protection framework, applicable rights may include:
Access
Rectification
Erasure
Restriction
Objection
Data portability
Withdrawal of consent
Rights relating to automated decision-making, where applicable
Where Nexus ERP processes information on behalf of a school, the school may be the relevant data controller and may handle requests from individuals.
52. California and Other U.S. Privacy Rights
Where applicable U.S. privacy laws provide specific rights, eligible individuals may have rights regarding:
Access to personal information
Correction
Deletion
Opt-out of certain processing
Information about data collection and disclosure
Non-discrimination for exercising privacy rights
The availability of these rights depends on the applicable law and the user's circumstances.
53. India and Other Applicable Jurisdictions
Where Nexus ERP operates in India, we seek to comply with applicable Indian privacy, information technology, data protection, and cybersecurity requirements as applicable to the Service and the parties using it.
Similar compliance principles may apply in other countries where the Service is offered.
Because privacy laws may change over time, this Privacy Policy may be updated to reflect legal and regulatory developments.
54. Corporate and School Accounts
When an organization or school creates an account, administrators may have access to information associated with users under that organization's account.
For example, a school administrator may be able to:
Create user accounts
View student information
View attendance
View academic records
Manage fees
Manage employees
Configure permissions
Access reports
Disable accounts
Users should contact their school or organization's administrator regarding organization-controlled information.
55. Employee and Staff Privacy
Information relating to school employees and staff may be processed for legitimate employment and school administration purposes.
This may include:
Recruitment
Employee records
Attendance
Leave
Payroll
Performance
Scheduling
Communication
Compliance
The school remains responsible for ensuring that employee information is processed lawfully.
56. Fraud Prevention and Abuse
We may process information to detect and prevent:
Unauthorized access
Account takeover
Fraudulent payments
Payment abuse
Suspicious activity
Cyberattacks
Data misuse
Unauthorized scraping
Attempts to bypass security
Other violations of our terms
We may suspend or terminate accounts where necessary to protect users or the Service.
57. Children's Data Is Not Sold
Nexus ERP does not intentionally sell student or children's personal information.
We may provide information to service providers necessary to operate the platform, including hosting, communication, payment, security, analytics, and other infrastructure providers.
Such processing is intended to support the Service and is subject to applicable contractual and legal requirements.
58. Changes to This Privacy Policy
We may update this Privacy Policy from time to time.
Changes may be made due to:
New features
New integrations
Changes in law
Security improvements
Business changes
Regulatory requirements
Changes in data processing practices
When we make material changes, we may provide notice through the Service, website, email, or other appropriate methods.
The "Last Updated" date at the beginning of this Privacy Policy indicates when the policy was most recently revised.
59. Contact Us
If you have questions, concerns, requests, or complaints regarding this Privacy Policy or the processing of personal information, please contact:
Nexus ERP
Product: Nexus School ERP
Privacy Contact: [Privacy Officer / Data Protection Contact]
Email: info@ambastunity.org
Support Email: support@ambastunity.org
Website: nexus.ambastunity.org
Registered Address: Delhi
Country: India
For school-managed accounts, users may also contact their school or educational institution.
60. Consent and Acknowledgement
By using Nexus School ERP, users acknowledge that they have reviewed this Privacy Policy.
Where applicable law requires consent for specific processing activities, appropriate consent mechanisms may be provided separately.
This Privacy Policy should be read together with the applicable:
Terms and Conditions
Cookie Policy
Data Processing Agreement
Acceptable Use Policy
Payment Terms
Service Agreement
School-specific privacy notices
61. Important Notice for Schools
Nexus ERP provides technology infrastructure to help schools manage their operations. Schools remain responsible for:
Determining what personal information they collect.
Determining why information is collected.
Obtaining required permissions and consents.
Providing required notices.
Configuring user access.
Maintaining accurate information.
Complying with education and privacy laws.
Responding to data subject requests where legally required.
Determining appropriate retention periods.
Managing third-party integrations.
Nexus ERP will process information according to the applicable service agreement, instructions from the school, and applicable law.
62. Complete Module Coverage
Nexus School ERP may provide or support modules including, but not limited to:
School Administration
School profile
Branch management
Academic sessions
Classes
Sections
Houses
Departments
User management
Role and permission management
Student Management
Online admission
Student registration
Student profiles
Student documents
Student ID cards
Parent/guardian management
Student history
Student transfer
Student promotion
Alumni management
Academic Management
Subjects
Curriculum
Timetable
Lesson planning
Homework
Assignments
Study materials
Academic calendar
Academic progress
Attendance
Student attendance
Teacher attendance
Staff attendance
Leave management
Biometric integration
QR attendance
Attendance reports
Parent attendance alerts
Examination
Examination planning
Exam schedules
Marks entry
Grades
Assessments
Report cards
Result publishing
Performance reports
Fees and Finance
Fee structure
Online fee collection
Multiple payment gateways
UPI
Cards
Net banking
Wallets where supported
Invoices
Receipts
Discounts
Scholarships
Concessions
Refunds
Outstanding fees
Payment reminders
Financial reports
Human Resources
Employee management
Staff profiles
Attendance
Leave
Payroll where enabled
Departments
Designations
Employee documents
Performance management
Transport
Bus management
Driver management
Route management
Stop management
Student allocation
GPS tracking
Transport attendance
Parent alerts
Library
Book management
Issue and return
Reservations
Fines
Library members
Reports
Hostel
Hostel management
Rooms
Beds
Student allocation
Hostel attendance
Visitor management
Hostel fees
Communication
SMS
Email
Push notifications
In-app notifications
Announcements
Circulars
Notices
Parent-teacher communication
Emergency notifications
WhatsApp or other communication integrations where supported
Parent Portal
Student profile
Attendance
Homework
Assignments
Examination results
Timetable
Fee payments
Receipts
Notices
Events
Transport information
Teacher Portal
Attendance
Timetable
Homework
Assignments
Marks
Examination
Student information
Communication
Leave
Reports
Student Portal
Academic information
Timetable
Homework
Assignments
Attendance
Examination
Results
Study materials
Notices
Mobile Applications
Android application
iOS application
Push notifications
Role-based mobile access
Parent application
Teacher/staff application
Student application
Admin application
Driver/transport application where enabled
Reporting and Analytics
Student reports
Attendance reports
Academic reports
Examination reports
Fee reports
Collection reports
Staff reports
Transport reports
Management dashboards
Operational analytics
Integrations
Payment gateways
SMS providers
Email providers
Push notification services
Maps and location services
Cloud storage
Accounting systems
Biometric systems
Communication platforms
APIs
Third-party educational services
The availability of individual modules and integrations depends on the subscription, school configuration, geographic availability, technical compatibility, and applicable agreements.
63. Final Statement
Nexus ERP is committed to protecting the privacy and security of the information entrusted to Nexus School ERP.
We aim to provide schools with a secure, reliable, and transparent technology platform while respecting the privacy rights of students, parents, teachers, staff, administrators, and other users.
For privacy-related questions or requests, please contact the Nexus ERP privacy team using the contact information provided above.
© 2026 Nexus ERP. All Rights Reserved.