This Privacy Policy applies to the mobile application School Management, package name com.schoolexammanagement, published on Google Play by Mohamad Nezam for Al-Mohsinia School.
This policy explains how Mohamad Nezam and Al-Mohsinia School collect, use, store, share, and protect information through the School Management application and related services.
1. Scope
This policy covers students, including minors, parents or guardians acting for students, teachers, administrators, and authorized support personnel. Access to the application is role-based.
2. Information We Collect
Student information
- Name, email address, phone number, school identifier, grade, class group, academic year, and semester.
- Account-linking status, registration codes, assigned subjects, and examinations.
- Exam attempts, answers, submission times, grades, results, and imported Excel assessment records.
- Calculated percentages, weighted results, trends, comparisons, strengths, weaknesses, growth indicators, and risk indicators.
- Notification history and exam reminder delivery status.
Teacher and administrator information
- Name, username, email address, phone number, role, and account status.
- Subject, grade, and class-group assignments.
- Questions, examinations, academic materials, imports, and administrative actions.
Account and security information
- Usernames, password hashes, registration or reset codes, authentication tokens, and account status.
- Login times, IP addresses, failed-login details, security audit records, and technical errors.
Device and technical information
- Firebase Cloud Messaging token, device platform, application version, build number, and notification permission status.
- Notification content, type, delivery time, delivery status, and technical delivery errors.
- Firebase Analytics events such as role, login method, screen views, and exam start or submission identifiers.
- Firebase Crashlytics reports, stack traces, device and operating-system information, and diagnostic data.
The application is not designed to collect location, contacts, camera or microphone data, biometric data, health records, payment information, or information for targeted advertising.
3. Excel Imports
Authorized administrators may upload Excel files containing student assessment records. The application processes these files to match students, subjects, grades, class groups, and assessment categories. The backend records the original file name, uploader, upload time, and records created from the import. The original workbook is not intentionally kept as a permanent application file after processing.
4. How We Use Information
- To create, link, authenticate, secure, and administer accounts.
- To organize academic structures and teacher assignments.
- To create, deliver, save, grade, and review examinations.
- To import, validate, normalize, reconcile, and display school grades.
- To provide academic performance, progress, comparison, risk, and intervention analytics.
- To send examination reminders, school messages, security alerts, and application updates.
- To investigate misuse, failed logins, security incidents, and technical errors.
- To operate, maintain, test, and improve the application and comply with legal obligations.
5. Educational Analytics
Analytics are decision-support tools and may be affected by missing, estimated, or incorrectly imported records. They must not be the sole basis for disciplinary action, exclusion, grading overrides, or another significant decision. Authorized staff must review the underlying data and educational context before acting.
6. Children and Students
The application operates in a school environment and processes information about children. Student data is used only for legitimate educational, administrative, safety, and security purposes. Access is limited to authorized users. Student information is not sold or used for behavioral advertising.
7. Sharing and Service Providers
Information may be shared only as necessary with:
- Authorized school administrators, teachers, students, and guardians according to their roles and authority.
- Hosting, database, backup, security, and technical-support providers acting for the application operator and school.
- Google Firebase for analytics, crash reporting, cloud messaging, and notification delivery.
- Authorities or professional advisers when required by law or necessary to protect legal rights.
We do not sell personal information or share student information for targeted advertising. Google may process Firebase information outside the user's country. See the Google Privacy Policy and Firebase Privacy and Security.
8. Retention
| Information | Retention approach |
|---|---|
| Student and academic records | Kept while required for enrollment, transcripts, educational history, and school recordkeeping obligations. |
| Exam attempts, answers, scores, and imported grades | Kept for the school's approved academic-record period. |
| Derived analytics | Kept no longer than the underlying academic records or until recalculated or deleted. |
| User accounts | Kept while active and afterward only where needed for academic integrity, security, or legal obligations. |
| Authentication tokens | Kept until expiration, rotation, revocation, or account termination. |
| Security and notification logs | Kept only as long as needed for security, delivery verification, investigations, and legal obligations. |
| Device tokens | Kept until logout, unregistration, replacement, invalidation, or account deactivation. |
| Firebase data and backups | Kept according to the configured Firebase retention and backup rotation schedules. |
9. Security
Security measures include authenticated and role-based access, password hashing, encrypted mobile storage for tokens, expiring and revocable sessions, HTTPS for production communications, rate limiting, audit logs, restricted administrative access, backups, monitoring, and incident response procedures. No system can guarantee absolute security.
10. User Choices and Rights
Users may disable notifications in device settings, log out, ask the school to correct inaccurate information, request access where legally available, and request human review of an analytics result. Certain academic, examination, security, and legal records may need to be retained.
11. Changes to This Policy
This policy may be updated when the application, service providers, laws, or school practices change. The effective date and version will be updated when material changes are made.
12. Contact
Application publisher: MHD Nezam
School: Al-Mohsinia School
Application: School Management
Package name: com.schoolexammanagement
Privacy, correction, access, and data-related requests may be submitted directly to the administration of Al-Mohsinia School through the school's official communication channels or in person. Do not include passwords, registration codes, or unnecessary exam information in a request.