Privacy Policy

1. Scope and developer

This Privacy Policy applies to RPPS Teacher ERP (package com.samvarg.rpps.teacher) and RPPS Parent Portal (package com.samvarg.rpps.parent), their related web portals, and the school ERP services used by those applications.

The applications are provided by Samvarg Solutions, India, as a technology service provider to participating schools. Privacy and security questions may be sent to samvargsolutions@gmail.com.

2. School control and tenant isolation

Each participating school or school group determines why its school records are maintained, who may use them, and how long they are required. Samvarg Solutions processes those records to operate the ERP on the school's instructions and under the applicable service arrangement.

As between the school and Samvarg Solutions, the school retains control of and responsibility for its respective school records. Samvarg Solutions does not claim ownership of a school's student, guardian, teacher, staff, academic, fee, document, or operational records.

Every school is assigned a separate tenant identity. Backend requests are scoped by school, user role, branch access, permissions, and record ownership. Users from one school are not permitted to view another school's student, guardian, teacher, attendance, fee, document, or operational records.

3. Information processed

Account and authentication information may include school code, username, employee code, admission number, role, permissions, account status, password verifier, login/session tokens, and sign-in timestamps.

Student information may include name, photograph, admission and roll details, class and section, admission date, date of birth, gender, phone number, address, category, nationality, house, blood group, height, weight, school UID/reference fields, attendance, timetable, leave, homework, classwork, assignments, conduct, marks, results, report cards, answer sheets, transport information, fee records, and documents supplied to the school.

Parent and guardian information may include names, relationship to the student, phone number, address or other contact details, qualifications, school UID/reference fields, linked children, and permissions granted for the linked child.

Teacher and staff information may include name, photograph, employee code, contact details, address, staff type, department, designation, qualification, joining date, assigned classes and subjects, timetable, attendance activity, leave, uploaded work or documents, marks, answer sheets, notices, and actions performed in the ERP.

Files may include authorized photographs, PDFs, admission or staff documents, answer sheets, homework, classwork, assignment attachments, and other school records uploaded by an authorized user.

Technical and security information may include IP address, request time, browser or Android runtime information, server and security logs, error details, school and branch context, audit events, and record-change metadata required to operate, secure, and troubleshoot the service.

4. Sources of information

Information is supplied by the school, its authorized administrators or staff, parents or guardians, students where enabled, and actions performed by authenticated users. The applications do not obtain school records from advertising networks or data brokers.

5. Why information is used

Information is used to authenticate users; provide role-appropriate school records; operate attendance, timetable, academic work, notices, leave, results, answer sheets, fees, reports, documents, and related school workflows; maintain auditability; prevent misuse; troubleshoot failures; back up records; and support the school.

School information is not used for behavioral advertising, third-party marketing, unrelated profiling, or sale. The current applications contain no advertising SDK, advertising identifier use, or third-party analytics SDK configured by Samvarg Solutions.

6. Sharing and service providers

We do not sell, rent, trade, or disclose school data to advertisers, data brokers, unrelated businesses, or other schools.

Within a school, records are available only to authenticated users whose role and permissions require access, such as administrators, authorized staff, teachers, parents, guardians, or students.

Limited infrastructure providers, including hosting, network, domain, backup, security, and application-distribution providers, may process only the technical or school data needed to deliver and protect the service. For example, the production ERP is hosted on infrastructure supplied by Hostinger, and Android distribution may be provided through Google Play. These providers are not authorized by Samvarg Solutions to use school records for advertising or unrelated marketing.

Information may also be disclosed when required by applicable law, a valid legal process, or when reasonably necessary to protect users, schools, the platform, or others from security threats or unlawful activity.

7. Children and student records

The service processes student information because it is an authorized school administration system. The Parent Portal is intended for parents, guardians, and authorized family accounts. Student access is enabled only where a school chooses to provide it.

The applications are not child-directed entertainment or social networking services. They do not display advertisements, perform behavioral advertising, or intentionally track children for commercial profiling.

Schools are responsible for providing required notices and obtaining any authorization or consent required for the student and guardian information they enter or instruct Samvarg Solutions to process.

8. Device access and local storage

The current Android wrappers require internet access. They do not request precise location, contacts, SMS, call logs, microphone, advertising ID, or broad device-storage permissions.

The portals store the verified school code, authentication tokens, and limited account or school context in application/browser storage so that the user can remain signed in and return to the correct school. Logout clears ERP authentication and account/session data while the remembered school code may remain until the user selects Change School or clears the app's data.

The service worker caches only public static interface files needed to load the app shell. Private API responses, media, student records, staff records, fee records, and uploaded documents are not intentionally stored in the offline cache.

9. Security safeguards

The live service uses HTTPS in transit, authenticated API access, expiring access tokens, refresh-token rotation and revocation, login throttling, school and role scoping, branch and staff permissions, private-file authorization, restricted cross-origin access, audit records, and server firewall controls.

Access credentials should be kept confidential and devices should be protected with a screen lock. Users should report a lost device, suspected account compromise, or incorrect access to their school immediately.

No online service can guarantee absolute security. Samvarg Solutions maintains reasonable technical and organizational safeguards and reviews protections as the platform changes.

10. Retention, backups, and deletion

Active school records are retained for the period required by the school for academic, administrative, legal, audit, and operational purposes. Samvarg Solutions does not use one fixed retention period for every record because schools and record categories have different requirements.

When the school instructs Samvarg Solutions to correct, deactivate, export, or delete an eligible record, the request is processed subject to identity verification, applicable law, legitimate school recordkeeping requirements, security logs, and technical backup cycles. Deleted production data may remain in protected backups until those backups expire or are safely overwritten and is not restored for ordinary use.

Account logout does not delete school records. Removing the application from a device removes local app data according to the device platform but does not delete records maintained by the school.

11. Access, correction, and deletion requests

Parents, guardians, students, teachers, and staff should first contact the relevant school administration to request access, correction, account deactivation, export, or deletion because the school controls the underlying education and employment records.

Platform privacy or security inquiries may be sent to samvargsolutions@gmail.com. Include the school name and a description of the request, but do not email passwords or unnecessary identity documents. We may ask the school to verify the request before changing protected records.

12. Fees and payments

The ERP may display fee structures, dues, offline collection entries, receipts, and manual payment records entered by authorized school personnel.

The current Teacher and Parent applications do not operate a bank account, wallet, lending service, investment service, cryptocurrency service, gambling service, or online payment gateway, and they do not collect payment-card or UPI PIN credentials.

13. Policy changes

This policy may be updated when the applications, service providers, legal requirements, or school workflows change. The current version will remain available at this public URL and will show its effective date.