1. Introduction
Carat HR Mobile is a mobile employee self-service application for human resources, provided under the Carat brand.
The application is intended for company employees and authorized approval managers. It does not offer public self-registration. Access requires an existing employee account using an employee code and password.
The app displays HR information and supports self-service actions (such as requests and approvals) through the company’s dedicated mobile backend. The mobile application does not connect directly to the company’s database; processing occurs through company server systems.
2. Information processed
The application relies on the company’s existing HR and account systems. Some information is entered by the employee in the app; other information is retrieved from company systems for display or service delivery.
2.1 Information entered or provided through the app
- Employee code and password at sign-in.
- Verification codes during password recovery, and during device verification if the company enables that step.
- A new password when changing or resetting a password.
- Leave and permission request content and related attachments when submitted.
- Profile photo and signature images when uploaded or replaced.
- Withdrawal and advance-related requests when those features are available to the employee.
- Resignation requests when that feature is used.
- In-app birthday greetings when available.
- Language preference (Arabic or English) on the device.
- Operating-system permission for push notifications when enabled.
2.2 Information retrieved from company systems
- Identification and employment details: name, employee code, job, branch, departments, manager, and company-held contact details.
- Profile information shown to the employee, including the employee’s own date of birth when present on the profile.
- Attendance and departure records for viewing only.
- Leave balances, leave and permission requests, and their statuses.
- Approval information for authorized managers.
- Account balance, statement entries, withdrawals, advances, and installments when available.
- Published company circulars addressed to the employee under company rules.
- A limited list of colleagues with upcoming birthdays (without year, age, or full date of birth in that list).
- In-app notifications linked to the employee account.
2.3 Device and session information
- An app-generated device identifier (not IMEI or advertising identifiers).
- Device platform, app version, manufacturer, model, and OS version for security and session management.
- Connection information such as IP address may be used for security in authentication systems.
- A device push-notification token when notifications are enabled.
3. Purposes of processing
Information is used only for HR and application-operation purposes, including:
- Employee account access and device session management.
- HR self-service features: attendance, leave, permissions, requests, approvals, account, withdrawals, advances, circulars, and notifications.
- Display of relevant employment and financial information according to company system permissions.
- Account security (authentication, verification where required, and session revocation).
- Delivery of in-app and push notifications when enabled.
- Application operation and troubleshooting related to sign-in and sessions.
The application does not currently include advertising or analytics tracking SDKs for those purposes.
4. Authentication and security
Sign-in uses employee code and password. After a successful sign-in, short-lived session credentials remain in application memory while the app is running, and session continuity credentials are stored in the device operating system’s secure storage.
The application does not store the employee password on the device. Employees can sign out on the current device, sign out from all devices, or manage devices and sessions from application settings when available. Changing the password ends mobile sessions associated with the account.
For password recovery: the employee enters the employee code; a verification code is sent to the mobile number registered with the company via WhatsApp when that service is configured; the employee then sets a new password and signs in again. The application does not display the mobile number during this process.
5. Biometric authentication
Employees may optionally enable Face ID or fingerprint unlock. Biometric verification is performed by the device operating system.
Carat does not collect or store biometric templates on its servers. The feature unlocks an existing on-device session; it does not replace server authentication.
After an explicit sign-out that revokes the server session, Face ID or fingerprint alone cannot create a new server session without signing in again with the password.
6. Push notifications
When notifications are allowed, the application requests operating-system permission and registers a device notification token with company systems to deliver HR-related notifications.
Push delivery uses platform notification infrastructure (including Apple Push Notification service and/or Firebase Cloud Messaging through the application platform’s supported delivery path). The device token is used for delivery, not for advertising.
Permission can be withdrawn in the operating-system settings or in the in-app notification settings when available. The application does not currently provide separate per-notification-type toggles in settings.
7. Photos, signatures, and attachments
Employees may upload or replace a profile photo and a signature image through the application. Files are transmitted to the company backend; they are not uploaded to public consumer storage services from within the app.
Images may be attached to leave requests according to request rules. Deleting the profile photo from within the app is not available in the current version; the photo can be replaced with a newer image. Other displayed profile fields are read-only in the app and are managed through company HR systems.
8. Storage and protection
- On the device: language preference, the app-generated device identifier, and limited helper flags for notification permission prompts.
- In secure device storage: session continuity credentials, and the biometric unlock preference when enabled (not biometric templates).
- In memory while the app is running: short-lived session credentials and temporarily displayed HR data.
- On company servers: HR and account records, requests, sessions, profile media, and notifications according to company systems.
Sensitive HR data is handled through the company API and is not kept as a durable on-disk application cache on the device. This policy does not claim end-to-end encryption for all data, and it does not promise absolute security.
9. Sharing and third parties
Employee information is processed primarily within company systems. The following may participate in operation or delivery:
- Company backend systems and databases as the system of record for HR data.
- The application development platform and operating-system services on Apple and Android devices.
- Push notification delivery services (including the platform delivery path and Apple and/or Google notification services).
- WhatsApp, when configured, for sending verification codes related to password recovery or device verification.
The application does not sell employee data and does not currently embed advertising or analytics tracking SDKs. Delivery providers may change based on company operations; this disclosure exists to acknowledge external delivery infrastructure where required.
10. Retention and deletion
HR, account, and request records are maintained within company systems under the organization’s record-keeping requirements. This page does not state fixed retention periods for every record type.
On sign-out, relevant local session data is cleared from the device according to application behavior. The application does not currently provide a “Delete my account” control because the account is created and managed by HR, not through in-app self-registration.
For access, correction, or deletion requests related to employee data in company systems, contact the email below so the appropriate team can review the request under company policy and applicable rules.
11. Employee privacy requests
Employees may contact the organization regarding:
- Incorrect employee information shown in the application.
- Requests to access or correct personal data.
- Deletion requests where applicable under company systems.
- Privacy questions or concerns.
Contact email: Tech@carat.ly. This page does not promise specific legal response deadlines unless adopted by the company.
12. Children’s privacy
The application is intended for company employees in an employment context and is not directed at children as a general public audience. It does not provide public self-registration.
13. Changes to this policy
This policy may be updated when application features or processing practices change. The current version is published on this public website.
14. Contact details
A registered legal entity name and physical address are not listed here because they have not yet been confirmed for publication.
15. Effective date
Publication date of this page: . Company legal or organizational approval should be completed before treating this text as a final binding legal policy.