Camera Locker CCIVN

Purpose: Camera Locker is deployed to manage camera enable/disable when employees enter or leave the workplace area in accordance with internal rules and security requirements. Installation and use are performed with employee consent and coordinated with the MIS department to ensure proper procedure, security, and respect for employee personal rights. Contents Scope Device Owner permission & consent Processed data & minimization principle Gate entry/exit confirmation via existing attendance/access system Security, access and retention Employee rights How to use (Flow chart) Contact Quick Summary Internal security purpose only and compliance with workplace entry/exit rules. (Security & workplace policy) No access to unrelated personal data (personal gallery photos, contacts, messages, etc.). Deployment/installation is carried out together with MIS, with guidance and recorded consent (as applicable). 1) Scope This policy applies to employees and company-managed devices (or devices approved to participate in the company’s management program) when using Camera Locker within the workplace context. 2) Device Owner permission & consent Device Owner (Android Enterprise / Managed): The application may be deployed with device administration permissions under company policy to enforce security configurations. Consent & notice: Before installation/enrollment, employees are clearly informed of the purpose, scope, and how it works; participation follows internal procedures. MIS coordination: Installation is performed with MIS support to ensure correct procedure, security, and no interference with personal data outside the necessary scope. 3) Processed data & minimization principle Camera Locker is designed following the data minimization principle: Operational data may include: employee code (emp_no), check-in/check-out time (if applicable), camera lock/unlock status, device status, and event logs for compliance checks. Not collected: unrelated personal data such as contacts, messages, browsing history, personal photos/videos in the gallery, or private account data. Not used for advertising or marketing. 4) Entry/exit confirmation via existing attendance/access-control system Integration principle: The app only calls an API to confirm employee entry/exit status (IN/OUT) based on the company’s existing attendance/gate control system. Purpose: to verify and ensure the camera is locked before the employee enters the gate, and to unlock the camera when the employee exits the workplace area. Minimal data: the API only requires operational information such as employee code and IN/OUT status + timestamp (if applicable) to make lock/unlock decisions. No biometric data storage: the app does not collect/store face photos, face templates, or any biometric identifiers from the phone. Important clarification: the app does not use the phone camera for face scanning. Any face scanning (if used) belongs to the company’s pre-existing attendance/access system at the gate. 5) Security, access and retention Access control: only authorized personnel (MIS/System Admin) can access the admin portal and logs. Logging: the system may retain logs for compliance verification and security incident investigation. Minimal retention: data is stored only as long as necessary for operations/compliance, then deleted/anonymized according to company policy (if applicable). Transport security: HTTPS is recommended; restrict access via internal network/VPN and apply least-privilege database access. 6) Employee rights Right to be informed about the purpose, scope, and operation of the application. Right to support from MIS for technical issues or concerns about access beyond the stated scope. Right to provide feedback/raise concerns if any privacy risk or deviation from the intended purpose is identified.