Clock-in locations are uploaded. Coordinates collected for clock-ins and correction requests are sent with your employee identifier and time to your company's configured server. Offline records are stored on your phone and synchronized later. This replaces the previous statement that location stayed only on the device.
1. Scope and responsibilities
OC考勤管理 (OC Attendance) is provided by KUANG LIAN CO., LTD. for companies and authorized employees. There is no in-app self-registration; your company supplies accounts and permissions. Available features depend on the app version and company configuration.
Your company determines the purposes, access permissions and retention of employee records. We process data within the scope needed for contracted software, hosting or support. Company-hosted systems are administered by the company. This policy supplements the company's own legally required notices.
2. Data and purposes
| Feature | Data processed and purpose |
|---|---|
| Connection and login | Company pairing key, account and password sent for verification; login token and device identification information for authentication and access management. |
| Employee profile | Company-provided or user-edited name, employee number, company, account, avatar and, where enabled, email, phone, birthday and gender, for identification, contact and profile management. |
| Clock-ins and corrections | Employee identifier, type, date/time, precise latitude/longitude, correction details and approval results. Stored locally and sent to the company server for attendance, location verification, working-time summaries and approval. |
| Leave, overtime, business trips and vehicle journeys | Application type, dates/times, reasons, attachments and approval records; vehicle features also include vehicle number, journey locations and mileage, for personnel and work-related administration. |
| Photos and files | Avatars, photos and attachments you capture or select are uploaded to the company system. Supporting documents may contain health or other sensitive information; supply only what the company lawfully needs. |
| Notifications | FCM/APNs tokens and Firebase installation information for delivery; FCM token and employee identifier are sent to the company system for work notifications. Local reminders are scheduled on the device. |
| Assistant, where enabled | Submitted text, conversation context and login authentication information are sent to the company system to answer requests. Conversation history is also stored on the phone. Do not submit passwords or unnecessary personal data. |
| Operations and support | IP address and request time needed for connections; app/OS version, device and error information needed to investigate reported problems and maintain security. |
Sources include you, your company and device/system services. Not every feature requires every category. Withholding required data may prevent login, clock-in or application processing.
3. Permissions, location and offline records
- Location is obtained when you initiate a clock-in or correction, not by continuous background tracking. Previously recorded coordinates may synchronize later; background synchronization is different from continuous location collection.
- Camera, photo and file access is used when you capture or select an avatar or attachment, without scanning your entire photo library or contacts.
- Notifications and scheduling support work alerts. Notifications may contain work information; configure lock-screen previews appropriately.
- You can change Android/iOS permissions. Denying location affects location-dependent clock-ins/corrections; denying photo or camera access affects attachments; disabling notifications affects alerts.
- Offline clock-ins are stored locally and synchronized when connected. Check receipt and approval status. Clearing data, deleting the app or replacing your phone may lose unsynchronized records.
4. Recipients and processing locations
Authorized company administrators, HR staff, managers and approvers can access employee information, attendance, clock-in coordinates, applications and attachments within their assigned roles. We process data only as needed for contracted operations or support, do not sell personal data, and do not use attendance, coordinates or attachments for advertising.
- Google Firebase Cloud Messaging handles installation information, push tokens and delivery data: Firebase privacy and security.
- Apple APNs handles iOS device tokens and notification delivery: Apple Privacy Policy.
- Company-selected hosting, storage and support providers handle operational data according to the deployment. Your company should identify its providers and processing regions.
- External services you open, such as maps, receive the information you hand over and apply their own policies.
- Necessary disclosure may occur to comply with law, valid authority requests or rights-related disputes.
Data is processed where company systems and these services operate, potentially including the United States or other countries. Before enabling additional analytics, AI or other third-party integrations, the company must provide the necessary notice about providers, purposes, data and regions, and obtain any legally required authorization.
5. Retention and deletion
- Company-held employee records, attendance, coordinates, applications and attachments follow necessary service periods and lawful company retention policies. Employers subject to Taiwan's Labor Standards Act must retain attendance records for five years under Article 30. This does not require keeping every photo, precise coordinate or other record for five years.
- Local settings, cache, offline records and assistant history remain until removed through app or system operations. The app runs local assistant-history cleanup at logout. Removing local data does not delete company server records.
- Push records, operational logs and backups follow the necessary notification, security and backup periods for the deployment and provider. Ask for the applicable periods and backup handling when submitting a deletion request.
- When no processing purpose or lawful retention basis remains, data should be deleted or de-identified. Legally retained or dispute-related data should be restricted to those purposes. Leaving employment or disabling an account does not immediately erase all attendance records.
6. Security
The app uses HTTPS for login and data APIs and applies authentication and company-defined role permissions. Local protection also depends on your device settings. Use a screen lock, protect company keys and credentials, and report suspected misuse to your administrator and us. No transmission or storage can be guaranteed completely secure.
7. Your rights and requests
Subject to applicable law, you may request access, copies, correction, supplementation, restriction or cessation of collection/processing/use, or deletion. Contact your company administrator or [email protected]; we will assist within our authority or coordinate with the company. Where processing relies on consent, you may withdraw it without affecting prior lawful processing or mandatory retention.
Provide your company name, employee number or login account and request details. Identity may be verified through your company or existing contact method. Do not send passwords, pairing keys, full identity documents or unrelated sensitive data. See Account deactivation and data deletion. Requests will be handled within applicable statutory periods; any retained data and reasons will be explained.
8. Children, changes and contact
This is a workplace service, not directed at children. Companies must ensure user eligibility and required authorization. Contact us about suspected inappropriate collection involving a child.
Updates are dated on this page. Material changes to purposes, categories or recipients require appropriate notice through the app, company announcements or other channels, and consent where legally required.
Provider: 鄺聯企業有限公司 (KUANG LIAN CO., LTD.)
Contact: [email protected]