SyncroConnect Apps Privacy Policy

Scanner Connect and Fatigue Management

Scanner Connect is the worker badge scanning app for authorised Fatigue Management managers and admins. Workers do not sign in to the scanner. Fatigue Management accounts and records are separate from SyncroConnect accounts and records. The information below applies when the corresponding Scanner features are used.

• Account and device security: company code, operator name, email, user and role identifiers, device identifiers and protected session credentials are used to authenticate the operator and restrict access. The sign-in password is sent to Fatigue Management over HTTPS for verification and is not saved by the app.
• Worker and scan records: worker names, references, employer associations, worker and badge identifiers, arrival/departure times, operator/device attribution, fatigue indicators and any override reasons are handled to identify workers, record attendance and support your organisation's fatigue-management and audit processes. Badge identifiers may be sent to Fatigue Management to resolve a badge lookup. Fatigue indicators are derived from working history.
• Camera and permissions: the camera reads worker QR badges on the device. Scanner Connect does not save camera frames as photographs or upload them to Fatigue Management. It does not request live location, contacts, microphone or photo-library access. Optional biometric unlock uses the device operating system; the app does not receive fingerprint or face templates.
• Scanner unlock code: the five-digit Scanner code is checked on the device using a protected verifier and local attempt records. It is separate from your device passcode and is not sent to Fatigue Management. Optional biometric authentication is handled by the device operating system.
• Local storage and transfer: downloaded worker information and queued scan records are held in an encrypted local database, with protected keys and session material in platform secure storage. Records are sent to Fatigue Management over HTTPS when synchronisation is available. A record waiting on the device is not proof that it has reached the server. Signing out is not a request to delete committed worker or scan evidence; records awaiting recovery may remain protected on the device.
• Barcode library diagnostics: Scanner Connect for Android uses Google's ML Kit barcode scanning library. Google collects device and app information, per-installation identifiers, performance and configuration details, feature events and errors for diagnostics and usage analytics. With automatic zoom enabled, this also includes a generated scan-session identifier, zoom changes and estimated barcode bounding-box coordinates. This diagnostic processing is separate from the worker records sent to Fatigue Management. See Google's ML Kit data disclosure.

Worker records, scan history, fatigue indicators and override reasons may be retained by your organisation for attendance, safety, audit and operational purposes. Ask your employer or organisation administrator to review, correct or delete your information where appropriate. Signing out does not delete records already held by the organisation. The sharing, retention and contact information below also applies.

Information we collect

• Login and account data: company code, email address, password verification, app session and access permissions.
• Employee profile data: name, email, payroll number, department, site, manager relationship, holiday allowances and similar workforce profile fields.
• Leave and workflow data: leave requests, cancellations, approvals, rejections, notes, absence history and related manager workflow actions.
• Attachments, files and photos: files or images you choose to upload in support of leave, absence or related workflow activity.
• Clocking and attendance data: clock-in/clock-out events, timestamps, work session records, exceptions and attendance history.
• Fire roll call data: on-site employee lists, site, department, job title, assembly point, payroll number, phone availability, safe/pending status, fire drill start and close events, reset actions and related audit history.
• Visitor data: visitor name, company, email address, phone number, vehicle registration, reason for visit, host, expected arrival, sign-in/sign-out timestamps, visitor question responses and visit status.
• Visitor photos and signatures: visitor photos and signature images may be captured where your organisation has enabled these Visitor Application features.
• Visitor QR and badge data: visitor booking QR tokens, QR lookup/sign-in/sign-out events, badge/pass print jobs, print status and local tablet queue status.
• Visitor tablet data: paired tablet name, tablet identifier, tablet token, app version, device platform, settings, kiosk status, connectivity status and sync diagnostics used to operate the visitor kiosk.
• Device and notification data: push notification token, platform, app build, device identifier/label where provided, and preference settings for notifications.
• Manager/admin workflow data: inbox items, approvals, rejections, reports, audit trails and actions taken in manager/admin workflows.

Camera, location, biometrics and passcodes

• Camera: the camera is used only in apps or features where a user chooses or is asked to take a photo, scan a QR code or upload an image. Syncro Connect Visitors may use the camera to capture visitor photos and scan visitor booking QR codes. Syncro Connect Roll Call does not require camera access for roll call checks.
• Location: location is used for clocking and location-related features when relevant to your employer's setup. Syncro Connect Roll Call uses existing site and assembly point data but does not require live device location for roll call checks.
• No background tracking: the app does not perform background location tracking unless such a feature is explicitly implemented, enabled and separately disclosed.
• Biometric and device-passcode usage: if your device uses biometric or device-passcode unlock for app access, authentication is handled by your device operating system. SyncroConnect does not receive or store your raw fingerprint, face template or device passcode. Scanner Connect's separate app unlock code is described above.

How we use information

• To authenticate users and protect account access.
• To process leave requests, cancellations and manager/admin approvals.
• To support clocking, attendance, time and location-related workforce features.
• To support fire roll call, fire drill checks, safe/pending status updates, employee call shortcuts and roll call audit records.
• To support visitor sign-in, visitor sign-out, QR booking lookup, host notification/workflow, visitor question capture, visitor photos/signatures and visitor badge printing.
• To send push notifications for leave updates, manager workflow activity and clocking exception events.
• To display employee photos, attachments and workforce records to authorised users.
• To display visitor records, current visitors, due visitors and visitor history to authorised users.
• To maintain audit trails, troubleshoot issues, support customers and improve service reliability.

Push notifications

Push notifications are used for workflow updates such as leave approvals, leave rejections, cancellation approvals/rejections, manager inbox activity, fire drill alerts and clocking-related exceptions like missing clock-out events.

Where push notifications are supported, they are delivered using Firebase Cloud Messaging (FCM). Notification delivery requires a registered device token and can be limited by device settings, user preferences or organisation setup.

Sharing and service providers

Data is shared only as needed to operate the service, follow your organisation's workflow and comply with legal obligations. This can include authorised managers/admins inside your organisation and service providers used to host or operate the platform.

• Hosting, database and infrastructure providers.
• Email and notification providers used to deliver service communications and push notifications.
• Support, security and operational service providers acting on behalf of the platform or your employer.

Data is not sold to third parties.

Storage, retention and deletion

• Data is stored in systems used to provide the relevant SyncroConnect or Fatigue Management services to your organisation.
• Retention periods are generally controlled by your employer or organisation and may vary depending on legal, operational and payroll requirements.
• Fire roll call and drill history may be retained for safety, compliance, audit and operational review purposes.
• Visitor records, visitor question responses, photos, signatures, QR events and badge print history may be retained for safety, site security, audit, reporting and operational review purposes.
• If you leave your employer, parts of your workforce record may still be retained for payroll, compliance, audit, safety or operational history purposes.
• If you want your account, workforce record or visitor data reviewed, corrected or deleted where appropriate, please contact your employer, host company or organisation administrator first.

Support and contact

For Scanner Connect privacy or product-support enquiries, contact Computime at info@computimeuk.com or 0113 350 9043.

For questions about your account, employment records, leave data, clocking history, visitor records, Scanner Connect worker/scan records or deletion requests, please contact your employer, host company, manager or organisation administrator who provided your app access.

If you are a SyncroConnect customer and need product support, use the support or onboarding contact route supplied with your SyncroConnect service arrangement.

This policy may be updated from time to time to reflect product, legal or operational changes. The latest version will remain available at this public URL.