1. Scope and roles
This policy applies to EduSaarthi websites, applications, support channels, and implementation services operated by Alethron Solution.
For records entered by a subscribing school, the school generally decides why and how the information is used. Alethron Solution processes that information to provide the configured ERP services and follows the school's authorized instructions, applicable agreements, and law.
2. Information we process
- School, branch, session, plan, billing, and implementation details.
- Account and profile information for administrators, staff, teachers, students, parents, and other authorized users.
- Student, guardian, academic, attendance, fee, transport, hostel, library, examination, payroll, and communication records where the relevant modules are enabled.
- Support requests, form submissions, configuration choices, and communication history.
- Device, browser, sign-in, session, security, audit, and diagnostic information needed to operate and protect the service.
3. Why information is used
- Provide, configure, secure, maintain, and improve the subscribed services.
- Authenticate users, enforce permissions, isolate school workspaces, and investigate suspicious activity.
- Generate school-authorized documents, reports, notifications, receipts, and operational records.
- Provide implementation, training, billing, support, backup, recovery, and service communications.
- Meet contractual, legal, accounting, security, and compliance obligations.
4. Student and child data
Schools must collect and use student information with the notices, permissions, and safeguards required for their institution. Parent or guardian requests about a child's school record should normally be submitted to the school, which can verify the requester and the relevant student relationship.
EduSaarthi does not ask children to create public marketing accounts. Student access is provisioned within an authorized school workspace.
6. Retention and deletion
Retention depends on the school agreement, enabled modules, legal obligations, backup schedules, and the type of record. Schools should define their own academic, financial, employment, and student-record retention periods.
When a subscription ends, export and deletion are handled under the applicable order, agreement, and verified school instructions. Security logs and backup copies may remain for a limited period before scheduled deletion.
7. Security
EduSaarthi supports role-based access, tenant context checks, private-file controls, audit trails, session controls, and backup safeguards where configured. No system can guarantee absolute security, so schools must also protect credentials, review access, and promptly report suspected misuse.
8. Requests and choices
Users may request access, correction, deletion, withdrawal of consent where applicable, or grievance support. Requests concerning school-managed records should first go to the relevant school. We may require identity and authority verification before acting on a request.
9. Contact and updates
Questions or privacy requests can be sent to the support contact shown on the EduSaarthi website. We may update this policy as the service, providers, or legal requirements change. The latest effective date will always appear at the top of this page.
Questions about this policy?
Contact amitedge69@gmail.com. Requests involving school-managed records may be referred to the relevant institution for identity and authority checks.