Effective date / Last updated: October 28, 2026
The provider of Chuqing Daka (the “Company”) values the protection of personal data. This Privacy Policy explains how the Company collects, processes, uses, and protects personal data when providing Chuqing Daka (the “Service”), including its web and mobile app versions (iOS/Android).
The Service is an internal attendance and personnel-management tool for business customers (each an “Employer”). Your Employer determines how your data is used for its personnel-management needs. The Company processes and stores that data on the Employer’s behalf under their service arrangement.
| Category | Data | When collected |
|---|---|---|
| Account information | Name, email address, employee number, department, and password (stored as a one-way hash that cannot be reversed by the Company) | When an account is created or updated |
| Attendance records | Punch time and punch type (clock-in/clock-out) | Each time you punch in or out |
| Location | GPS coordinates and location accuracy | When GPS verification is enabled by the Employer and used for a punch |
| Network information | Connected Wi-Fi network name (SSID) and access point identifier (BSSID) | When Wi-Fi verification is enabled by the Employer and used for a punch |
| Leave requests | Leave type, start and end dates, reason, review result, and comments | When a leave request is submitted or reviewed |
| Work reports | Report date and written work report | When a report is submitted |
| Temperature reports | Body temperature and submission time | When a temperature report is submitted |
| Schedules | Shift, working hours, and scheduled date | When the Employer creates a schedule |
| System notifications | Notification content and read status related to leave, reviews, and similar events | When a related event occurs |
| Device and sign-in information | Sign-in IP address, most recent IP address, User-Agent, platform, app version, device name, and a random device identifier. When the IP changes during a sign-in session, the most recent IP replaces the previous value. This field is not used to build IP history or infer your location. | At sign-in and while a sign-in session uses the Service |
| Account security and audit information | Sign-in time, sign-in device, operation records, and account-deletion request status | When you sign in, use the account, or request account deletion |
| Push registration and delivery | Push tokens, app installation identifiers, device platform and version, notification content, delivery status and necessary error records | During App initialization, notification activation, device registration or updates, or notification delivery |
| Subscriptions and transactions | Store product and transaction identifiers or purchase tokens, company association identifiers, purchase and expiry times, renewal and refund/revocation status, and test/production environment | During purchase, restoration, subscription synchronization or store status updates |
| Advertising data | The ad SDK may process IP addresses and approximate location inferred from them, available device or advertising identifiers, ad interactions, diagnostics and consent status | When eligible for ads, during ad consent procedures or when ads load |
The App obtains current location or Wi-Fi information when you use a punch function that requires that verification. On iOS it uses “When In Use” location authorization, not “Always.” It does not enable background location or continuously record a movement history. On Android it requests foreground location for the relevant functions, not background location permission.
Operating systems treat Wi-Fi names (SSID) and access point identifiers (BSSID) as location-sensitive information, so Wi-Fi verification may also require location permission. On iOS, Wi-Fi punches require precise location and may prompt for temporary full accuracy; this does not enable background tracking. You can deny or revoke permissions in system settings. The corresponding verification may then be unavailable; available punch methods depend on your Employer’s configuration and device support.
To verify receipt and processing of store subscription notifications, troubleshoot failures and prevent duplicate accounting, we retain Apple event and environment details, receipt times, transaction identifiers, verified company associations, processing results, safe error summaries and platform administrator action records. Unverified notification content does not prove payment or authorize access. Notification summaries are periodically removed after 90 days; official test query identifiers are encrypted and periodically removed after 7 days. Full signed notification payloads are not retained in these records, and company administrators and employees cannot access the platform notification log. Transaction and subscription data continue to follow the service and legal retention purposes described above and are not deleted with notification logs.
Personal data is retained during the employment relationship for attendance and personnel-management purposes. Sign-in IP addresses, most recent IP addresses, and device information are stored with sign-in session records. The Service currently does not set an automatic expiration time for sign-in tokens, so these records remain until the session is logged out, revoked by the user, deleted due to a password reset or account-status change, or removed through account deletion. A self-service deletion request made in the App by a non-employee account has a 24-hour reconsideration period. After it ends, the system deletes sign-in sessions and other data not required to be retained by law or contract. Employee-account deletion confirmed by an administrator of the same Employer immediately revokes access and removes direct account identifiers, without that reconsideration period. The next section describes the handling of historical records. Attendance, overtime, leave, or audit records that must be kept by law, labor-record retention requirements, or the Employer’s lawful personnel-management needs will have access restricted and will be deleted or de-identified when the retention period ends. If an Employer ends its use of the Service, the Company will delete or return the relevant data as agreed with that Employer.
Under Article 3 of Taiwan’s Personal Data Protection Act, you may request access to or a copy of your personal data, ask to supplement or correct it, request that its collection, processing, or use stop, or request deletion.
Self-service requests for non-employee accounts: Non-employee accounts may request deletion under “My Account / Account Security” in the App. A request has a 24-hour reconsideration period and may be cancelled during that period. After it ends, sign-in sessions and other data not subject to retention obligations are deleted.
Administrator deletion of employee accounts: Only an administrator of the same Employer may confirm deletion of an employee account in employee management. This feature cannot delete administrator accounts or accounts belonging to another Employer. It applies to active, disabled and resigned employee accounts. Employees cannot execute account deletion themselves in the App, but may contact their Employer’s administrator or use the contact details on this page to request data deletion. Administrator-confirmed deletion takes effect immediately, has no 24-hour reconsideration period and cannot be undone. The system revokes all sign-in tokens and push-device registrations, removes or replaces direct account identifiers such as name, email address and employee number, and removes the account from employee management. A newly created account is a new account; it does not restore the deleted account or automatically inherit its historical records.
Historical records and rights requests: Deleting an account does not delete all attendance data. Existing attendance, schedules, overtime, leave and other records that need to be kept under applicable law, contract or the Employer’s lawful personnel-management purposes retain necessary relationships after direct account identifiers are removed, with access restricted. They are deleted or further de-identified as required when the retention period ends. You may still use the contact details on this page to request access, correction or deletion; the Company will respond within the time required by law. Resignation and account deletion are separate actions: a resigned account that has not been deleted may view historical records under the existing rules; a deleted account can no longer sign in.
Browser local storage used to maintain sign-in is not used by the Company as a cross-site advertising tracking tool. Native ad SDK and consent processing are described under “Push, store subscriptions and advertising services” above.
The Service is intended for employees of Employers and is not generally intended for people under 18. If an Employer provides an account to an underage employee, the Employer is responsible for its obligations under applicable labor laws, including any notice or guardian-related duties.
The Company may revise this Policy to reflect changes in law or the Service. The revised Policy will be posted here with an updated “Last updated” date. For material changes, the Company will provide notice by reasonable means, such as an in-app notice.
If you have questions about this Policy or our handling of personal data, contact us: