Digital School
المدرسة الرقمية

1. Introduction

Enjaz Advanced Information Technology Systems Establishment ("Enjaz", "we", "us", or "our") operates the Digital School (المدرسة الرقمية) mobile application (the "Application").

This Privacy Policy explains how we access, collect, use, store, protect, and otherwise process information when you use the Digital School Application.

The Application provides digital services for schools, students, parents, teachers, and authorized school personnel.

2. Personal Information We Collect and Process

Depending on the user's role, school configuration, and features used, the Application may collect or process the following personal information:

• Name and basic profile information.
• Student ID number, where applicable.
• Parent ID number, where applicable.
• Teacher or staff ID number, where applicable.
• Email address.
• Mobile / phone number.
• School information, including the associated school or educational organization.
• Class and educational information, including grade, class, section, and related educational information.
• Authentication credentials, such as username and authentication-related information required to access the account.
• User IDs and account identifiers used to identify the account within the Application.
• Messages and chat content exchanged through the Application.
• Photos and images uploaded through supported features.
• Audio recordings created or uploaded through supported communication features.
• Files and documents uploaded or exchanged through supported features.
• Application interaction information, such as usage of application features and screens.
• Crash logs and diagnostics used to identify and resolve technical problems.
• Android, device, application, or other identifiers, including identifiers generated or used by supported Firebase services.

3. Firebase Services

The Application uses selected Firebase services provided by Google to support application functionality, analytics, diagnostics, notifications, chat, and file storage.

Firebase Analytics

Firebase Analytics is used to understand application usage, measure feature usage, analyze application and device-related information, and improve the performance and user experience of the Application.

Depending on the Firebase configuration and device environment, Analytics may process application interactions, application version information, device-related information, and other analytics information.

Firebase Crashlytics

Firebase Crashlytics is used to identify, diagnose, and resolve application crashes and technical problems.

Crashlytics may process crash reports, diagnostic information, device and operating system information, application version information, and configured user identifiers where applicable.

Firebase Cloud Messaging

Firebase Cloud Messaging (FCM) is used to deliver push notifications to users.

FCM may process device and notification tokens required to deliver notifications to the appropriate device.

Firebase Realtime Database

Firebase Realtime Database is used to support communication and chat functionality.

Depending on the features used, this may include chat messages, user information, groups, permissions, and related application data.

Firebase Storage

Firebase Storage is used to store files uploaded or exchanged through supported communication and chat features.

These files may include images, audio recordings, and documents.

4. Payment Services and HyperPay

HyperPay / OPPWA Mobile SDK

The Application includes the HyperPay / OPPWA Mobile SDK to support payment checkout and transaction processing functionality.

The presence of the SDK does not by itself mean that payment information is currently collected by the Application.

If payment functionality is enabled in a future version, this Privacy Policy and the applicable Data Safety disclosures may be updated accordingly.

Google Play Services Wallet

The Application includes Google Play Services Wallet components for supported wallet and payment-related functionality.

Google Play Services Maps

Google Play Services Maps components may be included transitively as a dependency of wallet-related services.

5. Huawei Services

The Application includes Huawei AGConnect Core for Huawei service initialization and compatibility with supported Huawei services and devices.

6. Application Communication and Networking Libraries

• Volley – communication with the application backend.
• Android Async HTTP – communication with the application backend.
• Retrofit – API communication.
• OkHttp – HTTP and network communication.
• Gson – JSON serialization and processing.

These are technical libraries used for communication and data processing. Their presence does not independently mean that additional personal information is collected.

7. Documents and PDF Processing

• Aspose.Words – document processing.
• Android PDF Viewer – PDF document rendering.
• PDFium – PDF rendering and display.

8. Images, Media, and User Interface Libraries

• Glide – image loading and caching.
• MPAndroidChart – chart rendering.
• HelloCharts – chart rendering.
• PhotoView – image viewing and zooming.
• Facebook Shimmer – loading animations.
• CircleImageView – circular image display.
• LovelyDialog – dialog interface components.
• WhatsApp Messenger View – audio-recording user interface.

These libraries primarily provide user interface, rendering, media, and presentation functionality. Their presence does not independently mean that personal information is collected or shared.

9. How We Use Information

• Providing and operating Digital School services.
• Authenticating users and managing accounts.
• Connecting users with their school and authorized services.
• Providing communication and chat functionality.
• Delivering push notifications.
• Providing educational and administrative services.
• Processing images, audio, documents, and supported content.
• Monitoring application stability and diagnosing technical problems.
• Understanding application usage and improving features and user experience.
• Maintaining security and preventing misuse.

10. Data Sharing and Service Providers

We may use trusted technology and service providers to process information on our behalf in order to provide application functionality.

These providers may include Google Firebase and other technology providers used by the Application.

We do not sell users' personal information.

Information may also be disclosed where required by applicable law, regulation, legal process, or where necessary to protect the security and rights of users, schools, our systems, or other parties.

11. Data Security

We use reasonable technical and organizational measures designed to protect personal information against unauthorized access, alteration, disclosure, or destruction.

Communications between the Application and supported backend services are protected using appropriate security mechanisms, including encrypted communication where applicable.

Access to application data is controlled according to user roles and authorized school permissions.

12. Data Retention

We retain information for as long as necessary to provide the services, satisfy legitimate operational requirements, comply with applicable legal obligations, resolve disputes, enforce agreements, and maintain security.

Retention periods may vary depending on the type of information, the purpose for which it was collected, and applicable school or legal requirements.

13. Account and Personal Data Deletion

Users may request deletion of their Digital School account and associated personal data through the dedicated account deletion page.

Certain information may be retained where retention is required or permitted by applicable law, for legitimate security purposes, dispute resolution, fraud prevention, or other legally permitted purposes.

14. Children's Privacy

Digital School is an educational platform that may be used by students, including minors, under the management or authorization of schools and authorized educational personnel.

Student information is processed for legitimate educational, administrative, communication, security, and service-related purposes.

Schools and authorized administrators are responsible for appropriately managing student access and information in accordance with applicable laws and institutional requirements.

15. User Rights

Depending on applicable laws and the user's relationship with their school, users may have rights regarding their personal information, including access, correction, deletion, and other applicable privacy rights.

Users may submit privacy-related requests using the contact information below.

16. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes to the Application, technology, services, legal requirements, or our privacy practices.

The "Last Updated" date at the top of this Privacy Policy indicates when the policy was most recently updated.

17. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or the handling of your information, please contact us: