Privacy Policy

STELMOVE Attendance (the “App”) is a workforce attendance application provided by PT. I Flex Indonesia (“we,” “us,” or “our”) for use by authorized employees and organizations. The App supports employee account access, attendance and schedule workflows, device registration, location-based attendance validation, photographic evidence, and, where enabled, Emergency SOS and device connectivity monitoring.

This Privacy Policy explains what personal data the App and related STELMOVE services process, why they process it, how it may be disclosed, how long it may be retained, and how individuals can make privacy requests. Access and processing may also be governed by the policies of the organization that employs or administers the user.

The App is intended for authorized workforce users, generally adults aged 18 and over. Accounts and organizational access are provisioned by authorized administrators through the STELMOVE identity and attendance systems. Users cannot independently create a public account in the App.

Depending on the features used and permissions granted, we may process the following categories of information:

A. Identity and employee information: name, preferred name, user or employee identifiers, email address, phone number, organization and tenant association, employment and organizational details, assigned site or zone, schedules, and emergency contact phone numbers supplied through the employee profile.

B. Authentication and access information: sign-in and session identifiers, access or refresh tokens, device approval and registration records, permissions, and information needed to protect accounts and control access.

C. Attendance and operational records: clock-in and clock-out events, event times, schedule references, attendance status, attendance history, offline sync records, submitted correction requests and reasons, and related audit records.

D. Location information: precise location coordinates, location accuracy, and related timestamps when location-based attendance checks or Emergency SOS require available location information. Location may be used to evaluate an attendance location or geofence. An SOS request may be created without an available GPS fix; in that case, the associated location may be missing or may be identified as a previously recorded location if that behavior is implemented and clearly labeled.

E. Photographs: selfies used as attendance evidence and, where the Face Enrollment workflow is required, face photographs captured for employee enrollment. These photographs may be uploaded to protected server-side object storage and associated with employee or attendance records.

F. Device and connectivity information: App installation or device identifiers, device registration and approval status, operating system and App version, device integrity-check data or tokens, the last time a device contacted the service, and, where device monitoring is enabled, connectivity/heartbeat status and relevant device health information such as battery level if implemented.

G. Emergency SOS information (when enabled): a unique SOS event identifier, employee and tenant association, related device identifier, the time SOS was activated, available location and accuracy data, the time the server received the SOS, delivery state, incident status, acknowledgment or resolution actions, responsible personnel, and related management authorization and audit information.

H. Technical and security records: API request metadata, timestamps, authentication/security events, error information needed to operate and secure the service, and service access logs. This description does not mean the App necessarily uses a third-party crash analytics service.

Information may be provided by the employee, supplied by the employee's organization or authorized administrators, generated when the employee uses attendance or emergency features, created during authentication and device registration, or collected through device permissions and connectivity checks when needed for an enabled feature.

Some records are downloaded from organizational systems for display and are not necessarily newly collected from the device. Information sent from the App to STELMOVE systems is processed in accordance with its relevant purpose.

We process information to:

• Authenticate users and enforce organization-, tenant-, and role-based access controls.

• Register, approve, and secure permitted devices.

• Record, validate, synchronize, and report employee attendance.

• Support schedules, profiles, history, and attendance correction workflows.

• Verify location-based attendance conditions where configured.

• Store and manage attendance selfies and face-enrollment photographs where applicable.

• Receive, display, route, acknowledge, and resolve Emergency SOS events where enabled.

• Monitor device connectivity and display last-known online/offline status where enabled.

• Diagnose operational problems, prevent misuse, maintain audit trails, and comply with applicable obligations.

The App is not intended to use attendance, location, face photographs, or SOS data for targeted advertising.

The App may request camera permission to capture attendance selfies and face-enrollment photographs, and location permission for attendance/geofence checks and Emergency SOS location reporting. Permissions are requested or used in connection with the applicable feature. Denying a required permission can prevent that feature from working, but SOS design should not require a successful GPS fix before a request is locally recorded or submitted.

Device connectivity monitoring does not, by itself, establish the physical safety or precise real-time location of an employee. The App does not need continuous background GPS tracking solely to report whether an Android device has recently contacted the server.

Where the Face Enrollment workflow is enabled, an employee may be required to capture and upload a face photograph. The enrollment service stores an associated file reference and enrollment status; the examined service does not establish that a biometric face template or automated face-recognition decision is generated by that particular upload operation. Face photographs are sensitive and are handled with additional care.

The current server-side enrollment implementation marks active face-enrollment file records for long-term preservation, without an automatic retention expiration. When enrollment is replaced, the earlier enrollment record may be marked revoked rather than physically deleted, and the associated stored file is not automatically removed by that action. Requests about these records must therefore be assessed separately from an employee account's soft-delete status.

Any future deployment of automated face matching, biometric templates, or additional biometric functions must be assessed and reflected in the relevant notice and permissions before use.

Emergency SOS is intended to help a user report an emergency. When the device can contact the service, the App attempts to transmit the SOS to the STELMOVE Attendance backend so that authorized dashboard users can receive an alert. An SOS can be activated independently of attendance schedule, clock-in status, or geofence checks, subject to valid application access.

IMPORTANT OFFLINE SAFETY LIMITATION:

If the Android device has no usable internet connection, activating SOS stores the event locally on the device for later synchronization. While the event remains only on the device, the AO, SSO/Platform, and FMS dashboards and emergency personnel HAVE NOT RECEIVED THE SOS and CANNOT KNOW FROM THE SERVER that the SOS button was pressed.

When connectivity returns, the App attempts to synchronize the pending SOS. Delivery is confirmed only when the server acknowledges receipt. Restoring connectivity does not guarantee an immediate delivery time; device, background-processing, authentication, or network conditions can cause additional delay. A locally stored SOS may never arrive if the device is destroyed, its data is lost, or connectivity does not recover.

The App should clearly distinguish “SOS stored on device / not yet delivered” from “SOS received by server.” The original activation time and the server receipt time are preserved as separate records so responders can identify a delayed alert.

Emergency SOS is not a guaranteed real-time emergency dispatch service and must not be relied upon as the sole method of obtaining urgent assistance, especially in locations with unreliable connectivity. Users should follow their organization's established emergency and workplace safety procedures.

The App may send device heartbeat or last-contact information to help authorized personnel monitor registered Android attendance devices. Connected device monitoring may also be presented alongside other STELMOVE-managed fleet equipment, with each device type reported by its responsible system.

An “offline” status generally means the server has not received an expected contact within a configured period. It does not necessarily mean the telephone is powered off or that the employee is injured. Android battery restrictions, background execution limits, network conditions, and user actions can affect contact frequency. An offline device indicator does not reveal SOS requests that remain unsent on that device.

After the backend receives an SOS, the event may be made visible through authorized Attendance Online (AO), STELMOVE Platform/SSO, and Fleet Management System (FMS) dashboards. Access is restricted by tenant and applicable permissions; users of unrelated tenants must not receive or access another tenant's emergency event.

Only designated supervisors, workplace safety (K3) personnel, or other authorized officials may acknowledge or close an SOS alert according to their assigned permissions. Authorized Platform administrators may perform an exceptional alert-closing action only following a management request and appropriate authorization. Such actions should record who acted, when, for which tenant and SOS event, and the stated reason or management authorization. Closing an alert does not erase its historical or audit records.

Information may be accessible to the employee's organization and appropriately authorized supervisors, administrators, HR personnel, and safety responders for legitimate workforce and emergency operations. Relevant data may be processed across STELMOVE AO, Platform/SSO, and FMS services to provide the requested functionality, subject to tenant isolation and role-based access.

We may use infrastructure, hosting, security, or other service providers to operate the service under applicable arrangements. We may also disclose information where required by law or necessary to protect rights or safety. We do not intend to disclose employee information to unrelated tenant organizations. Whether a particular flow qualifies as data “sharing” under Google Play's Data safety definitions must be assessed separately based on the actual recipients and processing arrangements.

The App communicates with configured production service endpoints over HTTPS. Authentication, permissions, tenant restrictions, and access controls are used to reduce unauthorized access. Certain information, including unsent offline attendance or SOS records, may be stored locally on the device until synchronization and in accordance with the App's local storage behavior. No technical measure can guarantee absolute security.

Attendance, account, device, SOS, and audit data may be retained as needed for their operational purposes, organizational policy, safety investigations, legal obligations, and legitimate recordkeeping. A universal automatic deletion period is not currently confirmed for all categories. In particular, active face-enrollment photographs are held without an automatic expiry in the current backend implementation, and revoking an earlier enrollment does not by itself guarantee deletion of its file.

The removal or deactivation of an employee's account may be implemented as a soft deletion. Soft deletion is not the same as immediate permanent erasure of every related database record, photograph, backup, audit event, or legal-hold file. A request for permanent removal must be reviewed in light of technical capabilities, applicable laws, and justified retention obligations; it must not be represented as completed until the relevant deletion process has actually occurred.

Depending on applicable law and organizational arrangements, individuals may request information about their personal data, correction of inaccurate information, access to applicable records, restriction or withdrawal of certain processing where available, or deletion when legally and technically appropriate.

STELMOVE employee accounts and records are generally administered through the employing organization. Employees should first contact their HR department or designated organization administrator for profile corrections, account deactivation, or personal-data requests. For privacy concerns or assistance, contact PT. I Flex Indonesia at support@dhuiss.com.

We will assess requests with the relevant organization and respond in accordance with applicable Indonesian personal-data protection requirements and other applicable laws. Some records may need to be retained for employment, safety, audit, or legal purposes, and requests may not result in immediate permanent deletion.

The App is designed for authorized workforce use, generally by adults aged 18 or older, and is not directed to children. If we learn of unauthorized processing involving a child, we will evaluate appropriate action under applicable law.

Technical service infrastructure or authorized service providers may process data in locations determined by the organization's deployment and service arrangements. Where cross-border processing takes place, we seek to apply safeguards required by applicable law. The App does not claim that all data remains in any particular country unless that can be verified for the deployment.

We may update this Privacy Policy when features, data flows, legal requirements, or organizational procedures change. Material changes, including changes related to Emergency SOS, device monitoring, facial identification, or data recipients, should be reflected in the policy and communicated as appropriate. The updated policy and its effective date should be made available through an accessible public webpage and, where applicable, within the App.

PT. I Flex Indonesia

Product: STELMOVE Attendance

Privacy and support email: support@dhuiss.com

Jurisdiction: Indonesia

For workplace account and employee-record requests, please also contact your organization's HR department or authorized administrator.