1. Operator and scope
Absensi Matahati is an iOS application for internal employee attendance and HR administration at Matahati Cafe. Information within the service is managed by Matahati Cafe through authorized company personnel (the Operator).
This policy covers the iOS app and the supporting server and backoffice services. The app is intended for employees and HR staff with company-issued accounts, not the general public or children.
2. Information we process and its sources
- Account and employment information: name, email, position/role, department, active status, and login session information. Authorized company staff may create or update accounts.
- Attendance, schedules, and requests: attendance times and history, work schedules, reasons for manual attendance or leave/sick requests, supporting photos, and HR approval decisions.
- Location and network: device coordinates when attendance/request features are used, resolved place names, and available office Wi-Fi SSID information used for location rules. In specific cases where GPS cannot provide a fix, the system may record location-unavailable status using placeholder coordinates 0,0.
- Facial images and identifiers: three face registration photos, photos taken for facial attendance, and face identification/matching data processed using AWS Rekognition. Attendance evidence photos are distinct from registration photos.
- Payroll: displayed payroll information, acceptance or rejection status, rejection reasons, and requests to email a payslip.
- Technical information: device information sent by the app, authentication session information, and server records needed for operation, security, and troubleshooting.
Data comes from company-provided records, user input, camera images captured during relevant features, location information during relevant workflows, and connected internal HR systems.
3. Purposes and device permissions
We use this data for authentication; attendance recording and verification; location/Wi-Fi checks; handling employee requests and HR approvals; schedules; payroll display; system security; audits; and personnel administration.
The camera is accessed when a user captures a photo. Location Services are required for attendance and request submissions; disabling them prevents submission. The app is not designed to track a user's movements continuously in the background.
Facial image processing is used for attendance verification, not advertising or marketing.
4. Service providers and disclosure
- AWS Rekognition: receives facial images via our server for registration, face identifier storage, and attendance matching. AWS deletion facilities are used when face registration is reset or during data purge.
- Nominatim / OpenStreetMap: the application server first checks its cached place names. If no suitable cached place name exists, coordinates may be submitted from the server to Nominatim to resolve a place name or address.
- Hosting and email services: support application hosting, databases, file storage, and emailing payslips at the user's request.
We do not sell data or use it for targeted advertising. Access is limited to authorized staff and service providers as needed for these functions, or where required by law. Some providers may process data using infrastructure outside Indonesia.
The Operator is responsible for assessing provider safeguards and processing terms, restricting disclosures to stated purposes, and seeking protection equivalent to this policy and applicable obligations.
5. Security and access controls
The app communicates with its server over HTTPS and requires authentication. Functions and data are restricted according to user roles and permissions, including departmental limits for HR staff where configured.
Users should protect account credentials and promptly report lost devices or suspected unauthorized access. As with any online service, absolute security cannot be guaranteed.
6. Data retention and deletion
Attendance and administrative records
Attendance history, leave requests, work schedules, and payroll records are retained during employment. When employment ends, an account may be deactivated without automatic deletion of past records. Records may be retained for administration, audits, legal obligations, or dispute resolution.
Eligible records may be deleted through an authorized data purge procedure in the web backoffice. Attendance and leave supporting photos may follow a separate operational retention policy and may be deleted separately from transaction records.
Face registration data
Face registration photos and AWS Rekognition face identifiers are retained as needed for attendance verification. When an employee resets facial registration, the previous AWS face identifiers and related registration photos are deleted. This does not automatically delete historical attendance evidence photos.
Account deactivation or the end of employment does not automatically erase any remaining biometric data. Remaining data is removed through an authorized data purge after relevant retention needs and obligations are considered.
7. Your choices, rights, and contact
You can request information, correction, a review of processing, or deletion of personal information through HR or it.matahati@gmail.com. Requests to terminate or delete an employer-managed account are handled by HR in accordance with relevant authority and employment obligations.
You can change camera and location permissions in iOS Settings. Revoking a permission limits the related features but does not automatically erase previously recorded attendance. To remove a current face registration, use the app's face reset feature or contact HR for assistance.
Do not send passwords or sensitive identity photographs by ordinary email. The support team may request appropriate verification before handling a personal data request.
8. Changes to this policy
We may update this policy when features, company procedures, or applicable requirements change. Updates are posted on this page with a revised date.
This support website does not embed third-party advertising or analytics scripts. The web server may record technical access logs for maintenance and security.